Related
So I've had a VZW Nexus for about 5 months, flashed all kinds of custom ICS stuff on it, never had problems.
When Jelly Bean ROMs come out I flash one built from AOSP, works great, after a while an updated version of the ROM hits Goo.IM, I dirty flash+GApps, and suddenly after a few days my phone seems to be stuck in headset mode, not allowing me to use the mic or make calls without using speakerphone mode.
Do full system wipe, factory reset of radios/system/bootloader back to IMM76K, the issue is still there at first boot, hmm, must not be a software issue then.
I Google, this seems like a known hardware issue with the headphone jack, get a replacement from Verizon, it works fine, no problem.
Until I flash an AOSP JB ROM on this working phone, then, just like before, after dirty flashing a JB AOSP ROM upgrade, a day or so later I get the exact same issue, and again full wipes/factory resets don't fix it.
Verizon sends me a new one. This time, I'm staying on IMM76K.
This seems fishy to me, the odds of getting this kind of hardware failure on two different phones after the same sequence of events and there being no relation is astronomically high.
Again, not running any OC's or anything weird. Never dropped the phone. Don't use it in humid environments. Don't even use actual headsets. Used the first phone for months with no issues. Tried SIM/battery pulls. The AOSP JB ROM in question is used by many without this issue, though I have found what seems to be a few more instances of this that have happened after JB upgrades via Google.
Any explanations? Is there a weird bug in AOSP that's frying stuff? Doesn't seem likely or even possible, but then why?
I've been having the strangest issues lately.
I'm running task's AOKP with ktoonsez's kernel. For the past month or so I've been getting random home button lag, wakeup stuttering, and general stuttery animations.
And I've recently discovered that I absolutely cannot use my phone at all while it is playing audio. If I perform ANY sort of action, music will stutter really badly (unlocking the device, turning off the screen, opening a folder on my homescreen, opening an app, clicking something within an app, literally almost ANY action that involves tapping the screen will cause a stutter). Happening on both Underwear and ktoonsez kernels, even on stock settings.
I've tried clean wiping many times (at least 5 times in the past 3 days) and clean wipes tend to fix the issues initially, but things gradually get sluggish again after a few days. I've tried ktoonsez's kernel on straight up stock settings, and I've tried task's Underwear kernel on stock settings, and I still get these things.
Now, I see no one else in any of the threads having issues like this. So I really don't think I can blame the ROM or kernel.
So is my phone just all of a sudden hating custom ROMs and kernels? Is my processor caving or something? I can't think of any other good reasons why my phone and only my phone is buckling under the latest ROM releases. I've tested my SD card and speeds are what they should be.
Do I need to literally purge my phone, return to bone stock firmware, and start over? I'm not sure how else I can 100% determine whether it's my phone acting up or something software/firmware related. But I'm wary also of issues with jumping from 4.2 to 4.1 and back.
This is all just kinda frustrating. I'd just like to know whether it's possible that my phone is simply deteriorating before me in some form or fashion. Could the flash memory be acting up? Could the GPU be problematic? I really have no idea.
MdX MaxX said:
I've been having the strangest issues lately.
I'm running task's AOKP with ktoonsez's kernel. For the past month or so I've been getting random home button lag, wakeup stuttering, and general stuttery animations.
And I've recently discovered that I absolutely cannot use my phone at all while it is playing audio. If I perform ANY sort of action, music will stutter really badly (unlocking the device, turning off the screen, opening a folder on my homescreen, opening an app, clicking something within an app, literally almost ANY action that involves tapping the screen will cause a stutter). Happening on both Underwear and ktoonsez kernels, even on stock settings.
I've tried clean wiping many times (at least 5 times in the past 3 days) and clean wipes tend to fix the issues initially, but things gradually get sluggish again after a few days. I've tried ktoonsez's kernel on straight up stock settings, and I've tried task's Underwear kernel on stock settings, and I still get these things.
Now, I see no one else in any of the threads having issues like this. So I really don't think I can blame the ROM or kernel.
So is my phone just all of a sudden hating custom ROMs and kernels? Is my processor caving or something? I can't think of any other good reasons why my phone and only my phone is buckling under the latest ROM releases. I've tested my SD card and speeds are what they should be.
Do I need to literally purge my phone, return to bone stock firmware, and start over? I'm not sure how else I can 100% determine whether it's my phone acting up or something software/firmware related. But I'm wary also of issues with jumping from 4.2 to 4.1 and back.
This is all just kinda frustrating. I'd just like to know whether it's possible that my phone is simply deteriorating before me in some form or fashion. Could the flash memory be acting up? Could the GPU be problematic? I really have no idea.
Click to expand...
Click to collapse
downgrading your phone shouldn't be a problem at all.
download stock, wipe clean, flash through odin.
MdX MaxX said:
I've been having the strangest issues lately.
I'm running task's AOKP with ktoonsez's kernel. For the past month or so I've been getting random home button lag, wakeup stuttering, and general stuttery animations.
And I've recently discovered that I absolutely cannot use my phone at all while it is playing audio. If I perform ANY sort of action, music will stutter really badly (unlocking the device, turning off the screen, opening a folder on my homescreen, opening an app, clicking something within an app, literally almost ANY action that involves tapping the screen will cause a stutter). Happening on both Underwear and ktoonsez kernels, even on stock settings.
I've tried clean wiping many times (at least 5 times in the past 3 days) and clean wipes tend to fix the issues initially, but things gradually get sluggish again after a few days. I've tried ktoonsez's kernel on straight up stock settings, and I've tried task's Underwear kernel on stock settings, and I still get these things.
Now, I see no one else in any of the threads having issues like this. So I really don't think I can blame the ROM or kernel.
So is my phone just all of a sudden hating custom ROMs and kernels? Is my processor caving or something? I can't think of any other good reasons why my phone and only my phone is buckling under the latest ROM releases. I've tested my SD card and speeds are what they should be.
Do I need to literally purge my phone, return to bone stock firmware, and start over? I'm not sure how else I can 100% determine whether it's my phone acting up or something software/firmware related. But I'm wary also of issues with jumping from 4.2 to 4.1 and back.
This is all just kinda frustrating. I'd just like to know whether it's possible that my phone is simply deteriorating before me in some form or fashion. Could the flash memory be acting up? Could the GPU be problematic? I really have no idea.
Click to expand...
Click to collapse
Try a full wipe and a clean flash first without ktoonz kernel. I know some phones just can't run it without issues.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I've noticed AOKP's rom and Task's AOKP can sometimes have issues like these, even when doing a full wipe/clean install when coming from anything other than stock. Once you go back to stock, wipe and reflash, I think you'll be alright. When I flash aokp that way, it's usually such a good running rom I have to talk myself into even considering putting anything else on my phone
So. I decided to wipe, flash back to bone stock 4.1.1 through Odin, re-root (root-injected tar method), re-install TWRP, wipe, and re-install AOKP fresh (no ktoonsez kernel).
On the fresh install, I logged into Google, downloaded Play Music, and started playing an MP3. Aaaaand...the stuttering is still there. Music still stutters essentially every time I touch something on the screen.
And every few transition animations is still choppy.
What to do now?
I suppose I'll re-download AOKP to see whether I got a bad download, but I doubt it. EDIT: Nope, same hash.
My phone just doesn't seem to like the latest AOKP builds very much...
I'll play around with it some more.
Just go to recovery, wipe cache n dalvik, and you should be good
Sent from my SAMSUNG-SGH-I747 using xda premium
did you see if the problem persists while on stock?
sent from my i747 with xda-premium
Did you get the same lag and abrupt behaviour when using a different music player app?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I would try a different music player and perhaps even a 4.1.2 aokp instead of the latest 4.2. This would help narrow down/eliminate the issue
I also have this stutters in any rom/kernel i test. micro stutters here and there, when a few weeks ago there was none. all of a sudden stutters and lags on drawer and opening applications. antuntu benchs show the same results so i dont get it.
for future reference: benchmarks don't matter here. there are a few who use them to show how good their phone is, what really matters is real world performance.
if it's happening with everything including stock, I'd gander that it's a hardware issue and you should try for a warranty exchange.
sent from my i747 with xda-premium
Or just flash another ROM
Sent from an ATM machine
Before I start with this, please forgive me if I have touched on something that has already been covered, but this is driving me crazy.
As of recent, I have noticed my phone is locking up while I am on a call. Kind of intermittent, so it has been hard for me to track down the source, but so far this is how it is working:
When I am on a call, I will pull the phone from away from my face and will notice it is locked up. It will freeze on the call screen itself, but I am still able to talk to the person on the line for about 10-20 seconds and then it kills the conversation. The only fix is to pull the battery and reboot.
At first I read somewhere this happened to others on the ROM I was currently using (Build 3 of Slimbean). To fix I figured I would revert to a build 2 version, but still had the issue sometimes. Flashed tasks AOKP and it was still doing it (seemed more frequent actually). Currently I am downloading a TW ROM and will be testing that as well.
At this point, I am pretty sure this is ROM related as it is only locking up when I am on a call (maybe 50% of the time and at different times)and it would be odd for hardware to be the cause of it. Just seems weird to me.
Before it is mentioned, I am using TWRP and never do dirty flashes. For testing purposes, I have been wiping cache, dalvik, factory reset, format system and formatting data. Never had this issue before and I dont recall having it before most AOSP roms updated to 3.4.
gaveup said:
Before I start with this, please forgive me if I have touched on something that has already been covered, but this is driving me crazy.
As of recent, I have noticed my phone is locking up while I am on a call. Kind of intermittent, so it has been hard for me to track down the source, but so far this is how it is working:
When I am on a call, I will pull the phone from away from my face and will notice it is locked up. It will freeze on the call screen itself, but I am still able to talk to the person on the line for about 10-20 seconds and then it kills the conversation. The only fix is to pull the battery and reboot.
At first I read somewhere this happened to others on the ROM I was currently using (Build 3 of Slimbean). To fix I figured I would revert to a build 2 version, but still had the issue sometimes. Flashed tasks AOKP and it was still doing it (seemed more frequent actually). Currently I am downloading a TW ROM and will be testing that as well.
At this point, I am pretty sure this is ROM related as it is only locking up when I am on a call (maybe 50% of the time and at different times)and it would be odd for hardware to be the cause of it. Just seems weird to me.
Before it is mentioned, I am using TWRP and never do dirty flashes. For testing purposes, I have been wiping cache, dalvik, factory reset, format system and formatting data. Never had this issue before and I dont recall having it before most AOSP roms updated to 3.4.
Click to expand...
Click to collapse
It's quite possible that your phone isn't handling the 3.4 kernel very well. Although, did you try Task's last update (4/9)? I haven't had lockups on the last couple builds.
But if you keep getting them, revert back to a 3.0 kernel/ROM build until 3.4 is more stable.
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.."
Hi All,
I was hoping someone might be able to shed some light on an issue I'm having. It is occurring with Franco Kernel, and it also used to happen with BluSpark, and with EX. I'm not sure it was happening on stock, as I have been flashing custom kernels since at least the Oreo betas.
Frequently when my OP5T (re)joins a public wifi (here in London it's on the Underground), it freezes and reboots. It's not every time it rejoins the network, but it is happening every day, several times. It's the sort of network with a sign in splash screen. It is driving me crazy.
Does anyone have any idea why this is? Is it likely to be a custom kernel issue (since I hear that OP custom kernels use a different WiFi solution than the stock kernel)? I don't want to go back to stock permanently since I like the SOT and the sound mods on custom kernel.
I've just flashed stock kernel again and will see if that fixes things, but I'd prefer a solution that still allows for bumping up the volume (already using V4A).
As always thank you all!
This is still happening to me... Does anyone have any idea of how to troubleshoot this. I have reinstalled stock kernel... still same problem. Dirty flashed the beta again... still a problem. It only seems to be happening with one specific (unfortunately useful) wifi network, the London Underground WiFi.
The Wifi icon gets the little circle with the 'x' in it, then the whole phone freezes. It doesn't happen every time the phone rejoins the network, but about every 4th or 5th time.
Someone has recommended factory resetting... but I'm not sure that's not a nuclear option at this point. Any idea WHAT might be causing it and is there a way to just tackle that?
help?!