Related
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
I've been experiencing the following symptoms in the last 24 hours or so, on a Tilt2, stock ROM:
-Frequent unsuccessful attempts to wake the phone from sleep. Often takes a few tries, usually successful, but I've felt the need to reset at least twice today.
-Occasional full-screen random color pixellation upon wake attempt. This generally goes away after a second or two, but sometimes I need a few wake attempts to get it off.
I am speculating that this might have something to do with the GMail IMAP issues that some people are having in the last day or two, or at least that's my best guess at associating it with a known issue, but I have really no idea. I've changed nothing, and I can't think of any possible traumatic experiences the device has gone through recently.
Everything worked fine yesterday, and has worked fine for over a year.
Follow-up, I hadn't yet noticed patterns in the issue until more recently. Now, I see that the problem occurs more in portrait.
Symptoms include:
-Landscape - generally normal touchscreen operation, I remember one time having some odd hardware keyboard behavior, though can't remember exactly what it was doing. I have also noticed that the power button seems to have no effect when in landscape.
-Portrait - phone is sluggish to wake, occasionally waking up to that random color pixel screen. Screen often freezes. Sometimes it comes back to normal, other times not. Power button seems to work normally, at least in toggling sleep/wake states.
I'm now thinking this probably does NOT have to do with the GMail IMAP issue, as some screen difficulty is occurring immediately upon power-on at times, before WinMo even begins to start.
I'm thinking some bad circuitry somewhere for whatever reason, and it might soon be time to evaluate repair/replacement options. Not sure what happened.
Which begs the side question, anyone have any idea what AT&T is replacing the Tilt2 with on insurance claims these days?
Problem summary
Known cause (might be others): selecting an app from the Recents list (Task Switcher)
Temporary fix: turn the screen off, then back on
Workaround: avoid using Recents list (you can use a 3rd party task switcher instead)
How to test: open Messaging, hit Home, hit Recents, select Messaging from the list. Your screen will be less sensitive until you turn the screen off and back on. You can view the pressure by going to Settings -> Developer Options -> turn on Pointer Location. This will allow you to see the Prs of each tap in your status bar. Normally your lightest taps that register will show anywhere from 0.28 to 0.32. However, after this bug is activated, you will mostly get values over 0.40 for your light taps. This is actually a very noticeable increase, especially when trying to type quickly.
Please report any other known methods to "activate" this bug. After re-assigning my Recents button to a 3rd party app (I'm using Simple Task Switcher), I haven't seen this bug at all. It seems that a couple of people have seen it produced by something other than Recents, but they haven't narrowed it down (or reliably reproduced it on purpose).
Please star this issue officially so Google can fix:
Link is http://code.google.com/p/android/issues/detail?id=29734
Note: Downloading & using Screen filter application from play store, with brightness set to
Your hands are really dirty or really dry. Try moisturizer or something.
Been using my screen for almost hour straight now. No issues.
--------+++--------
iphone. helping computer illiteracy become popular since 2007.
Hehe yes this s gonna be a difficult one to confirm. But it is definitely not dirty hands. To clarify, a quick press of the power button to lock then unlock completely fixes the issue. Same fingers suddenly register perfectly. This is driving me nuts as the phone is not even usable right now. Literally.
@rbiter said:
Been using my screen for almost hour straight now. No issues.
--------+++--------
iphone. helping computer illiteracy become popular since 2007.
Click to expand...
Click to collapse
ios 6.2 doesnt get issues.
I don't know about your other experiences, but as far as the browser goes I have the same scrolling effects as you do. I think this is how it is meant to be. They tightened the scrolling a lot and I kinda like it. Before one small flick would send me across the whole page, which was kinda annoying. Just my preference.
I'm not having this problem. It would drive me crazy too. Been using my phone alot over the past two days and I didn't run into this problem even after almost 1h of continuous surfing. Also a few checkpoints of Shadowgun didn't trigger it.
But you can confirm your problem if you enable "cursor position" in the dev options (hope that's what it 's called in english). "Prs" and "Size" should need a lot more than around 0.30-0.40 to register your touch if you have the problem you describe.
I am sorry that you're experiencing this, but 4.0.4 has nothing to do with this. 4.0.4 is just software, Galaxy Nexus is not a pressure-sensitive device, it is merely touch-sensitive. Which means that software gets an analogue signal from the touchscreen, either 1 or 0. It has no 'range' of sensitivity, so it cannot decrease in sensitivity in software (if it did, then it would not work at all).
This is entirely hardware issue and I suggest either making sure your screen is clean, your screen protection thing (if you use one) isn't acting up or if your hardware has become faulty (have you dropped it recently?).
If problem persists then return under warranty.
My wife had this issue once.
It was the third party launcher she was using.
I don't think its a matter of touch sensitivity dropping, its a matter of the system just being too slow to really work right.
It was ADW EX, fwiw.
kristovaher said:
I am sorry that you're experiencing this, but 4.0.4 has nothing to do with this. 4.0.4 is just software, Galaxy Nexus is not a pressure-sensitive device, it is merely touch-sensitive. Which means that software gets an analogue signal from the touchscreen, either 1 or 0. It has no 'range' of sensitivity, so it cannot decrease in sensitivity in software (if it did, then it would not work at all).
This is entirely hardware issue and I suggest either making sure your screen is clean, your screen protection thing (if you use one) isn't acting up or if your hardware has become faulty (have you dropped it recently?).
If problem persists then return under warranty.
Click to expand...
Click to collapse
Lol that is hilarious. You forgot the step where its the OS that actually processes the input data, so in that process, a ton of problems can arise.
And personally, since 4.0.4 I have also been experiencing a "similar" issue. When scrolling down (and only down), I experience a kind of "lag" like if it only registers the swipe movement half an inch lower. Its not a big deal, but still an issue.
Edit : What he explains as "pressing very hard" is most likely the fact that when you press harder you actually cover more surface, so the amount of extra input data can definitely impact the behavior.
I had issues for a few hours after the 4.0.4 update, where my softkey buttons weren't responding. Thankfully, it seems to be fine now, but it was a cause for concern.
Sent from my Galaxy Nexus
gokpog said:
I'm not having this problem. It would drive me crazy too. Been using my phone alot over the past two days and I didn't run into this problem even after almost 1h of continuous surfing. Also a few checkpoints of Shadowgun didn't trigger it.
But you can confirm your problem if you enable "cursor position" in the dev options (hope that's what it 's called in english). "Prs" and "Size" should need a lot more than around 0.30-0.40 to register your touch if you have the problem you describe.
Click to expand...
Click to collapse
Thank you my friend, I should have thought of this; now I have numbers to confirm this. So with cursor option enabled I can get down to 0.30, managed 0.28 once. However when the bug starts, I can confirm that I cannot get below 0.60. It just refuses to register that input for some reason.
I lock the screen, 1 second is all it takes, and now it registers down to 0.30 again and all touch works properly. Its almost like some type of memory leak issue is the way it feels to me. It only starts happening after a few min of use.
Its definitely an issue now that I can see the pressure numbers. The question is what the hell can I do about it. I flashed aokp29 with the latest 4.0.4 ota merged in, problem still occurs. I'm gonna try stock 4.0.2 or 4.0.1 just to see. Thanks.
I have never had much luck upgrading Linux versions. That's why I start fresh every time with Android. Lol
Sent from my Galaxy Nexus using Tapatalk
Before I start digging, anyone know specifically which driver controls the touch input? I'll try looking thru github.
Also I was on stock 4.0.1 prior to this. So this could be normal behavior for everyone but everybody is used to it since nobody stayed on 4.0.1 like me. Cause I can easily say this is difficult to notice if you aren't paying attention. The question is, why does locking the screen temporarily change it back...
I can confirm some of what you are saying..sometimes when I'm browsing the scrolling tightens up..I lock the phone then unlock it and it is smooth again..doesn't happen all the time tho..doesn't bother me but I've noticed it
Sent from my Galaxy Nexus using XDA
I can also confirm. This morning I found the Swiftkey was lagging on Facebook. Something like the phone did not receive the touch. Then I rebooted and now it is ok.
I did not get this issue on 4.0.2 and I don't install anything new on 4.0.4.
The way I installed 4.0.4 was from the official factory image, so my phone is fresh! I reinstalled all apps manually as well. Nothing fancy apps.
I know this is my first post, but I can definitely confirm this issue.
I use my Galaxy Nexus for development, so the screen is always on. The sensitivity goes down very quickly.
My phone was an International GNEX that I loaded the US firmware on and then I flashed the OTA 4.0.4 update.
kristovaher said:
I am sorry that you're experiencing this, but 4.0.4 has nothing to do with this. 4.0.4 is just software, Galaxy Nexus is not a pressure-sensitive device, it is merely touch-sensitive. Which means that software gets an analogue signal from the touchscreen, either 1 or 0. It has no 'range' of sensitivity, so it cannot decrease in sensitivity in software (if it did, then it would not work at all).
This is entirely hardware issue and I suggest either making sure your screen is clean, your screen protection thing (if you use one) isn't acting up or if your hardware has become faulty (have you dropped it recently?).
If problem persists then return under warranty.
Click to expand...
Click to collapse
Just to point out, the phone is all digital. It does not get an analog signal from touching the screen. Also to that point you said analog but then described digital with the 1 and 0
Has anyone affected tried going between 4.0.2 and 4.0.4? To check the possibility of a driver or some related value changing.
Also, if not fixed by going back to 4.0.2, this could be due to current leakage from somewhere causing the touch to not work properly. I've seen it on other capacitive touch devices, though mainly when a non-compatible charger is connected. When you shut the screen off, the charge causing the problem/interference with the touch is temporarily dissapated, but then comes back after you use it again. Probably very unlikely in this case, unless Google changed something in the touch driver that makes it more sensitive to interference, which in turn messes with actual input from fingers.
TechNoir said:
Has anyone affected tried going between 4.0.2 and 4.0.4? To check the possibility of a driver or some related value changing.
Also, if not fixed by going back to 4.0.2, this could be due to current leakage from somewhere causing the touch to not work properly. I've seen it on other capacitive touch devices, though mainly when a non-compatible charger is connected. When you shut the screen off, the charge causing the problem/interference with the touch is temporarily dissapated, but then comes back after you use it again. Probably very unlikely in this case, unless Google changed something in the touch driver that makes it more sensitive to interference, which in turn messes with actual input from fingers.
Click to expand...
Click to collapse
Its possible. I was on 4.0.1 so perhaps this issue originated in 4.0.2 but I never noticed since I didn't update then. I can add that I did multiple wipes and clean flashes, and also tried both aokp 28 and 29 (new 4.0.4 ota merged), and happened on both.
I'll post what I just sent to arbiter which gives more insight.
From my extra testing under normal use my light touches register 0.28-0.33. Especially on swipes, the end of the swipe registers 0.28 as the finger travel breaks contact with the screen giving that swipe extra input which pushes the swipe motion further extra boost. When the bug starts the touch swipe won't even break 0.38-0.40, and that extra swipe data is lost resulting in the end of the swipe data points being excluded and swipes travel half the distance.
This gets exacerbated on the keyboard when fast typing light pressed. Its so bad it frustrates my face off cause typing just ceases to be possible. Such a difficult issue to diagnose.
Click to expand...
Click to collapse
Yes my face literally flew off!
Is anybody getting this weird issue when they're typing: The keyboard all of a sudden just goes away on it's own after 2 or 3 keystrokes. It happens a lot when I use the Bing Search function. I'll get two or three letters down then the keyboard abruptly goes away. So I have to get two or three key presses in each time I restart the process.
Anybody know what could be causing this? It's not just limited to my Bing Search, I literally got so frustrated trying to start this thread through my phone's browser that I had to dig out the laptop instead.
And this is happening on a Lumia 900?
Sent from my Lumia 900 using Board Express
sorry not I
iiDeadSeriousii said:
Is anybody getting this weird issue when they're typing: The keyboard all of a sudden just goes away on it's own after 2 or 3 keystrokes. It happens a lot when I use the Bing Search function. I'll get two or three letters down then the keyboard abruptly goes away. So I have to get two or three key presses in each time I restart the process.
Anybody know what could be causing this? It's not just limited to my Bing Search, I literally got so frustrated trying to start this thread through my phone's browser that I had to dig out the laptop instead.
Click to expand...
Click to collapse
the symptoms are those of the disappearing keyboard issue with mango. Its supposedly fixed in this release of mango. However several people have reported seeing it.
I suggest you report it to Nokia at the web site. You won't be able to fix it on your own.
alodar1 said:
the symptoms are those of the disappearing keyboard issue with mango. Its supposedly fixed in this release of mango. However several people have reported seeing it.
I suggest you report it to Nokia at the web site. You won't be able to fix it on your own.
Click to expand...
Click to collapse
This still happens to me occasionally on both my original Focus, and my Lumia 900. Both are updated.
alodar1 said:
the symptoms are those of the disappearing keyboard issue with mango. Its supposedly fixed in this release of mango. However several people have reported seeing it.
I suggest you report it to Nokia at the web site. You won't be able to fix it on your own.
Click to expand...
Click to collapse
Ok, I didn't know if it was a symptom of Mango or the Lumia. It's just so weird when it happens, I notice it when I'm low on battery more often, but idk what sort of relevance that would have. Thanks for the tip though.
Yeah, I get it quite often on my Lumia 900. Also my Radar still has it happen occasionally, my girlfriends Radar has it happen more than mine. All updated as well.
Sent from my Lumia 900 using XDA Windows Phone 7 App
Are you sure you're not accidently rubbing you hand/finger on the back button? The back button, since it's universal, will remove the keyboard if it's on screen. And because Back, Home and Search button all use capative touch instead of having to push them, simply rubbing or bumping them will cause them to activate.
I had this problem when I first got my Lumia, but I've adjusted and adapted.
SwimSwim said:
Are you sure you're not accidently rubbing you hand/finger on the back button? The back button, since it's universal, will remove the keyboard if it's on screen. And because Back, Home and Search button all use capative touch instead of having to push them, simply rubbing or bumping them will cause them to activate.
I had this problem when I first got my Lumia, but I've adjusted and adapted.
Click to expand...
Click to collapse
For me, definitely not. I've tested it many times on my Lumia and my Focus. It's definitely something to do with the keyboard deactivating itself. It happens to me a lot if I try to share an article I read in WP7 News app and go to email. When I try to type my name in the TO: field, I get one or two letters, then it goes away and I end up clicking/typing in the message body.
It seems like if I give it a moment to rest, then start typing, it's less likely to do it, but that's a little annoying, since I want to check my stuff and get on with things. Not a huge issue, mind you, but annoying none the less.
No, im not accidentally touching the back buttons.I'll ask my girlfriend if she's having the same problem, but it's gotta be a software issue from what I'm hearing now.
SuperSport said:
For me, definitely not. I've tested it many times on my Lumia and my Focus. It's definitely something to do with the keyboard deactivating itself. It happens to me a lot if I try to share an article I read in WP7 News app and go to email. When I try to type my name in the TO: field, I get one or two letters, then it goes away and I end up clicking/typing in the message body.
It seems like if I give it a moment to rest, then start typing, it's less likely to do it, but that's a little annoying, since I want to check my stuff and get on with things. Not a huge issue, mind you, but annoying none the less.
Click to expand...
Click to collapse
Huh, this doesn't happen to me though. Guess it's only effecting certian modles... Nonetheless, this kind of defeats their whole add campaign (Smartphone beta test is over)
iiDeadSeriousii said:
Ok, I didn't know if it was a symptom of Mango or the Lumia. It's just so weird when it happens, I notice it when I'm low on battery more often, but idk what sort of relevance that would have. Thanks for the tip though.
Click to expand...
Click to collapse
at&t has not rolled the fix out yet, but the lumia supposedly has it. Other carriers that rolled out the fix, still report some problems, though not nearly as widespread. AT&T says they will roll out the fix around the tango release timeframe..i think it needs more work.
Mine is doing it now after updating to the latest software, this sucks! I hope they fix it asap, very annoying when composing text and the keyboard disappear!
humblehyper said:
Mine is doing it now after updating to the latest software, this sucks! I hope they fix it asap, very annoying when composing text and the keyboard disappear!
Click to expand...
Click to collapse
I have actually noticed this problem less and less as the weeks have gone on. It's not so much that I'm getting used to it, cause I notice when it does happen, I think it was just a weird thing. I haven't had a problem personally since the update either.
Hi,
I don't have this issue on my 900 nor does my wife see it on hers. That said, let me offer what I know about the keyboard disappearing from previous hardware/builds.
When I had this issue on earlier hardware (Focus/Focus S) it was caused by apps set to run in the background. When an app is set to run in the background, the app would shift focus away from the current user task for a split second, and if you have the keyboard out the keyboard thinks you've switched to a different task and it closes. The way I worked around it was to disable background tasking for all my apps (settings -> applications -> background tasks. Note that when an app updates itself, it will reset this background task setting so you have to reset it. I never saw this problem again after I updated my Focus S to 8107. Still, it might not hurt as a troubleshooting step to disable background tasks and see if the problem reappears.
Michael
so far, i've not encounter this issue with my phone yet, but seems to be affecting mango version only, coz mine is already on tango....
Sometimes, not always, when I restart my phone, things get a little crazy and somehow they must be all related. It happens as often as approx once a week. What happens is the following things:
1- I get an email from Where's My Droid that my SIM card or phone number has changed
2- Network-provided time zone changes to Central European Summertime
3- Wifi calling is turned off (however this doesn't normally stay on for some reason)
4- Visual voicemail in the phone app is missing despite still being turned on
5 - APN is not selected (the circle next to Verizon is empty aka does not have the blue dot in it)
I am on 7.1.2 and rooted. Does this happen to anyone else and is there any fix? What could be the cause?
Edit: I doubt this is related, but since I am looking for general feedback for strange bugs with my phone...
Another thing that happens is sometimes while using my phone, apps randomly reload (lack of a better word)
By reload, what happens is the app does not fully close and reopen. What happens is the app remains open ("heading" bar at the top remains) but the rest of the page I am on goes completely blank and then returns with any previous changes undone.
So say I was writing an email in gmail, the red bar at the top with the back arrow and trash can, etc. stays while the rest goes blank and any text I wrote will be gone and I have to start from the beginning. Usually when this is happening, it continues to happen repetitively for a little while. Eventually it just stops on its own. It does not seem to be related to any specific app (since it happens with a bunch of apps) unless maybe it is related to something like Swype keyboard that is always on.
Does that happen to anyone else too? What is causing this??
If your phone is 128g your nand is bad and you need a replacement. Google is aware of the issue and should swap no problem.
DR3W5K1 said:
If your phone is 128g your nand is bad and you need a replacement. Google is aware of the issue and should swap no problem.
Click to expand...
Click to collapse
Thank you! I do have 128GB. I'm glad I finally asked!
NP glad to assist Buddy