Database Users

Compass super lag

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

[Q] Nexus 4 Random Power Off

As the title states. Nexus 4 random power offs. Has anyone seen anything like this?
Here is the background info:
My parents have Nexus 4 phones as do I. All of our phones were ordered at the same time about 2 months or so ago when they became available again. All phones are the 16GB version. All phones bone stock with just OTA updates, not unlocked or rooted other than how they are shipped. All using T-Mobile prepaid plans.
My phone and my father's seem fine. My mom's however seems to shutdown on its own. It is random. Initially I thought that it may be an issue where she isn't used to a smart phone and isn't charging it enough. It happens though at times while it is connected to the charger. It also has happened while carrying it off the charger.
One odd thing is that when they got the phone they brought them to my house and dropped them off to have me set them up. One had the plastic screen protector with the printing on it from the factory the other didn't. I don't know which is which though now. It is a 50/50 shot if this is the one.
I have been around android since the G1 days and run the same phone. I can't think of a setting on the phone that would power it down at a certain time or period of time. She really doesn't have much for apps and is a very light user.
Not sure what to try but I was thinking about doing a wipe of the phone to see if it helps.
Anyone else have any ideas? If the wipe doesn't help the only other thing I can think of is that there is a physical issue with the phone.
I haven't seen this on my phone but there was a period of time where HD Widgets on my N7 would cause a reboot. That was fixed with an app update. This isn't a case where the device reboots. It is a complete shutdown which I find odd. So I have seen an app cause issues kind of like this. For the most part the apps that she has on her phone, I also have on mine. Well I have way more but there really isn't anything on her phone that I am not also running.
I should add that she has the phone in a TPU case. As we all do. My case design is a little different than theirs but they have cutouts for the buttons. So it isn't a case where the case is pressing on the power button. That could be an issue with my case as it covers the power button but I haven't had that issue.
Thanks

Sounds like it might be a defective battery...
Sent from my Nexus 4 using xda app-developers app

BigDig said:
Sounds like it might be a defective battery...
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
That is what I am kind of thinking. Either the battery or the smart battery chips. I think I will try a wipe first but like I said but it is odd.

sennister said:
One odd thing is that when they got the phone they brought them to my house and dropped them off to have me set them up. One had the plastic screen protector with the printing on it from the factory the other didn't. I don't know which is which though now. It is a 50/50 shot if this is the one.
Thanks
Click to expand...
Click to collapse
That sounds kind of questionable (fishy) to me... I also have the 16GB version, and I also did the OTA when I got it. But to be honest the stock OS lasted only about an hour before I rooted and started trying out custom ROMs I have not had the issue you're describing though. How are the results from your factory reset?
Also, would you consider putting on a stock-based custom ROM (such as rasbean vanilla) for your mother's phone? If the problem is software based then a reset or a new ROM might yield different results. But if the problem persists it might be hardware and I'd suggest you contact Google about servicing.

amartolos said:
That sounds kind of questionable (fishy) to me... I also have the 16GB version, and I also did the OTA when I got it. But to be honest the stock OS lasted only about an hour before I rooted and started trying out custom ROMs I have not had the issue you're describing though. How are the results from your factory reset?
Also, would you consider putting on a stock-based custom ROM (such as rasbean vanilla) for your mother's phone? If the problem is software based then a reset or a new ROM might yield different results. But if the problem persists it might be hardware and I'd suggest you contact Google about servicing.
Click to expand...
Click to collapse
I don't want to root and have my mom run a modified ROM. They live about a half hour from me so I haven't tried a wipe of the phone yet and because of the distance I don't want to deal with the issues that sometimes come up when you go with modified ROMs when I am not there. She is a very basic user and this is the first smartphone for my father and mother. Keep in mind they are in their early 70s and not really that strong on the tech side of things. I have to get some time to run over there and take a look at it. Maybe later next week.
I was just wondering if anyone else has had this issue. I think if a wipe doesn't help I will talk to Google. A search really didn't show much other than some people that were seeing a random reboot issue. I have seen apps doing that.
I have been through their warranty replacement process and it is a bit of a PITA. I am on my 3rd Nexus 7 due to hardware issues with the first 2. My N4 and my fathers have been rock solid.
While I have run custom ROMs in the past, I usually run stock until I find a need that requires me to root. Eventually I will probably root and go with a custom ROM on my N4 but

