[Q] 1 Year Later - Potential Build Issues? - Nexus 4 Q&A, Help & Troubleshooting

So I've had my Nexus 4 for almost a year now and somethings I've just lived with because I passed them off as insignificant. However, with my one year warranty from Google expiring soon, I was wondering if I should get my Nexus 4 replaced/if I have legitimate problems?
Note: I'm running Stock 4.3 with root/unlocked bootloader.
1. Is anyone else's Nexus 4 not recognized sometimes via USB?
Most of the times when I connect my Nexus 4 to my PC via USB the Nexus 4 is not recognized so I have to unplug and then replug it in and then its recognized. I'm not sure if this is a software issue or a problem with my computer?
2. During/After taking a photo, my Nexus 4's camera will start making a crackling/rattling sound.
Is this normal?
3. During a call, my Nexus 4 turn the screen black/off when I hold it up to my ear, but when I move it away the phone will sometimes remain off/black screen forcing me to toggle the power button off/on.
4. Wifi disconnects randomly.
There are times, albeit infrequent, when my Nexus 4 will disconnect from Wifi for no apparent reason. Sometimes it will soon reconnect but most of the times I have to toggle Wifi off/on.
Software issue. Is this normal? I've noticed this since 4.2 and still with 4.3.
So are these problems normal, or is my Nexus 4 just starting to get old/deteriorate?

I don't know about those other bugs, but the connection issue sometimes rears its head for me when I have USB-Debugging on.
Usually I only turn it on when i'm using a Toolkit as these sometimes need that, and when I forget to turn it off, the phone is sometimes not recognized correctly and I can't access the internal drive.
Try that, maybe it'll help.

jadephyre said:
I don't know about those other bugs, but the connection issue sometimes rears its head for me when I have USB-Debugging on.
Usually I only turn it on when i'm using a Toolkit as these sometimes need that, and when I forget to turn it off, the phone is sometimes not recognized correctly and I can't access the internal drive.
Try that, maybe it'll help.
Click to expand...
Click to collapse
Just tried turning off USB Debugging and the problem still occurs.

For the screen not turning on, see if you still have the original screen protector on. Sometimes that would cause an issue with the proximity sensor
Sent from my Nexus 4 using Tapatalk

Devhux said:
For the screen not turning on, see if you still have the original screen protector on. Sometimes that would cause an issue with the proximity sensor
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I took off that screen protector a long time ago lol. I did but on a new screen protector so maybe that is it? Also does no one have the camera issue? I thought that was prevalent with all Nexus 4s, but is it just mine?

Related

Wifi issue

Hello,
I recently noticed an issue with my wifi (stock 2.3.3), where an app that needs to update regularly didn't seem to be doing it when the screen was off. As the phone always sits on its dock when I'm at home, I "solved" the issue by making the screen never turn off.
However, today I decided to give SIPdroid another go, as I tested it when I first got my phone and it wasn't working properly. I found out why, the second I put the phone to my ear, the screen turns off and the sound cuts. If I take the phone away, I suddenly get all the audio high speed as it catches back up.
A bit of googling showed this to be a known issue, the wifi goes into power saving mode when the screen turns off - on SIPdroid there's an option to keep the screen off and it seems to work well, it just dims the screen instead. But that's still an unnecessary battery drain.
I had trouble finding any recent info on the issue (within the past 6 months), maybe I was just using the wrong keywords. So I thought I'd ask here. Does anyone know anything about this issue? Is it likely to be fixed in the next version of android if it ever comes to the desire HD? Maybe there's a fix out there already (preferably without rooting and/or installing custom rom, my phone is just right as it is now...).
Settings>Wireless & Networks>Wifi settings>Hit 'Menu'>Advanced>Wifi sleep policy>Never
That'll prevent the wifi turning off when the screen turns off.
Sent from my Desire HD using xda premium
I tried that before posting, it makes no difference whatsoever (besides, the sleep policy is either never or 15 minutes, this problem occurs the second the screen goes off).
If u re root: change radio... try anyone.
stock: mmm default reset to try. (i think)
No:
http://code.google.com/p/sipdroid/issues/detail?id=268
http://code.google.com/p/sipdroid/i...Status Priority Milestone Owner Summary Stars
Reading through the comments, it seems a more general android problem. A reset wouldn't fix it.
Also:
http://code.google.com/p/android/issues/detail?id=9781

