Related
Hello all,
As developers start to use firmware 1.5 I have updated the GPS status app to work with the new firmware.
The good news is that I no longer have to use internal APIs. Some features have been removed or changed:
- Screen orientation settig has been removed as it can be configured globally in 1.5
- Magnetic declination setting is removed too, but the good news is that declination is now automatically calculated (without internet access) based on a geomagnetic model. The model also gives the absolute value of the magnetc field at your location which is also displayed.
- finally: the GPS is not automatically turned on, because average programs can no longer turn on the GPS (it is possible only by using the system settings program) (GPS switch appliction will no longer work)
Have fun, comments are welcome.
Rudolf
If you start the app without enabling GPS first, it crashes right away.
Karolis said:
If you start the app without enabling GPS first, it crashes right away.
Click to expand...
Click to collapse
Thanks, noted the issue.
Crash on 5.0.1Gr3.
I switch GPS ON before launching.
It shows the first screen, and "force close" ...
i hope this works because GPStatus is my favorite app.
g force registers at 1.00 as default... it doesnt seem to be as accurate as gps status was on 1.1, or its more sensitive i dunno.
without moving, my heading goes frim 78-81deg.
joeydsmith said:
g force registers at 1.00 as default... it doesnt seem to be as accurate as gps status was on 1.1, or its more sensitive i dunno.
Click to expand...
Click to collapse
Right, I've detected this too. It seems that the new formware is doing much less filtering than the 1.1 version. This gives a faster response with much more errors. Unfortunately I cannot do anything about it at the moment.
Having acceleration at 1.0 g is correct (at least GPS Stus 1.5 works the same way) as we are standing on the surface of the earth Thats a different stiry whether it is correct to call it "acceleration" for ordinary people (I know Einstein would not mind it )
lol yeah cant u jsut make it x-1? or sumthing lol, but yeah you are right we exipreince 1 g all the time.
joeydsmith said:
lol yeah cant u jsut make it x-1? or sumthing lol, but yeah you are right we exipreince 1 g all the time.
Click to expand...
Click to collapse
Version 1.4 did that, but that was not correct.
The problem is that acceleration is a vector not a scalar. I.e. I have to add/substract vectors not scalars...
example:
- If you would accelerate horizontally with 1g and in addition the earth has also 1g gravity, you would feel (and your phone would measure) approximately 1.41g (sqrt(1g^2+1g^2))
- on the other hand if you would accelerate vertically (upwards) with 1g, your body would feel 2g
The real problem: it is not possible to measure the direction of your acceleration (and according to Einstein its not even distinguishable from the gravity at all).
Maybe I will assume that the acceleration is horizontal (which is true for most ordinary people, moving on the surface of Earth). The rest (astronauts during launch, parachute jumpers) will get slightly wrong results, but I'm hoping they will have better equipment than relying on their G1
Rudolf i am a fan of your gpsstatus.apk and since i load the 1.5 in my dev phone i wanting for your upgrade. really i do not understand what happens with this firmware but i think that the compass do not work anyway and all operations that in the past (and that work in my g1-not updated- phone) put to work the compass now is not responding...i have my compass pointing near the east!!!...
may be (that you says) is the automatic magnetic declination are actuating but the pointing i shure that is a mistake...
i am very fustrated and worried if this issue and if you can help me to understand this, it would be very appreciated...
meanwhile i thanks so much your work and hope gpsstaus.apk go to work in the future at least good that we have working in the past...
best regards and electronics greetings from spain
I noticed a small problem with the magnetic declination, the mag declination here is - 6° 39' west according to ngdc.noaa.gov, anyway when the compass moves slightly west from north it shows -1 to -6 then jumps to 350...
rhornig said:
Right, I've detected this too. It seems that the new formware is doing much less filtering than the 1.1 version. This gives a faster response with much more errors. Unfortunately I cannot do anything about it at the moment.
Click to expand...
Click to collapse
Running average of the last 5 results would smooth it out, but yea less responsive, if you hooked it into the accelerometer to notice a suden change to reset the smoothing should take care of responsiveness...
unicornio said:
Rudolf i am a fan of your gpsstatus.apk and since i load the 1.5 in my dev phone i wanting for your upgrade. really i do not understand what happens with this firmware but i think that the compass do not work anyway and all operations that in the past (and that work in my g1-not updated- phone) put to work the compass now is not responding...i have my compass pointing near the east!!!...
Click to expand...
Click to collapse
That sounds like the compass is being influnced by a magnetic field, try waving the phone in a figure 8 to get it to reset itself.
koxx said:
Crash on 5.0.1Gr3.
I switch GPS ON before launching.
It shows the first screen, and "force close" ...
Click to expand...
Click to collapse
Thanks. Fixed (hopefully) and updated the first post.
delta_foxtrot2 said:
I noticed a small problem with the magnetic declination, the mag declination here is - 6° 39' west according to ngdc.noaa.gov, anyway when the compass moves slightly west from north it shows -1 to -6 then jumps to 350...
Click to expand...
Click to collapse
Yepp. Thats a bug. Thanks for finding I will fix it for the next release.
unicornio said:
Rudolf i am a fan of your gpsstatus.apk and since i load the 1.5 in my dev phone i wanting for your upgrade. really i do not understand what happens with this firmware but i think that the compass do not work anyway and all operations that in the past (and that work in my g1-not updated- phone) put to work the compass now is not responding...i have my compass pointing near the east!!!...
may be (that you says) is the automatic magnetic declination are actuating but the pointing i shure that is a mistake...
i am very fustrated and worried if this issue and if you can help me to understand this, it would be very appreciated...
Click to expand...
Click to collapse
After firmware upgrades or if you experience strong magnetic field the internal compass must be recalibrated. Check the heading reading in the upper left corner. If it contains ?, ?? or ??? after the number, then your compass is inaccurate and must be recalibrated.
As alsready mentioned, you should draw big 8s in the air with your phone for about a minute. If everything goes well, the ? marks should go away and your compass should be much more accurate.
rhornig said:
Thanks. Fixed (hopefully) and updated the first post.
Click to expand...
Click to collapse
It works now ! thank you !!!
delta_foxtrot2 said:
Running average of the last 5 results would smooth it out, but yea less responsive, if you hooked it into the accelerometer to notice a suden change to reset the smoothing should take care of responsiveness...
Click to expand...
Click to collapse
Thanks. Good idea, however the android framework itself should do the filtering (i'm already using the slowest possible update frequency which means the highest filtering). I will wait until the final 1.5 firmware comes out, and then revisit the issue.
Yay. It works. The compass does look a little faster
Does anyone have a solution for phantom taps on your NC?
I'm on my 3rd Nook Color when I pick up the replacement unit this afternoon.
My general issues are phantom taps - or the NC doing things I don't want it to. So far a very poor experience when typing, turning a page in a book, or even just navigating the ui. The whole issue may be me, it happens regardless if I am plugged in or not. I keep a very clean screen so there is very to little gunk.
I do have sweaty palms on occasion but not out of the ordinary. I have other touch devices that have never given me this issue. If anything I think the screen is overly sensitive - hardware or software issue?
Nope it's not just you. Mine has a multitude of issues with the touchscreen...
Essentially I cannot use the touchscreen when the device is plugged into stock charger/cable as wherever I put my finger, a random touch appears somewhere on the x-axis near my finger.
It seems that the device does not like changes in temperature or humidity either when it is unplugged. Using my tablet while cold was impossible, and likewise while it had been warm.
I'm on my second tablet from Best Buy-- the first one had dead pixels galore (enough to make the best buy rep say "dang!"), and now this one has a bad touchscreen and hard to press power button.
However: I purchased one of these for my mother a few days before mine at Barnes and Noble, and it has no issues whatsoever... at least not yet.
I've come to the conclusion that this hardware is quite beta, but I'm willing to give them a chance since it is the best bang for the buck, even if I have to go through a couple of returns... it's honestly almost worth the time for me since a tablet is so valuable for schoolwork.
Fortunately mine does not do this. I think maybe for those that are having this issue it may be able to be fixed in a firmware update.
My EVO had extremely similar problems when it first came out with the touchscreen and not being able to use the dropdown menu while the device wasn't grounded. After a firmware update the phone was great with touch sensitivity.
my first one did this also. so far the second is doing fine, but the first didn't have any problems till the 13th day of owning it.
i'm hoping it's just an issue that can be fixed via software - maybe someone put an incorrect voltage input somewhere.
I was having the same issues. I bought a screen protector and that seemed to solve it. So far, it's been working fine.
I noticed the screen protector stabilized the touchscreen a lot. Before I seem to have a problem finding the sweet spot for a touch. Now it seems better.
However, my phantom pinky is always touching something while I am trying to navigate. As long I only get one finger near the screen, it's fine.
Mine came from B&N.
The only other issue I have is the magnetic clasp in the cover seems to throw the internal compass/magnetometer off a lot.
Awats said:
The only other issue I have is the magnetic clasp in the cover seems to throw the internal compass/magnetometer off a lot.
Click to expand...
Click to collapse
Considering the Nook has neither I think you are okay.
khaytsus said:
Considering the Nook has neither I think you are okay.
Click to expand...
Click to collapse
Then how is it managing to correctly position the screen with Google Sky? Is it just spooky smart?
Mine only has problem when screen gets dirty. Try a screen protector or use gloves.
is there really a compass in this thing? I just assumed there wasn't. if there is I'm buying another tomorrow!
Screen protector helps to solve my problem.
Are you seeing more issues right after cleaning the screen? I see issues then and I think it is because I an using some moisture on the cloth. If I just dust it lightly with a dry cloth and live with a few finger prints there seem to be less of an issue.
Awats said:
Then how is it managing to correctly position the screen with Google Sky? Is it just spooky smart?
Click to expand...
Click to collapse
Wifi location services provided by Google from data collection by Street Cars or by Location Services on Android phones.
iolinux333 said:
is there really a compass in this thing? I just assumed there wasn't. if there is I'm buying another tomorrow!
Click to expand...
Click to collapse
....no
khaytsus said:
Wifi location services provided by Google from data collection by Street Cars or by Location Services on Android phones.
....no
Click to expand...
Click to collapse
Oh well, it could be worse although I don't see how Google data can tell which direction I am facing.
Thanks dad!
Awats said:
Oh well, it could be worse although I don't see how Google data can tell which direction I am facing.
Thanks dad!
Click to expand...
Click to collapse
Nor can your Nook Colour.. Using something like TetherGPS would have some heading information, but the NC itself without help would not.
It might show 0, dunno there. Maps for me just shows a dot, if yours is showing different, that'd be... interesting.
For S&G I tried "Compass", it of course FC's immediately like almost all apps that try to use the GPS. Enabled TetherGPS (with no server, just the client) and it ran, but of course no data, no heading, etc.
Is this occuring when the nook is plugged in? sometimes the charger can cause phatom touches with the touchscreen. Cleaning the screen and being on a stable ROM usually gets rid of that problem.
If only I weren't so stupid ...
khaytsus said:
Nor can your Nook Colour.. Using something like TetherGPS would have some heading information, but the NC itself without help would not.
It might show 0, dunno there. Maps for me just shows a dot, if yours is showing different, that'd be... interesting.
For S&G I tried "Compass", it of course FC's immediately like almost all apps that try to use the GPS. Enabled TetherGPS (with no server, just the client) and it ran, but of course no data, no heading, etc.
Click to expand...
Click to collapse
LOL! Ok, I sat down with it and played for a bit. It appears some tilt sensor is handling the up and down tilt. If you raise the screen over your head, it shows those stars and if you tilt it down, I see what is below the horizon. That is pretty consistent. But it's also "simulating" a compass inadvertently.
By that I mean that if I happen to turn it on facing north, it appears to track as you turn in a circle but it's really just me tilting it and it's rotating he view. If you do it enough it has no clue the direction it's facing.
I'm just glad I figured this out before I got lost in the Amazon.
Just got mine plugged it in and unplugged and within stew minutes phantom touches couldn't even reboot it im on cyanogen mod 7
Sent from my SCH-I500 using XDA Premium App
Nook Screen Recalibrate
You guys can try my app from the market
assid2 said:
You guys can try my app from the market
Click to expand...
Click to collapse
Wow, it seems to have improved the accuracy! I need to play with it more to be sure.
Hey guys,
Thought I'd post this here and keep you guys updated on further developments.
I live in the Netherlands and bought a 32GB version at Dixons at the 13th of November 2012
I had found the touchscreen a bit unresponsive sometimes in the past.
But couldn't really find out why it was acting up. I finally isolated the issue.
It is exactly the same as this guys vid:
(Thanks for the vid injahnet)
Together with a little backlight bleeding, I decided to send for repair.
(The problem persisted after a factory reset, no other apps were open when testing.)
I went back to Dixons and showed the problem to the Dixons dude.
He acknowledged there was an issue and sent it for repairs or replacement.
Due to the holidays this can take some time. Maybe even next year
I was about to open my tablet for a look inside one of these days, boy am I glad I didn't do that yet
Anyway to get a good view on this issue globally, are there more people that have the same issue?
You could go to: Settings > Developer options > and then under "Input" you can enable Show touches. and try to to the same procedure as in the vid. (Thanks Peterk-1)
Or you could test with MultiTouchTester like Injahnet.
The weird thing is, my dad's N7 16GB does the same.
Update 17-12-2012: Please do not test while plugged in as the device will be grounded and the issue will not occur. (Thanks dad)
Feedback is really appreciated!
Please vote in the poll above!
Cheers,
Daan
I have zero problems with multitouch while using my Nexus 7. Working just fine, but you must disable any apps which interfere with gestures or it'll steal events.
Can't say I've ever used multitouch with the N7 laying on a random object however.
But sure, send it in for repair......... I'll keep using mine.
If anyone thinks they have multi touch problems then loading an app isn't required. Just go into Developer Options and under Input you have two options to display touch and track detail.
peterk-1 said:
If anyone thinks they have multi touch problems then loading an app isn't required. Just go into Developer Options and under Input you have two options to display touch and track detail.
Click to expand...
Click to collapse
Nice one. I'll add that.
khaytsus said:
I have zero problems with multitouch while using my Nexus 7. Working just fine, but you must disable any apps which interfere with gestures or it'll steal events.
Can't say I've ever used multitouch with the N7 laying on a random object however.
But sure, send it in for repair......... I'll keep using mine.
Click to expand...
Click to collapse
I've done a factory reset before I tested No apps are open except MultiTouchTester
It's in for repairs
Well... Over 200 views. And only 4 votes, which includes mine
Community feedback is failing hard.
Anyway, I'll keep you guys posted on the repaired Nexus.
At the moment of writing we know that three people are having this issue.
I know someone else with a nexus I'll check if he has the issue too.
Cheers,
Daan
Yes, i have this problem. And only while device is laying on the table.
Wow, this is bizarre, thanks for pointing it out. I can confirm it happens when it's laying on my pillow, and doesn't when I'm holding it.
Thanks for the vote guys.
By the way, it seems obvious that the Nexus should not be plugged in while testing.
However I cannot test this 'cause mine is at the shop
Would anyone be willing to test?
I'll add that in the original post (+ a mention of your name and a thank you of course))
Cheers,
Daan
Mine was unplugged while testing.
Sent from my Nexus 7 using Tapatalk 2
if the two touch-points got the same X or Y coordinate my nex7 does only detect one of them. i don't think this is an issue.
herrrevo said:
if the two touch-points got the same X or Y coordinate my nex7 does only detect one of them. i don't think this is an issue.
Click to expand...
Click to collapse
However, zooming in Google maps for example will become quite difficult
Anyone try and see if taping the ground pin on the wifi antenna fixes the issue? This seams like a grounding problem.
ionstorm66 said:
Anyone try and see if taping the ground pin on the wifi antenna fixes the issue? This seams like a grounding problem.
Click to expand...
Click to collapse
Exactly! I was also thinking of this.
Do people who have this issue also have the flickering issue!?
ecoviws buttress
Just an FYI, I installed CM 10.1 with Trinty Seven. Now I get 10 touches on pretty much any surface.
I don't have a multitouch issue, but I do have an entire band on my screen which has stopped responding to touch at times. It all started when I let my tab shut down due to low battery. Initially, the Nexus 7 neither charged (when put on charging, obviously), nor did it boot up. After trying for several hours, somehow it started charging. And since then, sometimes certain areas of my touchscreen become unresponsive to touch. Since the band which is unresponsive is towards the upper part of the screen, using notifications becomes completely impossible. It keeps 'snapping back up' when I try to pull it down, cos while I am pulling it down, the notification tray encounters an unresponsive area, so it just goes back up. Called up Google and they will be sending a replacement device. All I am afraid about is that I have an 8gb version, and they would be sending an 8gb as well, so I hope it isn't refurbished or something, as Asus has stopped making the 8gig model.
I'm having an issue where the screen, ( mostly in a webpage or document,) starts moving up and down and zooming in and out without my input.
Sent from my Nexus 7 using xda app-developers app
Just tested this out and yes, my device is doing it too. Interesting. No other issues like screen flicker (except the auto brightness bug in 4.2). My n7 is c9O
DaanJordaan said:
Well... Over 200 views. And only 4 votes, which includes mine
Community feedback is failing hard.
Anyway, I'll keep you guys posted on the repaired Nexus.
At the moment of writing we know that three people are having this issue.
I know someone else with a nexus I'll check if he has the issue too.
Cheers,
Daan
Click to expand...
Click to collapse
community feedback is not failing hard, more like you're just starting a new thread without bothering to search if issue/topic already exist.
this isn't new and there is no fix, that is just how the touchscreen function. the N7 isn't the only device to have this.
dilldoe said:
community feedback is not failing hard, more like you're just starting a new thread without bothering to search if issue/topic already exist.
this isn't new and there is no fix, that is just how the touchscreen function. the N7 isn't the only device to have this.
Click to expand...
Click to collapse
Don't feed the trolls!
Must... not... feed... aaargh....
You are kinda missing the point of this thread.
It is to see how many people have this issue.
There is no thread capturing that in an easy way unless you want to count every post.
Now please tell your brain to start functioning again and leave this thread alone if you have nothing to add.
Asus Google Nexus 7 32GB touch death zone
Hi DaanJordaan,
Found out that my brand new N7 seems to have a similar "no touch zone" issue; an area the size of my little finger on the left lower part of my screen does not seem to react to touch! It interferes with typing the keyboard in portrait mode (no keyboard problems in up-side-down portrait mode).
When I use the Easylabs Multi Touch test I can see the dot changing color when I move over this area, doesn't happen anywhere else on the screen..
Using the developer tools (turning on the two options that allows to show touch/leave a trail of touch) it becomes even more clear that this area does not react to touch! I can "paint" lines around the "no touch zone" (it actually splits into 2 touch areas using one finger around the "death spot"), and the "no touch zone" reveals itself by not showing any trail/history line of touch..
Oh yes, and it does not matter if I lay the N7 on the table, or hold it in my hand, the issue is always there.
Therefore I returned the N7 back to the MediaMarkt, and they will send it in for repairs...
I've got a bad feeling about this | - )
I am curious to hear about experiences with your N7, once you have it back!
I'll report mine here, in three weeks or so (that's the outlook...).
Cheers!
NeverMind
I have only had my tf701 a day but Ive noticed sometimes when docked to the keyboard if you dont touch the mouse for a few seconds sometimes when you move the mouse again it will make a flicker around where the mouse is located, it doesnt always do it, just wondering if anyone has noticed this or is it a fault with my tablet?
I can live with it, but if there is a known fix it would be nice to sort it.
Thank You
After a bit of messing about I think it only does it with live wallpapers? Which isnt a problem as I wont be setteling on a live wallpaper anyway found them far too distracting.
Would still be nice to know this is fixable though.
Thank You
I was wrong its not to do with live wallpapers, just seems to do it on some apps, for example if I go to apex launcher then settings, if I leave the mouse for 10 seconds or more than rouch to move it, it makes the strange flash across the screen.
Could anyone else please test if theirs does this?
Thanks
Asus considers it to be a feature - not a bug - and calls it "smart backlight adjuster".
For most people it goes away upgrading to 4.3 which I guess you haven't done?
berndblb said:
Asus considers it to be a feature - not a bug - and calls it "smart backlight adjuster".
For most people it goes away upgrading to 4.3 which I guess you haven't done?
Click to expand...
Click to collapse
Yeah I am running 4.3?
I have noticed it does it on the drawer too, only when using the dock and leaving the mouse dormant for 8 seconds or more than moving it again it sends horizontal lines across the screen for a split second, is this the bug *ahem* feature you speak of?
Thanks
berndblb said:
Asus considers it to be a feature - not a bug - and calls it "smart backlight adjuster".
For most people it goes away upgrading to 4.3 which I guess you haven't done?
Click to expand...
Click to collapse
Also when you say adjuster, that sounds like it would be something that requires adjusting but it still does this with screen set to full brightness, or least brightness, with auto off, also wit outdoor on or off, it still does the strange flicker.
I can happily live with it, doesnt bother me that much just dont want it to be something that is going to get worse as Im very close to unlocking the device and dont want to blow all warranty if I already have a fault.
Thanks
dougie175 said:
Also when you say adjuster, that sounds like it would be something that requires adjusting but it still does this with screen set to full brightness, or least brightness, with auto off, also wit outdoor on or off, it still does the strange flicker.
I can happily live with it, doesnt bother me that much just dont want it to be something that is going to get worse as Im very close to unlocking the device and dont want to blow all warranty if I already have a fault.
Thanks
Click to expand...
Click to collapse
No what I had in mind was the screen dimming and brightening. What you describe sounds more like the "flashing black lines" the TF700 has (which seems to be due to some nvidia driver issue). I have not noticed those on the TF701 but then, I am so used to them from the 700 I probably wouldn't even notice. Have not read anything about them in the forums though, so I suspect your situation is unique.
Are you in the US? Get a Squaretrade warranty. I find the peace of mind is worth the $75 since they don't care about locked/unlocked...
berndblb said:
No what I had in mind was the screen dimming and brightening. What you describe sounds more like the "flashing black lines" the TF700 has (which seems to be due to some nvidia driver issue). I have not noticed those on the TF701 but then, I am so used to them from the 700 I probably wouldn't even notice. Have not read anything about them in the forums though, so I suspect your situation is unique.
Are you in the US? Get a Squaretrade warranty. I find the peace of mind is worth the $75 since they don't care about locked/unlocked...
Click to expand...
Click to collapse
No I am in the UK Im afraid, hmmmmm its deffo a tf701 not a 700 hehe
Can you please test for me open your drawer, leave the mouse in the centre for 10 seconds then move it and see if it does the black lines?
Also did the issue ever get resolved or get any worse on the 700 or is it just something the user gets used to?
Thank You
dougie175 said:
No I am in the UK Im afraid, hmmmmm its deffo a tf701 not a 700 hehe
Can you please test for me open your drawer, leave the mouse in the centre for 10 seconds then move it and see if it does the black lines?
Also did the issue ever get resolved or get any worse on the 700 or is it just something the user gets used to?
Thank You
Click to expand...
Click to collapse
Don't have the keyboard for the TF701 - yet. So I can't help you with your test.
The black lines on the 700 are benign - I don't even notice them anymore. But I don't think my 701 has them, so there is a possibility that your tablet has a glitch...
berndblb said:
Don't have the keyboard for the TF701 - yet. So I can't help you with your test.
The black lines on the 700 are benign - I don't even notice them anymore. But I don't think my 701 has them, so there is a possibility that your tablet has a glitch...
Click to expand...
Click to collapse
Thanks, I have sent Asus an email to see if they will help me, I bought the tablet second hand though so they probably have no interest even though it is only 3 months old and hasnt been out long enough to be out of warranty.
If they will fix or replace it for me ill take that, if not i can happily live with it
dougie175 said:
No I am in the UK Im afraid, hmmmmm its deffo a tf701 not a 700 hehe
Can you please test for me open your drawer, leave the mouse in the centre for 10 seconds then move it and see if it does the black lines?
Also did the issue ever get resolved or get any worse on the 700 or is it just something the user gets used to?
Thank You
Click to expand...
Click to collapse
Just tried your test and I see no lines. Maybe because I'm not on the stock rom exactly?
dougie175 said:
Thanks, I have sent Asus an email to see if they will help me, I bought the tablet second hand though so they probably have no interest even though it is only 3 months old and hasnt been out long enough to be out of warranty.
If they will fix or replace it for me ill take that, if not i can happily live with it
Click to expand...
Click to collapse
I don't want to be negative here, but waiting for Asus' response is pretty useless. Their support staff has two answers for questions beyond: "Where do I find my pictures?" and they are:
a) Factory reset, and if that does not help:
b) Send it in for repair - which may or may not cost you a bundle...
If you do send it in get written confirmation that your tablet is still under warranty first and take pictures of your tablet documenting its condition, how you packed and shipped it etc.
Thanks for the replies
This is what I get
dougie175 said:
Thanks for the replies
This is what I get
Click to expand...
Click to collapse
That is entirely different from what I thought it was and I have no idea what could be causing it. Do you get that ever when the dock is not connected?
berndblb said:
That is entirely different from what I thought it was and I have no idea what could be causing it. Do you get that ever when the dock is not connected?
Click to expand...
Click to collapse
No it cannot be replicated when the dock is not connected or when just touching the screen with or without the dock connected, it only does it on some areas of the system such as drawer and some apps if the mouse if left dormant for 8 seconds or so then moved.
I have done a factory reset and cold boot as requested by Asus, but the problem still persists as shown here in the new video
http://s9.photobucket.com/user/dougie175/media/Mobile Uploads/MOV_0020.mp4.html
dougie175 said:
No it cannot be replicated when the dock is not connected or when just touching the screen with or without the dock connected, it only does it on some areas of the system such as drawer and some apps if the mouse if left dormant for 8 seconds or so then moved.
I have done a factory reset and cold boot as requested by Asus, but the problem still persists as shown here in the new video
http://s9.photobucket.com/user/dougie175/media/Mobile Uploads/MOV_0020.mp4.html
Click to expand...
Click to collapse
Mine definitely doesn't do that. Try switching the cursor mode to gesture mode for me and see if that makes a difference. (I doubt it will but you never know)
Then go to the system settings, about and click the build number 7 times to enable developer mode. Then go into developer settings and look for force GPU rendering and disable hardware overlays. Check both. Reboot - any difference?
Check the cables
When troubleshooting a screen flicker, I always check the cables first. Several TechRepublic members agree. Ian C B, Bruceb, Crjordan, and Aqmike all suggested checking the video and monitor power cables before doing anything else. Ian C B reminds us to confirm that the cables are screwed in tightly and to replace the cables with new ones to see if the problem persists.
"The color changes are almost always a faulty wire in the cable," Crjordan said. "Try working the cable back and forth near both connectors. If this causes the color change, you could have a broken wire in the cable, or a loose pin in one of the connectors. Make sure the cable is out of the way (from feet, hands, and other objects). You may also try zip-tying it to itself or another stable object until you can replace either the cable or the monitor."
Check the environment
If a cable isn't the culprit, then the user's workspace should be next on your hit list. Monitors are notoriously sensitive to magnetic fields. Speakers, florescent lights, fans, cell phones, radios, and any other electrical device can cause a wide range of monitor problems. (See Figure A.) "Check what's around the [monitors]," Vilefileman said. "Cell phones are known to cause screen flickers, among other things, and plugging a radio or fan into the same receptacle can also cause screen flickers."
Maybe its like some kind of electrostatic interefereence in your environment more to do with the power being supplied to the device. Check cables. Etc. I think its interference or something.
sbdags said:
Mine definitely doesn't do that. Try switching the cursor mode to gesture mode for me and see if that makes a difference. (I doubt it will but you never know)
Then go to the system settings, about and click the build number 7 times to enable developer mode. Then go into developer settings and look for force GPU rendering and disable hardware overlays. Check both. Reboot - any difference?
Click to expand...
Click to collapse
I have noticed one other thing, it will not do the fault on first reboot, until the screen is locked, once unlocked it starts doing this fault
Gesture mode made no difference
Also done the developer options and they made no difference :crying:
sbdags said:
Mine definitely doesn't do that. Try switching the cursor mode to gesture mode for me and see if that makes a difference. (I doubt it will but you never know)
Then go to the system settings, about and click the build number 7 times to enable developer mode. Then go into developer settings and look for force GPU rendering and disable hardware overlays. Check both. Reboot - any difference?
Click to expand...
Click to collapse
I was wrong disabling hardware overlays does seem to resolve the issue?
However each time I reboot the option is un ticked that's why I thought it didn't do it
YayYouFixedIt said:
Check the cables
When troubleshooting a screen flicker, I always check the cables first. Several TechRepublic members agree. Ian C B, Bruceb, Crjordan, and Aqmike all suggested checking the video and monitor power cables before doing anything else. Ian C B reminds us to confirm that the cables are screwed in tightly and to replace the cables with new ones to see if the problem persists.
"The color changes are almost always a faulty wire in the cable," Crjordan said. "Try working the cable back and forth near both connectors. If this causes the color change, you could have a broken wire in the cable, or a loose pin in one of the connectors. Make sure the cable is out of the way (from feet, hands, and other objects). You may also try zip-tying it to itself or another stable object until you can replace either the cable or the monitor."
Check the environment
If a cable isn't the culprit, then the user's workspace should be next on your hit list. Monitors are notoriously sensitive to magnetic fields. Speakers, florescent lights, fans, cell phones, radios, and any other electrical device can cause a wide range of monitor problems. (See Figure A.) "Check what's around the [monitors]," Vilefileman said. "Cell phones are known to cause screen flickers, among other things, and plugging a radio or fan into the same receptacle can also cause screen flickers."
Maybe its like some kind of electrostatic interefereence in your environment more to do with the power being supplied to the device. Check cables. Etc. I think its interference or something.
Click to expand...
Click to collapse
Theres not really any cables I can check, I have checked the connection is pushed in correctly which it is.
I have just tried to replicate the error outside with my phone turned off inside the house so no chance of interference and the error was still present.
Don't think this is quite the issue as it only does it when moving the mouse after leaving it on certain apps for 8 seconds.
Thank you for the help though
I picked up the nexus 6 from AT&T a couple days ago and love it but I have one issue. The compass is off by 90 to 180 degrees. If I spin it around enough it usually calibrated itself but only lasts until the next time I start maps.
I've seen a couple of comments indicating similar issues but I'm not sure if it is a hardware issue and should be replaced.
Does the compass work correctly for everyone else?
Sent from my Nexus 6 using Tapatalk
Same issue here
I have the same issue with my Nexus 6 64Gb blue, bought in Germany from Amazon.de.
Calibration helps but it decalibrates soon, and then the compass is off by 90° or 180°.
DontHaveACLue said:
I picked up the nexus 6 from AT&T a couple days ago and love it but I have one issue. The compass is off by 90 to 180 degrees. If I spin it around enough it usually calibrated itself but only lasts until the next time I start maps.
I've seen a couple of comments indicating similar issues but I'm not sure if it is a hardware issue and should be replaced.
Does the compass work correctly for everyone else?
Click to expand...
Click to collapse
That would NOT be a hardware issue. That is entirely software.
doitright said:
That would NOT be a hardware issue. That is entirely software.
Click to expand...
Click to collapse
Why are you so sure it's a software issue if the sensor loses calibration no matter what?
max.shirshin said:
Why are you so sure it's a software issue if the sensor loses calibration no matter what?
Click to expand...
Click to collapse
heres one way to calibrate a compass in android.. https://www.youtube.com/watch?v=AzQSsUsOWJc
simms22 said:
heres one way to calibrate a compass in android..
Click to expand...
Click to collapse
Exactly, except that in case of Nexus 6 the calibration only helps for about half an hour. It corrects the compass sensor and it starts behaving as it should, only to start showing random direction when you open Google Maps the next time. I've been testing it for several days, both inside and outside, in different places, running calibration several times a day. In no less than a couple of hours (usually even faster) it goes nuts again.
If you own a Nexus 6 as well, and do NOT have this issue, please let us know where you bought the device and which exact model it was (white or blue? memory size?)
Thank you very much in advance!
ingdir said:
Exactly, except that in case of Nexus 6 the calibration only helps for about half an hour. It corrects the compass sensor and it starts behaving as it should, only to start showing random direction when you open Google Maps the next time. I've been testing it for several days, both inside and outside, in different places, running calibration several times a day. In no less than a couple of hours (usually even faster) it goes nuts again.
If you own a Nexus 6 as well, and do NOT have this issue, please let us know where you bought the device and which exact model it was (white or blue? memory size?)
Thank you very much in advance!
Click to expand...
Click to collapse
bought mine through tmobile. black(blue) 32gb version
max.shirshin said:
Why are you so sure it's a software issue if the sensor loses calibration no matter what?
Click to expand...
Click to collapse
Calibration *IS* a software function. You feed corrections into the compass driver to compensate for the magnetic fields generated by the phone itself. If it is losing calibration, it CAN ONLY be a software issue. The data generated by the compass HARDWARE is not affected by calibration. The calibration adjustments are applied to values after they have been received from the hardware by the driver, and before being passed on to userland.
---------- Post added at 08:02 PM ---------- Previous post was at 07:50 PM ----------
ingdir said:
Exactly, except that in case of Nexus 6 the calibration only helps for about half an hour. It corrects the compass sensor and it starts behaving as it should, only to start showing random direction when you open Google Maps the next time. I've been testing it for several days, both inside and outside, in different places, running calibration several times a day. In no less than a couple of hours (usually even faster) it goes nuts again.
Click to expand...
Click to collapse
Are you totally certain that this is a function of losing calibration and not of needing a NEW calibration? The problem is that a compass reads magnetic fields. Nearly EVERYTHING generates magnetic fields, ABSOLUTELY EVERYTHING that uses electricity will generate magnetic fields. Everything with IRON in it will generate magnetic fields, typically in line with earth's magnetic field so it won't interfere (much), but if that thing with iron in it is MOVED, it will DEFINITELY interfere for quite a long time until it resets.
What the calibration does, is it tries to sort out all the competing magnetic fields in order to lock in to the true earth magnetic field. If you keep switching the compass on at different locations, then absolutely YES, it will spit out various incorrect values. In fact, if you go get yourself a regular old fashioned magnetic compass (with a needle on a pin in an oil bath) and you move it around, it WILL react to all the different things that produce a magnetic field.
Maybe try going into a forest, calibrating it, sitting around for a few hours (maybe a camp fire?), and then checking if it keeps its calibration.
doitright said:
Calibration *IS* a software function. You feed corrections into the compass driver to compensate for the magnetic fields generated by the phone itself. If it is losing calibration, it CAN ONLY be a software issue.
Are you totally certain that this is a function of losing calibration and not of needing a NEW calibration?
Click to expand...
Click to collapse
No, I'm not. Well, here are some possibilities to consider:
1. External magnetic fields affecting the phone in a way the compass goes nuts.
Before Nexus 6, I had Nexus 5 for 1 year and its compass worked perfectly in the same locations where Nexus 6 compass fails: same apartment, same office, same places around the city. Moreover, I don't even remember calibrating my Nexus 5, the compass just worked. Now I have Moto G as a temporary phone as I've sent my N6 back to Amazon, and Moto G compass works excellently as well -- again, no calibration required. So we have at least two devices with compasses working fine in the same environment.
2. Software bug that causes calibration data to be dropped.
I had the compass problem both on stock Lollipop and on CM. I also have a friend who did NOT have any compass issues while running exactly the same setup (first stock, then the same builds of CM) on the same Nexus 6 model. In Android, apps typically can't work with drivers on such a low level that could affect the calibration, and I don't run any special apps (except Google Maps) that do something with the compass. So it CAN be a software bug, but then it has to be very picky. Running a phone on pure CM without Google Maps for several days could be a good test as Maps is the only app that had something to do with a compass on my phone.
3. Some magnetic interference inside the device itself, or the sensor being too sensitive and/or having a hardware problem of its own.
This one seems the most likely to me, as it fits a pattern: the problem happens consistently on one device while never happening on other devices with identical configuration, several users have this problem (there are threads on reddit and other places, too) while the majority seems to be unaffected, and other devices with a compass work just fine in same locations.
Anyway, there obviously ARE devices around which can have a compass working just fine, and be it either a software or a hardware issue with Nexus 6, it's good if more people report a similar issue (or a lack thereof).
I have the same issue. I have calibrated from home and on the road in several states. I does not hold calibration.
I'm road warrior, and this is a real problem when traveling.
Sent from my Nexus 6 using XDA Free mobile app