Nexus 7 2013 - Strange Accelerometer issue - Nexus 7 (2013) Q&A

Hi all,
Having a strange issue with the accelerometer on my 2013 Nexus 7, wondering if anyone has experienced this.
I must admit I need to do one further test which is return to stock but I'm skeptical it'll make a difference.
Whilst running a custom ROM the accelerometer just cut out of its own accord. I assumed it was a software issue so I did a clean flash of the same ROM. It was working fine again. Great. Except a few hours later all of a sudden it stopped again.
I've since flashed another 2 entirely separate ROMs cleanly and the exact same thing has happened every time.
Can't think what it could be, I assumed it was software seeing as it works briefly but now I'm not sure at all. Will try stock as soon as I can but thought I'd ask while I wait until I have a chance.

Related

[Q] Touch stops working for some letters

Hi folks,
I'm not sure what's up with my phone. I have CM10 beta on it and since earlier today the D button on the keyboard is completely unusable. Also, I have a hard touch hitting R. I have tried touching the same area in other apps and it seems to work fine. Maybe there's a tool out there I could use to confirm this?
I had this happen before on an earlier build of CM10. When it happened before (and as of now), rebooting doesn't fix it. Last time I gave up and just upgraded my CM10 ROM, and it has been working ever since (around a month or so).
Today, the touch screen experienced some "glitches". What I mean is, I took it out to use it and it seemed like it was detecting touch/drag events in various spots, and I had to put it to sleep to get it working again.
I have no idea where to start with diagnosing this. It doesn't seem to be a hardware issue, since re-flashing before fixed it. Any ideas?
Go back to stock, if you have the same problem then it will probably be hardware issues.
Sent from my One V using xda premium

[Q] A different kind of screen problem