sleep of death

I'm now on my third nexus 7 and in general absolutely love the device but I'm getting fed up with the issues.
My first device suffered from sever flickering, the second had the backlight bleed and now the third refuses to wake after the screen is turned off about fifty percent of the time.
This is not the same issue as people are reporting in other posts as the charger is never connected when I have a problem. It doesn't matter if the screen times out or if I press the power button to after I finish using the device.
I'm using the stock ROM (with the 4.1.1 update), no root and have only installed the kindel app so its about as vanilla as can be.
The second nexus I had did this once but I had already organised the return and didn't think much of it.
Anyone else having similar issues or able to recommended a fix as this nexus is perfect in every other way?
Factory reset, leave it that way for a while, does it happen? If no, then you probably have an app doing something wonky.
Turn off automatic backlight, manually set it to around 40% and see if the flicker and the "SOD" goes away.
As the poster above said, turn off automatic brightness and see if that fixes it.
Nospin said:
As the poster above said, turn off automatic brightness and see if that fixes it.
Click to expand...
Click to collapse
Automatic brightness is on my N7 (and other devices) 100% of the time... No SOD problems here.
lol, so far there's not an issue for you. But some have noticed that depending on the brightness settings it reads when you power on the screen, it can "think" it's either too bright or too dark and leave you with a screen you can't see.
This gets mistaken for "SOD" because you never see the screen-Why? Because it looks like the ratio for the lowest automatic brightness setting is a bit, um, TOO low. LOL
Most other devices won't exhibit this using stock settings, but the N7 will.
THANKS!
Just got my first nexus 7 yesterday and after pretty much falling in love, was dismayed about the unexplained black outs for no apparent reason. Could not wake up the device afterward without holding down the power key for 10 sec then leaving it alone for a while.
After reading your post, I realized that the incidents occurred after switching from manual to automatic brightness in a dimly lit room, followed by mysterious recoveries when moving to brighter room. I will monitor, but hope for the best. (Will probably just use manual settings as I found the automatic mode to be too dim in all settings anyway - old eyes!)
I am already pretty raw on this point as I just spent the last 10 years or so with a laptop that would not wake up from sleep, and just learned to live with it after wasting SO much time trying to get to the bottom of it. If you have saved me from that, or from having to exchange the n7, I owe you big time. Thanks again!
Compusmurf said:
lol, so far there's not an issue for you. But some have noticed that depending on the brightness settings it reads when you power on the screen, it can "think" it's either too bright or too dark and leave you with a screen you can't see.
This gets mistaken for "SOD" because you never see the screen-Why? Because it looks like the ratio for the lowest automatic brightness setting is a bit, um, TOO low. LOL
Most other devices won't exhibit this using stock settings, but the N7 will.
Click to expand...
Click to collapse
did you solve it or what?
I have the exact same issue and I'm about two second from returning this crap
so annoying
seven2099 said:
did you solve it or what?
I have the exact same issue and I'm about two second from returning this crap
so annoying
Click to expand...
Click to collapse
well that didnt fix anything.
Its a hardware issue, so i'm going back to stock and see what I can do, because if not, this baby is going back
seven2099 said:
well that didnt fix anything.
Its a hardware issue, so i'm going back to stock and see what I can do, because if not, this baby is going back
Click to expand...
Click to collapse
i have similar issue with forced sleep, it cannot waken sometimes. TnT
anyone can help?
Further investigation shows this has nothing to do with brightness and that all tablets with this issue should be returned/exchanged immediately.
Quick google search will allow you to find that comes directly from Asus support.
Total fail, asus ftl
new tab rendered more quality issues. opened it at the shop, returned it immediately and went samsung.
Asus will always be asus.. too bad cuz my tf300 was pretty decent in terms of quality, just had wierd screen lift and squeecky issues.
Galaxy Tab 2.0 7inch is a much better choice now.
I have exactly the same problem with my current device. About 30% of the time, the power button would just stop working so I couldn't turn the unit on or off, unless I plugged it in to the charger. It didn't turn on for a full day once so I did a full factory reset which included re-flashing the stock rom and the problem persisted, the button would still not work! So I packaged it up for return and left it sitting for a couple of days. Just before I went to post it, I checked that the issue remained and to my surprise it turned itself back on again! I kept it and since then, it has only happened once.
I do intend to return it though, but only when I hear Asus are shipping units which are built properly. Clearly a hardware issue but pretty weird since it seems random and is not reproducible by any means I know of.
I am experiencing a similar issue. Does setting a manual brightness fix the issue?
It is my 3rd Nexus now with exactly the same problem.
I found out that the Nexus is in APX-mode (NVFlash) when it's in this state (SoD). Windows tries to install a APX driver when it is connected via USB.
The problem occured always with 16GB Nexus. A friends 8GB works fine.
Nexus 7 (C9) - Stock Rom 4.1.2. - locked - not rooted
Turning off the auto-brightness fixed the issue for me. Minor workaround to a major problem.