sennister said:
She is a very basic user and this is the first smartphone for my father and mother. Keep in mind they are in their early 70s and not really that strong on the tech side of things.
Click to expand...
Click to collapse
Yeah, I know what you mean. I'm giving my parents my old LG P990 phone and I just put an AOKP rom on it. I also installed Nova Launcher for them and configured it so there's just one texting app and one calling app the one and only one homescreen. No dock either, just in case they click something by accident or get lost in the app drawer
Since you have the same phone as your mom, a self-less workaround would just be to give her yours (pre-configured), and then you can fiddle around with the problematic one until you find a decent solution. :good:

amartolos said:
That sounds kind of questionable (fishy) to me... I also have the 16GB version, and I also did the OTA when I got it. But to be honest the stock OS lasted only about an hour before I rooted and started trying out custom ROMs I have not had the issue you're describing though. How are the results from your factory reset?
Also, would you consider putting on a stock-based custom ROM (such as rasbean vanilla) for your mother's phone? If the problem is software based then a reset or a new ROM might yield different results. But if the problem persists it might be hardware and I'd suggest you contact Google about servicing.
Click to expand...
Click to collapse
amartolos said:
Yeah, I know what you mean. I'm giving my parents my old LG P990 phone and I just put an AOKP rom on it. I also installed Nova Launcher for them and configured it so there's just one texting app and one calling app the one and only one homescreen. No dock either, just in case they click something by accident or get lost in the app drawer
Since you have the same phone as your mom, a self-less workaround would just be to give her yours (pre-configured), and then you can fiddle around with the problematic one until you find a decent solution. :good:
Click to expand...
Click to collapse
Hmm. That is a good idea. The PITA part would be to get everything loaded from my phone to hers. I really wish I could run Titanium backup without root as it would make it super easy to move the apps over. Though I don't have that much loaded on my phone. Things that are a pain to set up have configuration export methods like Tasker. It would rule out the end user being the source of the issue. I don't think that is it though. If we swap and it goes away, then I can consider the wipe as the solution. If the problem moves to me then it is a physical issue and call Google. If the problem persists with her, I load all her apps on the phone I carry as well to see if I start to have the issue or it becomes a training issue. The thing I like about this the most is that it is a clear process to rule out several things. I can go over there and sit with the phone but if it doesn't power off when I am there I don't gain much other than spending some time with my parents.
I don't think this is an issue but I did have to provide my IMEI# when doing the activations. In the past though on T-Mobile I have handed phones down to others and all we did was a SIM swap. I would imagine that is the case here.
Oh and one thing I did leave out. They were using their old cell phone chargers on the N4 phones. I told them to swap chargers and use the ones that came with the phone. The old ones may not put out enough power and the phone could in theory run down to the point where it shuts off and slowly charge from that point and I don't think it would turn back on. Keep in mind a retired user who just had a knee replacement so she is at home more often than not.

Did you find out the cause? I have the same issue happened twice today

The random shut off either charging or not happens to me but as mentioned before in a related thread, a lot of the times it also happens on Wi-Fi, and having WiFi optimization on.. purple were turning that off and some fixed the issues. This is my second nexus 4, so I right id give it a try and not use wifi and hasn't happen since I received mines on the 4th of may
Sent from my Nexus 4

noodles2224 said:
The random shut off either charging or not happens to me but as mentioned before in a related thread, a lot of the times it also happens on Wi-Fi, and having WiFi optimization on.. purple were turning that off and some fixed the issues. This is my second nexus 4, so I right id give it a try and not use wifi and hasn't happen since I received mines on the 4th of may
Sent from my Nexus 4
Click to expand...
Click to collapse
So you're saying it's a software issue?

