Hoping someone can help me out with a serious ongoing problem I've been having with my N7.
I'm getting random reboots where the screen will go blank - all black, or one colour with lines, will be completely unresponsive and will either stay like this until I do a reset with a long press of the power button, or reboot itself after about 30 seconds. The reboot is often accompanied by a loud buzzing from the speaker.
It will then get caught in a bootloop between the Google screen and the boot animation.
It seems to be related to the battery somehow because it doesn't happen when I'm plugged into the charger or connected to an external battery pack.
I'm almost certain it's a hardware rather than a software issue as I've tried a full wipe and ROM restore to no effect.
I'm wondering if someone could help me out with diagnosing or some advice.
Is this a warranty case or something I could fix easily, etc?
Thanks in advance for your help.
Sent from my Galaxy Nexus using xda premium
Are you overclocking, undervolting, or using a non-stock kernel?
If so, restore stock to your N7 for a while and see if the problem persists.
If the problem persists after that it probably is hardware as you suggest. (Even mildly-overclocked/undervolted default settings in a kernel could theoretically cause instability problems for a small fraction of processors - so you need to eliminate that as a possibility by running stock for a while.)
You might actually want to go so far as to restore the lock state of the bootloader after you restore to stock; that way, if things get worse and your warranty period has not yet expired... well, you get the idea...
good luck
Running the latest 'stable' PA and M kernel with default settings as far as clocking and volting AFAIK.
I will try returning to stock unlocked though to eliminate the possibility of some incompatibility between my device and custom kernel.
Thanks for the suggestion.
Sent from my Galaxy Nexus using xda premium
I am facing same issue with me but since its in under warranty i am going to RMA it with asus, but i lives in india its not yet launched in india & bought from USA so i dont know i may or may not get battery replacement.
Does anyone know if popping off the back to look inside would break warranty?
Sent from my Galaxy Nexus using xda premium
heccubusxda said:
Does anyone know if popping off the back to look inside would break warranty?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
No unless & untill you open it without letting them know so open it carefully , There are various videos on youtube on how to open back cover of Nexus 7 .
Related
I'm running stock rooted with latest trinity kernel and having touch response issues when the tablet is under heavy load and heats up. Screen off then back on fixes temporarily but trying to figure out if there is a way to improve touch response. Anyone have suggestions? It seems like a software problem due to the fact it comes and goes but I'm not sure if I had the issue on stock kernel or not. Anyone experiencing any similar issues and what are the solutions if any? Thanks for the assistance its always appreciated.
Sent from my Nexus 7 using XDA Premium HD app
edited: I contacted Google and they told me it is a known hardware defect and they initiated a return. I will get a new device in 3 - 5 business days and then have to send them the defective one through UPS. This was the only issue with my first Nexus 7, no screen bleeding or dead pixels or lifting. I am extremely disappointed that the touch response became such a problem because everything else about the device is beyond my expectations. Hopefully the next one will be perfect.
I'm new to the whole Android thing but I used to install lots of roms on my trusty old Windows Mobile devices over the years. I remember then that trying out different roms sometimes meant things would stop working.
Here's my problem. I have a Nexus 7 and it works fine on stock unrooted 4.1.2. I think. I've used the Nexus Root Toolkit to (very easily) unlock and root it. When rooted on stock rom (4.1.1 or 4.1.2), it takes a couple of seconds to turn on from sleep, sometimes needs to reboot, sometimes the gyroscope/acceslerometer locks and doesn't work as it should...
Is a rooted Nexus 7 less stable/reliable than an unrooted one?
littld said:
I'm new to the whole Android thing but I used to install lots of roms on my trusty old Windows Mobile devices over the years. I remember then that trying out different roms sometimes meant things would stop working.
Here's my problem. I have a Nexus 7 and it works fine on stock unrooted 4.1.2. I think. I've used the Nexus Root Toolkit to (very easily) unlock and root it. When rooted on stock rom (4.1.1 or 4.1.2), it takes a couple of seconds to turn on from sleep, sometimes needs to reboot, sometimes the gyroscope/acceslerometer locks and doesn't work as it should...
Is a rooted Nexus 7 less stable/reliable than an unrooted one?
Click to expand...
Click to collapse
Rooting doesn't make a difference on stability (or shouldn't)
All rooting does is give you admin rights to parts of the phone not accesible without rooted. Basically...
Customer ROM's for the Nexus at the moment (and sorry about this devs but its true) are not yet up to par with the Stock ROM.
Its stable pretty fast and not bad with battery.
Hope this helps.
Right so after lots of erratic behaviour with rooted stock 4.1.2, I unrooted and relocked the boot loader. It was better already but I've also run the Forever Gone thing and it's now working perfectly.
I would like to root again but not at the expense of stability. I had previously use the Toolkit if it makes any difference.
littld said:
Right so after lots of erratic behaviour with rooted stock 4.1.2, I unrooted and relocked the boot loader. It was better already but I've also run the Forever Gone thing and it's now working perfectly.
I would like to root again but not at the expense of stability. I had previously use the Toolkit if it makes any difference.
Click to expand...
Click to collapse
Rooting and/or unlocking the bootloader will have no direct effect on stability. What you do with your device after rooting is entirely a different issue.
Wilks3y said:
Rooting doesn't make a difference on stability (or shouldn't)
All rooting does is give you admin rights to parts of the phone not accesible without rooted. Basically...
Customer ROM's for the Nexus at the moment (and sorry about this devs but its true) are not yet up to par with the Stock ROM.
Its stable pretty fast and not bad with battery.
Hope this helps.
Click to expand...
Click to collapse
This would be true if it weren't a Nexus device. We can more or less compile the same ROM that Google shipped. CyanogenMod 10 in my experience has been rock solid stable, though obviously there are still some bugs, I have encountered none. I also used EOS for a little, and that was equally great.
littld said:
Is a rooted Nexus 7 less stable/reliable than an unrooted one?
Click to expand...
Click to collapse
Nope.
IF you flash a non stock rom and/or kernel, then it depends on what you use. Read notes and user replies.
Sometimes I do get random shut downs when not in use, both while charging and not charging. I am not sure if that is a 4.1.2 issue or if it's tied to the rom I'm using. Have had it happen on two different roms.
alkemist80 said:
Nope.
IF you flash a non stock rom and/or kernel, then it depends on what you use. Read notes and user replies.
Sometimes I do get random shut downs when not in use, both while charging and not charging. I am not sure if that is a 4.1.2 issue or if it's tied to the rom I'm using. Have had it happen on two different roms.
Click to expand...
Click to collapse
I lost the ability to control the music app with my headphone controls after rooting, it didnt happen when I opened the box and played with the nexus
Some apps are written to block rooted devices but there's no way the mere act of unlocking and rooting would affect overall stability.
Sent from my Nexus 7 using Tapatalk 2
After a day on stock rom I thought it was settled but no...
The battery drained down and after that it kept getting stuck at the Google Cross animation. I spent a while re-flashing stock rom and eventually it starts up. Sometimes. The accelerator issue remains but it is less frequent.
I contacted Google who put me on to Asus. They are going to send me an RMA number and we'll take it from there.
how do you revert or reset to a factory state???
I´m new with the nexus 7 so really have no clue
To reset your device, go to "settings", then "backup & reset", and finally "factory data reset".
The difficult in waking is something I went through with my N7. I found there is a bug with the auto-brightness setting. If I use the manual option I don't experience any problems.
I rooted my N7 the day I got it (had experience with SGS and Gnex) and haven't looked back. I haven't had any other issues than the "sleep of death".
Hope this helps.
alankstiyo said:
how do you revert or reset to a factory state???
I´m new with the nexus 7 so really have no clue
Click to expand...
Click to collapse
Bit Banger said:
To reset your device, go to "settings", then "backup & reset", and finally "factory data reset".
Click to expand...
Click to collapse
If you mean stock non rooted, then the above will set you back to factory.
If you are rooted, that will not remove the root. You will need to flash a stock image to completely return to stock and then re-lock the bootloader.
I seem to have had more problems if the power runs down. I have turned off the auto brightness and I agree it's better in terms of starting up. I still have the issue with rotation not always working. Also, I notice it takes several seconds for the screen to come on when I press the power button. Is that normal?
littld said:
I seem to have had more problems if the power runs down. I have turned off the auto brightness and I agree it's better in terms of starting up. I still have the issue with rotation not always working. Also, I notice it takes several seconds for the screen to come on when I press the power button. Is that normal?
Click to expand...
Click to collapse
No, that is not normal, whether you're rooted or not.
Sent from my Nexus 7 using xda app-developers app
alkemist80 said:
If you mean stock non rooted, then the above will set you back to factory.
If you are rooted, that will not remove the root. You will need to flash a stock image to completely return to stock and then re-lock the bootloader.
Click to expand...
Click to collapse
will the toolkit help me do this???
if so will it delete the sd card??
Sent from my Nexus 7 using xda app-developers app
Okay now it's getting weird. I got an RMA number and they are due to collect it tomorrow and fix it. Since I got the RMA number it has behaved perfectly. I did make a video of the problems but since making the video I've not been able to reproduce them. The battery is down to 14% now, will see what happens when it is fully drained. One major difference is the power button instantly switches the device on whereas it used to wait a few seconds.
Can hardware just fix itself like that? I'm concerned they'll get it and say they can't detect any problems and charge me for the shipping...
I'll keep on testing until morning but if you guys have any ideas please let me know.
alankstiyo said:
will the toolkit help me do this???
if so will it delete the sd card??
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I've used Wug's toolkit to return to compete stock. It will wipe everything. It's a two step process, you will still need to lock the boot loader. Go read the thread in the Android development section.
Sent from my PG86100 using xda app-developers app
It's fine, even rooted so have cancelled the RMA. Hopefully it was just a short term fluke.
Several weeks on I have had no more repetition of these problems. I did have a line flicker occasionally before installing 4.2 but even that problem has gone away now. I just don't understand how the behaviour can be so unpredictable like it needed to settle into its new home or something.
When taking pictures in low light situations with flash (it seems low battery enhances the probability) sometimes the pictures get artifacts (white lines close to the top/bottom of the picture).
And sometimes the phone gets stuck and reboots. The camera tends to make clicking noises right before it reboots that are louder than when usually focusing.
Look at the screenshot and at the end you can see the reboot. You can see a sudden battery level drop after the reboot.
I don't know if this is hardware or software related but a user suggested this to be a problem with the stock camera app.
I had this problem on two devices already and it seems to be on all devices, maybe just rarer for some people? Not sure.
If you have this problem vote for the following issue and hope google fixes it:
http://code.google.com/p/android/issues/detail?id=49702&#makechanges
I had something similar happen to me once last week. I was viewing my photos in the stratosphere mode and would hit the back button. I had to repeatedly do this to scroll to the next images after viewing them. When hitting the back button it would take me back to take a picture, but one time, it took me to a blank screen with the camera buttons still working. I ended up needing to restart my phone. Not sure what happened there.
I have only seen this once. It didn't occur again, so I haven't chased it down
Ditto only happened once in the first week of using and has never happened again
Sent from my Nexus 4 using Tapatalk 2
AW: Reboot while in camera
Kinda sucks when it happens randomly, today it happened twice to me and that in 4.2.2!
Sent from my Nexus 4 using xda app-developers app
I also have it, but less frequent, about one or two times per month. It happened on 4.2.1 and no one could solve it in my thread about this .
Facing the same issue more frequently
ruzkay said:
While taking pictures my phone suddenly got stuck and rebooted. This is the second time now. My camera makes strange click noises sonetimes wheb focusing but that seems to be normal.
The device was a little hot but not as hot as when in gaming and in gaming it never reboots.
Look at the screen shot and at the end you can see the reboot. What I'm worried about is the sudden battery level drop after the reboot.
Are these reboots hardware or software related? Should I get a replacement?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I seem to have the same issue. So far, it has only occurred when I am trying to take a photo with the flash on. One more observation: seems to happen more often if the battery is low. However, both of us might be having defective devices, as it doesn't seem to be a common issue looking the forums here.
No solution found so far. Tried a factory reset. Tried using another camera app. Nothing helped. Might try flashing a custom ROM.
AW: Reboot while in camera
sumit29 said:
I seem to have the same issue. So far, it has only occurred when I am trying to take a photo with the flash on. One more observation: seems to happen more often if the battery is low. However, both of us might be having defective devices, as it doesn't seem to be a common issue looking the forums here.
No solution found so far. Tried a factory reset. Tried using another camera app. Nothing helped. Might try flashing a custom ROM.
Click to expand...
Click to collapse
All oft the things you described apply to my situation too. Also I noticed that pictures tend to have artifacts (white stripes close to the top/bottom). They always have the same distance from top/bottom but their length differs.
Also after the forced reboot there sometimes appears an extra picture in the gallery that is fully grey.
Sent from my Nexus 4 using xda app-developers app
I don't seem to have the artifact problem that you described. Also there is a creaking sound sometimes just before it restarts.
Have you tried flashing a custom ROM? Did it help? Otherwise RMA is possibly the way to go.
I ordered the phone from US using a mail forwarding service, so an rma will cost me another $100 or so. If you or anyone else can confirm that it is definitely a hardware issue which can be resolved by getting a replacement, i might go for it.
Sent from my Nexus 4 using xda app-developers app
sumit29 said:
I don't seem to have the artifact problem that you described. Also there is a creaking sound sometimes just before it restarts.
Have you tried flashing a custom ROM? Did it help? Otherwise RMA is possibly the way to go.
I ordered the phone from US using a mail forwarding service, so an rma will cost me another $100 or so. If you or anyone else can confirm that it is definitely a hardware issue which can be resolved by getting a replacement, i might go for it.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I was on AOKP PUB Krait 05/02 by Stevespear and Harsh Kernel and I did have a reboot there once too. Also this is already my third Nexus 4 since I had to replace it 2 times due to issues (bottom side creaking 1st device / yellow blotches 2nd device) and this one really looks good only this camera reboot issue is left.
But my first phone did have the issue too, I didn't have the 2nd phone long enough so didn't see it happen there. I have no idea if it is a hardware or software issue but my bet is that all Nexus 4's have that issue.
It just seems that it appears rather rarely and most people don't notice it. Or it could be that the voltage is too low and that would explain why it happens on some phones more than on others since not all chips are equal. I was wondering if somehow setting the flash to be weaker so it draws less power would solve this. But I am just a user and don't really have an idea.
PS: I won't get my phone replaced since I can live with this issue (it happens rather rarely) and I went through 2 replacements to get this device which is close to perfect but I wouldn't mind if someone came up with a solution.
That makes me feel really lucky to have gotten a nearly perfect device. Anyway, guess we just have to live with it then. Lowering the flash intensity sounds like a good idea. Will check if some rom/kernel/app can do it for me.
Sent from my Nexus 4 using xda app-developers app
Just added issue 49702 on code.google.com. whoever is facing this problem, add your comments.
Sent from my Nexus 4 using xda app-developers app
Having the same problem here on 4.2.1 and 4.2.2. I think it might be the buggy stock camera/gallery app because I can't replicate the problem on the Camera Zoom FX app.
Edit: I remember having this problem on 4.2.1 and then clearing the gallery app data and not ever seeing the issue happen again. I will try the same on 4.2.2 and see if it fixes it too.
I added a link to the issue on OP guess that is all I can do.
sierratango88 said:
Having the same problem here on 4.2.1 and 4.2.2. I think it might be the buggy stock camera/gallery app because I can't replicate the problem on the Camera Zoom FX app.
Edit: I remember having this problem on 4.2.1 and then clearing the gallery app data and not ever seeing the issue happen again. I will try the same on 4.2.2 and see if it fixes it too.
Click to expand...
Click to collapse
I have had this issue with the Camera FX Zoom app also. So, at least in my case, I guess it's a hardware/camera driver issue. Anyway, I also cleared the gallery app data a few days back and haven't faced this issue since then, but haven't taken enough pics with flash to confirm that the issue is truly gone.
sumit29 said:
I have had this issue with the Camera FX Zoom app also. So, at least in my case, I guess it's a hardware/camera driver issue. Anyway, I also cleared the gallery app data a few days back and haven't faced this issue since then, but haven't taken enough pics with flash to confirm that the issue is truly gone.
Click to expand...
Click to collapse
Has the issue disappeared after clearing the app data for you? I certainly have not faced any reboots since doing it.
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
Not sure if new threads needed couldn't find a post to on it. Anyways my camera on the rear seems fine in daylight buy when the light drops I get loads of lines flickering. These show in picture below (on the roof top and bottom of windows right across the screen) . This is brand new phone (3 days old)
Should I take it back?
Sent from my SM-N9005 using xda app-developers app
Dont ...... take it back yet. The next device u will get most likely will have the same issue.
This particularity happens when the device is connected to a wifi network. Try again while disconnected from a wifi network.
I also have this problem and changed the device the same day i got it. Same issue tough.
JAMIE1000UK said:
Not sure if new threads needed couldn't find a post to on it. Anyways my camera on the rear seems fine in daylight buy when the light drops I get loads of lines flickering. These show in picture below (on the roof top and bottom of windows right across the screen) . This is brand new phone (3 days old)
Should I take it back?
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
i got those once too. I was in my house and now that i think of it i was connected to wifi. Is it possible that they overlooked such a huge bug?
I have the same issues yes.. I think this is a big manufacturer bug when you are connected on WIFI.. not cool samsung, hope you can fix it with a software update but I think its hardware related..
I read this too late. I took the device back today and I'm now on my second note. I have literally just got in the door and connected to my wifi. Haven't tested it on wifi yet but there was no lines in town in dimmed light.
Another reason I took it back was because I kept having unresponsive power and home key buttons.
This was temperamental but still an issue.
Just did the 2 updates from Samsung hopefully this one will be alright
Sent from my SM-N9005 using xda app-developers app
Just had a look while connected to wifi.. seems fine now.
Sent from my SM-N9005 using xda app-developers app
I had the same issue with my ex note 3. I guess all of them are same. I was almost killing shop assistant while trying to get new one. You will see the same lines when you are reacording.
Solution
I added a simple tasker rule to disable wifi and mobile data while the camera app is running. I also mutes the dial tone volume to get rid of shutter sounds...
This phone needs some patching until rooting becomes possible without loosing warranty.
I am so pissed at Samsung. Their hardware team created perfection only to be ruined by the monkeys who make their software
vgergo said:
I added a simple tasker rule to disable wifi and mobile data while the camera app is running. I also mutes the dial tone volume to get rid of shutter sounds...
This phone needs some patching until rooting becomes possible without loosing warranty.
I am so pissed at Samsung. Their hardware team created perfection only to be ruined by the monkeys who make their software
Click to expand...
Click to collapse
I couldn't agree with you more.. Very disappointing that I spend a lot of money on a device i believe to be probably the best on the market for it to be ruined by something as simple as taking pictures.
But. . Touch wood.. This one hasn't produced the same lines... It did however lock up one on the day i got it requiring battery pull.
@JAMIE1000UK what's your new phone's software version? Mine's still MJ1 and I'm guarding it like gold, because with this I still have some chance of rooting, when I gather up the courage...
I'm running mj7 too. I'm pretty much the same. . Holding back on root.
Having said that. When I took out the phone I got phones4u care with it.
Meaning I get a direct replacement no quarrels within 21 days of purchase so shouldn't be a problem.
Sent from my SM-N9005 using xda app-developers app
This is becoming a serious and annoying problem. Does anyone have a fix??? I hope it's not a harware issue...
Riqz said:
This is becoming a serious and annoying problem. Does anyone have a fix??? I hope it's not a harware issue...
Click to expand...
Click to collapse
People are reporting that it only happens when using the camera when using wifi.
I took the device back as I use my camera every day. The bloke in the shop knew exactly what I was talking about before I'd even shown him the images.
Must be something in the configuration. Our maybe just the camera module.
No idea. Id take it back on Warrenty.
My new replacement is Absolutely fine.
Sent from my SM-N9005 using xda app-developers app
vgergo said:
I added a simple tasker rule to disable wifi and mobile data while the camera app is running. I also mutes the dial tone volume to get rid of shutter sounds...
This phone needs some patching until rooting becomes possible without loosing warranty.
I am so pissed at Samsung. Their hardware team created perfection only to be ruined by the monkeys who make their software
Click to expand...
Click to collapse
There's a setting to disable the camera shutter sound, FYI
hfuizo said:
There's a setting to disable the camera shutter sound, FYI
Click to expand...
Click to collapse
no there isn't in many regional versions, such as the European Now that I am rooted, i could probably switch to a different region, but it would cause a factory reset, which I don't have time for currently
Sent from my SM-N9005 using Tapatalk
vgergo said:
no there isn't in many regional versions, such as the European Now that I am rooted, i could probably switch to a different region, but it would cause a factory reset, which I don't have time for currently
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Germany dbt
No sound at all (silent mode of phone)
hit 'thanks' if i helped you
SM-N9005 DBT-DMJ7 0x0
XDA Developers 4 premium app
i have that lines to, and i dont really care about it
its not worse as my old htc one :
I have these lines on my device. I haven't rooted yet as my device came with MJ6 firmware.
I read that the problem goes away on MK2 firmware:
jesper10 said:
Downloaded this tonight, haven't had the change to comment on battery life but one thing it does seem to have fixed is the issue I was having wit the camera in low light, the interference with wifi on seems to have disappeared now...no horizontal lines on screen
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=48585178&postcount=18
Can anyone else confirm this?
Mine happened on the original device I had after I'd fully updated it.
I'm on same firmware on the new device and I've never had the problem. Baring in mind that the phones arrived from same store on the same firmware probably from the same batch that they had delivered. .
Sent from my SM-N9005 using xda app-developers app