Rattle - Galaxy Note5 Q&A, Help & Troubleshooting

Just curious I know my some of my really old phones (aka iphone 4s) had a rattle to the camera when you shake it, unless you open the camera app. My note 5 does the same, any one else hear it. I'm not returning it or complaining, just curious if anyone else hears it. It's not all that loud.

Yeah, that's the image stabilization mechanism. BTW, per the sticky at the top of the General section, questions should be posted in the help/Q&A section.

Related

AT&T Commercial - Brewer/Sales guy

Has anyone seen the new commercial from ATT with the 2 guys starting a brewery business? They show the tilt a few times.
I almost fell of my chair laughing when the guy took a picture with his "customer" in a bar. The lighting in the room would have made my phone cry for light. Obviously it was all superimposed but funny none the less.
yep i noticed that too.
youtube link?
The thing that boggles my mind is that the superimposed images of the text message kind of look like WM6.1 in an orange color.
Commercial is first link on this page: http://www.skyscraperbrewing.com/events/commercial.html
I love how they use a flash transition between the scene where the salesman is using the camera and next scene where the brewer is looking at the picture. As if to imply that the phone actually has a flash.
Yea I've seen the advert. I think that when he takes the picture with the phone facing the wrong way due to the fact thar there is no front camera
fgrump123 said:
Yea I've seen the advert. I think that when he takes the picture with the phone facing the wrong way due to the fact thar there is no front camera
Click to expand...
Click to collapse
hahahah. yes i noticed that too, no front camera for crying out loud. how can they miss that. i guess it looks wierd if he was facing the camera the other way.

[Video] What's new in the HTC One Android 4.2 update

I was wondering what was new myself. This gave me a general idea so I figured I would share here. Sorry if a repost
Did I hear something about camera focus?
yeah, do ya think he could talk a little faster, duh??
Former debater, so this sounded like normal conversation to me. One of the funny places idiosyncrasies can help.
Damn though do I like the look of those quick toggles. There's basically nothing else I want more in 4.2.2 (well, besides the wonderful Dashclock widget, that is). Power Toggles is nice and I remember scoffing when Google's toggles first came out, but there's something about them that really caught my interest and held it.
Rirere said:
Former debater, so this sounded like normal conversation to me. One of the funny places idiosyncrasies can help.
Damn though do I like the look of those quick toggles. There's basically nothing else I want more in 4.2.2 (well, besides the wonderful Dashclock widget, that is). Power Toggles is nice and I remember scoffing when Google's toggles first came out, but there's something about them that really caught my interest and held it.
Click to expand...
Click to collapse
I think for me, it was the contact card.
I actually find his pace completely normal for a general overview. If it was any slower, it would be boring. NTM his pronunciation is much better than mine .
He dedicated all of 2 seconds or so to the camera tweaks (not including file storage etc). I really want to know what HTC has done to fix the problems this camera has focusing to infinity.
3:40-3:42

[Q] Sound when camera focuses

Hi guys!
I've been experiencing this 'issue' (I really don't know how to call it) for a while now; it's going to be more than five months since I have the Z with me (I'm a really happy costumer and I don't know precisely when it started, so I'm expecting for your fresh view on the subject
When in the Camera app, sometimes, it looks like the camera is really making an effort focusing, leading to a 'pop' (or 'tac') sound, like if the lens just jumped in there. I don't really know for sure, what's causing this. Not mentioning I'm kind of embarrased if this turns out to be a REALLY dumb question
Hope you guys can clarify my mind on this.
Cheers!
LeanTX said:
Hi guys!
I've been experiencing this 'issue' (I really don't know how to call it) for a while now; it's going to be more than five months since I have the Z with me (I'm a really happy costumer and I don't know precisely when it started, so I'm expecting for your fresh view on the subject
When in the Camera app, sometimes, it looks like the camera is really making an effort focusing, leading to a 'pop' (or 'tac') sound, like if the lens just jumped in there. I don't really know for sure, what's causing this. Not mentioning I'm kind of embarrased if this turns out to be a REALLY dumb question
Hope you guys can clarify my mind on this.
Cheers!
Click to expand...
Click to collapse
Same goes to me!! Do check this thread instead of opening a new one
http://forum.xda-developers.com/showthread.php?t=2423039