Looks like it.. Turning off optimization or not even using WiFi at all worked..
Sent from my Nexus 4

Touch screen sensitivity issue still in 38R

I wonder if anyone is also experiencing sensitivity issues with the new 38R OTA.
In my case It is evident when scrolling (homescreen, twitter, whatsapp....) and typing. Also the capacitive buttons seem a bit unresponsive from time to time.
What about you guys?
Edit: here you have the prove (bad scrolling and multitouch problem) i think i am going to RMA
Multitouch and sensitivity issues in 38R: http://youtu.be/KSAl1Uh_Src
Edit:
Suddenly the issue has been gone for a week, no problems at all since 15 October... I am so confused
Edit 2:
The sensibility issue is back on 24/10/2014 without changing anything

QuBeX said:
I wonder if anyone is also experiencing sensitivity issues with the new 38R OTA.
In my case It is evident when scrolling (homescreen, twitter, whatsapp....) and typing. Also the capacitive buttons seem a bit unresponsive from time to time.
What about you guys?
Click to expand...
Click to collapse
Yes, I also still have troubles with it. I especially notice it when typing.

gr4nchio said:
Yes, I also still have troubles with it. I especially notice it when typing.
Click to expand...
Click to collapse
Do you think it could be hardware problem? I am not sure, because sometimes it works perfect, but it is the 10% of the whole time

QuBeX said:
Do you think it could be hardware problem? I am not sure, because sometimes it works perfect, but it is the 10% of the whole time
Click to expand...
Click to collapse
I am really not sure... the last couple days I was on 33R CM11S with AK kernel and did not notice the problem at all. But it is not something that happens often in my case. So it is possible that I just did not wait long enough for it to appear.
I will stay on stock cm11s 38R for a few more days and then probably switch back to AK kernel to see if my previous experience is reproducible.
Did you even try to use a different kernel? Did you still have the issue?

gr4nchio said:
I am really not sure... the last couple days I was on 33R CM11S with AK kernel and did not notice the problem at all. But it is not something that happens often in my case. So it is possible that I just did not wait long enough for it to appear.
I will stay on stock cm11s 38R for a few more days and then probably switch back to AK kernel to see if my previous experience is reproducible.
Did you even try to use a different kernel? Did you still have the issue?
Click to expand...
Click to collapse
Just flashed AK, It seems that the unresponsiveness is still there
I am really dissapointed, i though this OTA would solve sensitivity problem...

QuBeX said:
Just flashed AK, It seems that the unresponsiveness is still there
I am really dissapointed, i though this OTA would solve sensitivity problem...
Click to expand...
Click to collapse
Sorry to hear it did not help.
I have also just noticed this post http://forum.xda-developers.com/showpost.php?p=55195972&postcount=62 which suggests macgyvering an improved grounding for the phone. I have to admit that I don't understand exactly what to do. But it might become clearer if I get frustrated enough to actually open up the phone
Please let me know if you try it and it works.

Touch screen is still going to be an issue. You can check the original bug which was reported here (still says in progress) https://jira.cyanogenmod.org/browse/BACON-55

gr4nchio said:
Sorry to hear it did not help.
I have also just noticed this post http://forum.xda-developers.com/showpost.php?p=55195972&postcount=62 which suggests macgyvering an improved grounding for the phone. I have to admit that I don't understand exactly what to do. But it might become clearer if I get frustrated enough to actually open up the phone
Please let me know if you try it and it works.
Click to expand...
Click to collapse
It could work but i don't want to touch inside the phone very much, I don't want to void my warranty. I think I will RMA with this video I just made. Multitouch and sensitivity issues in 38R: http://youtu.be/KSAl1Uh_Src

QuBeX said:
It could work but i don't want to touch inside the phone very much, I don't want to void my warranty. I think I will RMA with this video I just made. Multitouch and sensitivity issues in 38R: http://youtu.be/KSAl1Uh_Src
Click to expand...
Click to collapse
You should just know that OPO's customer service while polite, will give you the run around a while. Took me about a month before they finally granted the RMA.

