Related
I have a Desire running HTC Sense, and I have just noticed that the home screen pinch has stopped working. Does anyone have any idea's why this would have stopped working?
The only apps I have installed that I think could effect it are the "Home Switcher" and "HelixLauncher2", but I am currently using the Sense launcher as my current and default one.
Thanks,
Rob
Mine stops working every now and then too (i'll bet you've lost pinch to zoom in google maps and photos too?)
A reboot will sort it out, but my money is on some app i've downloaded that screws with it once opened. I don't have the ones you mentioned.
It happens to me all the time when I switch to Android keyboard to use the speech to text functionality. When I switch back to the original keyboard it works fine.
Press 'Home' when on Main screen, does it work? If so, Looks like it may be a 'Pinch Gesture' issue. If not, A Home replacement App Possibly
KYI
zonkkk said:
It happens to me all the time when I switch to Android keyboard to use the speech to text functionality. When I switch back to the original keyboard it works fine.
Click to expand...
Click to collapse
Actually, that reminds me that i have swype installed - i'll bet that's what's stopping my pinch to zoom from working. I really don't miss it and would rather have Swype
Rebooting does fix it. I have Swype also so looks like that could be causing it.
My friend and I both have Swype installed and can confirm that this happens to us on a regular basis too.
sellhimechoes said:
My friend and I both have Swype installed and can confirm that this happens to us on a regular basis too.
Click to expand...
Click to collapse
even if Swype is not active? it effects the pinch to zoom? what do you do to fix it, change the keyboard layout to android one and than the pinch works or even with that sometimes it stays this way?
I have the same issue, with the home screen, photo's and browsing. Happend twice now, just reboot the phone and it's working fine for a while.
I too believe it's something I have downloaded, doesn't bother me that much and I can't be bothered trying to work out which app in might be. Maybe when I'm bored one day I'll have a look through.
I have the same issue when I have swype keybord activated. its intermittant, but annoying. and a re-boot always seems to fix it.
Not the same as I don't have that keyboard installed I do however have Smart keyboard pro.
Do you guys HAVE to reboot to fix it!!! I think just making any other keyboard the default (by press-holding, and selecting input method) would solve it!!
Interesting, because Swype + Desire port to the N1 doesn't have this problem.
I have the same issue, but I don't have swype installed. I have installed the Scandinavian keyboard with support for gestures tough. I have turned off gestures, going to see if that helps.
Regards,
PK
As far as I can tell, it happens whenever you change input method. So even changing from a 3rd party back to the HTC default will lose it. Reboot always fixes.
Mods, this is a common enough question that it might be worth stickying it? Seen about 5 threads in the last 2 weeks.
DJGibbon said:
As far as I can tell, it happens whenever you change input method. So even changing from a 3rd party back to the HTC default will lose it. Reboot always fixes.
Mods, this is a common enough question that it might be worth stickying it? Seen about 5 threads in the last 2 weeks.
Click to expand...
Click to collapse
Exactly this.
If you change keyboards, just reboot and all pinch functionality will return. Annoying, but I don't change often enough to notice it. If you change and change back, then the pinch functionality remains without a reboot.
DJGibbon said:
As far as I can tell, it happens whenever you change input method. So even changing from a 3rd party back to the HTC default will lose it. Reboot always fixes.
Mods, this is a common enough question that it might be worth stickying it? Seen about 5 threads in the last 2 weeks.
Click to expand...
Click to collapse
Not true on my device! Switching from HTC keyboard to Scandinavian keyboard by long press in any text field definitely breaks pinch-to-zoom (with or without gestures enabled in the Scandinavian keyboard). Switching back to HTC keyboard restores the pinch-to-zoom functionality in all applications.
Rebooting with Scandinavian keyboard enabled will cause pinch-to-zoom to work until a switch to HTC keyboard and back again is performed.
I'm a noob to Android,just got my Desire yesterday. I installed GOOGLES GOGGLES,GOOGLE MAPS and BATTERY WIDGET,and had the same pinch-problem. I uninstalled the apps again,problem solved. Didn't try to reboot though. But I'm glad to hear that the reboot will solve the problem,would be a shame if we couldn't have any apps installed without problems!
Ever since i flashed to the CM6 Nightly builds i've been encountering a few problems. These problems didn't exist with my previous rom which was the damage control 3.2 i think.
First problem is the on-screen keyboard, it seems like this keyboard is the one that comes with the new froyo update, i dislike this keyboard mainly because everytime i try to type anything in the web browser box the whole keyboard screen slides up after each button press. this gets extremely annoying, this keyboard also doesnt have the directional buttons so editing documents or just simply editing typos is cumbersome. I would like to switch back to the keyboard i had before, i believe it was the keyboard that was on 2.1
Second problem is the flash player doesn't work at all, it definitely worked on Damage Control but for some reason it doesnt work on this CM6 build, yes i've tried uninstalling and reinstalling but nothing seems to fix this problem. Is this a known problem in the CM builds? Mainly flash videos don't work. i've yet to try it on games like miniclip.com.
any help on these two problems would be greatly appreciated, thank you!
I just remembered I have 1 more question its about a voicemail app that let's u hear ur voicemails straight from the app I remember there's a play, last, and next button I remember I had it on the stock sprint rom. can anyone tell me what the app is called and where I can get it?
http://forum.xda-developers.com/showthread.php?t=729802
hi, had my desire z about a year now, since ive had it, quite rarely ive had a problem of it seeming to have a mind of its own, for example, icons may be selected, or the home screen will slide accross by itself etc. ive always put this down to a trackpad problem.
the other day (after having a miui rom installed for about 2-3 weeks, which was fine untill now), it started acting up strangely, the above problem started happening, but more severe, also the touch screen and softkey buttons would stop working for periods of time (or stop completely untill reset), but screen rotation etc would still be working, which shows that the O/S has not frose and is still working behind the scenes (making me think its a hardware problem).
now, i think ive worked out that this seems to be triggered (mostly) when i open the keyboard. (as also, when the touchscreen stops working etc, sometimes, sliding the keyboard open and close several times, will sometimes seem to unfreeze the touchscreen etc, and will be back to normal, for a while). ive tried doing full wipe and reflashing etc, but i still have the same problems mainly when using the slide out keyboard, which again, makes me think its hardware (possibly keyboard ribbon cable?)
i really dont want to send it off as that means getting it all back to stock etc, and last time i needed the screen replaced, took 6 weeks to get it back!
if anyone could pinpoint the likely source of the problem, id rather replace the part myself..
would anyone have any ideas, as they would be very much appriciated... Thanks...
anyone at all?
I got 2 Zs meanwhile but dont have any problem with the keyboard.
But sometimes when its charging i got the same issues like you - no touch is working and the screens are sliding nearly automatically.
I think this has nothing to do with the keyboard...
Hope this had helped you a bit
Sent from my HTC Vision using XDA Premium App
thanks for the reply, unfortunately im still no closer to finding source of the problem, its intermittant, happened lots yesterday, not so much today, maybe the digitiser? its like there is another invisible finger touching the screen..
This would happen when i was on stock froyo, like it would cause the home screen to hang, but if i was ion an app it worked fine. I would use it to refresh of sorts when my phone was hung up or i need to reload my apps from sd lol. Sounds weird I know, but even with stock froyo i had problems with my keyboard but with the prerooted GB its as smooth as butter...
still going on, and getting more frequent, i dont think it is to do with the keyboard anymore. im now guessing it is the digitizer, its like someone is pressing an invisible finger on the screen, roughly in the center. it comes and goes, it happens for about 3 days, then goes away for a couple of days etc.
also there is very little info anywhere on the net that can help, including replaceing the digitizer itself
anyone ever replaced one on a disire z/g2?
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!
I've been a longtime iPhone user, and got my feet wet a few months back with my first Android device, a Samsung Galaxy S3. I immediately rooted it, and tried CM 10.1, but I was in over my head, and I hadn't even used my phone enough to know what I wanted to do with it, so I went back to stock.
However, I've run into a few issues with Samsung's stock 4.1.1 ROM, and there doesn't appear to be any definitive answer to if and when they'll update to 4.1.2 or 4.2.x. So I decided to revisit Cyanogenmod.
I installed CM 10.1 (cm-10.1-20130304-EXPERIMENTAL-d2att-M2) last night, and I'm making my way around the system, learning a few things here and there, but I've run across two possible issues. I don't know if it's a bug, or if I'm just doing something wrong:
1. I can't seem to add the camera to the lockscreen as a slider shortcut. In the settings, it gets added just fine, I can see it there, and it saves. But when I go to actually use the slider shortcuts on the lockscreen, the camera isn't there. It doesn't matter which position it's in, either. There's just a blank spot where the camera shortcut should be.
2. The battery light -- I can change the color easily enough, but the option for pulse length is greyed out, and the option for pulse speed doesn't seem to save. When I tap "Test", it works, but once I tap "ok", it goes back to "custom", which seems to be a steady color, no blinking. Again, is this a bug, or just something that I'm doing wrong?
Thanks
The lock screen shortcuts I think you have to save before you exit that screen. There will be a floppy disk looking thing you need to press before backing out. I dunno about the notification pulse, it should be set once you've put in the value you want. Unless the ROM just doesn't actually have that functionality.
Sent from my SAMSUNG-SGH-I747 using xda premium
Ok, I just double-checked to make sure that I did, in fact, tap that save button. I did, but it's still not showing up. I tried blanking it out, saving it, and re-adding the camera and saving it, but it still won't show up.
One other "issue" that I just remembered, too... is there any way to get a counter of unread emails on the email icon, like the standard ROM does?
D'oh. You don't need to set the camera app to your luck screen shortcuts because all you have to do is swipe to the left from the right most border of your lock screen and it goes to the camera app.
I don't think there's an unread counter function in cm, but you can try googling it. I know nova launcher has that, but I've never seen anything like that for trebuchet.
Sent from my SAMSUNG-SGH-I747 using xda premium
Oh, I see that now.
Anyway, it seems to work after I reloaded CM 10.1. Originally, I was using TitaniumBackup to restore all system and app data from my stock Samsung 4.1.1 ROM, which I believe was causing problems (email was crashing constantly, for example). Once I restored only the non-system apps/data, everything seems to work as advertised (except for the counter badges, which seems to be limitation of Trebuchet).
Now that that's solved, I have another question....
When I go to make a photo a wallpaper image, I get a weird "plus" shaped resizer, which prevents me from using the whole image as a wallpaper. See the attached image. Is there any way to discard the side pieces, and just resize the wallpaper for a single screen?