So yesterday I was messing around with rooting and setting up CWM. It was quite frustrating, but not for the usual reasons: turns out that my Nexus 7 likes to turn the backlight completely off during parts of the boot process (the google and X logos) and always in CWM so it looks like it is off when it in fact is doing something. To be able to see anything I have to shine a very bright light (using Torch on my phone right now) on the display. However during normal usage, there are absolutely no issues with the backlight.
Any Ideas?
I can try to take pictures of it later, but I don't have a very good camera.
Bump. Anybody?
Same problem here. No idea why it happens.
I contacted Google and they're going to replace it.
Sent from my Nexus 7 using xda app-developers app
Return it to stock bootloader and ROM to rule the changes didn't introduce issues.
I did, it's definitely a hardware issue
Sent from my Nexus 7 using xda app-developers app
I don't mind it actually since it only happens during boot. Not much of a problem here.
Sent from my Nexus 7 using XDA Premium HD app
If you intend to flash custom roms it's a huge problem lol.
Sent from my Nexus 7 using xda app-developers app
In low light or dark conditions, the auto flash doesn't seem to work. I'm a xylon ROM user but I've also noticed it on other ROMs. If I tap the screen, the manual focus will turn the flash on and I can take a picture w/ flash, but for only that one time. Also, I've flashed official gapps for the official camera, and the auto flash works fine by itself in low light/dark conditions when taking pictures. Has anyone else observed this? Is there a way to get auto flash working correctly on aosp camera? I really would like to be able to use the power button shutter option from aosp but the broken auto flash thing bugs me.
Sent from my Nexus 4 using xda app-developers app
Bumperz...
Sent from my Nexus 4 using xda app-developers app
I want to ask if anybody has similar bugs to a non-rooted, locked, stock nexus 4 on 4.2.2 and would like to know on how to fix them. I have factory reset the phone and always seem to get the same results. I don't mind these little bugs, but they are making me want to root my phone.
1. While listening to Google music, I would try to unlock my phone and Google music screen widget would flicker and shake and make unlocking difficult I provided the picture on the attachment.
2. Another bug while still listening to Google music; it would dim more than normally it would in a shorter amount of time on lock screen.
3. Almost every time I open YouTube, the YouTube window animation flickers.
4. Battery drops 2-5% when the phone is rebooted.
5. Phone battery % drops after being fully charged and unplugged.
Sent from my Nexus 4 using xda app-developers app
4 and 5 are caused by a slightly wrong calibrated battery if you reset the calibration files (here is a tut somewhere) or just do only full cycles for a few weeks this shouldn't be a problem because it is just a displayed drop I think I'm rooted and don't listen much to Google music so no comment to 1 and 2.
3 isn't known to me.
Just a quick answer haha
Gesendet von meinem Nexus 4 mit Tapatalk 4 Beta
Thank you, I'm going to look on how to properly calibrate the battery. These little bugs can get frustrating at times.
Sent from my Nexus 4 using xda app-developers app
Don't know about 1 and 2.
3) The youtube app is a buggy piece of sh*t, so I wouldn't sweat it too much.
4) The battery percentage drop on rebooting has occured on every ROM I tried so far, so I don't really care. Well, maybe not 5%, but 1-2% is normal for me.
5) Happens to me occasionally, I don't really mind if it drops to 99% straight away, it's only correct. 100% would mean that your battery is perfectly fully charged. When you unplug it, some tiny (seriously) amount of power is being used due to the fact that your screen turns on, right?
Try cleaning the app data and cache for Play Music and Youtube (settings > apps) and see if it gives any result.
Thank you for helping. I forgot to mention another bug that is probably the worst. When receiving a phone call, I pick up the phone and the screen turns off. I try to turn the screen on and it doesn't respond. This bug has made me miss calls various times.
Sent from my Nexus 4 using xda app-developers app
reiko09 said:
Thank you for helping. I forgot to mention another bug that is probably the worst. When receiving a phone call, I pick up the phone and the screen turns off. I try to turn the screen on and it doesn't respond. This bug has made me miss calls various times.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Mh well your on/off presses sometimes interfere with the proximity sensor on your phone this "issue" sometimes causes wild screen on/off during call because I click the button but the screen was already turning on because I no more held it next to my ear so it turns off again so I click again to turn on but hold the phone to my ear shortly to check whether the other person is still in call so proximity sensor reacts.... Repeat n-times. But that doesn't sound like your problem. Could you describe it more specific?
Gesendet von meinem Nexus 4 mit Tapatalk 4 Beta
When receiving a phone call, I pick it up the phone and the screen turns off and doesn't respond to the power button. I have to tilt the phone until it turns on and until I get a chance to answer the call. Proximity sensor/s does sound to be the cause of this. Any way to fix this?
Sent from my Nexus 4 using xda app-developers app
Phew I don't think so... But changing habits... I'm working on a solution for my random clicking but I think the only way to solve that is to give the phone more time to react before pressing power button because it'll turn screen on/off as you would like it to but it needs a short period of time for that
Gesendet von meinem Nexus 4 mit Tapatalk 4 Beta
Hopefully Android 4.3 fixes some of these bugs. The Nexus 4 Lg adapter was garbage, I dropped it once and after that it stopped working.
Sent from my Nexus 4 using xda app-developers app
1 & 2 Yes!
I told Google about this back in February.
Sent from my Nexus 4 using xda premium
What did Google say? Its frustrating listening to music and having this happen.
Sent from my Nexus 4 using xda app-developers app
reiko09 said:
What did Google say? Its frustrating listening to music and having this happen.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
They said to clear cache/data & uninstall updates. Then update.
It did not work. I told them & they said they will Look into fixing this issue in a update later on.
Sent from my Nexus 4 using xda premium
Yeah, uninstalling and updating apps doesn't work. I've been doing that since the longest and no fix. Factory resetting or even flashing stock doesn't seem to fix these bugs either. Hopefully later on they find a solution. I didn't mind these bugs at first, but after a while, it got frustrating.
reiko09 said:
I want to ask if anybody has similar bugs to a non-rooted, locked, stock nexus 4 on 4.2.2 and would like to know on how to fix them. I have factory reset the phone and always seem to get the same results. I don't mind these little bugs, but they are making me want to root my phone.
Click to expand...
Click to collapse
1. While listening to Google music, I would try to unlock my phone and Google music screen widget would flicker and shake and make unlocking difficult I provided the picture on the attachment. Don't use the lockescreen and/or the music app. Google play music works fine on my end.
2. Another bug while still listening to Google music; it would dim more than normally it would in a shorter amount of time on lock screen.
Don't notice this because I always sleep the phone manually after choosing music.
3. Almost every time I open YouTube, the YouTube window animation flickers.
Never have experienced this.
4. Battery drops 2-5% when the phone is rebooted.
This can happen, yes. Stop rebooting so much.
5. Phone battery % drops after being fully charged and unplugged.
This happens about 95% of the time. Nothing to worry about.
Sent from my Nexus 4 using xda app-developers app
Thanks for your reply. For the Google Music apk, I don't use any lock screen widget. When I listen to the music and try to unlock it, that's when it gets buggy. Either the widget shakes or the screen dims more than normally it would. I only reboot I once a day every morning in order to reduce lag and refresh the system.
I guess I don't know what you mean with the music app. What Rom are you on?
Sent from my Nexus 4
I'm on stock rom, unrooted and locked. I was on cyanognemod, unofficial miui, and decided to go back to stock. I have enjoyed stock until bugs started happening. When I listen to Google Play Music; there are times when I turn my phone on and try to unlock the screen, the Google Music widget shakes and makes it difficult to unlock.
Found another bug. Not annoying but its just there. When applying a stock wallpaper and you immediately scroll left or right, you get this result.
Sent from my Nexus 4 using xda app-developers app
May be it's just the universe trolling you saying "one does not simply not root a nexus".
Yes most of the bugs you mentioned are present and they are fixed in most of the custom ROMs.
Disappointed in the quality. I'm 90% sure it's physically out, but let's see if there's any way to troubleshoot.
Basically, was working fine initially, but it is not something I often use camera/camera flash. I found a thread about the hidden "torchlight" setting so that holding up on the volume when the screen is off turns on the light of X amount of seconds. It was working fine, but then yesterday I saw that it wasn't working.
I didn't think much of it, maybe some app I downloaded caused a conflict. But I just tried it with the camera flash and other flashlight apps and I get no light at all.
Any suggestions? Or am I going to have to deal with VZW.
Had the same problem. Camera flash and flashlight app stopped working. Tried different apps no help. Rebooted the phone and all is working now. Mine is still stock, not rooted
Sent from my SM-N900V using XDA Premium 4 mobile app
ContractorDude said:
Had the same problem. Camera flash and flashlight app stopped working. Tried different apps no help. Rebooted the phone and all is working now. Mine is still stock, not rooted
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That did it, thanks. Still wonder why this happened though
Idk but don't get me wrong I came from a Note2 to the Note 3 and I absolutely love this phone but there's quite a few little bugs I've noticed. We definitely need a software update! Idk if u guys experienced it yet but a few times now I had all my apps that were in folders I made just get completely thrown out of them. At first I thought it was just with 3rd party launchers but then it happened once with TW too. I am not rooted either.
Sent from my SM-N900V using Tapatalk
I believe there has been a small software update to the Canadian and European note 3's. We should get that soon enough. Overall though a great phone
Sent from my SM-N900V using XDA Premium 4 mobile app
This happens when I focus on an object with the flash enabled .after taking the picture when it again auto focuses it gives a crackling sound and freezes and soon after the phone reboots itself .
This is so frustrating. Lollipop has arrived but still this bug is living .
Sent from my Nexus 4 using XDA Free mobile app
I have this problem too. This is Google Camera bug.You have to Install other camera app from google play, ex. Camera FV-5.
Sorry for my english
That's strange.. I don't have it.. But keep me posted
Sent from my Nexus 4 using XDA Free mobile app
Red-Devil1894 said:
This happens when I focus on an object with the flash enabled .after taking the picture when it again auto focuses it gives a crackling sound and freezes and soon after the phone reboots itself .
This is so frustrating. Lollipop has arrived but still this bug is living .
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
My wife's N4 has this exact same issue, I was able to reproduce the issue while running logcat and nothing really popped out at me. I'm going to be looking further into it.