Related
My keyboard has been lagging and doing other strange things that has got me worried. I did a hard reset on it yesterday and before I even installed any software I was forced to use the on-screen board for a spell as the slide out was un-responsive. I chalked it up to some background process being a hog and moved on. Now I'm finding some consitencies.
On a fresh reboot if I open the notes app in landscape mode and start typing I can see the cursor moving but nothing else till I get about 75% across the screen and then there are some black artifacts that now look like a ton of characters all bunched up in the space of about 3 positions wide. If I keep typing till it does a return then the entire line of text shows up and the process repeats itself on the next line.
If I have a full page of text open in say Total commander's text editor in portrait mode and slide the keyboard out, it will make a pattern of those black artifacts diagonally down the screen toward the left side and it will not correct itself. If I go back to portrait mode all is well again. There is seriously something wrong here.
I can't find any information from searching on the problem but hoping one of the experts here could shed some light on it and let me know if it's time to think about a return. Will try to uncover more if I can.
Many Thanks,
Eidolen
I took some screens of the problem. Both pics on the bottom are the same document but left is with TC's editor and the right is Word. Upper right is word as well. Hopefullt the attachment makes it through, if not I can host and link to it.
If you are running a stock ROM without any customizations (you said you hard reset your device), then chances are you have a defective Fuze. You should exchange it through AT&T's 30 day return policy.
If you're not running a stock ROM, then maybe you have an unstable one. Flash Da_G's clean ROM and see if the issue still occurs. Since that ROM has very little installed by default, the chances of a software conflict are slim.
Please post back here with your status.
I was thinking the same thing but the one thing I can't reproduce is when the keyboard doesn't respond at all. Maybe the graphics and the responsiveness are 2 different things?? I'm wondering if clear-type might have something to do with the graphics but that shouldn't lag the keyboard.
Gonna disable Clear-type now and will report back.
Eidolen
Well if I would have done a search with cleartype I would have found my answer, sorry I didn't figure it out sooner. At least pople can see what cleartype looks like on the Fuze in landscape mode if they were wondering. Apparently there is no fix known other than to turn it off. Hopefully the laggy response clears up as well but not getting my hope up. Thanks for your response.
Eidolen
What an odd thing for ClearType to do in landscape mode... as for laggy response, flashing a clean ROM would give you a good gauge as to how preinstalled apps can affect such lag.
Same thing happens to me but in txt'in sometimes my keyboard dont work at all and i have to restart the device, but this has happen to me only 3 times and the keyboard still have life cuz when i hit the fn key or shift the light comes on indicating that i put them on. as for screen lag i bearly get screen lag, because i did some hack i saw in this thread and it seems to of help alittle
by the way am using the ROMeOS2, i was wondering if i was the only person with this problem but apperently not.
Yep I got the same problem. I installed the NullKb cab on my phone to keep the kb from popping up in Opera. It didn't work. I uninstalled NullKb, It still shows up as selectable under other input options. The lag got progressively worse and even resets will not get the keyboard to work.
I've got the same problem. It's really strange.
I used ROMeOS but now am back to Australian Three official rom.
It seems like, when ClearType is active, I can't see what I am writing with the keyboard in LandScape mode. Even stranger is that when you write an SMS, the keyboard writes fine as there is T9 active.
I really need a fix for this as this has started to frustrate me.
I found having "clear type" activated was my problem as well. I turn it off and my kb is back to usual normal. I have a euro stock unit. Very happy with the rest of it's performance. I can live without cleartype.
eidolen said:
My keyboard has been lagging and doing other strange things that has got me worried. I did a hard reset on it yesterday and before I even installed any software I was forced to use the on-screen board for a spell as the slide out was un-responsive. I chalked it up to some background process being a hog and moved on. Now I'm finding some consitencies.
On a fresh reboot if I open the notes app in landscape mode and start typing I can see the cursor moving but nothing else till I get about 75% across the screen and then there are some black artifacts that now look like a ton of characters all bunched up in the space of about 3 positions wide. If I keep typing till it does a return then the entire line of text shows up and the process repeats itself on the next line.
If I have a full page of text open in say Total commander's text editor in portrait mode and slide the keyboard out, it will make a pattern of those black artifacts diagonally down the screen toward the left side and it will not correct itself. If I go back to portrait mode all is well again. There is seriously something wrong here.
I can't find any information from searching on the problem but hoping one of the experts here could shed some light on it and let me know if it's time to think about a return. Will try to uncover more if I can.
Many Thanks,
Eidolen
Click to expand...
Click to collapse
Hi:
I had the same problems. I fixed it by disabling cleartype in landscape (using Diamond Tweaks), and then installing the Fuze Keyboard fix cab, which I am attaching here for you, in case you want to try it. I'm sorry I don't remember the original post I got it from. After doing these 2 things, everything seems to be working great for me.
On my unrooted phone the "Steamy Window" application worked fine
If I pressed a little it would make a little line in the "steam", and if I were to push my thumb down on a large area, it would detect that and make a "thumb" sized print.
Now using JF1.41 no matter what I do it only makes a TINY TINY line, about a pixel or two in size.
Did the modification of the screen change an api that the Steamy Window app is using to work different?
Well, maybe you should go back to an unrooted phone so that you can play with your steamy window....
LPChris, I would expect a little more maturity from a "senior member"
I am trying to contribute to make JF the best it can be. Maybe your just having a bad night or something, but theres no need to be so childish.
:ed:
Looking through your posts it seems like your just having a bad night
Back on topic:
While this may be a stupid little problem with one application. Should finger-area sensitive applications continue to be made this could isolate JF1.41 from the market. Naturally I dont care much for steamy window, but I would like to prevent other issues in more... useful... applications
I've seen some weirdness where my home screen has a jitter. I've also had accuracy issues with clicking menu items and buttons. I'm going to backup my phone and load JF 1.31 back on to see if it is the screen or the img.
Interesting...I just reflashed with 1.41 RC30 and the problem went away. I was using the fade to blue theme .99.
sjbayer3 said:
On my unrooted phone the "Steamy Window" application worked fine
If I pressed a little it would make a little line in the "steam", and if I were to push my thumb down on a large area, it would detect that and make a "thumb" sized print.
Now using JF1.41 no matter what I do it only makes a TINY TINY line, about a pixel or two in size.
Did the modification of the screen change an api that the Steamy Window app is using to work different?
Click to expand...
Click to collapse
Ditto about LPChris lol, a lot of his posts sound like that, but yeah I noticed the same thing about the steamy window app before and after using JF 1.41.
Steamy window, LOL! sorry guys. anyway keep up the great work.
Yes, this is a trivial example, but it does identify a real issue.
I was reading through the various google android groups last night and I ran into some info that seems to addresses this issue. From what I was able to gather, the JF1.x implementation of multi-touch uses a community hack that reassigns the value that normally keeps track of the size of the touch input. This value is now used to keep track of the distance between two touches. (see: http://groups.google.co.uk/group/android-platform/browse_thread/thread/209b512a9fdf7367?hl=en)
your Steamy Window app seems to make use of the size value as it was originally designed. Now with the change, with only one finger input, this value is set to some minimum, producing a thin line.
To test this theory, see if when you touch the screen with two fingers the size of the mark gets bigger.
Why can't a capability bit or other mechanism be defined that could be used to indicate whether or not an application were multi-touch aware, so that the touch handling behavior at the lower levels would revert to "standard" behavior for normal (non-multi-touch) apps? Trying to make the multi-touch hack fully backwards compatible may not be practical.
I tested your idea about multituch possibly fixing steamy window
My only results are really strange.
If I touch with two fingers it will make a line about the width of my 2 fingers, but its located in the top left, no matter where my fingers actually are. Furthermore the line isnt straight its curved.
Now, after my first touch, it seems if I touch it again it just crashes.
ex-MN said:
From what I was able to gather, the JF1.x implementation of multi-touch uses a community hack that reassigns the value that normally keeps track of the size of the touch input. This value is now used to keep track of the distance between two touches. (see: http://groups.google.co.uk/group/android-platform/browse_thread/thread/209b512a9fdf7367?hl=en)
Click to expand...
Click to collapse
Edit: Hmm... the x-y data of the second finger is stored in separate fields. I think the usage of the size field is just as a boolean to tell multitouch capable programs that second finger data is being sent.
themes and JF RC versions. be careful
TheDudeOfLife said:
I've seen some weirdness where my home screen has a jitter. I've also had accuracy issues with clicking menu items and buttons. I'm going to backup my phone and load JF 1.31 back on to see if it is the screen or the img.
Interesting...I just reflashed with 1.41 RC30 and the problem went away. I was using the fade to blue theme .99.
Click to expand...
Click to collapse
it seems as tho themes have to be matched to the rom, a theme for 1,30 may flake out on 1.41, most of the themes I have seen and used so far were marked as to which rom the were intended to theme...
BhanG
bhang said:
it seems as tho themes have to be matched to the rom, a theme for 1,30 may flake out on 1.41, most of the themes I have seen and used so far were marked as to which rom the were intended to theme...
Click to expand...
Click to collapse
After some more testing I have this same issue on 2 1.41 compatible themes (rusty metal and fade to blue) I am going to go back to themeless 1.41 but I think it is more related to the multitouch 'hack' than the theme themselves. I find it hard to believe that a bunch of icons could mess this up. I watches my screen jitter between the left and right screen for 3 minutes today before I just performed a soft reset on my phone.
Note: I also applied each theme from a fresh flash of 1.41...not on top of each other.
this happens with screen crack also, but it doesnt affect me that much until i start not being able to select stuff. i know it may be important its just not to me... yet *knocks on wood*
Yeah Ive noticed it too..
I thought that it was just the app at first.
I might be switching back to .31 then at least til this gets fixed.
Steamy window def is NOT reading my fingers location or size properly.
I've also seen it affect touch paint found in the API Demos. Doesn't even register touch anymore.
It appears multi-touch is premature at this point and to implement multi-touch throughout the OS and not just the browser like everyone seems to think isnt good. It is definitely is throughout the OS and probably will affect any application that uses the second touch value to register touch size.
My other concern is that dev's won't take this hacked multi-touch into account so they will continue to write programs that won't be compatible since its not the "norm"
Taken from and android forum...this is my biggest concern
"Please think about soft keyboards when considering multi-touch APIs,
where the problem isn't detecting the distance between two finger, but
rather is allowing a 2nd finger (or thumb) to come down on a 2nd key
before the first finger (or thumb) has been released. The proposed
API to provide only a centroid and the distance between fingers won't
work at all for this sort of application.
I think you'd ultimately want to package this as additional
GestureDetector subclasses, depending on whether the type of gesture
detection wanted was pinch/zoom or multiple/overlapping taps.
Keyboards (and maybe games) would use one class, browsers another.
Providing the right information from a touch panel to drive either
detector might be challenging, especially if the panel provides
'unpaired' x and y coordinates rather than individual touch locations,
but I believe it could be done. "
JesusFreke,
Any thoughts on this?
Yeah lets hear what JF's got to say.
I originally thought that the multitouch was embedded in the browser, It's too soon to have it throughout the entire OS...
How about 1.41=with multitouch and 1.42=without
I've installed JF1.41 and I have an unusual bug....sometimes the screen behaves like it isn't calibrated..i press the screen on a button and it is pressed another one....have anyone encoutered this problem?
I invite everyone to do the following to find out how ur touch registers on ur screen. Open anycut. Get it if u don't have it.
Click activity and find raw image viewer. Click ok and then click on the shortcut.
Now start moving your finger around and see the results.
Let's all post our results here so we can figure this out.
Post in the same format as me:
ROM: JF1.41
1 finger - it surpisingly followed my finger perfectly. It only registered the very center point of my finger.
2 fingers - it appears that it made the same point as the 1 finger, however now the point was exactly in between my fingers and stayed there as I moved them around.
Ok so now we need ppl with stock rc30 and 1.31 so we can test this out!
You wanna have some real fun? Try it with 3 or 4 fingers.. It goes nuts..
Hello to all, am going to ask if anybody of you have a problem in TPs Touch Capacitive Pad? I used this app
Nav Debug Tool by HTC
http://forum.xda-developers.com/showthread.php?p=2511016
To check out this multi touch stuff in my TP (though I know before that it has a multi touch feature, I just want to check if it's working properly) but it seems that the pad has a problem. The problem was sometimes, it can register my touch and most of the time, not.. sometimes it can register the multi touch, and most of the time, not .. even the nav wheel has a problem which doesn't register the rotation most of the time. Is this a common problem in TPs or even Diamond??
I even use the signed os WM6.1 but still has a problem.. so I wonder if any of you guys having the same..
thanks!
It's been happening to me for about a year already as well. Seems like it's just defective. It resets thought after sleeping the phone and waking it. I'm not sure if it was because I used to use Sensor scroll or it's a little scratched up.
I hear the d-pad was a good conceptual idea but that is about it... I personally don't use the d-pad at all because of this, much less any of the buttons (to include the power button). On the other hand, from what I can tell about the d-pad "sensor" from using the NDT(Nav debug tool), it does seem pick up points but it seems to not like repetitive touches. It almost seems like the sensor overloads the processor to the point that it fails in terms of keeping up with the actual location that is being touched; if that makes any sense?
R^7Z said:
I hear the d-pad was a good conceptual idea but that is about it... I personally don't use the d-pad at all because of this, much less any of the buttons (to include the power button). On the other hand, from what I can tell about the d-pad "sensor" from using the NDT(Nav debug tool), it does seem pick up points but it seems to not like repetitive touches. It almost seems like the sensor overloads the processor to the point that it fails in terms of keeping up with the actual location that is being touched; if that makes any sense?
Click to expand...
Click to collapse
that made sense but why would HTC permit a buggy front pad???
You know, it seems many phone brands/cooperations come under fire due to lack of something or another; maybe proof of concept? Perhaps the debug tool is to blame? Or even the sensor degradation over time? One can only speculate so far before it becomes a volatile thought... Again, I point out the idea being good, conceptually. So, I don't know where that exactly puts us as being end users? Then again, I've never really had a decent experience with phones, much less with newer phones; my thoughts and expectations may be slightly on the negative/lesser side of things because of this.
I have the same issue. I used to use GScroll to flip pages in e-books, but finally it got so buggy I had to dump it (other GScroll features were almost impossible to use). I've used NavPad DBug. What I do find is that running the compact heaps command of SK Tools will temporarily fix things, at least most of the time. When I have NavPad DBug running, if it's logging compact heaps will clear out the traces. Somehow or other, it cleans things out when the nav pad gets confused or overloaded with inputs. But even compact heaps doesn't work all the time.
It would be sweet if the capacitative area really worked, but unfortunately it appears to get worn out about the time that you figure out all the things you can do with it. Lol.
Edit: I wonder if the device has problems distinguishing a single touch of your finger vs. several touches. That could really screw up the function of the device.
this may not explain all screen issues, but it may explain the issue of the screen freezing and also the issue of it reacting on its own. i believe that this screen is highly sensitive. my current theory is that dirtiness and dullness cause screen lag. this can result in freezing, but i think more commonly what happens is for it to cause a delay in the screens responsiveness. so lets say you touch the screen and it doesnt respond right away. so you tap the screen again, and it does respond. but maybe its responding to the first time you touched it, and then you exit out of that screen or do something else, and forget that you touched the screen again. but the phone remembers and responds, and the phone does something odd, seemingly on its own. now remember this is just a theory of mine, and i am no expert on touchscreens. it just occurred to me that this could be a possibility, because i cleaned my screen really good and the screen seemed a good bit more responsive than usual. feel free to share your thoughts and opinions on this.
There are times when a greasy/wet touchscreen will misbehave, but I think the majority of our touchscreen problems stem from a buggy driver which tends to crash during low memory conditions.
yea i definitely think its just a buggy phone. wish it was as simple as keeping it clean, but i have these problems even when clean sometimes. its not a deal breaker though, at least not for me.
i just wish we could have custom lock screens or AOSP lock screen that wouldn't break the damn auto-rotate.
i know this is a different subject than my op, but i have a question. i converted several apps to system apps. two browsers, opera mobile and dolphin mini, dolphin to replace my stock browser and opera for desktop browsing, as well as a volume control app and a few others. i use an app called optimize android toolbox to clean my cache. before converting these apps to system, they all stored a cache. now, opera and dolphin dont. the volume control app still does though. i dont think its a problem, it just perplexes me. any possible explanation for this?
JonathanBarca10 said:
yea i definitely think its just a buggy phone. wish it was as simple as keeping it clean, but i have these problems even when clean sometimes. its not a deal breaker though, at least not for me.
i just wish we could have custom lock screens or AOSP lock screen that wouldn't break the damn auto-rotate.
Click to expand...
Click to collapse
Ayoteddy got us the aosp lock and the puzzle lock, using it right now no prob.
sent from my....WAIT THIS ISNT MY PHONE?
When it's cold mine never responds.
I put a screen protector on my phone and I haven't had any touch screen problems since. Might just be a coincidence, though.
before i got this phone, i read a review that said only one android phone has a more functional lock screen than the sidekick. of course, that statement is based on phones with stock roms, but still, thats definitely saying something. i like the stock lockscreen a lot. i like the media room lockscreen widget. tried other music players with lockscreen widgets, but they take up the whole screen. then you have to exit the widget to unlock the screen. plus you can slide down to unlock or slide up to launch an app. thats pretty tight.
I'm not saying the stock lock screen isn't clever. It's really is quite cool... when it works.
So often I've had to struggle to unlock the phone because the screen was lagging badly. Or the home screen has come up for a second before the lock screen. This is especially a problem when text messages come in, and often result in my phone doing crazy crap in my pocket. Next time I pull it out I discover that it's gone to CNN, changed my brightness, turned on bluetooth, etc.
This is the most annoying POS program I have ever seen , whether I have a stock rom or custom rom this annoying program pops up whenever it wants usually while Im doing something , but it also just starts for no reason while sitting on a table ! Yes I turned it off in setting , that doesnt turn it off , that doesnt do sh1t , I mean at least have an on off button for this annoyance , anyone know of a place in the registry to cut this off (gooddaytodie, heathcliff,Jax ???)!!
It's easy enough to remove it from a custom ROM, but if you're getting the app triggering randomly like that, it's probably not a software problem. That sounds like a hardware issue, with either the capacitive buttons being too sensitive (a problem some phones will exhibit, especially while plugged into a charger and then laid on their backs) or with something in the case being messed up. I've had TellMe trigger a few times when I was gripping the phone really hard playing Z0mb1es, but not since then and never while just lying there.
I was hoping Id get your attention and yes I figured it was a hardware issue with the capacitive buttons , but is there any way to disable tell me and yet retain the actions of the capacitive buttons? its really annoying , it may be a hardware issue however after researching this its quite prevalent on the new nokia phones as well I am using a samsung 1st gen focus and I do have a custom rom , if you can point to the right location in the registry to remove this pest I would be appreciative , I will report back to you to let you know how it works out?
Thanks again GDTD , always pleasure hearing from you!
I know of no way to just "disable" it, though that's probably just because I haven't looked. It's part of WebSearch.exe, which if removed or renamed would prevent TellMe from launching (it would also break the other functions of that app, though, such as the barcode scanner and Bing Music).
The Focus is indeed the device I've most commonly heard complaints of having over-sensitive buttons / touchscreen that occasionally push* themselves. I've never tried, but I've heard there's a tool - in the Diagnostics app, I think - that lets you adjust the buttons. Maybe that would help?
* I was going to say "touch", but that... didn't look right.
Thats exactly what I was thinking that there might be some controls in diagnosis that adjust the sensitivity , but, alas I dont know what they would be , if you have the time could you look for me?
I don't have any Samsung phone, and the Diagnostics app is completely different between OEMs. You're better off just doing some searches of the forums, especially the Focus sub-forum.
yep I have been, I used to know all the good codes , but I guess I will have to start searching again, thanks anyway! I think I might be heading back to Android ,after this fone has run its course , just so much you can do with the platform ,unlike windows and crapple ! I am really ticked off how Microsoft keeps sabotaging itself , win 8 phone kills win 7 phone as win 7 phone killed mobile , every two years ,ya have to start all over again ,you will never catch apple and wont even catch a dream of android!