Bluetooth Issues

So, for some reason, my Bluetooth doesn't function properly as it should, which is weird, since my phone is still on stock, and the only modifications I've made are unlocking the bootloader and rooting the device. I also installed Power Toggles, but I don't think that's the issue at hand.
Pretty much, whenever I turn the bluetooth on, it tries for a while to turn it on, then gives up and won't let me turn it on. At that point, I have to restart the phone, and when it reboots back up, the bluetooth is on without me having to start it up. Then it works properly, but if I wish to use the bluetooth again the next day, I have to repeat the process of rebooting the device. Any ideas?
I had this issue when I Downloaded a FM radio app from the Play store to see if it would work. I just deleted the app. Went into safe mode then into normal mode and it fixed it.
Don't know what you case can be. But you can try going into safe mode and back to normal and see if there are any different results.
Sent from my Nexus 4 using Tapatalk 2
I had this same problem after installing Torque, and using it with default settings that auto-enabled/disabled bluetooth. After turning all that crap off it is back to normal.
I use bluetooth for audio playback and an hf/A2DP headset dialing via Motospeak, as well as Torque with a bluetooth odb2 interface, and it all works perfectly since disabling Torque's auto-bluetooth settings. My only issue is that it takes Motospeak a bit long to restore audio playback after a hf call command.
I would look for an app that you have that is the controlling bluetooth on/off.
I wonder if it isn't a software bug. I have the same issue but I don't have any apps that are causing the issue of atleast from what I can tell. I'm also unlocked and rooted.
I removed Bluetooth from Power Toggles. It's been two days and all seems well. Now we wait.
yahoowizard said:
So, for some reason, my Bluetooth doesn't function properly as it should, which is weird, since my phone is still on stock, and the only modifications I've made are unlocking the bootloader and rooting the device. I also installed Power Toggles, but I don't think that's the issue at hand.
Pretty much, whenever I turn the bluetooth on, it tries for a while to turn it on, then gives up and won't let me turn it on. At that point, I have to restart the phone, and when it reboots back up, the bluetooth is on without me having to start it up. Then it works properly, but if I wish to use the bluetooth again the next day, I have to repeat the process of rebooting the device. Any ideas?
Click to expand...
Click to collapse
This happened to me as well
Sent from my Nexus 4 using xda app-developers app
strobex said:
This happened to me as well
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Similar problems here, the weirdest thing is idk which app causes that. Because I didnt install that much. Only thing I notice is it happened when the wifi is on.. Does anyone have similar problem??
Same problem here. I have a lot of apps but none I can think of that do anything with Bluetooth.
Sent from my Nexus 4 using xda app-developers app
yahoowizard said:
I removed Bluetooth from Power Toggles. It's been two days and all seems well. Now we wait.
Click to expand...
Click to collapse
Nope, still doesn't work.
Try going into safe mode.. See if it works, and then go back to normal mode.
Sent from my Nexus 4 using Tapatalk 2
Nothing yet? I'm just curious as to whether it's just a few people experiencing this, or a lot, since there doesn't seem to be that much talk about it.
I use Bluetooth everyday on my way home from work just to connect to my Bluetooth headset. Out of 14 days I may get one day where I turn Bluetooth on that I don't have to reboot for it to work.
Sent from my Nexus 4 using xda app-developers app
So we're on 4.2.2, I've went through safe mode and back a few times, and I've uninstalled and installed applications having to do with the Wi-Fi. Problem still seems to be there. It's just somewhat of a hassle to have to power down my phone completely, then start it back up, everytime I get into my car. I feel a hard reset mighttt fix the issue, but just looking for another way as of now.
My phone also have the same problem.. the bluetooth won't turn on.. stock 4.2.2 locked bootloader and not root yet.. anyone has a solution..