jlevy73 said:
You should just know that OPO's customer service while polite, will give you the run around a while. Took me about a month before they finally granted the RMA.
Click to expand...
Click to collapse
Will they RMA for a refund or just a new phone? I'm not convinced this will ever be fixed in software, and I'd rather go back to a mainstream manufacturer at this point.

dipdewdog said:
Will they RMA for a refund or just a new phone? I'm not convinced this will ever be fixed in software, and I'd rather go back to a mainstream manufacturer at this point.
Click to expand...
Click to collapse
Not sure since I just requested a new phone.

dipdewdog said:
Will they RMA for a refund or just a new phone? I'm not convinced this will ever be fixed in software, and I'd rather go back to a mainstream manufacturer at this point.
Click to expand...
Click to collapse
They will, at least, replace your phone. I did and am waiting for my new one to arrive. If multitouch issues remain (and most likely will) i'll ask for a refund. I don't really care if the phone is "cheap for specs", this flaw is unacceptable.
My S3 is much worse hardware wise and feels SO much better while typing or anything else touch related. I did have to open a ticket and later show up a few videos of multitouch malfunctioning to oneplus. They decided it was a malfunctioning unit and i was eligible for a replacement. They never mentioned bacon 55 or a "known issue" common to every phone that would be solved at some point later on.
It's taking forever too. It's been over a month and it's mainly their fault because they take so long to reply to every single email. They did ask my VAT number before hand so they could send an invoice with it to my customs that would facilitate the returning process. Despite that, my phone got stuck on my country's customs precisely because they sent them an invoice without it and was up to me to ask it to oneplus. I waited about a week for what seems an poorly excel made document (compared to my country's invoices this is a joke of a document ). I sent it to the courier who picked up and they forwarded it to customs. Stuff went smooth from that point on. Oh yea, i'm from Portugal and even though my phone was sent to me from the UK the first time, to return a phone, you're going to send it to Hong Kong. All free of charge. I did have to print loads of pre made documents (about 10 pages?), because apparently sending anything with a battery is a big deal safety wise.
Even though they are, like someone said, polite, they do take a good while to reply to anything and aren't very keen to answer to anything that falls a bit out of their "process". For example, I've asked them several times if they would send me a new phone before or after a return mine. They never really cared enough to answer. Their English also seems translated by google sometimes. Several different people may take care of the same case. I've had about 5 or 6 different names reply to me and they all just use their first name like "Wilona". It made me stop to think i was sending my already paid phone to some place across the world because this randomly named guy told me so by email - in any other different scenario this would scream of a scam. But I've placed my RMA through an official ticket on their website, they actually made a new order request from their store on their website, they use very well known couriers with tracking numbers and it's the only way i'm ever getting a chance of having a properly working phone.
I did warn them before sending my "faulty" unit back they can expect me asking for a full refund if this new one isn't working any better.

I have been on liquidsmooth rom since I got the phone, no problems with touchscreen whatsoever, Installed new 38 CMS today and started to experience that problem. Also, cms lags compare to AOSP, this is pretty weird

QuBeX said:
Do you think it could be hardware problem? I am not sure, because sometimes it works perfect, but it is the 10% of the whole time
Click to expand...
Click to collapse
Flashing ColorOS for me gave a much better touchscreen experience, things worked flawlessly in all apps for me(Amazon is my biggest issue, any scrolling over a description/review would select it and move you to that section to read it, does not happen at all in ColorOS), so im thinking its software

This issue is so exaggerated...
Sent from my A0001 using Tapatalk

What is the touchscreen issue that people are referring to? Mine seems perfect? The only issue is the slight yellow at the bottom but you only notice it if you actually go looking for it.

jojohnson250 said:
This issue is so exaggerated...
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Not really. It's bothersome.
Sent from my OnePlus One using Tapatalk

Mines slightly yellow at the bottom, appears to be getting a bit better though, unless thats just my eyes playing tricks on me. I haven't noticed touchscreen issues except i can't seem to press the spacebar properly

My touchscreen seems to be very picky as to where I touch. Sometimes it takes a few attempts. Since 38 I have had random reboots. I m stock rooted without anything else flashed.

jojohnson250 said:
This issue is so exaggerated...
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
If you can say that you're a lucky one. It can render your phone completely unusable. Imagine your phone randomly assuming touches when you're not even touching it, non stop (stuff opening, key input, etc). You can't do anything else while it happens and the only way to stop is by rebooting. 5 to 10 times a day, everyday. Also, just about anything multitouch like simply zooming on a webpage has a 50% chance of working or send your phone spazing on a zooming in/out frenzy. So I'd say it isn't exaggerating, you just aren't experiencing the worse of it.

Nexus 6 Issues thread

I thought it might be a good idea to come together and list issues we may have found.
I have to say that I love this phone.
Issues list:
1) Apps/widgets that need to access the secured/encrypted storage either crash or report that there is no sd-card, or the sd-card is unreadable.
2) The screen turn on sensor seems a little too sensitive. For instance riding in the car with the phone sitting on my leg, the screen would come on any time the road was bumpy or coming to a stop quickly.
As this will be a running list, please chip in. I am hoping we can track these as well as if fixes are released, or we decide to take them on and fix them ourselves.
I do not want any of the junk like have been in other threads about weight and size, etc. Please keep these to real issues with the phone or the software.