I've had my HOX for about 4 months now, working like a charm, and doing what they say its supposed to do.. Now however, it has changed to an unusable brick..
I Rooted my phone about a month ago, and ran with a near stock ROM (I can't really remember what it is anymore), and about a week ago, I upgraded to the latest patches. The phone now has its own life, where it seemes like picture it tries to show, is distorted, unreadable, sometimes one of the three primary colors goes missing and it looks like it refreshes a small portion of the screen every second. The touch system still works fine, and if I could work it blind, it wouldnt be a problem.. I can get to recovery/fastboot without any problem, and if I reboot the phone, it works like it should from 10 seconds-1 hour. I've tried to restore to defaults, tried the Viper ROM, but nothing seemes to work. Also, if I lock the phone while it is doing the bug, I get the "dark screen" bug as well..
I suspect it must have something to do with the update, since the phone have been handled with great care, and not dropped on the floor/pressed hard on the screen. I'm now turning to you guys, since you know pretty much about this phone. I can take a picture with another phone to illustrate what its doing, if that helps, or my explenation is a bit vague.
so you actually tried to get the phone right back to stock? flashing a RUU?
matt95 said:
so you actually tried to get the phone right back to stock? flashing a RUU?
Click to expand...
Click to collapse
Yes, I tried that as well, but it didn't work as far as I could tell. It would last longer before it started to bug out, but it would happen still..
hmmm, well it could also be a HW issue...
matt95 said:
hmmm, well it could also be a HW issue...
Click to expand...
Click to collapse
It might be, but it would be so strange that it first came right after an update.. Might be some overheating that have caused bad connectivity on a lead, can be some plug that isnt right, but I have a sneaking suspicion that the update did this..
well if even the RUU didn't solve this then it could only be HW related... just one question, how could you run a RUU if there ins' any RUU for the latest update yet?

[Q] Touchscreen problems after update?

The touchscreen stopped working on the phone a few months ago and a few weeks ago, after the phone had been dormant for a while, I decided to check if it worked and it was fine. But after a software update it stops working when you leave the phone for an hour or two, but if you turn the screen off and then back on it works (make sense?) Anyway, I'm assuming this is a software issue and there has been another update since then, current firmware is 4.2.2 and HTC Sense is 5.0, and I can't see this being a hardware issue. It doesn't really bother me that much but I want to sell the phone and I want it to be working perfectly when I do (I was thinking of putting a disclaimer but I fear the issue might worsen or the buyer will miss it). I've looked around for similar issues but there doesn't appear to be any, for most people it is a continuous thing (but it happened for others after updates as well.) Does anyone have any fixes for me?
sirman2 said:
The touchscreen stopped working on the phone a few months ago and a few weeks ago, after the phone had been dormant for a while, I decided to check if it worked and it was fine. But after a software update it stops working when you leave the phone for an hour or two, but if you turn the screen off and then back on it works (make sense?) Anyway, I'm assuming this is a software issue and there has been another update since then, current firmware is 4.2.2 and HTC Sense is 5.0, and I can't see this being a hardware issue. It doesn't really bother me that much but I want to sell the phone and I want it to be working perfectly when I do (I was thinking of putting a disclaimer but I fear the issue might worsen or the buyer will miss it). I've looked around for similar issues but there doesn't appear to be any, for most people it is a continuous thing (but it happened for others after updates as well.) Does anyone have any fixes for me?
Click to expand...
Click to collapse
Have you tried resetting the OS (if you're on stock)?
If not tried flashing a new rom or reflash it?
Bobbi lim said:
Have you tried resetting the OS (if you're on stock)?
If not tried flashing a new rom or reflash it?
Click to expand...
Click to collapse
I tried after I made this thread but the problem continues to persist.
Try to flash a coustom kernel like Alex-Kernel, XM-Kernel or lONELyX...

Urgent and Serious issue with audio! HELP needed. please!

Guys, I have this one major issue with audio in my phone and its the rarest of the problems! The whole audio output stops completely. By completely, i mean even the receiver sound. completely dumb! cant hear anything if someone calls me. This has been occurring since a month or so. I am running on Cyanogenmod 11 M8. Even if i restart the phone its stays the same way. And all of sudden, randomly, the audio back again, working properly. when it goes dumb it stays like that for 5 6 hours. it happens quite often. this is throwing me off totally.
Device : Galaxy S3 SGH i747 - At&t
This problem happens:
1) when i am on call, suddenly it goes mute.
2) when the phone is kept idle for more than 3 4 hrs. So every morning its dumb when i wake up.
These are what I've tried and what I've found out:
1) I reverted back to stock 4.3 to check if its the problem with audio hardware. But in stock it worked perfectly and flawlessly. no issues there. SO its definitely got to do with cyanogenmod.
2) I flashed ktoonsez kernel on CM 11 M8, to check if its kernel problem. But its happening again. SO its not the problem with kernel.
3) I recently found out that if I wipe the cache from recovery, audio is back working. SO its definitely something in the cache thats messing with the audio. Some app may be.
this thread can be referred for more details on this issue:
http://forum.cyanogenmod.org/topic/81373-audio-stops-working-from-time-to-time/
and I dont know what else to do now. Ive tried uninstalling all the apps that access audio. But the problem still persists.
I really really need help fixing this one. PLEASE HELP.
s.vivekananda007 said:
Guys, I have this one major issue with audio in my phone and its the rarest of the problems! The whole audio output stops completely. By completely, i mean even the receiver sound. completely dumb! cant hear anything if someone calls me. This has been occurring since a month or so. I am running on Cyanogenmod 11 M8. Even if i restart the phone its stays the same way. And all of sudden, randomly, the audio back again, working properly. when it goes dumb it stays like that for 5 6 hours. it happens quite often. this is throwing me off totally.
Device : Galaxy S3 SGH i747 - At&t
This problem happens:
1) when i am on call, suddenly it goes mute.
2) when the phone is kept idle for more than 3 4 hrs. So every morning its dumb when i wake up.
These are what I've tried and what I've found out:
1) I reverted back to stock 4.3 to check if its the problem with audio hardware. But in stock it worked perfectly and flawlessly. no issues there. SO its definitely got to do with cyanogenmod.
2) I flashed ktoonsez kernel on CM 11 M8, to check if its kernel problem. But its happening again. SO its not the problem with kernel.
3) I recently found out that if I wipe the cache from recovery, audio is back working. SO its definitely something in the cache thats messing with the audio. Some app may be.
and I dont know what else to do now. Ive tried uninstalling all the apps that access audio. But the problem still persists.
I really really need help fixing this one. PLEASE HELP.
Click to expand...
Click to collapse
I've had that issue a month or two ago but haven't seen it on the latest ROMs. I'm not sure what causes it but I would suggest you flash another ROM if CM messes up with your sound (or another version of CM).
BWolf56 said:
I've had that issue a month or two ago but haven't seen it on the latest ROMs. I'm not sure what causes it but I would suggest you flash another ROM if CM messes up with your sound (or another version of CM).
Click to expand...
Click to collapse
Hi, Thanks for the response. I personally like CM and the extent of customization it offers. I actually dont mind switching cuz sound is bigger deal. Would you mind suggesting ROMs that are similar or comes closer to CM and also good at the same time? which ROM are you on?
s.vivekananda007 said:
Hi, Thanks for the response. I personally like CM and the extent of customization it offers. I actually dont mind switching cuz sound is bigger deal. Would you mind suggesting ROMs that are similar or comes closer to CM and also good at the same time? which ROM are you on?
Click to expand...
Click to collapse
I don't suggest ROM to avoid flaming but you can look in my sig
BWolf56 said:
I don't suggest ROM to avoid flaming but you can look in my sig
Click to expand...
Click to collapse
Hey it got fixed in the latest nightly ( cm-11-20140721-NIGHTLY ). I had put it in cyanogenmod forum, I guess they read the issue and fixed it. Audio is perfectly fine now! Feels so great to use cyanogenmod again.
Thank you cyanogenmod!
I have this issue too but it doesn't have to do with the audio disappearing; it's simply gone from the get-go after clean flashing a ROM.
As you've said, stock FW and ROM works fine, but anything custom will just totally break it. Seems to be a very isolated issue with the phone itself, I've searched all over for people with the same problem but could never find anything.
gsm22 said:
I have this issue too but it doesn't have to do with the audio disappearing; it's simply gone from the get-go after clean flashing a ROM.
As you've said, stock FW and ROM works fine, but anything custom will just totally break it. Seems to be a very isolated issue with the phone itself, I've searched all over for people with the same problem but could never find anything.
Click to expand...
Click to collapse
Oh. It used to happen to me once or twice. No audio when I install CM, after it boots the first time. I think you should check the new nightly of 7/23. Looks like its fixed. They've fixed a number of audio issues over the last few nightlies. And I've always preferred CM over any other roms, so I've no idea about why it isn't working on other roms.
s.vivekananda007 said:
Oh. It used to happen to me once or twice. No audio when I install CM, after it boots the first time. I think you should check the new nightly of 7/23. Looks like its fixed. They've fixed a number of audio issues over the last few nightlies. And I've always preferred CM over any other roms, so I've no idea about why it isn't working on other roms.
Click to expand...
Click to collapse
Thanks for the suggestion, I may as well give it a try since most everything else I've tried has had the same issue.
edit:
Clean flashed latest CM nightly, sound worked for around 2 minutes, then stopped when I plugged headphones in. Rebooted, got it to work via speakers again but then DSP manager force closed and left me without sound.
Rebooted into recovery, cleared cache, still no dice.
Going to try another clean flash to see if I can get sound to last a while longer.
edit 2: It seems to be screwed completely now, no sound after install + reboot.
Same logcat lines as in http://forum.xda-developers.com/galaxy-s3-att/help/audio-wide-custom-roms-t2825135