"Smart cover" issues

I just got my case today and my N7 doesn't always wake when I open the cover. I'd say it works about 80% of the time and it seems worse after the tablet has been sitting for a while. Almost as if it's sleeping too deeply to wake. A press of the power button fixes it but I'm wondering if anyone else is having this issue. If not, I need to think about whether I have a bad case or a defective tablet.
Sent from my Nexus 7 using xda app-developers app
Well what case have you got?
I have no such problem on my Portenzo hardback case.
RKight said:
I just got my case today and my N7 doesn't always wake when I open the cover. I'd say it works about 80% of the time and it seems worse after the tablet has been sitting for a while. Almost as if it's sleeping too deeply to wake. A press of the power button fixes it but I'm wondering if anyone else is having this issue. If not, I need to think about whether I have a bad case or a defective tablet.
Click to expand...
Click to collapse
On mine, if you lose WiFi connection while it is asleep it won't magnetic wake.
sfhub said:
On mine, if you lose WiFi connection while it is asleep it won't magnetic wake.
Click to expand...
Click to collapse
Same. WiFi on or off seems to work okay... WiFi on and searching is always touch and go for me. Hopefully it can be fixed pretty easily in software down the road... before it starts to actually bother me.
Noticed this on mine as well. Different than my 2012 model but not a real problem
Sent from my Nexus 7 using Tapatalk 4
RKight said:
I just got my case today and my N7 doesn't always wake when I open the cover. I'd say it works about 80% of the time and it seems worse after the tablet has been sitting for a while. Almost as if it's sleeping too deeply to wake. A press of the power button fixes it but I'm wondering if anyone else is having this issue. If not, I need to think about whether I have a bad case or a defective tablet.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I've found that it does actually wake up, eventually. I just tested it myself. When I got my Poetic slimline case, I was obviously messing with the Nexus 7 and it worked every time. I'd left the device sleeping (wifi set to not run during sleep, BT off), and when I grabbed it just now and opened the flap, nothing happened for almost 10 seconds. Crazy. However, it did eventually sleep/wake by itself. When I closed the cover and then opened it, it instantly awoke. So it seems like after the device has been sleeping for a while it just takes it a bit to wake up. Of course you can just hit the power button, too..
WilliamG said:
I've found that it does actually wake up, eventually. I just tested it myself. When I got my Poetic slimline case, I was obviously messing with the Nexus 7 and it worked every time. I'd left the device sleeping (wifi set to not run during sleep, BT off), and when I grabbed it just now and opened the flap, nothing happened for almost 10 seconds. Crazy. However, it did eventually sleep/wake by itself. When I closed the cover and then opened it, it instantly awoke. So it seems like after the device has been sleeping for a while it just takes it a bit to wake up. Of course you can just hit the power button, too..
Click to expand...
Click to collapse
With WiFi set to stay on during sleep it works fine even during very long sleeps, like overnight. It's almost a non-issue for me since I always have WiFi on and if I go out I just remember to toggle it off or turn on tethering on the trusty old N4.
negroplasty said:
With WiFi set to stay on during sleep it works fine even during very long sleeps, like overnight. It's almost a non-issue for me since I always have WiFi on and if I go out I just remember to toggle it off or turn on tethering on the trusty old N4.
Click to expand...
Click to collapse
Yeah. All I know is I have the wifi set to not run during sleep, and all seems fine, - just that it takes the Nexus a good number of seconds to come alive after it's been asleep a while.
I decided to wait patiently and see if it would wake on its own. It did but took a full 20 seconds. On my first gen N7, it woke instantly every time. Hopefully it's something they'll eventually fix.
Sent from my Nexus 7 using xda app-developers app
RKight said:
I decided to wait patiently and see if it would wake on its own. It did but took a full 20 seconds. On my first gen N7, it woke instantly every time. Hopefully it's something they'll eventually fix.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
lol should start a contest! Whose Nexus 7 2013 takes the longest to wake up?!
Same for me.
I noticed if WIFI is ON, or device is connecting to power/USB. The wake will works perfectly and instantly.
But if WIFI is OFF or not USB connection, the wake is not function after closed the cover for few seconds.
WilliamG said:
lol should start a contest! Whose Nexus 7 2013 takes the longest to wake up?!
Click to expand...
Click to collapse
mine...mine...
Last night (I timed) it took 30seconds.
This morning (1st wake of the day, didn't exactly timed) it was more than a minute.
USPS has had my replacement "out for delivery" since early yesterday ... but never made it.. talk about the
organization in trouble... I usually see the man parking his truck in the shade, taking his time.
hyperxguy said:
mine...mine...
Last night (I timed) it took 30seconds.
This morning (1st wake of the day, didn't exactly timed) it was more than a minute.
USPS has had my replacement "out for delivery" since early yesterday ... but never made it.. talk about the
organization in trouble... I usually see the man parking his truck in the shade, taking his time.
Click to expand...
Click to collapse
That's impressive! I'm sure it's a bug that affects all Nexus 7 2013 devices, but it's still lame.
For anyone having this issue, I found a thread on the Google product forums about this. That's apparently how they became aware of the other issues that have been reported. If you could, please post your problem in this thread: http://productforums.google.com/forum/m/#!category-topic/mobile/android-devices/8MTpqfFmw8Q
Sent from my Nexus 7 using xda app-developers app
Are we sure this is actually an issue? Based on the threads I'm reading about this, the cover only seems to wake the screen when you open it while things are running that would normally keep the N7 out of deep sleep. Isn't the tablet being able to enter deep sleep mode successfully a good thing?
The reason I say this is because a lot of you, including myself are reporting that when Wifi is off, and the tablet is unplugged, opening the cover won't wake the screen if it's been closed for a long time but it will after just short periods. This indicates deep sleep being entered successfully. If the cover is able to wake the screen in that mode, I'd be more worried that deep sleep mode isn't being entered successfully.
I guess the main question is: Is 4.3 along with the Nexus 7 hardware actually designed to only be able to be powered on by the power button itself during deep sleep? Do not services have to be running in the background constantly in order to allow something else to wake the screen? For example, in order for one of those 3rd party screen apps that use either proximity sensors, or light sensors or position sensors (shake) in order to wake your screen to work, all of the better ones I've seen not only require administrator permission, but also running background services.
In other words, they use the hardware sensors inside the Nexus 7 to wake the screen but also require some kind of additional resources running in the background. Which means resources being consumed. Smart covers also use hardware inside the N7 to wake the screen but without an app consuming resources in the background to so do. Which means NO resources consuming battery or memory, which is a good thing.
I'm not so sure I even WANT this fixed if it's going to mean my tablet has to have stuff running in the background in order for it to work. If Google can make it so that's not the case, then I have no problem with it. I could be completely wrong as well, I'm just speculating so if Google says it is actually a software bug then I guess I am.
omnius1 said:
Do not services have to be running in the background constantly in order to allow something else to wake the screen?
Click to expand...
Click to collapse
I guess that depends on the magnetometer chip they are using. If it can generate an async interrupt on a change in magnetic field, then that is one thing, if it has to be polled, that's something else. I don't find it too great a hardship to occasionally have to press the button, so if it is doing this to save more power, that suits me.
I think this thread is about all the "odd" things happening, specifically to the some 2013 Nexus 7 (some people don't have this problem).
I also have the 2012 N7 and the Nook HD+ with smart covers, both are running JB4.3.
Both can go into deep sleep and whatever (wifi on/off, things running or not) and will wake up in an instant as normal.
This is not normal !!
By the way, I received the replacement and similar results. I didn't expect it to fix the issue anyway as I think this is similar
to the tough issue with some N7s (I don't have this issue) which is a google problem.
A little off-topic about deep sleep... my Nook HD+ can sleep for a whole day and only take 1% of the battery.. best I've seen.
Edit: just in case somebody thinking about a ROM problem, I've tried multiple ROMs including stock.. all have same issue.
Moko smart cover is the best
It should wake up within a second, at worst, period. Ideally it'll wake up "almost instantaneously". There's something wrong.
I wish the mods would merge these two threads so the nonsense is at least in one place.
Mine sometimes will wake after a delay and will sometimes just sit and do nothing at all until I press the power button. It has turned on after a 30 second delay, after being idle all night, but has also completely failed to turn on after being idle for just five minutes. This thread is definitely aimed toward the odd inconsistences and what I indeed perceive to be a problem.
Sent from my Nexus 7 using xda app-developers app

Some issues on my LgV20

Hi, my phone version is Lg V20 H990DS, software version V10c-TWN-XX and
1) daily I'm noticing a large data usage by OS Service (I find out that in My Data manager app). Why?
2) When I connect my bluetooth headset for audio I don't hear enough loud when I set at maximun level. (My previous Note 4 gave in my headset a louder sound). Why?
3) When I play a clip and I set at maximum​ level and after I play a second clip the volume is set at a lower level automatically.
Do you have the same issues and eventually how did you fix them?
Sent from my LG-H990 using Tapatalk
I'm having bluetooth issues with mine , also it takes awhile for the GPS to lock on to my location. This seems to be an ongoing issue because I also encountered the GPS issue with my G3.
enigmaco said:
I'm having bluetooth issues with mine , also it takes awhile for the GPS to lock on to my location. This seems to be an ongoing issue because I also encountered the GPS issue with my G3.
Click to expand...
Click to collapse
I haven't had any GPS issues with the V20. My note 4 was slow and dropped occasionally, but the V20 has been good for me and my wife.
Sent from my LG-H918 using Tapatalk
Some reason with my nexus and the samsung I had it would lock on in seconds. With my v20 it takes up to a minute. Do you leave it on all the time.
Yes, but when I come out of the building it doesn't see anything. But it locks within 10-15 seconds after that.
Sent from my LG-H918 using Tapatalk
Yeah but its still pulling location data from wifi and mobile. Have it off for awhile completely turned off and turn it back on and see if it connects that quickly.
enigmaco said:
Yeah but its still pulling location data from wifi and mobile. Have it off for awhile completely turned off and turn it back on and see if it connects that quickly.
Click to expand...
Click to collapse
Ok I'll try it when I get home.
Sent from my LG-H918 using Tapatalk
enigmaco said:
Yeah but its still pulling location data from wifi and mobile. Have it off for awhile completely turned off and turn it back on and see if it connects that quickly.
Click to expand...
Click to collapse
Sorry I forgot to do this Friday. I just checked and mine gets GPS lock very quickly. Have you checked any connectors on the back of the device? I know on my old note 4 the connectors had a terrible connection until I bent them a bit so it touched better.
Sent from my LG-H918 using Tapatalk

Categories

Resources