Well.... the app/widget issue is probably more of an issue with the app/widget itself requiring an update for better Lollipop compatibility.
As for the ambient display.... pretty sure they wanted it to be something that's convenient and easy to use. Not something that would require you to violently shake your phone to get it to turn on. I can pick it up off my desk without it turning on, then put it into my other hand, only letting it fall into my hand ever so slightly, and the ambient display turns on. Of course it's going to turn on if you're going down a bumpy road with it on your leg.

Has anyone experienced a crash and reboot yet? It happened to me a few minutes after installing the software update.

Can't connect to Moto360 watch. Thought that was very odd. Seeing if anyone else is having issues with android wear

thelowsters said:
Has anyone experienced a crash and reboot yet? It happened to me a few minutes after installing the software update.
Click to expand...
Click to collapse
Negative on the reboot part. I did have cloud print crash a few times when I first got it this morning, but no longer.

Rizz67 said:
Can't connect to Moto360 watch. Thought that was very odd. Seeing if anyone else is having issues with android wear
Click to expand...
Click to collapse
My lg g watch connected just fine.

Rizz67 said:
Can't connect to Moto360 watch. Thought that was very odd. Seeing if anyone else is having issues with android wear
Click to expand...
Click to collapse
Did you try resetting the watch? I had to reset my G Watch before it would pair.
Sent from my Nexus 6 using XDA Free mobile app

Rizz67 said:
Can't connect to Moto360 watch. Thought that was very odd. Seeing if anyone else is having issues with android wear
Click to expand...
Click to collapse
I had an issue getting my 360 to connect at first too. Ended up having to factory reset the 360 to get everything working properly.

Thanks! The reset did the trick. Must be a bug somewhere

Rizz67 said:
Thanks! The reset did the trick. Must be a bug somewhere
Click to expand...
Click to collapse
That's actually the intended method to pair an Android Wear watch with a new phone. Not a bug.

thelowsters said:
Has anyone experienced a crash and reboot yet? It happened to me a few minutes after installing the software update.
Click to expand...
Click to collapse
Nope. No crash
Rizz67 said:
Can't connect to Moto360 watch. Thought that was very odd. Seeing if anyone else is having issues with android wear
Click to expand...
Click to collapse
Mine worked fine. Just needs a reset.

Anyone getting strange whining feedback through 3.5mm headphone jack? I'm at work and can't try it with my Piston's but my car audio jack had crazy feedback. Same cable worked fine with my nexus 5, OPO, m8 and any other phone I've tried ?
Sent from my Nexus 6

