Hello guys,
I have Note 3 (SM-N9000Q)
Android version: Stock 4.4.2 N9000QXXUDND2 -Turkey-
I get this phone new.
After having a call screen comes up with very low bright. Do you know what would be the reason? Software? Hardware?
* I did auto-brightness off (I using full brightness)
* Auto adjust screen tone off
* Adapt display off, but did not improve.
After some calls to very low the screen brightness :S
I making a call, I'm holding my hand over the sensor
and the occasional screen brightness too low to be opened.
Help
@serdar_gs if you cover the sensor when talking on a call, screen goes off.
Is this you want to say?
Sent from Galaxy Note 3 SM-N9005
@thahim, I do not use cover but screen has a protective transparent gelatin.
@serdar_gs what I mean to say when you put ur hand on the sensor near the ear peice while in a call. Not the cover.
Sent from Galaxy Note 3 SM-N9005
@thahim sorry for my bad english
I do not use cover. no cover.
There is gelatin screen saver.
Not a problem with this constant, I call and occasional screen is low brightness opened by.
Sometimes to be opened with normal brightness, sometimes unfold with low brightness :S
@serder_gs which language do you speak. Ill try to translate
Sent from Galaxy Note 3 SM-N9005
@thahim my speak Turkis and i using google translate
Help guys What is the solution?
Try to do a factory reset to make sure that it's not a software issue. If the issue persists, it may be a hardware issue (sensor maybe?)
@Bibz0r I did that test proximity sensor. Everything seems normal. I'm downloading rom, I will do the installation from scratch.
Is there anyone experiencing this issue?
I think this might be an issue KitKat =)
I'm using a KK ROM now but I had stock KK before and never had this issue.
I'm curious, what ROM are you installing?
Bibz0r said:
I'm using a KK ROM now but I had stock KK before and never had this issue.
I'm curious, what ROM are you installing?
Click to expand...
Click to collapse
I using and installing stock 4.4.2 turkey rom. I get this phone new. I dont install other roms and root.
I did wipe data and again install stock 4.4.2 rom. problem continues =)
I think the this problem is that 4.4.2 ROM turkey
serdar_gs said:
I did wipe data and again install stock 4.4.2 rom. problem continues =)
I think the this problem is that 4.4.2 ROM turkey
Click to expand...
Click to collapse
Have you installed a stock ROM from SamMobile? You can get them here :
http://www.sammobile.com/firmwares/
Let me know if you are still having issues.
@Bibz0r yes I did download it from there.
Don't rule out a possible hardware issue too. Or maybe a bug in the Turkish ROM, like you said.
If it's a new phone, you still have warranty?
Yes new phone and have warranty
Then I would suggest you contact your carrier/manufacturer to get it checked.
Let me know how it goes.
ok thanks
Related
Hello. I have a problem with my proximity sensor. When I call, the screen dims instantly. Androsensor always shows 0. I have no screen protector. ROM and kernel is stock. What can I do?
Wololo7 said:
Hello. I have a problem with my proximity sensor. When I call, the screen dims instantly. Androsensor always shows 0. I have no screen protector. ROM and kernel is stock. What can I do?
Click to expand...
Click to collapse
Check that your radio version is compatible with your android version (i.e. .48 with 4.2.2). If it is, it might be a hardware problem :/
Sent by carrier pigeon
Sadly the modem is .48 with Android 4.2.2. Tried downgrading, didn't help. Thank you for answering.
Sounds more like a hardware problem if you're unrooted and still on stock. Has it only happened on 4.2.2 or was it the same on 4.2.1?
BrutalUK said:
Sounds more like a hardware problem if you're unrooted and still on stock. Has it only happened on 4.2.2 or was it the same on 4.2.1?
Click to expand...
Click to collapse
Well I got this phone with the defect. It was 4.2.2. Tried to downgrade to 4.2.0. But it did not help. I am covered under warranty though.
Hi from Turkey !
Guys i bought a G2 a few days ago and i detected a problem on phone which is about ''Auto Brightness''.Unfortunately i think its not working :/
I choose auto brightness then going balcony of home (coming direct sunlight) but there is any changes about brightness :/ Or when room is dark, i open lambs but again no changes.But i know The Light Sensor is working cause when im making a call its close the screen light.
Is there anybody who have this problem too ? And how can i solve it without roms, root or extra programs ?
Cause if this is a hardware problem, i will send back it to LG for exchange before its been too late for exchange.
Thanks...
Check out this thread...
http://forum.xda-developers.com/showthread.php?t=2539736
answer
redduc900 said:
Check out this thread...
http://forum.xda-developers.com/showthread.php?t=2539736
Click to expand...
Click to collapse
Always i saw it yesterday but still im not satisfaid about my question
Hey guys,
I have a question about what I am noticing and is bugging the heck out of me.
When I am on a call the screen goes black like it should, but once I remove the phone from my ear, the screen always came back on by itself..... Until I upgraded to Kit Kat. Now it just stays black and I have to press the power button to turn the screen on.
Is there a setting for this somewhere that I am missing?
Thanks!
Sent from my Nexus 4 using Tapatalk
Hmm, sounds like an issue with the proximity sensor. It should turn back on based on my use of the N4 from 4.2.2, 4.3, and 4.4.2.
Maybe try re-loading the OS?
Itz mostly that your proximity sensor bug !! What you can do is download a proximity sensor app from the play store like proximity on/off and test whether that works !! If it doesn't that means you have a bug in your ROM !! If u have unlocked your boot loader then flash the stock image or if u have rooted+custom recovery you can flash custom or a stock zip file
I hope it resolves your issue !! Hit the Thanks button if you find my post useful !!
Sent from my Nexus 4 using Tapatalk
Hmmm yeah I just tried a sensor app and it just says no change detected. It's weird cause I am running stock rom downloaded straight from Google. Just rooted and unlocked bootloader.....
Sent from my Nexus 4 using Tapatalk
So maybe the Proximity Sensor doesn;t work at all on this phone ... (I just got it through a warranty exchange because on my old N4 the screen broke).
I just flashed factory images again (EVERYTHING) and the Proximity Sensor still doesn't work. It shows it doesnt detect anything, even if I put my finger right over it. It does say Proximity Sensor is available though ....
so idk ...
If you go back to 4.2.2, does the proximity sensor work?
Proximity sensor is definitely broken, it's not a software issue. If you've still got warranty you should send it in.
audit13 said:
If you go back to 4.2.2, does the proximity sensor work?
Click to expand...
Click to collapse
I'm gonna flash 4.2 later and see. I just got the phone as a warranty exchange 2 days ago so if it still doesn't work I'm locking it all back up and telling tmo.
Sent from my Nexus 4 using Tapatalk
Talked to T-Mobile.... They're sending me another one. Glad I caught that early. Thanks for all the input yall!
Sent from my Nexus 4 using Tapatalk
Hello everyone,
When I try to answer a call the ringtone volume will spike for a very short of time. The spike will make the volume peak at it highest. Anyone has this problem?
very annoying
Anyone
I've bought the note 4 just 5 days ago and I've just recently noticed this particular sound issue too. I'm wondering if it's just a software bug... It's so weird that just you and me are having this issue that I'm really thinking that it could be a hardware issue...
My friend also has the same problem. He use N910c as well
Yathani said:
My friend also has the same problem. He use N910c as well
Click to expand...
Click to collapse
Do you still have this problem? Do you think that it's software related or hardware related? Does flashing a newer rom stones this issue?
davi_ssilva said:
Do you still have this problem? Do you think that it's software related or hardware related? Does flashing a newer rom stones this issue?
Click to expand...
Click to collapse
I would love to have answer as well, but i'm in the same boat. However, I tried to set the same ringtone as an alarm with max volume and when i try to stop/snooze it doesn't do that. I even tried the MOD that is on the app section which change the volume on the note 4. It did increase my speaker volume but i didn't do anything in fixing the issue. I also tried to install an app called "Disable Increasing Ring" which remove the low volume on the first ring but it didn't help either.
I tried to post this on another forum looking for help and one guy said "Check the setting that maximizes the volume on ringing." I don't know what does that mean.
Yathani
Yathani said:
I would love to have answer as well, but i'm in the same boat. However, I tried to set the same ringtone as an alarm with max volume and when i try to stop/snooze it doesn't do that. I even tried the MOD that is on the app section which change the volume on the note 4. It did increase my speaker volume but i didn't do anything in fixing the issue. I also tried to install an app called "Disable Increasing Ring" which remove the low volume on the first ring but it didn't help either.
I tried to post this on another forum looking for help and one guy said "Check the setting that maximizes the volume on ringing." I don't know what does that mean.
Yathani
Click to expand...
Click to collapse
I tried the "Disable Increasing Ring" app too, because I initially tought that it was a bug of the increasing ringtone feature that is present since Android v.4.3... But it didn't work. I've also flashed another rom and the issue persisted.
I don't know... What drives me crazy is that some people have this problem but the majority just don't! Of it is a firmware problem, it should happen with everyone that has the same rom...
I'm also worried because this spike in the ringtone volume may damage the loudspeaker through time...
To be honest, I'm just about to return my phone!!!
Same here. 910c version.
davi_ssilva said:
I tried the "Disable Increasing Ring" app too, because I initially tought that it was a bug of the increasing ringtone feature that is present since Android v.4.3... But it didn't work. I've also flashed another rom and the issue persisted.
I don't know... What drives me crazy is that some people have this problem but the majority just don't! Of it is a firmware problem, it should happen with everyone that has the same rom...
I'm also worried because this spike in the ringtone volume may damage the loudspeaker through time...
To be honest, I'm just about to return my phone!!!
Click to expand...
Click to collapse
What rom did you try on your Note 4? I think I will wait until the SC810 Note 4.
Yathani said:
What rom did you try on your Note 4? I think I will wait until the SC810 Note 4.
Click to expand...
Click to collapse
I've tried 02 official stock roms: ZTO (Brazil - International Unlocked) and ZTA (Brazil - Claro Branded).
I did the Factory Reset and wiped the Cache Patition using the Stock Recovery, and then flashed these roms using Odin 3.09
Then I started the phone, didn't logged in my google account nor in my samsung account, and so I did'd download nor intalled any app. I didn't make any changes on the phone's configuration menu.
Then, with the phone like this, I've called myself using my girlfriend's phone and, unfortunately, when I swiped to answer the call the damn sound bug was still present!!!
Since I know many other users that run these roms and don't have this problem, I'm assuming that it's a hardware issue particular to my note 4 unit.
So I have no other choice: I'll return my phone as soon as possible!
davi_ssilva said:
I've tried 02 official stock roms: ZTO (Brazil - International Unlocked) and ZTA (Brazil - Claro Branded).
I did the Factory Reset and wiped the Cache Patition using the Stock Recovery, and then flashed these roms using Odin 3.09
Then I started the phone, didn't logged in my google account nor in my samsung account, and so I did'd download nor intalled any app. I didn't make any changes on the phone's configuration menu.
Then, with the phone like this, I've called myself using my girlfriend's phone and, unfortunately, when I swiped to answer the call the damn sound bug was still present!!!
Since I know many other users that run these roms and don't have this problem, I'm assuming that it's a hardware issue particular to my note 4 unit.
So I have no other choice: I'll return my phone as soon as possible!
Click to expand...
Click to collapse
SO you installed another Samsung rom? that won't help to identify the issue.
Yathani said:
SO you installed another Samsung rom? that won't help to identify the issue.
Click to expand...
Click to collapse
Why not??? The point is that people running the same Samsung rom that I have simply don't have this problem. The fact is that every note 4 unit should be able to run a stock rom and not present this particular bug. I mean, it must be a hardware issue because my method excluded all the particular changes in the sistem that could be caused by apps or some configuration options... So, after excluding all those factors, if two identical models are running the same identical roms, the only reason that one unit has a bug and the other don't is that they aren't really identical, i.e. because one of them has a hardware problem/difference.
The other point is that if I want to use my warranty rights, I must not have root access nor use a custom rom, because I don't wat to trigger my flash counter or my knox counter...
So it makes absolutely no sense that I must loose my warranty and use a coustom rom to get rid of a problem that doesn't even exists in the vast majority of note 4 units that are able to run the stock rom without presenting this issue.
davi_ssilva said:
I've tried 02 official stock roms: ZTO (Brazil - International Unlocked) and ZTA (Brazil - Claro Branded).
I did the Factory Reset and wiped the Cache Patition using the Stock Recovery, and then flashed these roms using Odin 3.09
Then I started the phone, didn't logged in my google account nor in my samsung account, and so I did'd download nor intalled any app. I didn't make any changes on the phone's configuration menu.
Then, with the phone like this, I've called myself using my girlfriend's phone and, unfortunately, when I swiped to answer the call the damn sound bug was still present!!!
Since I know many other users that run these roms and don't have this problem, I'm assuming that it's a hardware issue particular to my note 4 unit.
So I have no other choice: I'll return my phone as soon as possible!
Click to expand...
Click to collapse
davi_ssilva said:
Why not??? The point is that people running the same Samsung rom that I have simply don't have this problem. The fact is that every note 4 unit should be able to run a stock rom and not present this particular bug. I mean, it must be a hardware issue because my method excluded all the particular changes in the sistem that could be caused by apps or some configuration options... So, after excluding all those factors, if two identical models are running the same identical roms, the only reason that one unit has a bug and the other don't is that they aren't really identical, i.e. because one of them has a hardware problem/difference.
The other point is that if I want to use my warranty rights, I must not have root access nor use a custom rom, because I don't wat to trigger my flash counter or my knox counter...
So it makes absolutely no sense that I must loose my warranty and use a coustom rom to get rid of a problem that doesn't even exists in the vast majority of note 4 units that are able to run the stock rom without presenting this issue.
Click to expand...
Click to collapse
I feel like people have this problem but they don't pay attention to it as much as we do. But let me know please how it goes with you. If a replacement worked with you or not.
Thanks
Well, it bother me, but I believe Samsung will fix it. Let wait for lollipop update.
https://play.google.com/store/apps/...+ring&pcampaignid=APPU_BSSmVKC9CsTZoASSpIHACQ
ohbreeeezy said:
https://play.google.com/store/apps/...+ring&pcampaignid=APPU_BSSmVKC9CsTZoASSpIHACQ
Click to expand...
Click to collapse
We're already using this app, but it didn't solve our problem.
Same issue on a SM-N910C in Bulgaria. Phone taken from operator Telenor. I hope that there is a solution.
Sent from my Galaxy Note 4
Any update ?
solution
Hey guys, fb messenger causes such problems.
Just disable it and you'll be fine.
Tried that after reading... I disabled the app and uninstalled the updates... same sh*t...
Sent from my Galaxy Note 4
So I'm on a ported s6 rom (aurora) for note 3 (n900w8).
I've been noticing this problem, where a phone call would come, but no vibration with it even though the mode was set as vibration mode.
I have missed many phone calls because of this.
At first I thought I simply failed to notice the vibration, but yesterday I witnessed it not vibrating during the incoming phone call. Screen comes on, incoming call screen pops, but no vibration.
This problem persisted ever since lollipop (I think). Had the same problem in the previous roms (other note 3 lollipop roms).
Oh and it happens when the phone is in idle. If a phone call comes while i'm using the phone, it vibrates just fine.
So I was suspecting it might be blocked wakelock or alarm issue. But then again, the only app i'm using for that purpose is Servicely (by chainfire), and I only have a couple apps checked (ie. facebook, google play services, keep, mega, supersu...etc).
TW 5.0.2.
No xposed framework installed.
Rooted/deodexed.
Anyone experiencing the same problem? Any fixes? Help plz. This is starting to bother me a lot...
anybody at all ?
Well as long as the vibrating motor is okay I don't think there is much to think. You are on a ported ROM, so some bugs are to be expected. If you were experiencing the same on an official 5.0 ROM that would be bothering, but as its not you should ask about this in that ROM's thread.
Do you have enabled the power saving option? If yes, try to deactivate it and see if it still not working.
Flash an official rom.
'Ported' Roms are usually very poorly done, as they are meant for other devices.
Sent from my SM-N9005 using Tapatalk
ithehappy said:
Well as long as the vibrating motor is okay I don't think there is much to think. You are on a ported ROM, so some bugs are to be expected. If you were experiencing the same on an official 5.0 ROM that would be bothering, but as its not you should ask about this in that ROM's thread.
Click to expand...
Click to collapse
celderic said:
Flash an official rom.
'Ported' Roms are usually very poorly done, as they are meant for other devices.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
hm... The last rom I was on was Note 3 LP 5.0 rom built on official note 3 firmware (Vision X from Tmobile Note 3 xda forum), and I still saw that happening.
so yea it wasnt a problem of being ported rom or not...
and I dont want to go back to stock odex rom..
Thx for the replies anyways guys
IEAL said:
Do you have enabled the power saving option? If yes, try to deactivate it and see if it still not working.
Click to expand...
Click to collapse
and no I dont have them on