Random reboots after Andorid 7.0 Nougat update

I took the plunge to Android 7.0 Nougat, however I am having some major problems. Initially I had everything stock, and every once in a while my phone would reboot when on WiFi. Sometimes it rebooted within 5 minutes of booting back up, sometimes it would reboot 1 hour after booting back up. There is a whole thread about it here (note: not the bootloop issue occasionally talked about in that thread, although it could be related I guess): https://productforums.google.com/forum/#!topic/nexus/kaMOvuf093Q
I was wondering if anyone else has run into this issue? It definitely seems to be linked to WiFi only. A bunch of users apparently narrowed down a few apps that triggered the reboots more frequently (Napster, for example), but the problem seems deeper than just a rogue app. Safe mode does seem to alleviate the issue, but this is not really an acceptable solutions to me. I tried another kernel (Franco's), but that didn't fix anything. I was wondering if anyone who had this problem had any success fixing it by changing ROMs or kernels? I also read that turning off WiFi scanning may also help--I will report back if this fixes anything.
Any suggestions welcome, thanks!
This could be part of the hardware issue that is happening, it talented to me and I finally have my phone back
Sent from my Nexus 5X using Tapatalk
Which Model of LG 5X?
Do you have H-790 or H-791 Model?
Cheesejam said:
I took the plunge to Android 7.0 Nougat, however I am having some major problems. Initially I had everything stock, and every once in a while my phone would reboot when on WiFi. Sometimes it rebooted within 5 minutes of booting back up, sometimes it would reboot 1 hour after booting back up. There is a whole thread about it here (note: not the bootloop issue occasionally talked about in that thread, although it could be related I guess): https://productforums.google.com/forum/#!topic/nexus/kaMOvuf093Q
I was wondering if anyone else has run into this issue? It definitely seems to be linked to WiFi only. A bunch of users apparently narrowed down a few apps that triggered the reboots more frequently (Napster, for example), but the problem seems deeper than just a rogue app. Safe mode does seem to alleviate the issue, but this is not really an acceptable solutions to me. I tried another kernel (Franco's), but that didn't fix anything. I was wondering if anyone who had this problem had any success fixing it by changing ROMs or kernels? I also read that turning off WiFi scanning may also help--I will report back if this fixes anything.
Any suggestions welcome, thanks!
Click to expand...
Click to collapse
sorry my bad, wrong thread
ashokabs said:
Do you have H-790 or H-791 Model?
Click to expand...
Click to collapse
I have a H-790 Nexus 5x on Verizon.
has been happening to me too -- reboots randomly about once or twice a day. (only realize it since fingerprint scanner does not work and i am forced to key my passcode at first login post reboot).
It seems that the H 790 production series are faulty
Nexus 5x reboot problems
Yes it would appear so. However, I have read one post in Google Forums that speaks of problems with H791. However, it could be related to the wifi problem. There are two problems - one is problem booting initially and finally phone does not boot into the ROM and cannot be recovered. This seems to be related to hardware problem in H-790 series. The other has been isolated to the WiFi scanning which causes a crash.
giannism13 said:
It seems that the H 790 production series are faulty
Click to expand...
Click to collapse
Yeah, I am definitely having a problem with the WiFi crash. Would a custom kernel fix this? A custom ROM would, right? Any ideas for a fix for this?
ashokabs said:
Yes it would appear so. However, I have read one post in Google Forums that speaks of problems with H791. However, it could be related to the wifi problem. There are two problems - one is problem booting initially and finally phone does not boot into the ROM and cannot be recovered. This seems to be related to hardware problem in H-790 series. The other has been isolated to the WiFi scanning which causes a crash.
Click to expand...
Click to collapse
I have read the same too, but he's the only one among the hundrends of h790 users who have the same problem.
Cheesejam said:
Yeah, I am definitely having a problem with the WiFi crash. Would a custom kernel fix this? A custom ROM would, right? Any ideas for a fix for this?
Click to expand...
Click to collapse
You could try too, but I doubt it will fix anything. Its a hardware problem
giannism13 said:
I have read the same too, but he's the only one among the hundrends of h790 users who have the same problem.
You could try too, but I doubt it will fix anything. Its a hardware problem
Click to expand...
Click to collapse
I thought the bootloop issue was hardware related, but not the random reboots issue? Ex: Safe mode fixes the problem for me.
ashokabs said:
There are two problems - one is problem booting initially and finally phone does not boot into the ROM and cannot be recovered. This seems to be related to hardware problem in H-790 series.
Click to expand...
Click to collapse
IMO opinion this is just the eMMC dying problem that people have reportedly sporadically over the past 12mo. That problem has affected both H790 and H791. It likely just became more likely to show up after the 7.0 update because that was a large update, but by no means is a large update going to cause the problem by itself. The core problem is eMMC that was waiting to fail and could have happened just when web browsing but a large update just pushed it over the edge. Some phones you can do many large updates and never see a problem, then boom, one day randomly it just reboots and bootloops, with no amount of flashing or resetting making any difference.
Cheesejam said:
I thought the bootloop issue was hardware related, but not the random reboots issue? Ex: Safe mode fixes the problem for me.
Click to expand...
Click to collapse
If safe mode fixes the problem, then I was wrong. Try to find which app conflicts with the system and uninstall it
giannism13 said:
If safe mode fixes the problem, then I was wrong. Try to find which app conflicts with the system and uninstall it
Click to expand...
Click to collapse
I really wish Google would fix this, this isn't really an acceptable solution to me. :/
I have a h790 nexus 5x and haven't seen this issue, knock on wood. However if it's linked to wifi scanning that was issued in another post you may try disabling wifi scanning to see if the issue is resolved. If not it's definitely the emmc in my opinion
Sent from my Nexus 5X using XDA-Developers mobile app
Cheesejam said:
I really wish Google would fix this, this isn't really an acceptable solution to me. :/
Click to expand...
Click to collapse
If it is indeed not a a hardware problem, then don't wait for Google to fix it overnight. Besides, it may be the case that there is no bug at all, and you flashed a corrupted firmware. Your Best bet right now is to try some custom Roms and kernels and see if it fixes the problem. If you don't want to mess with user made firmware then I would suggest you to reflash the latest stock image form Google. If both of the above fail, the you are forced to roll back to marshmallow
You can try to disable wifi scanner on sleep,.
After the Nougat upgrade, I was having random reboots on my 5X (LG-H791). It always happened when my 5X was sleeping (laying on my working desk or on my bedside table for some time). After the reboot it was working fine again for some hours, so it does not seem to be the bootloop issue. I remember that I had a few rare reboots after upgrading to Nougat 7.0, but after the last 7.1.1 upgrade the reboots occured at least every second day.
Last Friday I had enough of it. I downgraded to the last stock Marshmallow 6.0.1 (MTC20K), and it didn't crash a single time after that.
My wife's 5X is having the same random reboots. The reboots are less frequent (but still occur) when WLAN is turned off. I will downgrade her's too, if my 5X is still still stable after the next weekend.
I wonder if this is a different problem, or if this is just a first symptom of the bootloop issue. If it's a bug in Nougat, then shouldn't much more (if not all) 5X owners experience these random reboots?
Cheesejam said:
I took the plunge to Android 7.0 Nougat, however I am having some major problems. Initially I had everything stock, and every once in a while my phone would reboot when on WiFi. Sometimes it rebooted within 5 minutes of booting back up, sometimes it would reboot 1 hour after booting back up. There is a whole thread about it here (note: not the bootloop issue occasionally talked about in that thread, although it could be related I guess):
I was wondering if anyone else has run into this issue? It definitely seems to be linked to WiFi only. A bunch of users apparently narrowed down a few apps that triggered the reboots more frequently (Napster, for example), but the problem seems deeper than just a rogue app. Safe mode does seem to alleviate the issue, but this is not really an acceptable solutions to me. I tried another kernel (Franco's), but that didn't fix anything. I was wondering if anyone who had this problem had any success fixing it by changing ROMs or kernels? I also read that turning off WiFi scanning may also help--I will report back if this fixes anything.
Any suggestions welcome, thanks!
Click to expand...
Click to collapse
hi, i had the exact same problem with my nexus 5x from carphonewarehouse (uk), and when it was given in to repair i was promised money in return, however they ended up refusing to give money and gave a replacement phone instead, the only way to fix this issue is apparently to get a replacement, as it is most likely a hardware issue google haven't accounted for
I've had the random restart issue for a while now. I got a "new" replacement in November for a different issue and have been on 7.0 the whole time (until last week when I got 7.1.1 OTA). I'm going to call today about another replacement. I've just had two restarts in the last hour.

Categories

Resources