housry23 said:
Anyone getting strange whining feedback through 3.5mm headphone jack? I'm at work and can't try it with my Piston's but my car audio jack had crazy feedback. Same cable worked fine with my nexus 5, OPO, m8 and any other phone I've tried ?
Sent from my Nexus 6
Click to expand...
Click to collapse
Are you charging the phone at the same time? If so unplug the phone from the charger and see if that solves the noise.

One thing I've noticed is that when wireless charging, when it hits 100%, it completely stops charging. You'd think this would be a good thing, but with my N5, it would drop to trickle-charge mode, but would at least keep the charging indicator active. Since the N6 stops charging completely, daydreams will stop functioning, and you'll go back to the home screen. Depending on the charge cycle, the phone may come awake or stay awake most of the night. in addition to making it worthless as a bedside clock, this also makes me concerned of burn-in. This is, after all, an AMOLED screen, which is prone to burn-in issues.

I will say that every now and again, my phone will make a static noise from the top speaker even though there's nothing audio playing. It did it significantly more before I installed the update and barely does it now.
Sent from my iPhone using Tapatalk

jonathan3579 said:
I will say that every now and again, my phone will make a static noise from the top speaker even though there's nothing audio playing. It did it significantly more before I installed the update and barely does it now.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
That is odd, I have had no such issue and no noise anywhere with this phone.

jimbridgman said:
That is odd, I have had no such issue and no noise anywhere with this phone.
Click to expand...
Click to collapse
It did it the most during setup when it was restoring my phone, then for a while before I installed the update, and barely now. I've only been using the phone about 12 hours now and I'm pulling it off it's first charge now. It may be a total non-issue but it's something I'm keeping my eyes and ears on.

jonathan3579 said:
I will say that every now and again, my phone will make a static noise from the top speaker even though there's nothing audio playing. It did it significantly more before I installed the update and barely does it now.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
This actually sounds like a hardware defect I would send back ASAP. Thank you all for posting your issues for those of us who are on the fence this helps what we maybe walking into when purchasing this device.

I have seen the restart issue once or twice and it seems like my GPS doesn't get a complete lock on me while using maps, it did at first and after 10 min or so it would no longer zoom in on you in google maps when it locked on your signal. Not sure if this is a google maps issue or a GPS issue though.

wondercoolguy said:
This actually sounds like a hardware defect I would send back ASAP. Thank you all for posting your issues for those of us who are on the fence this helps what we maybe walking into when purchasing this device.
Click to expand...
Click to collapse
Well, I got mine from T-Mobile so I don't think it's just as easy as getting another one. I freaking love the phone though. My biggest and only real gripe is the button placement. I hit the volume rocker almost every time I try to do anything on it. Lol.

Always on display and night clock issue

Hi guys
Recently I developed a problem where the entire screen is dimly lit when the night clock and always on display are used. It seemed to just happen out of nowhere, nothing that I did that I can think of but it sort of defeats the purpose of having it on an oled display if every pixel is lit. Phone is on the latest update, never rooted, and the always on display is at the latest version. I have tried everything up to a full factory reset. Any help is greatly appreciated.
One thing to add, I even tried flashing a new firmware through odin

I'm having the same problem. Did you manage to find a fix?

captainnebevay said:
I'm having the same problem. Did you manage to find a fix?
Click to expand...
Click to collapse
No. Seems that we're not the only ones with the issue but nobody seems to know anything about it. I was hoping the latest update would fix it, but no. My current theory is that it's a bug in the always on display driver, but that seems to be updated through the galaxy app store. If anyone knows how to revert to an old version of always on display, it may be helpful.

Well, spoke to Tmobile, getting a replacement phone.

Same issue here (it glowed in the dark); called TM for replacement. All better now
Thx for the tip.

HTCforme? said:
Same issue here (it glowed in the dark); called TM for replacement. All better now
Thx for the tip.
Click to expand...
Click to collapse
Yea, it seems like a rare problem, but definitely a hardware fault. Oh well, got a brand new, non-refurb device, thanks to Tmobile. Glad it worked out for you.