Related
finally got around to updating to GB (after Kies problems). Everything looked ok until I tried the compass.
Nothing seems to be working!
Tried several compass / GPS apps including Google Sky Map but the direction doesn't change with the orientation of the phone.
Anyone else come across this?
I have, I assume, the same problem as you.
I upgraded to 2.3.3 and now the compass doesn't work at all. For one thing, in Google Maps, if I hit the compass button the compass actually flips 180 degrees and points south instead of north. If I rotate the phone the compass rotates with it. In other words it doesn't track North at all. It just stays pointing in the same direction and turns with the phone, like it was stuck. I've tried every compass app I can find and have calibrated it over and over and still the same issue.
One thing I did find was if you type in *#0*# on the phone keypad you will open up a diagnostic screen. Tap the sensor button and you can see the magnetic sensor isn't reading north properly. But if you tap the magnetic button and then run the test is passes fine.
From what I've found browsing the web, it seems to be a common problem with Gingerbread 2.3.3 on HTC phones. So I'm assuming that it's the same problems that's affecting us on the Galaxy S (GT-I9000). And AFAIK, it's a known bug and has been reported to Google.
It's annoying for me, but not in the way that it will effect me in my day to day usage of the phone. I don't need the compass to work as I use Google Maps and GPS to navigate, not the compass. But of course I want it fixed because I do sometimes need to use the compass for other things. And of course because my phone has that feature and I paid for it so make it work FFS!
Anyway, hope there is a fix for it soon and Samsung doesn't take forever to release the update, like it did for Gingerbread. Of course, if someone come up with a fix that you need to be rooted for then I will take the plunge and root my phone. The only reason I haven't done it yet is that I can't find a simple and clear way of doing it on 2.3.3. Every guide I've read seems to be for Froyo and not Gingerbread. And when I downloaded "SuperOneClick" my Comodo Anti-Virus went nuts about a Linux exploit file in it. And although I don't think it was something that could be a danger to my Win 7 box, I cleared it just to be safe.
So, a long reply to basically say, "Me Too!!!11!!11!"
same probleme here. jvo
wurstel said:
same probleme here. jvo
Click to expand...
Click to collapse
Oh yeah, forgot to mention that it's JVO on mine too.
I have the same problem with the compass. Seems to be a Problem with Gingerbread and all programs that use the compass. Pretty bad news for me as I use it a lot. Looks like I'm going back to Froyo.
Sprint EVO 4G
I confirm that 2.3.4 still has the same prob.
sinkingslowly said:
finally got around to updating to GB (after Kies problems). Everything looked ok until I tried the compass.
Nothing seems to be working!
Click to expand...
Click to collapse
Same problem here
I got a couple of new Galaxy S last week, updated to 2.3 and found that the compass is totallly crazy (specially in one of the phones). I was sure that it worked before on 2.2 but I did not tested properly...thanks for this post, I know I do not have a faulty terminal...just a faulty software
Compass not working on JVP :-(
Sent from my GT-P1000 using XDA App
I now installed F1 JVP Mod V6 and can confirm that it has a working compass. It's an allover very smooth, stable and fast rom and I think it will be with me for a while.
All gingerbread phone has the same problem, I downgraded my phone to 2.2.1 because of this problem, as I frequently use the compass
maskr said:
All gingerbread phone has the same problem, I downgraded my phone to 2.2.1 because of this problem, as I frequently use the compass
Click to expand...
Click to collapse
The latest update 4.24.651.1 for the HTC EVO has the compass fixed.
I had the same problem.
I have 'Google sky maps' install and all is ok now...???
I'm on [ROM][F1 Galaxy S2 V4]
Please star this issue, if your compass doesn't work...
Nico12 said:
I had the same problem.
I have 'Google sky maps' install and all is ok now...???
I'm on [ROM][F1 Galaxy S2 V4]
Click to expand...
Click to collapse
WOW........ i am on JVP with CF-root and it realy is fixed.....
Did not worked before I installed Sky map.
Compass fixed with Google Sky maps install!!!
I just installed Google Sky Map and magically, now the compass works in all programs that use it (like Speed HUD, one of my favorites).
too bad they did not fix this with an update, but this does work.... now for that problem with Speech to Text not working in my car....
Had the same problem too. Solved now..... by
1. *#0*#
2. Diagnostic Menu, select "Magnetic"
3. Pressing "Start Test" in the Magnetic Sensor Test Menu, somehow reset the calibration.
4. Go back to Diagnostic Menu, select "Sensor"
5. All the sensor values will be shown, look at the black dial with a red need. If "1 need calibration" is shown just rotate the unit a few times..... then "2 need calibration" when just "3" is indicated .........calibration done. Make sure there no power lines and metal structures are not nearby.
1. *#0*# ?
Dial this? Did not work on my EVO...
pmoreau said:
1. *#0*# ?
Dial this? Did not work on my EVO...
Click to expand...
Click to collapse
Maybe it only works on Samsung Galaxy S?
This thread is about the compass error on these phone. Try the HTC forums to see if there is a solution for compass error on your Evo.
srsig said:
Had the same problem too. Solved now..... by
1. *#0*#
[...]
Click to expand...
Click to collapse
Thanks for this hint. Problem seems to solved on my Galaxy S
elhennig said:
Thanks for this hint. Problem seems to solved on my Galaxy S
Click to expand...
Click to collapse
I tried it on mine but the "fix" for the compass doesn't seem to stick. I have to calibrate it every time I want to use it in any program by doing the figure 8 wave.
Hi guys
Auto rotation is not working properly on my galaxy s...some times it doesn't even work...I tested it on both ICS and Gingerbread...Really it is hurting me...plss help me to solve this problem...
Thanks in advanced
plsss guys help me...im waiting for your replyyy
If its any help, my auto rotation was pretty buggered as well. It would work on gingerbread but only if you help the phone more vertical than you really needed to. ICS wouldnt work at all.
Mine also wouldn't work properly in google sky maps and similar apps, if you panned left and right, it would also twist the view a bit, difficult to explain but see if sky maps works as expected. Also compass wouldnt work properlly, only worked with phone flat, soon as you tilt it would start to change direction when should be pointing same way.
I went back to various stock roms, different modems, loads of stuff, reflashing boot loaders, unrooting everything and couldnt fix it.
was a hardware fault, no other reason i could see why it wouldnt work, and just got phone replaced under warranty. all good now.
what ROM you use or you are in stock ROM? go to settings/about telephone and write what you see in there
srinivas07 said:
Hi guys
Auto rotation is not working properly on my galaxy s...some times it doesn't even work...I tested it on both ICS and Gingerbread...Really it is hurting me...plss help me to solve this problem...
Thanks in advanced
Click to expand...
Click to collapse
Tried recalibrating from Settings, Display?
psych0phobia said:
Tried recalibrating from Settings, Display?
Click to expand...
Click to collapse
there is no calibration in settings.....what to do now?
I have a similar problem.
Autorotation of apps works ok on Ginger (2.3.5, 2.3.6), but on any ICS that I have tested doesn't work.
ICS has no horizontal calibration, so do not know what else to do.
Any hint?
i have the same problem on I9000 4.1.2 cyanogen mod,any solution?
I have installed different ICS roms to 3 different i9000s. All of them has touchscreen problems.
Some parts of the touchscreen does not react to your touch sometimes. You have to lock and unlock your phone to regain the full touchscreen. I have tried different kernels etc... No go. It really annoys when you are dialing a number, writing a message etc.
And interestingly no one mentions about it at ICS Rom and ICS kernel threads. Can I be that unlucky to have the problem on 3 different i9000s (They are not from the same batch, each one is bought from another part of the world, at different years).
I would really like a solution or suggestion. Till now i have tired different kernels, different ROMs (mostly ICSSGS (different versions), and Dark Knight (different Versions)). I even tiried diffrent schedulers and governors.
Peace.
That's weird, I have used SlimICS and have never had TS problems... Are you sure you flashed everything right? Please explain the way you've done it
with one phone installed team icssgs as it should coming from the stock , other phones back to stock with odin than cf root and flashing the roms after wipes factory resets. the usual flashing procedure....
Try flashing the team hacksung base first, afterwards flash your desired custom ROM. That should do it.
could you try to explain the diff. between flasiing without cm9 or or with cm9. whar would
be the difference at the end?
I don't exactly know why this is needed, but I would assume that TeamHacksung or CM9 have some frameworks included which are perhaps missing in custom ROMs. I'm just guessing, don't really know =/
Have you tried it? For a CM9 based ROM, flash CM9 first and for a TH based ROM, TH first
Hello,
Have you checked if the Problem still remains when you are on Stock ROM?
CU
tenos
Gesendet von meinem GT-I9000 mit Tapatalk 2
no i havent but it was working just before i flashed icd.
also i have 2 more phones with the same problem. So it is not my phone malfunctioning.
In ICS-333 from you can turn on show touches in developer options in settings menu you could see if its registering your touch immediately or at all. The browser is the only place I've experienced touch lag though.
Sent from my GT-I9000M using XDA
Hey I got ur prob and I know what causes it, it not a bug, its dirt or water on your screen that causes the prob if u keep the screen spotlessly clean u don't get it
Sent from my GT-I9000 using XDA
I have activated show touch before, it does not register your touch at all. also I have tried cleaning it no go, since this is happening with 3 different phone, i doubt it is dirt etc.
belmethos said:
I have activated show touch before, it does not register your touch at all. also I have tried cleaning it no go, since this is happening with 3 different phone, i doubt it is dirt etc.
Click to expand...
Click to collapse
I know what causing it. It a bug where dirt or water or something gets on the screen and because the drivers on ics is so sensitive it picks it up, try changing sensitivatiy or keep that screen very clean
Sent from my GT-I9000 using XDA
i have the same problem. its very frustating. never happened in gingerbread. only on ICS.the bug happened occasionally, the funny thing is it only affect the first row area of the screen. (lower left altheway up to upper left corner), it doesnt register tapping on the screen but it still register swiping from outside of the area..., like ussual i need to lock and unlock again to make the touch working again.
I have installed GB back and problem is gone? I am out of ideas anyone?
Flashed back ics bug returns, flashing jb same thing.
Exactly the same problem here
With Stock GB everything works fine, with custom roms the right side of the touch screen doesn't react. You have to lock and unlock your phone to regain the full touchscreen.
This is interesting this is far more than i anticipated anyone with a clue?
same problem here. my screen was working when i bought it (obviously). it was froyo then. the touchscreen problem appears when i upgraded to custom ICS rom. the middle part of my touchscreen does not respond to touch. none. nada. although the rest of the screen seems to be responding to touch so far. turning the screen off the on again temporarily fixes the problem, but not always. i put back a gb rom, the problem was gone. i was thinking maybe there's a different digitizer driver samsung put on their stock gb roms. it's really annoying.
any more ideas? should i replace my touchscreen digitizer?
Yes it's really annoying :crying:
What is different between stock gb/froyo and ics/jb custom roms that have such an effect on the touchscreen?
I will try the app SGS Touchscreen Booster to decrease the screen sensivity, maybe it helps
never heard of this problem in all the time i was ics.maybe time for some jellybean
Hi everyone,
I bought a Samsung galaxy s last week from an eBay auction. The phone was described as touch screen lag. I was thinking that flashing a new firmware will solve the problem. I got really cheap though
The touch screen stops suddenly in every 5/6 minutes and I have to lock the screen using power key and unlock again to make it working.
when I got the phone:
Non Samsung battery and chargers were used, I changed and using original ones.
Stock XXJVS firmware in it.
First I flashed stock 2.2.1 froyo and test the screen using *#0*# code. it got pass. But when I start using it, the problem was still there.
Then I flashed stock GB, same story, now slim ics, same thing.
Please someone help me, there is nothing I can do with it now.
I search few threads related to screen problem but couldn't find one with similar problem. So asking here.
mregmi121 said:
Hi everyone,
I bought a Samsung galaxy s last week from an eBay auction. The phone was described as touch screen lag. I was thinking that flashing a new firmware will solve the problem. I got really cheap though
The touch screen stops suddenly in every 5/6 minutes and I have to lock the screen using power key and unlock again to make it working.
when I got the phone:
Non Samsung battery and chargers were used, I changed and using original ones.
Stock XXJVS firmware in it.
First I flashed stock 2.2.1 froyo and test the screen using *#0#* code. it got pass. But when I start using it, the problem was still there.
Then I flashed stock GB, same story, now slim ics, same thing.
Please someone help me, there is nothing I can do with it now.
I search few threads related to screen problem but couldn't find one with similar problem. So asking here.
Click to expand...
Click to collapse
Sounds like a hardware problem to me..but it's really hard to say if it is. But it would definitely seem like it since it isn't ROM related. Maybe a water damage or faulty digitizer?
Sent from my GT-I9000 using Tapatalk 2
This happens to me sometimes very rarely though, it will be weird and hard to touch but speaking to someone with the same phone they said they had this problem to all I do to resolve the problem is lock and unlock the screen, I thought this was normal?
Sent from my GT-I9000 running remICS-UX using XDA premium
It shouldn't be normal. I am using another galaxy s for almost two years. But never had this problem in such extent, little bit lag on touchscreen when on froyo. But never after. Now with slim ics Temple run is more smooth then iphone 4.
Sent from my Galaxy S using xda premium
Kurre said:
Sounds like a hardware problem to me..but it's really hard to say if it is. But it would definitely seem like it since it isn't ROM related. Maybe a water damage or faulty digitizer?
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for reply. When I got it first time, it was really annoying, the problem was so frequent that it was almost unusable. Now in new rom, after unlocking the screen it works little longer then before. Works like a charm when it works. So not sure this is hardware problem.
Sent from my Galaxy S using xda premium
I don't think this is a hardware or problem either, I broke the screen and replaced it and I still have the same thing when though it is very rare, so if it was the screen it should of gone after I installed the new one, btw I installed a whole new pre built front so the bevil and LCD, and my phone has never hib water damaged? Maybe its something to do with the bootloader? As that doesn't change through ROM flashes
Sent from my GT-I9000 running remICS-UX using XDA premium
mregmi121 said:
Please someone help me, there is nothing I can do with it now.
I search few threads related to screen problem but couldn't find one with similar problem. So asking here.
Click to expand...
Click to collapse
try using a LCD modder LCD density modder https://play.google.com/store/apps/details?id=com.birdapi.android.dpi&feature=search_result
@xsenman;
I did that couple of times going through Advance slim setting. That didn't change anything. Now I'll try this as well.
I change touchscreen into chainfire sensitive option in semaphore app. Still lagging.
Tried over clocking to 1200 but it freezes and automatically reboots into recovery mode. I can use only after changing to default
Sent from my GT-I9000 using xda premium
Guys its really annoying now. Its behaving strangely. I played with it few hours and found out that the screen near the home button freezes first. I cant press the dock but still pull the notification bar? then stops working whole screen. I checked the show touches in developers options setting. Sometimes it works randomly actually without touching it , I just place my finger near the screen but didn't touch and on few occasion it works opposite direction, like I scrolled down but it gone up:crying:
Is this the sensor issue? Is there any way to fix? Any idea please?
mregmi121 said:
Guys its really annoying now. Its behaving strangely. I played with it few hours and found out that the screen near the home button freezes first. I cant press the dock but still pull the notification bar? then stops working whole screen. I checked the show touches in developers options setting. Sometimes it works randomly actually without touching it , I just place my finger near the screen but didn't touch and on few occasion it works opposite direction, like I scrolled down but it gone up:crying:
Is this the sensor issue? Is there any way to fix? Any idea please?
Click to expand...
Click to collapse
try this tool to verify where the problem is , if its hardware, you have no choice but to take it to a technician
https://play.google.com/store/apps/details?id=com.gombosdev.displaytester&feature=search_result
and this
https://play.google.com/store/apps/details?id=com.vital.tst.n7000&feature=search_result
https://play.google.com/store/apps/details?id=zausan.zdevicetest&feature=search_result
xsenman said:
try this tool to verify where the problem is , if its hardware, you have no choice but to take it to a technician
https://play.google.com/store/apps/details?id=com.gombosdev.displaytester&feature=search_result
and this
https://play.google.com/store/apps/details?id=com.vital.tst.n7000&feature=search_result
https://play.google.com/store/apps/details?id=zausan.zdevicetest&feature=search_result
Click to expand...
Click to collapse
Screen+digitizer panel can be changed by yourself. For it, you just need couple of tools and little nerves
Instructions can be found from YouTube, this forum and many other places..
Sent from my GT-I9000 using Tapatalk 2
Kurre said:
Screen+digitizer panel can be changed by yourself. For it, you just need couple of tools and little nerves
Instructions can be found from YouTube, this forum and many other places..
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
I tried all of those apps, nothing wrong. I think I should change the screen and digitizer, I might need to go to the repair center because my hands shake (my usual problem) and hard to fix tiny things. I want to do few experiments before taking it to repair. I already put it in the freezer for two hours it was acting like crazy after.
Suggest me more...
Sent from my GT-I9000 using xda premium
Me too!
and i thought i'm the only one experiencing this kind of problem. it is exactly what i'm having on my sgs. seems to be temporarily fixed by turning the screen off and then on again, but after a while, the screen doesn't respond on the same spot as you're having.
i've managed a low level debug on screen touch response using adb logcat, and my touch doesn't really register any on adb logcat console.
they might be correct on the hardware problem, but when i'm on any gingerbread rom (2.3.6), the problem is gone.
guys, any idea what kind of drivers they're using on gingerbread for our touchscreen?
I have this too on ics, left half of screen stops responding, lock on/off sorts it....until the next time! Bugs the hell out of me!
Me too! on ICS
btw, i'm already on ics team nyx
change
flash CF KERNEL and put ICS CM9
middle screen not responding
- when in stock gb firmware (official from samsung), the touchscreen problem is gone.
- but i want the features of an ics rom, so i flashed one (first was slim ics); the problem appeared first; first guess was the custom rom was still in its early stages.
- flashed back to gb, no touchscreen problem.
- flashed new ics rom from cm9 (nightlies), problem appears again (ugh!).
- flashed backed to updated slim ics since this was the fastest and easiest to install, touchscreen problem still persist.
- found a temporary fix by turning the screen off then on again.
did a adb logcat full trace log of touchscreen input: what i noticed was the whole vertical middle part of the screen is not responding to touch; dragging touch from one side to middle is working just fine, but not starting from the mid vertical part.
the problem may sometimes go away after a while, and sometimes persist even after the temp fix. it's very intermittent indeed.
help please.
psycotrompus said:
- when in stock gb firmware (official from samsung), the touchscreen problem is gone.
- but i want the features of an ics rom, so i flashed one (first was slim ics); the problem appeared first; first guess was the custom rom was still in its early stages.
- flashed back to gb, no touchscreen problem.
- flashed new ics rom from cm9 (nightlies), problem appears again (ugh!).
- flashed backed to updated slim ics since this was the fastest and easiest to install, touchscreen problem still persist.
- found a temporary fix by turning the screen off then on again.
did a adb logcat full trace log of touchscreen input: what i noticed was the whole vertical middle part of the screen is not responding to touch; dragging touch from one side to middle is working just fine, but not starting from the mid vertical part.
the problem may sometimes go away after a while, and sometimes persist even after the temp fix. it's very intermittent indeed.
help please.
Click to expand...
Click to collapse
So your sgs touchscreen working fine on stock gb rom! It might not be a hardware problem then. We have similar problem, only difference is I have problem on GB too. I've even tried stock froyo, same story
Sent from my Nexus S using xda premium
same problem here, left part of the screen would be unresponsive at times
can fix by locking the phone through power button and unlocking it, thats why i think its a software problem.
I dont remember having this problem in GB also.
maybe something is messed up during flash?
I have the same problem with ics and jb roms from the onecosmic ics times and i had a topic http://forum.xda-developers.com/showthread.php?t=1648287
I have written here but no one seems to now what it is, i have been using ics from onecosmics first release and had the problem from that moment on, different kernels, roms etc it is still here i have flashed gb again and problem is gone, flash again with ics the middle part still acts sometimes. ?...
We should request from kernel developers and rom developers to look into it. I have tried almost everything no luck so far
It seems that my Accelerometer isn't functioning correctly, it doesn't give me proper readouts unless the app in question has a calibration tool inside of it, and even then it doesn't fix it on other apps. I've tried the calibration tools in various apps to no success, I'm forced to use another app simply to change orientation while doing regular things like web and youtube.
When I have The Night Sky open it seems to be stuck looking down, and moving my phone just makes it turn left and right randomly.
Anyone have any ideas to help?
Flashing different ROMs and Kernels doesn't help.
Only thing I haven't tried is possibly flashing a GB rom and calibrating with that...