Replacement = Even more problems.

Had a n6 with half purple screen and had it exchanged.
This new one is horrible ..
It seems to get really warm compared to the other and when it does, boy does it lag. Just typing this out, it's lagging.
I also noticed that my Bluetooth has "silence" spots while listening to music. Every 2-3 minutes, it will stop for a split second like it can't buffer, even if the music is on the device.
Another thing that may just be me, it seems the keyboard doesn't predict as well, like it's not even touching the keys I'm swiping.
Lastly, half the screen is white and half is a really yellow color. Very irritated by this device. Makes me want to throw it against a wall.
Your first problem can be resolved by using a custom kernel that does not use mpdecision. Mpdecision is known to be power inefficient and sends your CPU to be sitting in wasteful frequencies causing your phone to generate additional heat. My phone became really warm with mpdecision on.
Secondly, I don't use bluetooth so I can't comment.
Third. That isn't a N6 problem, its a problem with the software of the keyboard application that you're using. SwiftKey works great for me.
Fourth, can't really comment on that. My screen looks good, your phone should be uniformly the same color, you can try changing RGB and see if it would do anything. I recommend turning off adaptive brightness.
Good suggestions I suppose.
Only problem with those, I'm not gonna root or use a custom kernel. The last n6 only had a faulty screen and no other problems. That one didn't need any custom root activities.
20degrees said:
Good suggestions I suppose.
Only problem with those, I'm not gonna root or use a custom kernel. The last n6 only had a faulty screen and no other problems. That one didn't need any custom root activities.
Click to expand...
Click to collapse
If you don't root, or use ROM's then why post about it on a developer forum? I'm not trying to be rude just wondering why here. If it has more issue call moto and have them send a new one. My RMA phone is fine 0 issues so far and I'm happy with it.
This is a user forum as well as a developer forum.
I'm posting here to show there is problems with these phones.
Why does it matter to you?
If you are having those problems on stock, and don't want to root/etc, then your only option is to return it again. Pretty simple.
If you are looking for confirmation that your experience isn't 'normal' on the stock phone, I can confirm it is not.
20degrees said:
This is a user forum as well as a developer forum.
I'm posting here to show there is problems with these phones.
Why does it matter to you?
Click to expand...
Click to collapse
I'm not trying to argue at all I was just curious. I would have the phone replaced if you want to gave those issues fixed without modifying the phone. Best of luck with the issues because it's not fun when you can't fix them.
Pilz said:
If you don't root, or use ROM's then why post about it on a developer forum? I'm not trying to be rude just wondering why here. If it has more issue call moto and have them send a new one. My RMA phone is fine 0 issues so far and I'm happy with it.
Click to expand...
Click to collapse
I scratch my head also. XDA is a developer's forum. There are tons of other sites more suitable to those not wanting to root/ROM it up.
Sounds good. Let's discuss dbrand skins and the such.
I doubt this has anything to do with memory leaks or anything that's been discussed on lollipop.
I'd say you have a faulty SOC and I would replace it. My wife had similar issues on an S5 where it would stutter and fall behind almost and get warm. The icing on the cake was while taking video, normal 1080p video, and it would drop frames like crazy. Maybe 22fps or so was al, it was getting.
I actually agree with 20degrees on this one... There are tons of non development/customization threads on here, and XDA has a pretty knowledgeable user base so it is a convenient one stop shop for info.
People just need to ignore/keep their comments to themselves in the Q&A and general sections if they have nothing constructive to add to the topic of the thread.

Ir sensor test app

