Related
Yesterday I installed a demo of the game 'Winds of Steel' on my Epic. It uses the accelerometer to control the motion of a fighter plane, but I immediately noticed that the motion sensing was way off. It jumps from extreme up to extreme down with no mid-range. Left and right movements are fine, but the up/down issue makes the game unplayable. I checked the forums and even chatted with the developer, and no one seems to have had a similar issue. I've reset the horizontal calibration, rebooted the the phone and even re-installed the game and I still get the same thing. A friend who has a stock Epic says it runs great on his phone, so I'm wondering if it has something to do with Froyo.
I'm running the Quantum ROM with the DK28 modem and EXT4 on my Epic. If anyone else has a similar problem, please let me know. Everything else runs flawlessly on this phone, so this one has me stumped.
Thanks!
I have the same problem from running dk28 (even though I'm back on 2.1 now). Have you tried rooting and then running sensorcalibutil_yamaha ?
Sent from my SPH-D700 using XDA App
You may have one of the Epics like mine that had their accelerometer borked when you went to DK28. The way I corrected it was:
1. Go to settings -> display
2. Choose Horizontal Calibration
3. Turn the phone over so it is face down, and place it so the bottom edge is hanging off of a table, so you can just access the "calibrate" button.
4. Hit "calibrate" (while phone is upside down)
5. Enjoy your properly calibrated accelerometer.
Those of us that had the problem think it is possible due to the sensor data getting written incorrectly on certain phones with DK28.
I wish I could take credit for the process I laid out, but I don't remember who told me about it a month or 2 ago.
Hope this helps!
Calibrating it upside down did the trick. Thanks! I never would have thought to try that.
I'll have to mention it to the developer in the event that other people contact him.
I don't think it's an issue with the game - I think the problem lies in the DK28 update, because I know there are lots of other programs that were affected by it, not just that game.
I'm just glad the solution worked out for you.
Yeah, this issue isn't game-specific. I can't play X-Plane or use Google Sky Map (to look up) because of it.
I've tried multiple times to fix it in 2.1, to no avail. I'm considering flashing to dk28 again to fix it and then hoping the fix will remain if I then flash back to 2.1
Update: I flashed to dk28, calibrated upside down, flashed back to 2.1, and then ran sensorcalibutil_yamaha to fix the rotation issue. It fixed my issue so now the pitch is registering correctly!
Sent from my SPH-D700 using XDA App
Once in a while when trying to answer an incoming call the unlock slider won't respond. I will slide my thumb to unlock and ...nothing. When this happens the call will just go to voicemail . The workaround is to touch the power button to turn off screen , then touch it again to wake it up ,then the slider will work and I can answer the call. Sometimes this takes too long and I miss the call.
This is not a deal-breaker as it only happens 5% of the time , still it is annoying. I have tried different roms with no real difference. Anybody else have this problem? Any advice other than get a new phone under warranty?
Ditto. And I always act as you did to work around the issue, only difference is, I haven't missed a call due to this.
In any case, based on experience, the chance of this happening could be minimized (if not eliminated) by always locking the phone from the "desktop" (e.g. do not lock the phone when an app is running).
BACK STORY:
I remember this happening (more than once) when someone called me up after a train ride. And the last thing I could recall is that I have locked the phone while playing Angry Birds / Fruit Ninja / Zenonia 2, etc.
But it still sucks that it happens.
I guess my real question is , are all Nexus s doing this sporadically , even rarely , or is my phone defective?
question... are the phones plugged in to a wall charger when this happens?
Nope. Only happened to me when I under clocked the CPU with Setcpu using the powersave profile (I was just testing things out).
DKYang said:
Nope. Only happened to me when I under clocked the CPU with Setcpu using the powersave profile (I was just testing things out).
Click to expand...
Click to collapse
can happen any time any place
ransome7 said:
I guess my real question is , are all Nexus s doing this sporadically , even rarely , or is my phone defective?
Click to expand...
Click to collapse
I'm not sure if everyone's having this, but I'm with you on this. I'm on stock but rooted 2.3.3. Experienced this since 2.3.1.
EDIT: My wife has this problem too, since 2.3.1 until 2.3.3 (not rooted).
cygnum said:
I'm not sure if everyone's having this, but I'm with you on this. I'm on stock but rooted 2.3.3. Experienced this since 2.3.1.
EDIT: My wife has this problem too, since 2.3.1 until 2.3.3 (not rooted).
Click to expand...
Click to collapse
Mine did it stock , I rooted and loaded roms to see if that would fix the problem , lessened but still there
My nexus s (i9020T) has exactly the same problem. I've also tried to flash different ROMs, including CM-7rc2 and stock 2.3.3, and the problem remains.
I tried to bind Multi-touch Visualizer 2 to long pressing home button, and found the when screen is unresponsive, it can still detect press near edges very well, but not the center. While I press at the edge and drap across the center, it keeps tracking my finger correctly. In addition, Locking and unlocking the screen can solve the problem temporally. I connect my phone with adb, and tried to "cat /dev/input/event0" The behavior confirms what I see in Multitouch Visualizor 2: the when the center of screen is unresponsive, nothing can be read from the device node.
I read the mxt224 touch screen controller doc, and it seems the chip features self-calibration, and thus I believe the "lock & unlock" will trigger the chip to tune it self in some way. I've also read the driver code of nexus s, htc incredible and moto droid x, all using the same controlling chip. Both HTC and moto would send calibrate command to the chip during resume, but sumsang does not. I guess this might be the reason, but I'm not skilled enough to port the drivers
I experienced it twice so far i think, but only have the device for a little more than 2 weeks.
I am on stock 2.3.1 currently.
Beside the lock&unlock method, I discovered a new way of getting screen back to work: rub your hands a couple of times and touch again... Anyway it seem the screen is not well calibrated.
problem seems fixed with my customized kernel
Last night, I modified the touchscreen driver and mach settings a bit on the source of netarchy's nice kernel, and compiled a kernel of my own. The screen now seems working well with my new kernel
Never have experienced this on the nscollab rom which is cm7 and kernel together stable. I suggest give it a shot
Sent from my Nexus S using XDA App
swa2k4 said:
Never have experienced this on the nscollab rom which is cm7 and kernel together stable. I suggest give it a shot
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
May I know how to perform the suggested steps, i have been experience twice since i bought it on 2 weeks ago
I would like to bring this issue up again (after so long) as I am still randomly experiencing this exact issue even with Ice Cream Sandwich 4.0.3 (Stock & Custom ROMs). Any fix yet?
I just purchased the gt540 but noticed that at the bottom of the screen there is some backlight bleeding and if pressed at the buttom it gives feedback. (I don't mean the regular feedback buttons but the actual bottom screen)
It's almost like it's intended to make typing a comfortable experience but it's not as the pressing doesn't extend to the full length of the keyboard. I suspect the top layer hasn't been put on properly. (Note that I'm NOT using a protective screen layer)
I'm also dealing with weird reception issues like not receiving txt messages or phone calls sometimes. Browsing is a weird experience to:
The phone constantly shows a 3g icon with full reception. When I start browsing it takes a really long time for the page to load, but then whilst still loading the page i can see the 3g icon change to Hsdpa and the page is suddenly loaded. Downloading is also really fast when it finally is going, so the potential speed is there.
This is ALWAYS the case and it just seems really weird and out of the ordinary to me, like it's some stupid bug or setting issue.
I was thinking that it might be a rom issue but I'm using cyanogen 7 m6 which is considered stable right?
Oh and the battery is also showing weird behaviour, going from half full to completely empty, but I've heard that more people are experiencing battery problems.
I really love this phone but all the problems are drastically reducing the user experience.
Is anybody else dealing with these problems? I'm also really curious about my screen issue.
Thanks heaps
Sent from my GT540 using XDA Premium App
Flash and calibrate battery
I recommend you flash the latest ROM http://twitter.com/#!/MrMur4ik and calibrate your battery http://forum.xda-developers.com/showpost.php?p=12728721&postcount=1952. If you think it's a physical defect, you should get another phone.
jhonnyx1000 said:
I recommend you flash the latest ROM http://twitter.com/#!/MrMur4ik and calibrate your battery http://forum.xda-developers.com/showpost.php?p=12728721&postcount=1952. If you think it's a physical defect, you should get another phone.
Click to expand...
Click to collapse
You cannot flash 'latest ROM' without flashing fastboot first. Latest ROM is actually 2.1. (2.3 is unofficial, also you should have pointed to XDA Thread and not Mur4ik's twitter.) Also flashing a new ROM won't fix screen defects.
www.myGT540.com
There you go
No fastboot?
How did you update to Swiftdroid v2.0 M6? I used Mur4ik's Twitter account because the forum on this board is NOT by Mur4ik himself and it can be sometimes out-of-date. You can get the latest ROMs ASAP from Mur4ik's Twitter account. You should get a new phone as it has physical defects.
Dear all,
i have a Dell Streak 5, with following specs:
Android Version: 2.2.2
Kernel Version: 2.6.32.9-perf
Build Nr: 15609
The issues are:
- If i use the phone on my pocket with screen to my leg, when i need to unlock screen, i usualy can't, its kind of crashed...
- If i have the wireless ON, and go out from home, usually phone crashes , and when i go to use it, i see there was a reset. Seems that this wireless is kind of instable and make mobile phone crash.
I would like to upgrade something to try to solve this small issues, can anybody help me?
Thank you
Tiago
I forgot:
Baseband Version: GAUSB1A135100-EU
thanks.
I don't know what to tell you as far as wifi crashing your phone. That's never happened to me. As far as the other issue, seems pretty common. I think the recommended "fix" is to not carry it with screen facing your leg. I'm sure that's not what you want to hear....but its the best I got.
i can't explain why you wifi makes your phone crash, but for the impossibility to unlock the screen. i had the same problem, and somebody told me the problem was the heat of the leg that makes the screen tilt. so i bought an otterbox case with a belt clip, so with the screen untouched it works perfectly.
for the screen against leg issue, I just toggle the power off then on and it works.
yes, i agree to lordmorphous, don't face your screen to your leg..
just in case, you may try to calibrate it, or if the problem still, maybe you can re-flash to another latest stock rom.
I have never experienced the screen issues involved with facing the screen towards my leg, and I always put my Streak in my pocket with the screen facing my leg. I guess so far I've gotten lucky.
Strephon Alkhalikoi said:
I have never experienced the screen issues involved with facing the screen towards my leg, and I always put my Streak in my pocket with the screen facing my leg. I guess so far I've gotten lucky.
Click to expand...
Click to collapse
+1......never had screen issue
Guendaline said:
+1......never had screen issue
Click to expand...
Click to collapse
+1 same here..
I had got such issue that can't unlock the screen when I used the official ROM.
But there is not such problem when I use the Power Rom V1.1 now...
Masterzer0 said:
+1 same here..
Click to expand...
Click to collapse
+1 same here
briantamhk said:
I had got such issue that can't unlock the screen when I used the official ROM. But there is not such problem when I use the Power Rom V1.1 now...
Click to expand...
Click to collapse
The ROM makes no difference. I run 360 on my Streak.
I met a guy in a train station, and since there are not a lot ppl with such mob, i decided to ask. In fact, with screen faced outside, the issue finished. Strange..
Related with stock ROM, i think this is my next step: upgrade! the process dell.com.blablabla is always crashing, and sometimes i need to wait to use the phone. awww, not to say that i can't synch with my outlook
I am a bit disappointed with this phone/tab, i was expecting that it could work better.
Any tips on ROM? I am actually trying to use titanum backup to backup data, but it says again cannot root! How i root it?
Thanks again.
Tiago
Everything You Always Wanted To Know About The Streak But Were Too Busy Bricking It
That link there is your first step, for it explains how to root and how to do various other things. Now...I tend NOT to recommend using Titanium Backup since in my experience it screws up when restoring items. Your mileage may vary.
As to a ROM, stick with a stock ROM for now until you are comfortable with the rooting process. I have attempted to use GingerStreak but had a problem with the camera app so I had to go back. Flashing a ROM could fix your issues since a bad flash has been known to be source of the force closes.
Hi again,
finaly i tried a simple method: the gingerbreak, and rooted. Now that is rooted, i want try a diff Android version (from 2.2 to 2.3?).
Is there any recommendation?
Of course first i would like to backup all the data (already from the SDCard) but i am talking about the ContactList (i tried to use the simple: export, but onde again i got an error :/)
Any tips?
Thanks for all the help.
KR
Tiago
I've been having lots of little problems too.
My device randomnly decideds to restart time to time. There doesn't seem to be a pattern to it that I've worked out yet. But it's crashing right now and I have to soft reset it.
Another thing, if I have it in normal landscape mode but turn it on while holding it portrait mode or the screen isn't in the same orientation that it was before the screen turned off, Dell Stage often crashes.
SuperKeeper said:
I've been having lots of little problems too.
My device randomnly decideds to restart time to time. There doesn't seem to be a pattern to it that I've worked out yet. But it's crashing right now and I have to soft reset it.
Another thing, if I have it in normal landscape mode but turn it on while holding it portrait mode or the screen isn't in the same orientation that it was before the screen turned off, Dell Stage often crashes.
Click to expand...
Click to collapse
Exactly, mine restart very often too, but i think i know why. Try disable wireless before leaving your "home network"... in my case, it solves that crashings... only crash if dell stage crashes too... but most of times, its solved.
The only "bugs" i have are: camera button does not work, and when i turn screen on, the "unlock slide button" is ALWAYS in the portrait position.
I wonder, if this is solved with a new android version, or dell "libraries" update?
Thanks.
Tiago
for all those who think the problem does show up when u put it in the pocket facing your leg ..... i had the same view two weeks ago when suddenly i ran into this problem. i think best solution is calibrating the screen .....
zeeshan2341 said:
for all those who think the problem does show up when u put it in the pocket facing your leg ..... i had the same view two weeks ago when suddenly i ran into this problem. i think best solution is calibrating the screen .....
Click to expand...
Click to collapse
Calibrating the screen was what i've done when i could not unlock my mob phone for 1 week, i was desperate
After that, i solved all the screen issues using screen outside and not against leg.
Tiago
I was one of the unlucky persons to deal with the dreaded touchscreen problem. When on the 44s build, it sometimes got so bad the phone was almost completely useless. The touch screen problems didn't go away in spite of flashing countless Rome with almost every possible combination of kernels.. But nothing seemed to help. The touchscreen got noticeably worse when the phone got hot..i was almost at the verge of giving up.. But that's when it happened.. The 05Q update solved all of my touchscreen problems. I've checked with touch Explorer and even multi touch works flawlessly.. I understand that this problem was identified as a grounding defect.. And I did buy it.. But since the 05Q update seems to have completely solved this issue, my faith in oneplus has been restored.. Did anyone else notice this? What could be the reason?
Nothing's changed for me :c
Sent via Telnet
I never used to have problems with the touchscreen, but since update, the double tap to wake sometimes doesn't work.
It's really annoying to have to try it several times when you want to check the phone. (I already got used to not using physical buttons).
Anyone else with this issue?
alexbo said:
I never used to have problems with the touchscreen, but since update, the double tap to wake sometimes doesn't work.
It's really annoying to have to try it several times when you want to check the phone. (I already got used to not using physical buttons).
Anyone else with this issue?
Click to expand...
Click to collapse
For me, it got better. I would have terrible touchscreen problems.. I wouldnt be able to wake the device via D2W and mostly resorted to the wake up button.. but ever since the update, the battery's been a little bit on the downside..but the touchscreen problems have been completely eliminated and i'm okay with the tradeoff.. I just dont understand how they've managed to fix it if it was a hardware issue? im greatly confused..
my problems
onefanboy3556 said:
For me, it got better. I would have terrible touchscreen problems.. I wouldnt be able to wake the device via D2W and mostly resorted to the wake up button.. but ever since the update, the battery's been a little bit on the downside..but the touchscreen problems have been completely eliminated and i'm okay with the tradeoff.. I just dont understand how they've managed to fix it if it was a hardware issue? im greatly confused..
Click to expand...
Click to collapse
I've been facing touch issues after this update. The double tap is working hardly and even the top middle dot of the pattern lock seems unresponsive or experiencing ghost touches
Anyone have similar problems or with possible solutions ? Also for heavy battery drain
alexbo said:
I never used to have problems with the touchscreen, but since update, the double tap to wake sometimes doesn't work.
It's really annoying to have to try it several times when you want to check the phone. (I already got used to not using physical buttons).
Anyone else with this issue?
Click to expand...
Click to collapse
I'm having some issues too with this! Sometimes, even the physical power button doesn't work and I have to press it multiple times!
I m also facing same issue
Any solutions to resolve this issue?
Glad to hear it is better for you. Unfortunately, I still am experiencing ghost touches... Double tap on the other hand is fine.
For those who are still having touchscreen issues.
I wasn't having any issues at 44S. OTA update to 05Q and I immediately noticed issues with 'fast typing'. None of the hacks online worked ex. cat some touch-screen related system file..
Looks like 05Q is legitimately slower performance-wise and at least to me the keyboard is unusable.
Anyway, I spent quite a bit of time on this. Updated to a CM12 nightly and it's gotten a lot better although the issue is still there although less noticeable. Just try typing 'this' quickly. I get a swipe gesture activated once in a while (vs pretty much 90% of the time on 05Q).
02/23 Nightly CM seems very stable and clean. Very usable
kewlstuffdudez said:
For those who are still having touchscreen issues.
I wasn't having any issues at 44S. OTA update to 05Q and I immediately noticed issues with 'fast typing'. None of the hacks online worked ex. cat some touch-screen related system file..
Looks like 05Q is legitimately slower performance-wise and at least to me the keyboard is unusable.
Anyway, I spent quite a bit of time on this. Updated to a CM12 nightly and it's gotten a lot better although the issue is still there although less noticeable. Just try typing 'this' quickly. I get a swipe gesture activated once in a while (vs pretty much 90% of the time on 05Q).
02/23 Nightly CM seems very stable and clean. Very usable
Click to expand...
Click to collapse
From my experience I could say that these 'gost touches' are related to a system slowness more than a touch problem. Sometime I feel I could type fast without any problem, sometime I had to type very slow. Also this is rom related. Some are really snappy others not so. Another thing to mention is that keyboard feels better after a reboot, so maybe a memory leak!?
Inviato dal mio A0001 utilizzando Tapatalk
I just hope it's not the hardware touchscreen / sensor. My observations are consistent with everything you mentioned above. Memory leak feels possible or some unoptimized code. I don't see any issue in ex Chrome. It's mostly Hangouts app that's super slow so perhaps Google also pushed some update to Hangouts that slowed things down enough to be noticeable.
anuradha1208 said:
The double tap is working hardly and even the top middle dot of the pattern lock seems unresponsive or experiencing ghost touches
Click to expand...
Click to collapse
Yup, definitely noticed DTTP is not working as well on 05Q vs. 44S.
Steelpapi said:
Sometimes, even the physical power button doesn't work and I have to press it multiple times!
Click to expand...
Click to collapse
Yes, same here!
kewlstuffdudez said:
I wasn't having any issues at 44S. OTA update to 05Q and I immediately noticed issues with 'fast typing'. None of the hacks online worked ex. cat some touch-screen related system file..
Click to expand...
Click to collapse
Same here - things were perfect on 44S, but screen has just turned to crap on 05Q!
Did you try going back to 44S, or did you just go straight to CM12 nightlies?
Cheers,
Su
I went straighten to CM12 nighties. The touchscreen issues still does up but not as much. Makes me think is a hardware issue with the touchscreen independent of firmware perhaps just didn't notice before. When I went to CM12 I did a full wipe, so everything from scratch
Sumanji said:
Yup, definitely noticed DTTP is not working as well on 05Q vs. 44S.
Yes, same here!
Same here - things were perfect on 44S, but screen has just turned to crap on 05Q!
Did you try going back to 44S, or did you just go straight to CM12 nightlies?
Cheers,
Su
Click to expand...
Click to collapse
I think I may have found a solution! Recently I enable the touchscreen buttons, but yesterday I disabled the quick launch shortcuts and it seems to be working.
Go to DEVICE - Buttons and disable it there!
Hope that helps!
I have not faced touch screen issue.
Even i have broken my display from top..
Sent from my A0001 using XDA Free mobile app
Steelpapi said:
I think I may have found a solution! Recently I enable the touchscreen buttons, but yesterday I disabled the quick launch shortcuts and it seems to be working.
Go to DEVICE - Buttons and disable it there!
Hope that helps!
Click to expand...
Click to collapse
Hey,
Which touchscreen buttons do you mean?
I made a short video showing the problem using a multi-touch test app. Basically if I have two or more touch points that are horizontally near each other, the screen totally flips out!
Thanks,
Su
A thread i created in the oneplus one forum after a bit of research from my side
https://forums.oneplus.net/threads/major-touch-screen-issue.282231/
Sumanji said:
Hey,
Which touchscreen buttons do you mean?
I made a short video showing the problem using a multi-touch test app. Basically if I have two or more touch points that are horizontally near each other, the screen totally flips out!
Thanks,
Su
Click to expand...
Click to collapse
Crazy stuff.. Looking at the video, I have almost bought that it's a software problem..
Mine works fine if and only if you turn off all those double tap settings (wake/sleep) and turn off ambient display.
I've gone through all the settings menus and turned off everything gesture or touch related... also switched to onscreen buttons.
Still have the same problem
I emailed support to arrange an RMA, but they want me to wait for Lollipop... WTF?