I downloaded the visualizer app (the one with the 2 dots and not the square)
and yea if I begin on the left side of the screen then touch the right and move around the points hang a bit when they cross and will hardly ever switch (unless u do complex rotating action with both points but then the switch is periodic at best)
but if I begin on the right side of the screen, the points ALWAYS switch...always...
Interesting...does that mean it's a software issue?
I already KNOW this is the wrong section but I feel this is something that could benefit from the most viewed sub forum.
edit: starting from the right side, the points fix themselves when I do the same complex rotating action that sometimes causes point switch starting from the left. I'd record it if I had a camera, but yea.
none of the 163 (at the time of this posting) viewers have anything to say?
not even a "WRONG SECTION NOOB" (Despite my non noobishness) post?
sheesh.
wrong section, noob.
wrong section noob.
hahahhaha LOVE IT.
another interesting update: The previous results were on a Cyanogen Mod...
Using Modaco Desire Alpha 14 I get the EXACT opposite results...
Starting with a finger on the left side of the screen then the right side point switch is guaranteed...whereas starting with a finger on the right then the left point switch is non-existent.
I think it is entirely a software fault...anyone who knows anything have anything to say about it?
then again, the overall finicky-ness of it is probably just a flaw period...though I think it can be fixed with a software update due to the different behavior between ROMs.
seems to switch points at random actually...on the desire ROM especially.
still wrong section noob. haha.
It has been covered by pretty much all tech blogs on the 'net already.
Some think it is a hardware bug, and others think it's software. Who knows.
I don't think it will matter for most people, although I consider it a serious flaw if it is not possible to fix it with software.
And yeah, this might be the wrong section, but it could also turn into a dev issue. "wrong section, noob" was funny the first time.
yea that's why I put it here in the first place, I shoulda added [Think Tank] and then squeezed my statements there...def belongs in General though...any Mod please move there without any Snarky comments prior.
i 'll move it but with snarky comment : use edit button when you want to replay to yourself instead of creating two posts
I just tried that Multitouch Visible Test, and it does not always switch the dots. It is a little bit strange though, because it seems like the dots are just put on the wrong intersect of the red and blue lines. If it is a hardware malfunction it is a very weird one. Some kind of random mirror function.
Maybe its a problem with the app itself and nothing with phones.... comon now, I don't have a problem with multitouch and I think that app is horrible to determine a bad phone..
No offence people, but these issues everyone brings up on this phone isn't a issue at all... the 3g issue is network not phone, the wonky screen is from the wrap around effect, the multitouch issue is retarded.....
The only valid one imo is the dust...... everything else seems irrelevant
temperbad said:
Maybe its a problem with the app itself and nothing with phones.... comon now, I don't have a problem with multitouch and I think that app is horrible to determine a bad phone..
No offence people, but these issues everyone brings up on this phone isn't a issue at all... the 3g issue is network not phone, the wonky screen is from the wrap around effect, the multitouch issue is retarded.....
The only valid one imo is the dust...... everything else seems irrelevant
Click to expand...
Click to collapse
The multitouch issue is not app based, otherwise it'd be present on the Droid as well (where it isn't, infact Droid's multitouch is damn near flawless looking at that video and having owned one) Though it's not going to be an issue for anything I and many others current use the phone for (Browsing, Maps, Gallery, anything else that uses pinch to zoom) it will become an issue and may already be for multitouch games...From what I saw it seemed like it is likely software based due to the fact that on the Cyan ROM one thing happened in one order and on the Desire ROM same thing happened (and a bit more buggy) in another order.
But yea, about the 3G issue..I never had that either...in fact my 3G with my N1 is better than the 3G i had with my G1.
AbsoluteDesignz said:
The multitouch issue is not app based, otherwise it'd be present on the Droid as well (where it isn't, infact Droid's multitouch is damn near flawless looking at that video and having owned one) Though it's not going to be an issue for anything I and many others current use the phone for (Browsing, Maps, Gallery, anything else that uses pinch to zoom) it will become an issue and may already be for multitouch games...From what I saw it seemed like it is likely software based due to the fact that on the Cyan ROM one thing happened in one order and on the Desire ROM same thing happened (and a bit more buggy) in another order.
But yea, about the 3G issue..I never had that either...in fact my 3G with my N1 is better than the 3G i had with my G1.
Click to expand...
Click to collapse
It may be just that There is different hardware/software in one vs the other.....
I still don't believe it will be a issue, I mean that app your sliding both fingers at the same time, and it only happens some of the time..... I don't believe there will be many games where your performing that kind of action, and even if so it don't happent all the time and may act completely differently in a game than it does in the app..... I mean, if it was a big deal we would notice it in the other pinch to zoom apps, I've tried on pinch to zoom to get it to do anything weird and it don't..... just saying, I don't think this video/app proves much....
Then again, who the hell am I.. lol I don't know shat like anyone....
temperbad said:
It may be just that There is different hardware/software in one vs the other.....
I still don't believe it will be a issue, I mean that app your sliding both fingers at the same time, and it only happens some of the time..... I don't believe there will be many games where your performing that kind of action, and even if so it don't happent all the time and may act completely differently in a game than it does in the app..... I mean, if it was a big deal we would notice it in the other pinch to zoom apps, I've tried on pinch to zoom to get it to do anything weird and it don't..... just saying, I don't think this video/app proves much....
Then again, who the hell am I.. lol I don't know shat like anyone....
Click to expand...
Click to collapse
In fact, N1 has only pinch and zoom multitouch whereas droid has native multitouch...
temperbad there are a lot multitouch app in the market which state that Nexus One is not supported due to its multitouch misfunction..
ping pong multitouch is one of these applications..
Propably it is a hardware issue.
temperbad said:
Maybe its a problem with the app itself and nothing with phones.... comon now, I don't have a problem with multitouch and I think that app is horrible to determine a bad phone..
No offence people, but these issues everyone brings up on this phone isn't a issue at all... the 3g issue is network not phone, the wonky screen is from the wrap around effect, the multitouch issue is retarded.....
The only valid one imo is the dust...... everything else seems irrelevant
Click to expand...
Click to collapse
Try it in the browser. Pinch zoom out, then rotate your fingers in a circle and continue pinch zooming out. Instead of zooming out, it zooms in.
jerhoyet said:
Try it in the browser. Pinch zoom out, then rotate your fingers in a circle and continue pinch zooming out. Instead of zooming out, it zooms in.
Click to expand...
Click to collapse
I have. No issues
temperbad said:
I have. No issues
Click to expand...
Click to collapse
It's not all the time, but it happens. It's caused my axis flipping.
maedox said:
It has been covered by pretty much all tech blogs on the 'net already.
Some think it is a hardware bug, and others think it's software. Who knows.
I don't think it will matter for most people, although I consider it a serious flaw if it is not possible to fix it with software.
And yeah, this might be the wrong section, but it could also turn into a dev issue. "wrong section, noob" was funny the first time.
Click to expand...
Click to collapse
Its supposed to a software bug.. The same thing produces two different results with two different ROMs....so its not a hardware issue....
AbsoluteDesignz said:
another interesting update: The previous results were on a Cyanogen Mod...
Using Modaco Desire Alpha 14 I get the EXACT opposite results...
Starting with a finger on the left side of the screen then the right side point switch is guaranteed...whereas starting with a finger on the right then the left point switch is non-existent.
I think it is entirely a software fault...anyone who knows anything have anything to say about it?
Click to expand...
Click to collapse
temperbad said:
I have. No issues
Click to expand...
Click to collapse
I too have absolutely 0 issues with pinch to zoom and rotating, getting my fingers really close together, etc. 0 issues whatsoever.
I'm on the Desire rom though.
Anyway, you have to remember this has absolutely NO importance whatsoever unless you play a lot of games.
If you don't, like me (I have a 360, so I couldn't care less), you'll never really have an issue with this.
Related
So I like most everything about my nexus but the way it takes pictures. Its not so much a real issue because it doesn't prevent the camera from working.. but it seems the chip/sensor they used for the camera gives a red spot in all pictures in the center of the image, most noticeably in pictures with a white or light background/image. I'll attach a picture so everyone else can confirm what I mean... I was hoping we could get HTC to replace the phones that have this issue via the warranty as this seems to be an issue with many nexus ones (based on a couple of reviews and the pictures they provided there). Here's my sample picture. You can also see it on screen when looking at what you're going to take a picture of.
Also I do research in a lab and its a procedure for an experiment I'm doing... just realized what I was posting might seem odd... didn't really read it before posting.
It is a software issue, so they are not going to do a warranty replacement. Droid had the same deal with it, seems to be something with the base 2.0/1 Android framework, I am sure it will be fixed when google releases their bug fix update(don't ask when, no legit idea beyond guessing sometime around the start of February, since that seems to be the typical timeline with phone bug updates, about 30 days after launch the first update is released).
Correction. It's a HARDWARE issue. Dont believe me? leave your cammera on for a couple minutes.. Goes away right? Its cuz droid camera was the same.. or similar? They had a bad batch. Mine has no pink eye(N1) =>
The Droid's issue was partially a software problem...
http://www.engadget.com/2009/11/17/motorola-droid-camera-autofocus-fixed-in-secrecy/
As well, it is a "who really knows?"
http://wmpoweruser.com/?p=10749
It seems many phones, with different camera's and so forth are having this issue... CCD seems to be the manufacturer of all the sensors, though, so perhaps there is a problem with the firmware from CCD causing this?
I highly doubt that every single camera sensor ever made by this company happens to have this sort of issue due to hardware. That would be pretty insane! However, if it was a firmware issue, then it would be present in every handset that uses a CCD manufactured/firmware supported camera, and this seems to be the case.
As well, it has already been stated the HD2 will get an update that fixes it. Hopefully the Nexus One is in the same boat. I didn't notice it on the test unit I used, but I asked the current tester if it was happening, and on all 3 it is present. It isn't noticeable in most pictures, though, especially with the flash on, FXcamera set to the proper white balance, and so forth.
EVERY Nexus One you get will have this issue. IT IS SOFTWARE. My N1 has it, the replacement I got has it too.
I've just taken a load of pictures and no pink from what I can see with both flash on and off.
Took pictures of a white surface and no pink. Must be hardware.
EDIT: http://picasaweb.google.com/lh/phot...authkey=Gv1sRgCNKM3fOF452TyQE&feat=directlink
http://picasaweb.google.com/lh/phot...authkey=Gv1sRgCNKM3fOF452TyQE&feat=directlink
Do you have any camera apps installed? FXcamera with proper white balance settings(sometimes auto is perfect, sometimes you have to do it manually) makes it go away a lot of the time too.
Eh Hem.. Guys are you all forgetting that my N1 DOES NOT HAVE PINK EYE
From what I understand this is a hardware issue. This was also present in an earlier HTC phone (I think the HD2) running a different OS altogether.
yes this was a widespread issue on the HD2... and it was completley fixed by a SOFTWARE UPDATE! >.<
A cursory search of the words "hd2 pink camera issue" on Google seems to imply that this is actually a hardware issue.
Edit: The source of the confusion http://www.redmondpie.com/fix-pink-camera-problem-on-htc-hd2-9140202/:
HTC first confirmed it as an hardware issue but then later they found out that it was infact a software issue, rather than a hardware one.
Click to expand...
Click to collapse
http://www.gsmarena.com/a_hardware_fault_causes_htc_hd2_*pink*_camera_issues_confirmed-news-1276.php
I believe the SOFTWARE update is just overcorrecting the blue/green settings on the center of the camera (Guess...) to cancel out the HARDWARE problem with YOUR camera. But again.. It is a Hardware issue for sure. Sorry guys xD I win!
I wouldnt trust htc if you ask them though.. I dont think they are certain what planet they are on half the time.. I asked about how they know that I unlocked my bootloader and his answer was basically.. voodoo. Soooo yaaahhhh... Notice that the cameras are the same for droid HD2 and Nexus one? and those are the only 3 with the issue? Not the G1 with ported software? => hardware folks
flamerider88 said:
I wouldnt trust htc if you ask them though.. I dont think they are certain what planet they are on half the time.. I asked about how they know that I unlocked my bootloader and his answer was basically.. voodoo.
Click to expand...
Click to collapse
You asked someone in support; customer support for any company is always uninformed. These aren't the people making press releases or even official forum posts.
flamerider88 said:
I believe the SOFTWARE update is just overcorrecting the blue/green settings on the center of the camera...
Click to expand...
Click to collapse
I agree, just because the manufacturer releases a software fix doesn't mean its a software problem to begin with.
The first day I had the phone, I really noticed the pink spot. Yesterday I took 30 pictures, I didn't notice it at all. Today If I look hard enough I think I see a little tiny pink, viewing the image of a white piece of paper in the same place (office) I first tested the camera.
Yeah I noticed this too. It only really shows up if I take pictures of white paper or a white wall. Every other normal pic I take turns out fine but I do hope they can fix it with a software update... wouldn't be too hard.
dinan said:
Yeah I noticed this too. It only really shows up if I take pictures of white paper or a white wall. Every other normal pic I take turns out fine but I do hope they can fix it with a software update... wouldn't be too hard.
Click to expand...
Click to collapse
My n1 has it too. Ive tried it now in room with room light and it gives this violett spot when i tak a picture with automatic colorbalance, if i put room light as colorbalance there is no spot...
google already knows about that issue and a fix will be released!
"I have great news! The issue has been fixed and should be included in the next update to Android. I say "should" because things can change at the last minute. Keep an eye on your notification bar for a system update."
source: http://www.google.com/support/forum/p/android/thread?tid=7a22ebb69da2b253&hl=en#all
navahoo said:
google already knows about that issue and a fix will be released!
"I have great news! The issue has been fixed and should be included in the next update to Android. I say "should" because things can change at the last minute. Keep an eye on your notification bar for a system update."
source: http://www.google.com/support/forum/p/android/thread?tid=7a22ebb69da2b253&hl=en#all
Click to expand...
Click to collapse
I followed the link, but didn't see the response you quoted...?
flarbear said:
I followed the link, but didn't see the response you quoted...?
Click to expand...
Click to collapse
That's because it was removed by Google. I read it this afternoon. Is not there any longer. The Google employee was "Tommy" and you can't find his posts any more.
You can read other people's response to his post but his don't show up any longer.
well, that post is very hopeful. i suppose all we can do is hope for the best. i dont know if google deleting the post is good or bad though
I suppose the rumors weren't true, then?
halorin said:
I suppose the rumors weren't true, then?
Click to expand...
Click to collapse
I saw someone on here posting a quote about the multi-touch fix... lemme find it
by Paul22000:
Also "A scale gesture detector API provides improved definition of multi-touch events."
I wonder if that means the N1's multitouch axes will be fixed for gaming!
halorin said:
I suppose the rumors weren't true, then?
Click to expand...
Click to collapse
since nobody has froyo yet, we dont know if it was fixed or not. i really hope they did though.
Thanks for the responses, guys. I guess in hindsight it might have been good to leave out any negative things in such a positive conference.
But still, some mention would have been comforting.
halorin said:
Thanks for the responses, guys. I guess in hindsight it might have been good to leave out any negative things in such a positive conference.
But still, some mention would have been comforting.
Click to expand...
Click to collapse
I feel the same way halorin. It's natural to voice displeasure over something important missed in an update (I would have loved 360* rotation, colored trackball, fm radio, etc) but I know your happy about the update when it does occur and a great guy to have on the forum
All progress is still progress toward perfection, no matter how small.
Thing is, they were just demoing the OS, not device specific things like the N1's trackball & whether it has working FM etc.
Very valid point, Rusty.
Yup, each device will have their own seperate updates with device exclusive things.
Rusty! said:
Thing is, they were just demoing the OS, not device specific things like the N1's trackball & whether it has working FM etc.
Click to expand...
Click to collapse
*in Kramer voice* ........ you just blew my mind...
ap3604 said:
I saw someone on here posting a quote about the multi-touch fix... lemme find it
by Paul22000:
Also "A scale gesture detector API provides improved definition of multi-touch events."
I wonder if that means the N1's multitouch axes will be fixed for gaming!
Click to expand...
Click to collapse
That quote is from the highlights web page:
http://developer.android.com/sdk/android-2.2-highlights.html
The axis problem can never be fixed 100% because the hardware doesn't report enough info to do it for all cases, but currently it is pretty bad and I think better drivers/software could get it close. I believe that Cyanogen's ROMs have had some tweaks that have greatly improved its responsiveness for some time now so perhaps the Android engineers adopted similar fixes. It will hopefully get good enough over time that you'd have to know exactly how the sensors work and deliberately try to fool the drivers in order to get it confused.
I tested a nexus one on froyo today at google i/o, some things that were absent, colored track ball, touch screen wise they didn't have any multi touch analysis program installed, but just pinching around I don't detect any notable differences, so i'm guessing no to those 2 features on nexus, at least on their current build
I was also at I/O and while I did play with a few different Nexus Ones that were loaded with FroYo, I was unable to determine if any screen fixes were applied.
I asked a few times and each time I was politely told that they could not talk about anything that was not already made public (fair enough btw).
However, pinching and zooming on maps seemed to be smoother (not sure if it just my impression or some actual change) and it seemed to respond overall to my finger movements more smoothly.
Also, some games that I demoed on a few different Nexus Ones did employ finger gestures and those games functioned flawlessly from the touch perspective.
I am not sure that translates into any real fix or just my biases, but I am putting it out here for whatever it is worth.
Dan
dan1431 said:
I was also at I/O and while I did play with a few different Nexus Ones that were loaded with FroYo...
Click to expand...
Click to collapse
Did you notice if there was 360 rotation? ie could you flip it from 12 to 3 O'Clock clockwise and get it to rotate to landscape when in a rotating app like Maps?
logger said:
Did you notice if there was 360 rotation? ie could you flip it from 12 to 3 O'Clock clockwise and get it to rotate to landscape when in a rotating app like Maps?
Click to expand...
Click to collapse
I hate to admit this, but I did not even think about testing that feature.
Dan
Dorick said:
I tested a nexus one on froyo today at google i/o, some things that were absent, colored track ball, touch screen wise they didn't have any multi touch analysis program installed, but just pinching around I don't detect any notable differences, so i'm guessing no to those 2 features on nexus, at least on their current build
Click to expand...
Click to collapse
Dorick, by any chance have you noticed wifi-n connection?
I'm almost certain from the API improvement and UI modifications listed on the Android SDK site that we have a software fix for the crazy multitouch issue.
Having said that, it means the screen won't go crazy when the paths "swap". But, it's still limited to two touchpoints and not 10 like the 3000 series screen.
A fix is a fix though. =)
Personally if the have fixed up pinch zooming somewhat and made it smoother that will cover me 99% of the way as I use the device so that will be pretty much a fix assuming we actually see it in the official N1 rom.
Anyone notice the compass as well as other sensors respond SUPER SLOW. Fire up skymaps and find mars. Go on ill wait... Broken GPS is getting all the talk.
-------------------------------------
Sent via the XDA Tapatalk App
There's an app called "Android Sensor Data" that can calibrate the accelerometer, but you have to run it at every boot. It doesn't fix the compass, which I expect us just broken.
The future looks so... Vibrant
Yup, it was one of the first things I noticed about the phone. The compas is definitely either broken or just not very good.
Sent from my SGH-T959 using XDA App
Its not only sky maps but also layer as well, once you stop moving the phone it takes a good 10 to 15 secs to position itself, very laggy, just patiently waiting for the fix now -_-"
Sent from my SGH-T959 using XDA App
one would think with Samsung preinstalling Layar on the phone the compass would work without a hitch... im hoping its a software issue not updating as frequent.
Based on how a compass works, (magnetism) I would hazard a guess that there is NO software fix. Buy a compass. If it doesn't work, it will never work. Software can't fix a bad magnet. I COULD be wrong...I HOPE I'm wrong...I DOUBT I'm wrong.
Magnets are not software. ):
The future looks so... Vibrant
I asked T-mobile if there would be a fix for the compass along with the GPS on Twitter. This was their reply:
"TMobile_USA: @fjohnette That's what is believed causing the GPS problem so its possible we will keep you updated. ^SG"
--http://www.twitter.com/TMobile_USA/status/20225466968
Sent from my Samsung Vibrant using the XDA app
fragimar said:
"TMobile_USA: @fjohnette That's what is believed causing the GPS problem so its possible we will keep you updated. ^SG"
Click to expand...
Click to collapse
So this means it's possible that they will NOT keep you updated??
Anyway, I think we now have the word of every t-mobile CS rep and tech support person and most (if not all) don't really have any idea. I guess it's worth the effort to keep pestering. It'd sure be more comforting to have an official response.
bryon13 said:
Based on how a compass works, (magnetism) I would hazard a guess that there is NO software fix. Buy a compass. If it doesn't work, it will never work. Software can't fix a bad magnet. I COULD be wrong...I HOPE I'm wrong...I DOUBT I'm wrong.
Magnets are not software. ):
The future looks so... Vibrant
Click to expand...
Click to collapse
You are completely correct in how a compass works... Basic magnetism... However. Just because our compass doesn't work doesn't mean the magnet bit isn't detecting north as it should. It could easily be that the other sensors that detect which way that magnet is oriented are reporting incorrect data, which is possibly fixable via firmware update. Or that the android itself is doing something wrong with that data, or any combination of the above. And these possible causes are far from exhaustive, just a few possibilities off the top of my head.
Sent from my Vibrant using the XDA app.
Typos, incorrect words, gibberish, and other nonsense brought to you courtesy of Swype.
bryon13 said:
Based on how a compass works, (magnetism) I would hazard a guess that there is NO software fix. Buy a compass. If it doesn't work, it will never work. Software can't fix a bad magnet. I COULD be wrong...I HOPE I'm wrong...I DOUBT I'm wrong.
Magnets are not software. ):
The future looks so... Vibrant
Click to expand...
Click to collapse
Yep, but every single thing about how that data is collected, interpreted, and passed on to the operating system is software, not to mention the interaction with the accelerometer sensors as Arr mentioned. Lots of potential points of failure here that have everything to do with software. Fingers crossed that it's not just a borked magnetometer.
Very true. As I said, I REALLY REALLY HOPE they can fix it... I'm just worried that we're going to be stuck with broken hardware. I'll never buy a phone on launch-day again...
The future looks so... Vibrant
bryon13 said:
Very true. As I said, I REALLY REALLY HOPE they can fix it... I'm just worried that we're going to be stuck with broken hardware. I'll never buy a phone on launch-day again...
Click to expand...
Click to collapse
this is my fear as well. It bugs the **** out of me to see people all over the forums violently defending samsung and saying with absolute certainty that a firmware fix is coming.
How do they know it can be fixed with firmware? I'm not saying that it's impossible, I'll be the first to admit I have no idea how the compass actually works, but to post saying that it will be fixed is so unbelievably stupid and irresponsible that I can only attribute it to buyers remorse manifesting itself as post-purchase rationalization.
Too many idiots to have any sort of productive discussion anywhere.
hollabax said:
this is my fear as well. It bugs the **** out of me to see people all over the forums violently defending samsung and saying with absolute certainty that a firmware fix is coming.
How do they know it can be fixed with firmware? I'm not saying that it's impossible, I'll be the first to admit I have no idea how the compass actually works, but to post saying that it will be fixed is so unbelievably stupid and irresponsible that I can only attribute it to buyers remorse manifesting itself as post-purchase rationalization.
Too many idiots to have any sort of productive discussion anywhere.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=7252169&postcount=21
The compass is definitely the one thing that annoys me about this phone. I really like Google Sky Maps and 3D compass and right now they are worthless.
DaMaDo said:
The compass is definitely the one thing that annoys me about this phone. I really like Google Sky Maps and 3D compass and right now they are worthless.
Click to expand...
Click to collapse
Agreed. The GPS issues are getting so much attention that the borked compass is falling by the wayside. I actually use the compass, so this is really annoying.
you guys are brave
I returned the phone after a few days and decided to wait for a fix.
When/if the fix comes, I can easily buy the phone again.
To keep the phone is the same thing as keeping you anxiety level high, waiting for a fix, checking every board twice a day.
Is it worth it?
DaMaDo said:
The compass is definitely the one thing that annoys me about this phone. I really like Google Sky Maps and 3D compass and right now they are worthless.
Click to expand...
Click to collapse
Google Sky maps works fine for me. It does lag slightly when rotating, (which seems to match what others are saying about compass lag), but i don't see how it's worthless. It's dead on for me.
Have you tried Google Street View (Compass Mode) or Yelp's 'Monocle' / Layar?
The compass will sometimes point to magnetic North. But most times, it spins around wildly, or simply points to the wrong direction and does not update correctly.
Morbo66 said:
Google Sky maps works fine for me. It does lag slightly when rotating, (which seems to match what others are saying about compass lag), but i don't see how it's worthless. It's dead on for me.
Click to expand...
Click to collapse
A friend and I bought our phones on the same day. Date on the stickers on the box (which I assume is a build date) is 7/17 on both of them. Side-by-side, Google Sky works perfectly for him, and doesn't work at all for me.
My compass points south no matter what orientation the phone is in, or what direction I face. Sometimes if I just stand still for a very long time, it'll slowly sort of drift in one direction or another, but I haven't had the patience to just wait and see whether it ever actually aligns with where I'm facing or if it's just random variation.
Check my little video on youtube about this issue demonstrating how slow the compass reacts.
YouTube, search for: SvAJrR5Gmy0
or "Samsung Vibrant Compass Issues"
still won't let me post links yet....
I did end up getting the other phone working instead of pointing in only one direction. I factory data reset the phone and tried agan and it started pointing in the correct direction at least, still very slow.
I also suggest looking at sensor data to see how your phone performs:
*#*#1472365#*#* >> Test Application >> Show Sensor data
Has anyone noticed this? Wherever there's something to scroll, web pages, menus etc., the motion is sort of stuttering as long as you keep your finger on the screen. When you release your finger and "throw" the page, it goes smooth. This makes me think that it's not a graphic performance issue, but it's more like if the resolution of the capacitive touch screen was lower than the actual display. I hope I'm wrong and it's software related...
Software related, doesn't always do this.
Edit-
On second thought I am not sure, sometimes it does this really badly and other times it is completely smooth. If we didn't have full resolution touch you would notice it on a multi touch test app.
Sent from my GT-I9000 using XDA App
I think I have found the cause.
Cpu scaling!
Lock setcpu to 1 ghz and it is much smoother.
What is happening is the cpu speed keeps throttling and jumping back to full speed causing problems
Sent from my GT-I9000 using XDA App
Actually...still unsure...ideas anyone?
Sent from my GT-I9000 using XDA App
"Problems" with CPU speed jumping up and down? Those are not problems but a design decision (jury is still out on whether the implementation is done right) to save energy.
Of course you can crank everything up to the max and never put peripherals or the CPU to sleep, but please don't start complaining when your battery runs flat before the day is done.
They set the ramp down cpu speed timer far too short. This can be modded in a kernel anyway.
Using a multi touch test we have at minimum 600x300 touch resolution, way more then enough to have lag free scrolling.
There's an acer android phone out with only about 32x 24 touch resolution. They manage
Sent from my GT-I9000 using XDA App
I don't think it's related. I'm experiencing this even with the cpu locked in performance mode. On the other hand, using a multitouch test app, I was able to move a pointer pixel by pixel at what seemed to be the screen's full resolution, so touch res is not the cause.
It's quite annoying cause even if you want to launch a fast scroll of, say, your contact list, you get that initial ugly small stutter... when browsing the internet this ruins the experience even more, since you are likely to keep your fingertip on the screen more.
Dunno about you guys but uninstalling Gesture Search by Google fixed it for me.
Never had that on my phone...
Bump... am I the only one bothered by this?
Am I?...
Rizlo said:
Am I?...
Click to expand...
Click to collapse
Could be, I had a HTC HD2 and it suffered from that problem alot. numerous videos have been posted on youtube because of it as well.
One possible way of minimizing the problem is to electrically discharge your screen, by putting an electric conductor, such as metal on it to remove and negative/postive ions still hanging around. Read that up somewhere and it somewhat helped my HD2.
Personally i have only experienced once on my Sgs and have not been able to replicate it since.
If you have big fingers that could also be a problem as the touch sensor can't decide on where to locate your finger...
Thank you for your answer! The electrical conductor you mentioned should go somewhere to discharge though... I can't walk around with a ground wire hanging from my phone all the time Plus, I really believe it's software. I know it always goes there but... iPhones have similar technology but they always scroll smooth. maybe it's interpolation we're missing here.
Btw I have particularly small hands!
Discharging it only has to be done only when the problem seems to be worsening. just try not to place your entire thumb on it but rather use the tips of yours fingers, that way it doesnt jerk.
I have to say this problem is pretty consistent, hence not worsening (or improving) whatsoever in any circumstances. It's just not fluid, ah my Touch HD used to be, but that was because of poor GPU (driver); we know that can't possibly be the case here, and as a matter of fact, regardless of load, stuff in the background etc, it's there all the time.
But as soon as you release the fingertip, the "inertial" part of the scrolling just goes as smooth as possible.
So I'd dismiss the electrostatic explanation, it seems like it was a non-interpolated low touch resolution... except that it's not...
Hi Folks, I have noticed the same problem running eclair 2.1 with Ryan's one click lag fix applied (the lag fix did speed it up quite a bit too!). It seems to do it after coming out of 'sleep' mode i.e when I wake it up from blank 'screen saver'. After a few scrolls or taps it starts to smoothen out a bit, but still not as I would like it to be.... Just my observations and sorry I can't offer up any Solutions... Any word if 2.2 update will make things better? Also, does anyone know when the update will hit Australia?
Welcome to android world, iphone users.
The world where not everything is super-smooth.
Actually it might be related to smoothing of touch input. Btw my scrolling is quite ok, but I come from Sybian world, world of lag.
xan said:
Welcome to android world, iphone users.
The world where not everything is super-smooth.
Actually it might be related to smoothing of touch input. Btw my scrolling is quite ok, but I come from Sybian world, world of lag.
Click to expand...
Click to collapse
'smoothing of touch input'? could you please expand on this?
BTW - I Never owned an iFone, and don't really go for it's comunistic ways... (although some people take comfort in it! )
Hm, touchscreen sends raw data to driver (noisy, with peaks) to driver. Driver cleans and interprets them.. (unless its done in TS firmware)
I think that more cleaning and smoothing at this stage would result in smother scrolling, but not-so-precise tracking (when drawing, etc).
I'm just speculating here, because I have no real knowledge about this.
OK... Although it seems like there is a delay in reloading to short term memory when coming out of hibernation? Would this sound like a place to start looking? if so, anyone have any ideas on how to manipulate this function?
I just bought a Nexus 4, and am waiting for it to arrive. I just read about this dreaded pinch zoom delay (i.e. delay when zooming). Is this still an issue with the latest ROMs/kernels out there? I can see this causing me a lot of frustration if not fixed.
I've already searched, and the threads I've found are all either old or have not been completely answered.
Thanks!
I have no problem with zooming, and I bet that you won't too. Just wait for the phone, and don't read all the bad stuff. It won't do you any good. There are some rare bugs, but most users don't have them.
I don't have any delay in zooming issue either.
filthykid said:
I don't have any delay in zooming issue either.
Click to expand...
Click to collapse
I doubt it
Sent from my Nexus⁴
There is no zoom delay, its a dead zone. You have to move your fingers a certain amount before it detects it as a pinch to zoom or zoom out. I think it is intentional. Try doing it extremely slow, you'll see what I mean.
bustem said:
I doubt it
Sent from my Nexus⁴
Click to expand...
Click to collapse
You shouldn't
username8611 said:
There is no zoom delay, its a dead zone. You have to move your fingers a certain amount before it detects it as a pinch to zoom or zoom out. I think it is intentional. Try doing it extremely slow, you'll see what I mean.
Click to expand...
Click to collapse
You've got it right. It's DEFINITELY present and those who don't see it either just innocently don't notice it or are denying it. Every single video review of the N4 I've seen has pointed out this issue (or feature, if you like) and I can very clearly see it on my device as well. OP, I'm not saying you should care about it (I don't even notice it any more) but it does exist.
I thought it was established long ago that the culprit was 'chrome' browser.. i just checked it in AOSP browser i cant seem to see any delay.
Nigeldg said:
You've got it right. It's DEFINITELY present and those who don't see it either just innocently don't notice it or are denying it. Every single video review of the N4 I've seen has pointed out this issue (or feature, if you like) and I can very clearly see it on my device as well. OP, I'm not saying you should care about it (I don't even notice it any more) but it does exist.
Click to expand...
Click to collapse
yeah its definitely there, but it is not lag, not even kind of, or delay or anything. it doesn't really bother me, i dont know why some people get so worked about it. what would happen if they cranked the dead zone down to zero... everyone would complain that its impossible to fine tune how close and far they are trying to zoom, or they keep zooming in and out on accident lol.
Yup, defiantly by design. If you start with your fingers already apart some, there is no delay at all.
Sent from my Nexus 4 using Tapatalk 4 Beta
Hate this deadzone!
username8611 said:
yeah its definitely there, but it is not lag, not even kind of, or delay or anything. it doesn't really bother me, i dont know why some people get so worked about it. what would happen if they cranked the dead zone down to zero... everyone would complain that its impossible to fine tune how close and far they are trying to zoom, or they keep zooming in and out on accident lol.
Click to expand...
Click to collapse
the iphone don't have it so does my sister's xtreamer joyz(newman n2) with android 4.1.1 no one ever complained about hard fine tuning zoom!
i have this dreadfull deadzone too on my htc one x running aosp based 4.3(cm10.2) while on my sister's phone its a pleasent user experience.
note: THIS "LAG" IS NOT PRESENT IN FIREFOX!(no deadzone at all)
so definatly its an andorid gallery/gmail/browser(and any relying software like g+ whatsapp etc...) thingy.
this minimal distance deadzone is coming into notice when you are used to start zooming with fingers close together.
aka how zoom should be.
any way of trimming that distance out?