i have been having issues with no sound coming from the LG nitro , all of a sudden it cut out yesterday and have hard reset numerous times and 1 out of 4 or 5 reboots the sound comes in but if you power off then on the sound disappears .. this is a stock phone with only root , anybody have any ideas or similiar issues ?
This is not any kind of development related topic but I'd suggest that you bring it in for repair or replacement as that sounds like a hardware issue. Maybe try flashing another rom.
Sent from my LG-P930 using XDA App
moved to general
I had a similar issue and ended up returning the phone to bell for a new one.
Here is the long story just in case it helps some one. Like all good Android users I started by rooting my phone, installing ROM Manager and making a nandroid backup. Once this was done I ran rooted stock for a few days. All was well.
Then I started to debloat my phone. After which everything seamed good. Then installed and played with RAM Manager and SD Speed Increase. TBH i did not notice any particular increase in speed on my phone but that might be due to the following issue.
After all this I decided to run a few test by using the phone into the ground. Added a bluetooth headset, while using navigation and making several calls. It was all running very well until I rebooted. Once rebooted whenever I connect my bluetooth headset I was no longer able to make calls. The phone dialer would completely lag out until I de-activated bluetooth. The the 10 or so test calls I tried making would all go through at once. This wasn't the end of the word for me so I continued to use the phone as everything else was working fine. The things started degrading by which time I was on the new CM9 nightly build. The phone had started being really sluggish. I finally decided to return my phone after it would no longer play any sound and whenever it called to any sound related function would lag out and/or reboot. The same behavior happen in stock, cm9 and NO! NO! ROMs. I tried flashing a few roms in a last ditch effort.
I could be wrong by my conclusion is that the audio portion of the snapdargon chip fried and since these phone are basically just 1 chip the phone simply degraded from there.
I would like to know of anyone else has had similar issue or if I just got a lemon and also your take on the cause of the issue.
Hope this can help someone.
Thanks!
Edit: Returned my phone for a new one and I've been flashing CM9 since the first release and no issues. I'm actually really happy with the replacement and would recommend the phone as long as you don't get a lemon ;-)
I am currently having some data connectivity issues with my E4GT. I have been running the Blu Kuban rom for some time now and have been a huge fan of it, but now my phone is acting really weird (no fault to the rom at all). First my GPS wouldn't lock as I thought this was kernel related I re installed the Blu Kuban rom with both of the other kernels and still couldn't get a GPS lock. Since I use GPS daily for work I went back to my classic Epic Venum rom and the GPS worked albeit poorly, it got me through the day. When on this rom whenever I used data my phone would drop down to zero percent battery and power off, this seems to occur only over 4g/3g and not over wifi. I tried flashing multiple modems from EG30 to FI27 on a multitude of roms (both GB and ICS) and using desktop Odin, but I cannot figure out what is causing my phone to crash (which now occurs consistently). I tried installing new roms (currently on AOKP build 37) which works great until the data is used and then it crashes again. I don't think this is cause from any specific rom, and I am now fearing it is a hardware issue. To summarize GPS now works, using data causes my phone to crash regardless of the rom used. Just thought I would ask the community, any help would be greatly appreciated. Thanks!
Update: I ended up restoring to stock to see if that would fix the problem and it didn't. So I took it to the Sprint store where they discovered I had a defective battery, and it just so happened that I bought the phone a year ago today so the new battery will be covered under warranty . I will update my status upon receiving the new battery, but I am feeling optimistic at this point.
These are the two setups I have used thus far (besides full stock), and this issue has occurred on both:
http://imgur.com/EgzxWFI
http://imgur.com/FZWrdwZ
The first is on ktoonsez kernel on stock rom. The second is Slimroms Kitkat. I have been using the first much longer than the second (which I moved over to just a few weeks ago).
Basically this soft reset tends to happen when I'm driving and using the GPS most often (and I notice that's also when the phone is usually the warmest). What happens is the phone just freezes up and sits there for a bit before finally doing a vibration and starting back up to the unlock screen. Kind of like I was restarting, but not quite. If it happened in the middle of calls, somehow it would keep the call going (at least on the stock kernel, I'm not sure about the new one yet). The other person just wouldn't hear what I was saying during the "soft reset"
On the stock kernel it used to happen even when not using the GPS. It was infrequent, but occurred I would say usually when I was using the phone more heavily... mostly just random though. Sometimes it would also not happen while using the GPS. That is to say it's a sporadic issue.
On this new Kitkat kernel it happened while I was navigating recently, but has not occurred when during any other operations (yet) that I can think of. Considering that was one of the first times I tried navigating with the kernel this worries me.
Does anyone know how I could approach this problem? Perhaps some logging I could do to get to the root issue? Some firmware I should perhaps try out?
Thanks.
Sounds hardware related to me. Especially if its happening on different roms.
Then again... I just looked at you image and you are still running 4.0.4 on one. But the other you are running 4.4.4. On one or tge other you most likely have a rather large gap between your firmware build and the rom. Id try flashing full stock firmware with Odin and test for a day or two. Up to you what build you want to use, but if it were me id update to 4.3. If you go to 4.3, keep in mind there is no going back.
I got my Nexus 7 when it first came out last year, rooted it, installed TWRP, and have been on several different ROMs since. Didn't have any issues with random reboots for several months. Early this year, I started having an issue where the tablet would freeze while I'm using it, then automatically reboot itself. I thought perhaps it was a problem with the ROM I was running, but I had switched ROMs a few times after that, and every single ROM I've been on since then has had the same problem. It usually only happens when I'm browsing the Internet (with Chrome being my browser of choice), but I've had it happen once while using the camera app, as well.
The other day, I upgraded TWRP to the latest version, and I installed the 4.04 bootloader in preparation for Lollipop ROMs. I was hoping on some slim chance that perhaps an upgraded bootloader might fix the problem, but I'm still getting random reboots.
I know I've seen people talk about random reboots as well, but in the past, I never saw anyone find any kind of solution. Is there one, or is it one of those things I just have to live with, at this point? It's odd to me that I didn't start experiencing this issue right away, and that it only started several months after I had had the device. To me, that makes it seem like it's not a hardware issue/ defect, but I guess no one has been able to pinpoint what the problem is, why it occurs, and how to fix it, huh?
mrw1215 said:
I know I've seen people talk about random reboots as well, but in the past, I never saw anyone find any kind of solution. Is there one, or is it one of those things I just have to live with, at this point? It's odd to me that I didn't start experiencing this issue right away, and that it only started several months after I had had the device. To me, that makes it seem like it's not a hardware issue/ defect, but I guess no one has been able to pinpoint what the problem is, why it occurs, and how to fix it, huh?
Click to expand...
Click to collapse
I'd tend to agree with you it's a software thing. However, my approach would be a bit more radical than yours: that I would erase everything, including formatting the internal storage twice (after making a backup, of course), then install a completely clean rom, use it for a while to make sure it doesn't act up again before restoring any apps.
On the side, I've seen a Nexus doing random reboots whose owner had opened the back and bent the cover somehow, which slightly depressed the power button. While the button operated normally, this condition forced it to "click" randomly, which caused the reboots. It stopped after the owner replaced the back cover. You might want to check this part. Good luck.
Most of the time, random reboots are kernel related. If you are overclocked try to set max CPU lower and see if the problem fixes itself. If you don't overclock try installing something like Trickster Mod, and lower max CPU to see if that helps. What ROM and kernel are you running?
Sent from my 2013 Nexus 7
"Until death, I will remain a Dirty Unicorn.."
I always recommend flashing back to stock to rule out software issues. If it continues, you've got a hardware issue.
I haven't really messed around with kernels, I've typically just used whatever was included in a particular ROM, and I never adjust to overclock or anything like that. I don't remember what all the ROMs I've been on are, but I've been on CM before, and I'm currently using CleanROM. I think the only time I ever specifically tried a different kernel was a while back, when I flashed an Elemental kernel, but I've since wiped and been on a different ROM.
For now, I'm trying to hold out wiping anything until a good, rooted build of Lollipop is available, at which point, I'll try wiping out everything, including internal storage, and see if that helps.
I guess I could also try flashing back to stock before I do that, though. I think I've seen one stock ROM for the N7 floating around. The only problem is, it's really hard to "test" this, because the reboots are very inconsistent. The other day, after I had updated the bootloader, I was browsing Chrome for over an hour before I got a random reboot. One time, I was browsing Chrome for an hour and had 4-5 random reboots within that hour. So, that makes it difficult to determine if it's fixed in a timely manner. :/
Alright, so now that there's a proper build of Lollipop out, I did a factory reset and wiped internal storage (twice), and I'm now running stock Lollipop. I spent about an hour or so getting everything set up, and no reboots thus far; but the reboots mainly occur when I'm using Chrome, and I didn't really do any browsing, as I was getting all my accounts and apps and whatnot set up. Hopefully within the next couple of days, I'll have used it enough to get a good idea as to whether or not I'm still experiencing issues.
So far, no reboots, though i don't want to jinx it, heh... I'll be glad if the issue is finally fixed, but I'll also feel kinda dumb that all it took to fix it was something as simple as wiping internal storage and/ or reflashing a stock ROM. Lollipop is pretty nice, as well.
Yeah I'm using a custom version of L myself. You need to flash custom kernel to get working root access with SuperSU BETA 2.19
Sent from my 2013 Nexus 7
"Until death, I will remain a Dirty Unicorn.."
I have a constant reoccurring problem where the mic stops working. At first, I thought it was a hardware problem, but every time it has happened, it has been temporarily remedied by a reboot. After rebooting, it works fine, but then it will stop working again at an unexpected time. It is clear to me that this is a software issue. This makes taking calls and using Assistant virtually impossible.
I was planning on flashing a custom ROM on the device to see if it fixes the issue, but I found out that I have the Verizon boot-loader locked model. I did go onto Google's developer site and flashed the latest OTA but to no avail.
I need help. I have seen not a single other person with the same problem as me. This makes the phone completely useless AS A PHONE. I have been recently using a Galaxy Note 8 as a replacement, but TouchWiz doesn't cut it for me, as well as being a version behind.
It is a hardware issue, all pixels made before 02/2017 might develop that issue.