Hi.
I'm new to Nexus 7 and after a short time using it I began experiencing some strange issue with the it. While surfing the web over WiFi (note that I'm using the first Nexus 7 with WiFi only) after a short time glitching lines appear on the screen (as shown on the image attached) and some loud white noise coming from the speaker. It's stuck like this for about 30 seconds and then reboots. After reboot, everything seems normal, till it comes again. It takes 15-30 minutes of surfing and I believe the time depends on the intensity of surfing. Seems like WiFi modem somehow affects the GFX driver.
Note that I was first running android 4.1.1 and recently updated to 4.2. Updated didn't fix the problem. I've rooted the device with "Nexus 7 root toolkit v.1.5". Note sure if the rooting affected it somehow, as I rooted the device on second or third day of use.
Anyone have an idea of what could be wrong or how I might fix it? Or it's HW issue and I should turn it to Google?
Thanks!
So I'm the first and only one with such problem???:silly:
I could be wrong here but that seems like more of a hardware(warranty) kind of issue. However, I had the speaker issue after flashing a custom ROM (sparks linario 4.2.1) and I had the speaker issue (along with a host of other bugs buts that's beside the point). I flashed stock and unrooted and the problem was fixed... I know it might not help your case but I thought ide let you know. Its possible the toolkit caused the issues and flashing back to stock and rooting with another method may solve your issue (that's what I would try). But if you end up sending it in under warranty for god sakes, unroot and relock your bootloader first! Otherwise Google probably won't honor your warranty.
Good luck friend.
Sent from my Nexus 7 using xda app-developers app
Related
Does anyone else experience the sleep of death bug (akin to what happened with Netflix) after having connected your HDTV through Slimport for a short while? It seems to happen regardless of what I'm doing on my phone, just having it connected for a short moment will cause it.
This is on stock Android 4.3 (JWR66V), whereas it was working just fine for me on 4.2. My phone is rooted, but there's nothing running that requires root access while this problem occurs.
Also, I'm using the "official" Slimport adapter, i.e. the only one that existed for quite a while.
Would hate having to send my phone back in, but alas that's what I'll do if it's just affecting me.
I've the same issues since 4.3 Everything was fine before with 4.2.2. When i unplug slimport from nexus4 i cant activate display anymore.
This hapepns sometimes after cahring, too.
So i think your device is ok, just an 4.3 fault like many other bugs
Thanks for the reply. So I'm not completely alone with this!
But I do find it odd that I could not find any existing discussion of this topic elsewhere on the net.. are there just not that many people making use of the HDMI feature or is the majority of people simply unaffected by this problem?
I'm not sure. I've the same issue with charging. I misspelled this on my first post. Same situation, unplug charging cable and i can't activate the display. I found a workaround for this issue, I unplug it only when the display is on. The latest OTA doesn't fix it. Maybe we should create a bug report on googles bug tracker.
There is a thread about this issue in Googles mobile support forum. You should post there, too. So maybe we get more attention about this serious problem. I can't post links yet, search for: "After 4.3 Android updated, the Nexus 4 always shuts off randomly !!! HELP!!!"
I'm having this issue with my Nexus 7 II. Very annoying, can't watch a movie without it disconnecting. Any fix for this?
Currently not, I hope that Kitkat will fix this
I'm having the same problem on 4.4
Does anyone know how to fix this?
Thanks in advance
Same here on 4.4 but it only happens when my photo is low on charge.
E.G when there's low charge slimport works o.k but when I unplug it the phone dies and requires me to push the power button for 10 seconds to get the photo to work again.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Maybe we should dump Logcat to get the reason why it dies. It tried it several times but with no luck. When i received System log ouputs via adb, the phone doesn't die.
Gesendet von meinem Nexus 4 mit Tapatalk
was found a solution for this problem?
Helllllo everyone!
So I apologize for being one of those people who just come here to ask questions. Unfortunately life doesn't have room for me spending time playing with my Android devices anymore, so having it 'work' is more important to me.
I am on 4.3, ParanoidAndroid 3.96. I am not on the latest because it took some time to have the app TouchControl work (with my Franco kernel), and Secure Settings etc. that I chose to just stick with it because it worked really well for me.
The problem!
I recently noticed that if I tried to switch to the front facing camera, it'd hang. After that, I would not be able to use my torch/led, and going into the camera would tell me that "The camera is not connected" or something like that. I could only fix this by clearing all the data on my Gallery, and shutting down, and then turning on again. Reboot would not work.
If I did that, I could go into my camera and use the rear camera fine. Take pictures, record video, etc. Torch works as normal. It's just that once I attempt to go into the front camera, this problem happens.
It's weird because I didn't flash anything or change any settings when this happened. I DID install https://play.google.com/store/apps/details?id=eu.mrogalski.saidit which wouldn't let me record a video while being used, but I since disabled/uninstalled it which solved that problem.
I have done a lot of googling on this problem, and noticed that I am not the only one who has this problem. For some people it seems like their phone is new, and some it just happens out of nowhere. For that reason I suspect it might be a hardware problem that can occur randomly, but it's weird that after triggering the problem, that my torch won't work anymore as well. Unless the torch is somehow tied to the camera/flash, and by triggering the problem when I try to access the front camera, it isn't able to 'call' the camera/flash anymore as a result?
I bought my Nexus 4 from Google in May 2013, so I believe I still have until May 2014 to RMA it, correct? Would I get another Nexus 4 at this point, or maybe I'd get a Nexus 5 instead?
Thanks in advance for any insight into my problem!
I know you would like to keep the rom you are on but to be on that rom you must have a custom recovery installed. So if I was you I would back you're rom up then flash something different to see if its hardware related or not . If so then return the phone.
Sent from my Nexus 4 using XDA Premium 4 mobile app
bladebuddy said:
I know you would like to keep the rom you are on but to be on that rom you must have a custom recovery installed. So if I was you I would back you're rom up then flash something different to see if its hardware related or not . If so then return the phone.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the reply.
I tried installing the latest PA rom, but came up with an error. I had the rom I was on originally still, so I tried wiping and flashing it again. Finished flashing, went and opened the camera and it still happened. Looks like it's a hardware problem then!
I guess I'll go look up a guide to flashing back to stock now.
I know this has been discussed before but I am also having issues with my Nexus 7 2012 Wi-Fi microphone and they do not appear to be connected to an (obvious) hardware issue. I had this issue some months ago when I had upgraded it to Lollipop OTA (5.0.2 to 5.1.1 turned to be completely slow and buggy messes for me, but I digress). The mic suddenly stopped working and no app could hear me when I spoke so I handed it in for a warranty repair (lucky me, it was on the last day before my warranty expired after 2 years!). I got the tablet back after a fortnight and the mic was working absolutely fine. Seeing as how my warranty had now expired, I decided to unlock my tablet (via Nexus Root Toolkit) and install good old smooth-running 4.4.4 on it. I had no issues for a lot of time, but recently I decided to flash 5.1.1 on it, just to see if it's usable on it. Of course, it was a lot slower than KitKat but before I got around to flashing it back, I realized my mic had stopped working again! Restoring my backup of 4.4.4 had no effect on the microphone so I took drastic measures and reflashed everything with Root Toolkit. The microphone actually started working after flashing 4.4.4 (I think the bootloader was involved as well) and then I restored my backup of the same Android version and the microphone kept on working. After a day or two it stopped again! I thought I had messed it up by using Xposed Framework (I had updated some modules on it) and I went over the same procedure again, seeing as how factory resets and backups had no effect whatsoever. After reflashing and restoring my backup I decided not to do anything with the tablet. The mic was working but... it stopped again, for no good reason a day later. The only thing that seems to (temporarily) fix it is reflashing KitKat in the Toolkit. I even tried disassembling the tablet and unhooking the mic module and putting it back in but to no avail.
I think it's a software related issue, seeing as how a simple reflash fixes the microphone but then it stops working again. Attempting to mess with it on the hardware side does nothing. Anyone else experienced the same problem? Anyone found a permanent fix for it? It kind of my makes my tablet unusable on day-to-day basis, since I use Skype and whatnot on it.
Thanks in advance!
Hi guys.
I'm here to share a problem I'm having with my Nexus 6P: it often gives a crash randomly, needing to be restarted by force.
This does not happen because of a specific app and sometimes happens even at boot , when Google logo still not appeared.
I already using the phone about two weeks.
I received him with rom stock 6.0.1 and had the upgrade to Nougat available.
I thought the upgrade to 7.0 would correct the problem, but it was not what happened.
From the update I also felt that the crashes were more frequent when the battery was at a very low level, between 20 and 15% (as commented in a reddit threat that I can't copy here).
Following some recommendations that I found , I formatted the Nexus 6P with the factory settings to see if the problem returned.
Yes, it happened again.
I formated again and was gradually installing my apps to check if it was not a specific app.
I did it at last three times.
On these occasions, apps like Google Keep, Duolingo, ES File Explorer, Google Fit, Podcast Republic and even the Play Store gave the crash.
I formatted again and installed each app one by one again to try to identify a culprit and had the same results.
To try to work around the problem, I decided to go for a clean install of the entire OS with the latest build using the SDK (adb and fastboot).
Even with the flash of the latest build I continued to have this crash problem.
So I decided to go for custom roms.
I installed Pure Nexus and Sinless, and continued having problems with crash.
I tried to install the CyanogenMod, but failed. After flashing the rom, GAPPS and vendor image, the device crash in the Google logo.
My last attempt was to go deeper and replace the kernel as well.
I installed ElementalX (7.0) and Pure Nexus as ROM.
In the beginning, I still had many crashes, so decided to make some changes in the kernel ElementalX.
In a desperate attempt, I decreased the CPU clock all to minimum (1248 MHz).
Interestingly the crashes started to occour less frequently, but they still happen randomly and unexpectedly.
I have no idea if this reduction in CPU speed had any effect or was placebo.
What matters is that I'm still having crashes and I wonder if anyone has any idea of this solution to my problem.
Thank you guys!
PS.: the return of the phone is not an option. I'm in Brazil.
PS2.: sorry for my bad english.
Wow you have exhausted every idea... Return sounds like all that's left unless you wanna try putting the phone in the oven to see if it's just bad solder.
Sent from my Nexus 6P using Tapatalk
I'm thinking you've got some damaged or corrupted internal storage there.
Sent from my Nexus 6P using Tapatalk
Hello.
My friend got a nexus 6p one year ago. One month ago he started to have problem. He was on stock rom
-First when he pressed the touch screen he heard small weird noises (hard to describe)
Then progressively :
-Speaker stopped working
-he could not play youtube video in you tube app : a weird error message (every time different) appeared. Gallery videos don't work as well
-But weirdly enough video played in the web browser including youtube videos, works, still without sound.
-He cannot make calls
-Jack plug doesn't works either, but he can use his Bluetooth headphones
We tried to install a custom rom (lineage os). We succeeded, but the above problem appeared again.
Then we flashed the factory image [url]https://developers.google.com/android/images[/URL] for nexus 6p. We also succeed but the above problem appeared again.
Thanks in advance for your help
ilininja said:
Hello.
My friend got a nexus 6p one year ago. One month ago he started to have problem. He was on stock rom
-First when he pressed the touch screen he heard small weird noises (hard to describe)
Then progressively :
-Speaker stopped working
-he could not play youtube video in you tube app : a weird error message (every time different) appeared. Gallery videos don't work as well
-But weirdly enough video played in the web browser including youtube videos, works, still without sound.
-He cannot make calls
-Jack plug doesn't works either, but he can use his Bluetooth headphones
We tried to install a custom rom (lineage os). We succeeded, but the above problem appeared again.
Then we flashed the factory image [url]https://developers.google.com/android/images[/URL] for nexus 6p. We also succeed but the above problem appeared again. Thanks in advance for your help
Click to expand...
Click to collapse
The 6P has two speakers, and they wouldn't both fail at the same time. Sounds like he's damaged the phone somehow. The audio jack and speaker output both not working seem to back this up. I've seen the headphone jack part available separately, and there are guides available to replace it. Before flagging it as a hardware issue and opening the phone up, you want to make sure you wiped the phone completely by formatting the partitions (system, userdata, cache) and use the flash-all.bat included with the full Google image. There is a remote chance it is software related, but I doubt it.
You could always flash a custom kernel, use a kernel manager app to turn off the large core cpu and see if the problems go away. If they do its related to the build problem that causes the 6P to boot loop but those particular symptoms aren't familiar. It's still worth a try if flashing the stock image doesn't fix the problem.
jhs39 said:
You could always flash a custom kernel, use a kernel manager app to turn off the large core cpu and see if the problems go away. If they do its related to the build problem that causes the 6P to boot loop but those particular symptoms aren't familiar. It's still worth a try if flashing the stock image doesn't fix the problem.
Click to expand...
Click to collapse
You mean disabling the big CPU ?
ilininja said:
You mean disabling the big CPU ?
Click to expand...
Click to collapse
Yes. You can always turn it back on but turning it off apparently fixes the permanent boot loop problem on the Nexus 6P. If the problems you are describing are related to the same build problem then turning it off might make them go away. Sometimes people's phones would start acting odd before going into the permanent bootloop. That phone could be on its way there.
this is purely a guess but the problem may be hardware related with the headphone jack. it could have a physical short somewhere. if thats the case the device may think a headphone jack is being used and wont play through speakers because its being told its plugged in. But wont play because of some physical short or an open.