I've got a feeling one of the sensors on the front of this phone isn't working. I can usually position the phone at an angle to see the faint red lights from the ir sensors on only 3 of them, but the top left corner I see nothing.
The phones responsiveness seemed better when I first got it a couple months ago but doesn't seem to wake up as easily as before.
Rooted moto x 2014 running stock and xposed, unlocked bootloader
Anyone know of an app that will test ir sensors?
eqjunkie829 said:
I've got a feeling one of the sensors on the front of this phone isn't working. I can usually position the phone at an angle to see the faint red lights from the ir sensors on only 3 of them, but the top left corner I see nothing.
The phones responsiveness seemed better when I first got it a couple months ago but doesn't seem to wake up as easily as before.
Rooted moto x 2014 running stock and xposed, unlocked bootloader
Anyone know of an app that will test ir sensors?
Click to expand...
Click to collapse
Turn off your lights, or use a camera from about 10 inches away and look very closely at your phone and you can actually see the emitters working with your own eyes. They turn on when Display is off, and the moment Display turns on, the emitters turn off. There are 3 emitters total- two at the bottom and one just to the right of the earpiece. Their purpose is to essentially bathe your hand in IR light, which the sensor (to the left of the earpiece) then detects. That's how the system works. When documentation states that there are 4 low power sensors, it's really just for the layman who wouldn't necessarily understand the actual way it works without it being explained. Yes there are 4 devices on the face of the phone to make it work, but only one of them is an actual sensor, the other 3 are emitters. Hence, the 3 bright and less frequency blinking lights. If you use a camera, you can see the fainter 4th light, which is the actual sensor. When the sensor detects a slight fluctuation in it's readings, it causes the 3 emitters to stay on constantly instead of blinking for a couple of seconds thereby increasing the chances of detecting the hand. If you're still enough you can see the 3 emitters going back to blinking to save battery.
Approaching the phone from a very less height, will not cause the IR to be deflected to the sensor to the top of the phone. When you reach for the phone, your hand needs to be high enough from it when you come in from the bottom that it is within the sensor's field of view. Otherwise it won't work. It seems that 3-4 inches is the lower limit. Anything closer than that and it won't pick up your hand until it's closer to the top of the phone.
That's great news that it isn't malfunctioning. I was worried that xposed was causing a problem. Only reason I'm not upgrading to 5.0 is because of xposed.
manrock said:
Turn off your lights, or use a camera from about 10 inches away and look very closely at your phone and you can actually see the emitters working with your own eyes. They turn on when Display is off, and the moment Display turns on, the emitters turn off. There are 3 emitters total- two at the bottom and one just to the right of the earpiece. Their purpose is to essentially bathe your hand in IR light, which the sensor (to the left of the earpiece) then detects. That's how the system works. When documentation states that there are 4 low power sensors, it's really just for the layman who wouldn't necessarily understand the actual way it works without it being explained. Yes there are 4 devices on the face of the phone to make it work, but only one of them is an actual sensor, the other 3 are emitters. Hence, the 3 bright and less frequency blinking lights. If you use a camera, you can see the fainter 4th light, which is the actual sensor. When the sensor detects a slight fluctuation in it's readings, it causes the 3 emitters to stay on constantly instead of blinking for a couple of seconds thereby increasing the chances of detecting the hand. If you're still enough you can see the 3 emitters going back to blinking to save battery.
Approaching the phone from a very less height, will not cause the IR to be deflected to the sensor to the top of the phone. When you reach for the phone, your hand needs to be high enough from it when you come in from the bottom that it is within the sensor's field of view. Otherwise it won't work. It seems that 3-4 inches is the lower limit. Anything closer than that and it won't pick up your hand until it's closer to the top of the phone.
Click to expand...
Click to collapse
Wow, way to blatantly plagiarize my post without quoting me and giving me credit.
http://forum.xda-developers.com/moto-x-2014/help/ir-sensors-t2963401
_MetalHead_ said:
I'm telling you, it's the case. Turn off your lights and look very closely at your phone and you can actually see the emitters working with your own eyes. They turn on when Moto Display is off, and the moment Moto Display turns on, the emitters turn off. There are 3 emitters total- two at the bottom and one just to the right of the earpiece. Their purpose is to essentially bathe your hand in IR light, which the sensor then detects. That's how the system works. When documentation states that there are 4 low power sensors, it's really just for the layman who wouldn't necessarily understand the actual way it works without it being explained. Yes there are 4 devices on the face of the phone to make it work, but only one of them is an actual sensor. Like I said, the other 3 are emitters.
All that said, when you reach for the phone, your hand needs to be high enough from it when you come in from the bottom that it is within the sensor's field of view. Otherwise it won't work. It seems that 3-4 inches is the lower limit. Anything closer than that and it won't pick up your hand until it's closer to the top of the phone.
Click to expand...
Click to collapse
manrock said:
Turn off your lights, or use a camera from about 10 inches away and look very closely at your phone and you can actually see the emitters working with your own eyes. They turn on when Display is off, and the moment Display turns on, the emitters turn off. There are 3 emitters total- two at the bottom and one just to the right of the earpiece. Their purpose is to essentially bathe your hand in IR light, which the sensor (to the left of the earpiece) then detects. That's how the system works. When documentation states that there are 4 low power sensors, it's really just for the layman who wouldn't necessarily understand the actual way it works without it being explained. Yes there are 4 devices on the face of the phone to make it work, but only one of them is an actual sensor, the other 3 are emitters. Hence, the 3 bright and less frequency blinking lights. If you use a camera, you can see the fainter 4th light, which is the actual sensor. When the sensor detects a slight fluctuation in it's readings, it causes the 3 emitters to stay on constantly instead of blinking for a couple of seconds thereby increasing the chances of detecting the hand. If you're still enough you can see the 3 emitters going back to blinking to save battery.
Approaching the phone from a very less height, will not cause the IR to be deflected to the sensor to the top of the phone. When you reach for the phone, your hand needs to be high enough from it when you come in from the bottom that it is within the sensor's field of view. Otherwise it won't work. It seems that 3-4 inches is the lower limit. Anything closer than that and it won't pick up your hand until it's closer to the top of the phone.
Click to expand...
Click to collapse
Hey that's Bs bro to take someone else post and try to make it look like it was your. Very unprofessional I may say so myself
ewalk4866 said:
Hey that's Bs bro to take someone else post and try to make it look like it was your. Very unprofessional I may say so myself
Click to expand...
Click to collapse
Yeah man, it's rude as hell. Appreciate the support.
---------- Post added at 12:53 PM ---------- Previous post was at 12:18 PM ----------
eqjunkie829 said:
That's great news that it isn't malfunctioning. I was worried that xposed was causing a problem. Only reason I'm not upgrading to 5.0 is because of xposed.
Click to expand...
Click to collapse
Yeah, you're fine. A few people were confused about how the IR system works, so you aren't alone. And agreed about Xposed. Both my Moto X and Nexus 5 are still on 4.4.4 because I think KK+ Xposed blows Lollipop out of the water. The only way I'll switch to Lollipop is when I buy a new phone that ships with it.
I am bumping this thread so people can see what not to do on XDA. Taking someone else's post and trying to pass it off as your own is not cool, and is very rude and disrespectful. What @manrock has done here is a smack in my face. He clearly tried to pass my post off as his own by adding his own words to it, and didn't cite/quote me as the original source of the information. Ladies and gentlemen, if you don't know the answer to a question, either don't post at all, or make it clear that the answer you are giving is not your own, and give credit where credit is due.
/rant
_MetalHead_ said:
I am bumping this thread so people can see what not to do on XDA. Taking someone else's post and trying to pass it off as your own is not cool, and is very rude and disrespectful. What @manrock has done here is a smack in my face. He clearly tried to pass my post off as his own by adding his own words to it, and didn't cite/quote me as the original source of the information. Ladies and gentlemen, if you don't know the answer to a question, either don't post at all, or make it clear that the answer you are giving is not your own, and give credit where credit is due.
/rant
Click to expand...
Click to collapse
Ok, first off, my apologies for not mentioning you being the source of information. I was too lazy to jump into the other thread to get your name again.
Now that we've got that out of the way, I don't understand why are you being so sentimental about this. You bumped the thread yesterday, bumped it today, you even sent me a frickin PM. To prove what????
I understand what I did was a mistake, and i apologise again, but you seem so tied up with me "STEALING" your reply, you're forgetting the reason why I did it. It was to help someone, not to show myself off. It seems what pissed you off is the fact that I didn't give you credit. And as I understand, that is of paramount importance to you. But is it even more important than the purpose for which the forum was built, to help others. Is it so important that you have to rant about it, spamming the forum.
If it is, then I apologise. again.. I'm now gonna go thank one of your posts, cause from your rants you've insinuated, i was trying to steal one from you. I don't wanna owe you anything and risk another rant . Have a good day
manrock said:
Ok, first off, my apologies for not mentioning you being the source of information. I was too lazy to jump into the other thread to get your name again.
Now that we've got that out of the way, I don't understand why are you being so sentimental about this. You bumped the thread yesterday, bumped it today, you even sent me a frickin PM. To prove what????
I understand what I did was a mistake, and i apologise again, but you seem so tied up with me "STEALING" your reply, you're forgetting the reason why I did it. It was to help someone, not to show myself off. It seems what pissed you off is the fact that I didn't give you credit. And as I understand, that is of paramount importance to you. But is it even more important than the purpose for which the forum was built, to help others. Is it so important that you have to rant about it, spamming the forum.
If it is, then I apologise. again.. I'm now gonna go thank one of your posts, cause from your rants you've insinuated, i was trying to steal one from you. I don't wanna owe you anything and risk another rant . Have a good day
Click to expand...
Click to collapse
It's because you CLEARLY tried to pass off my reply as your own. You weren't too lazy to search for an answer, copy mine, and add to it, but you were too lazy to cite me as your source? Right. You could have just copy/pasted the link to the thread that my answer was in, that's what most people would have done. But instead, you wanted to post it as your own response. However you want to look at it, it's a load of crap. And don't worry about thanking one of my posts, I get enough thanks without copying other people and having to ask for them in my signature.
_MetalHead_ said:
I get enough thanks without copying other people and having to ask for them in my signature.
Click to expand...
Click to collapse
Considering the fact that that's all you care about, I'd say you've got a great thing going.
manrock said:
Considering the fact that that's all you care about, I'd say you've got a great thing going.
Click to expand...
Click to collapse
Right, says the guy who asks for them in his signature. What I do care about is when I take the time out of my day to type up a thorough response to someone's question, and someone else comes along, copies it verbatim, and passes it off as their own. Go ahead and keep deflecting, it doesn't change the fact that you're dishonest and like to take credit for other people's work.
I'm done now, feel free to get the last word in.
eqjunkie829 said:
That's great news that it isn't malfunctioning. I was worried that xposed was causing a problem. Only reason I'm not upgrading to 5.0 is because of xposed.
Click to expand...
Click to collapse
+1
OMGoodness..seems as thow a thread cleaning is @ hand..
_MetalHead_ said:
Wow, way to blatantly plagiarize my post without quoting me and giving me credit.
http://forum.xda-developers.com/moto-x-2014/help/ir-sensors-t2963401
Click to expand...
Click to collapse
Dude, we all share info and re-share it. That's what's so great about this community. I know what I know from learning from others, and I try to help others with that info by re-sharing it. I don't feel obliged to credit those who have made "discoveries" and neither should others. UNLESS, it's code where the author has specifically requested permission to recycle it. I mean, when would your "patent" expire in the future, where you wouldn't feel offended that others recycled what you contributed - 1 month, 1 year, 10 years?
floepie said:
Dude, we all share info and re-share it. That's what's so great about this community. I know what I know from learning from others, and I try to help others with that info by re-sharing it. I don't feel obliged to credit those who have made "discoveries" and neither should others. UNLESS, it's code where the author has specifically requested permission to recycle it. I mean, when would your "patent" expire in the future, where you wouldn't feel offended that others recycled what you contributed - 1 month, 1 year, 10 years?
Click to expand...
Click to collapse
Re-sharing info is one thing, but that's not what was done here. I'm actually surprised that you don't see how it can be taken as disrespectful. Whatever though, it's done and over with and I have no interest in getting into another conversation over it.

Categories

Resources