Related
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
Hello,
I was wondering if someone could help me out. I am having issues since the past few days with making and receiving calls. The phone FREEZES while on a call, (there is no set time as to when this happens) and I have no choice but to take out the battery and put it back to restart the phone. It is becoming a quite a nuisance and was wondering if this was due to some application or something else I'm unaware of. I had a phone protector and I've taken it off since the past few days but it still freezes while on a call. FYI...I use the GO Dialer EX for the calls, have avast mobile security installed as a virus protection. I have *TheCollective* AoCP - CP5.3 installed with AOSP JELLYBEAN 4.2 Linux 3.0 Ktoonsez kernel.
Any help would be appreciated. This freezing is driving me insane...
harryrasul said:
Hello,
I was wondering if someone could help me out. I am having issues since the past few days with making and receiving calls. The phone FREEZES while on a call, (there is no set time as to when this happens) and I have no choice but to take out the battery and put it back to restart the phone. It is becoming a quite a nuisance and was wondering if this was due to some application or something else I'm unaware of. I had a phone protector and I've taken it off since the past few days but it still freezes while on a call. FYI...I use the GO Dialer EX for the calls, have avast mobile security installed as a virus protection. I have *TheCollective* AoCP - CP5.3 installed with AOSP JELLYBEAN 4.2 Linux 3.0 Ktoonsez kernel.
Any help would be appreciated. This freezing is driving me insane...
Click to expand...
Click to collapse
Such problems can be something hardware. I had a similar issue with my old cell phone, freeze for 10-15 seconds maybe, and then reboot. There was an error in the Sd-card. My suggest is to use some app for check/scan your sd cards for errors. If your sd card is corrupted for some reason, or has some files corrupted, read or write from it can produce unpredictable results, like a freeze.
Yeah, could be any number of things, including a corrupted file on your SD. You can check for errors on your SD by following these steps:
http://www.ehow.com/how_8748172_check-integrity-android-sd-card.html#page=0
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I thinks it probably your under clock or overclock try messing with your CPU speeds
Sent from my SAMSUNG-SGH-I747 using xda premium
Thanks folks for your suggestions. I have used the avast internet security app to scan the apps as well as the SD card and it hasn't found anything wrong. I did a fresh install of a new ROM today (AOKP) and it did the same thing today. While making calls it was freezing up at random times. I did try one though, which is use the PHONE icon as opposed to using the GO Dialer EX and it didn't hang but I may have to try that several times to come to come to any conclusion.
Would formatting everything and doing a fresh install fix it?
harryrasul said:
Thanks folks for your suggestions. I have used the avast internet security app to scan the apps as well as the SD card and it hasn't found anything wrong. I did a fresh install of a new ROM today (AOKP) and it did the same thing today. While making calls it was freezing up at random times. I did try one though, which is use the PHONE icon as opposed to using the GO Dialer EX and it didn't hang but I may have to try that several times to come to come to any conclusion.
Would formatting everything and doing a fresh install fix it?
Click to expand...
Click to collapse
so you're saying that when you use the included android dialer you have no issues? so we can conclude that go dialer is the culprit?
---------- Post added at 11:29 AM ---------- Previous post was at 11:27 AM ----------
and formatting everything might fix things. if you're going to make the effort, i'd wipe data, cache, dalvik, format /system, flash rom/gapps, wipe data and cache again.
its also common to have issues when not coming from stock when you flash an aosp-based rom
I am having the same issue. Phone freezes sometimes during calls. I can finish the call, but then the phone is frozen, I have to take the battery out or wait for phone to restart after a while...Also, sometimes looks like proximity sensor doesn't work, as it doesnt turn on screen in call when I remove phone from ear.
Alcatel X'Pop, Stock Android 4.1.1, exdialler installed(not go dialler)
Same issue here on a GS4 with latest CM11 nightly and no custom dialer. Been having the issue for a couple of months. I've tried different ROMs including back to stock with the same issue. I though perhaps it was a defective proximity sensor but several appss show the sensor working correctly. Open to any ideas!
Hi all!
I'm running CM11 24.06 nightly, along with Devil3 kernel on my n7100.
I've recently updated from 06.06 nightly (I believe), which was a fresh install (full wipe, no updates before), but I have had this issue before already. I think it starts to happen after I perform an update to the newest nightly. Rolling back to previous one doesn't help - another full wipe and fresh install is required to fix this or at least I didn't find a solution.
So, what's the issue? There are four issues that, to me, are connected:
1. Waking up - I'm experiencing serious lag when waking up the device. Sometimes the device doesn't want to wake up for half a minute, sometimes it doesn't wake up at all and it requires me to restart it by holding the power button
2. Lag after unlocking - Most of the time though, when device is actually successfully woken up and I want to fe. go straight to SMS app from lock screen and type something immediately, phone freezes for a second and when I'm able to type (touchscreen reacts, letter-press animation plays) - the letters aren't appearing. Sometimes it takes a while after I can type, sometimes I have to close the app. I've tried different SMS apps, deleting big conversations, different keyboard apps (I'm using SwiftKey, but stock app is the same - this one actually remembers what I type, recommends me something, but when I tap to use the recommendation, nothing is being typed into the text box) and some other things.
3. Application start up time and white status bar - Apps are starting to drop in performance as well. For example, when I run, let's say Play Store, the status bar on top of the screen is flashing white and it takes a bit longer to be able to use them (just like the SMS app).
4. % battery usage of certain (unexpected?) apps - Most battery hunger process is Android System. I've reset battery stats, for the last 1h and 45min used phone to type 2-3 messages, and it's usage is @27%, whereas 2nd process is screen with 18% and 3rd is Android OS with 11%.
Restarting the device seems to temporarily fix first three issues. They start to come back as soon as I start using the device, like opening apps, etc.
As I said before, it all happens after performing an update. Maybe I'm doing something wrong? I usually flash the update, restart device, go to recovery, flash kernel and restart. Since the issue happened again, I've tried to flash the new nightly and kernel together before, it didn't help. Clearing cache/dalvik is not helping (before, after).
I don't have any backups made (I know, I should've made one), so, I guess I'll prolly end up performing a full wipe again. But does anyone have some ideas what may be causing this? So I can prevent this for good next time, hopefully.
Ksenios said:
Hi all!
I'm running CM11 24.06 nightly, along with Devil3 kernel on my n7100.
I've recently updated from 06.06 nightly (I believe), which was a fresh install (full wipe, no updates before), but I have had this issue before already. I think it starts to happen after I perform an update to the newest nightly. Rolling back to previous one doesn't help - another full wipe and fresh install is required to fix this or at least I didn't find a solution.
So, what's the issue? There are four issues that, to me, are connected:
1. Waking up - I'm experiencing serious lag when waking up the device. Sometimes the device doesn't want to wake up for half a minute, sometimes it doesn't wake up at all and it requires me to restart it by holding the power button
2. Lag after unlocking - Most of the time though, when device is actually successfully woken up and I want to fe. go straight to SMS app from lock screen and type something immediately, phone freezes for a second and when I'm able to type (touchscreen reacts, letter-press animation plays) - the letters aren't appearing. Sometimes it takes a while after I can type, sometimes I have to close the app. I've tried different SMS apps, deleting big conversations, different keyboard apps (I'm using SwiftKey, but stock app is the same - this one actually remembers what I type, recommends me something, but when I tap to use the recommendation, nothing is being typed into the text box) and some other things.
3. Application start up time and white status bar - Apps are starting to drop in performance as well. For example, when I run, let's say Play Store, the status bar on top of the screen is flashing white and it takes a bit longer to be able to use them (just like the SMS app).
4. % battery usage of certain (unexpected?) apps - Most battery hunger process is Android System. I've reset battery stats, for the last 1h and 45min used phone to type 2-3 messages, and it's usage is @27%, whereas 2nd process is screen with 18% and 3rd is Android OS with 11%.
Restarting the device seems to temporarily fix first three issues. They start to come back as soon as I start using the device, like opening apps, etc.
As I said before, it all happens after performing an update. Maybe I'm doing something wrong? I usually flash the update, restart device, go to recovery, flash kernel and restart. Since the issue happened again, I've tried to flash the new nightly and kernel together before, it didn't help. Clearing cache/dalvik is not helping (before, after).
I don't have any backups made (I know, I should've made one), so, I guess I'll prolly end up performing a full wipe again. But does anyone have some ideas what may be causing this? So I can prevent this for good next time, hopefully.
Click to expand...
Click to collapse
i think this kernel issue..mybe u should stay with stock cm kernel..
Sent from my GT-N7100 using Tapatalk
Azhery said:
i think this kernel issue..mybe u should stay with stock cm kernel..
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Well, like I said, everything is working fine after a fresh install (with full wipe prior to it), is it possible for kernel to cause that after a nightly update?
Ksenios said:
Well, like I said, everything is working fine after a fresh install (with full wipe prior to it), is it possible for kernel to cause that after a nightly update?
Click to expand...
Click to collapse
mybe problem on nightly..do you hve try other cm based rom?
Sent from my GT-N7100 using Tapatalk
Azhery said:
mybe problem on nightly..do you hve try other cm based rom?
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Some time ago I had OmniRom and after few OTAs I actually started noticing similar issue if I recall correctly (that was the reason for me to switch back to CM).
mybe u try..full wipe..wipe data..wipe cache..wipe system..wipe internal storage..
Sent from my GT-N7100 using Tapatalk
But that's the point, I'll probably end up doing it since restarting my phone every 30-60 minutes is out of the question. But, then what? every few nightly/snapshot I'm gonna perform a full wipe?
Ksenios said:
But that's the point, I'll probably end up doing it since restarting my phone every 30-60 minutes is out of the question. But, then what? every few nightly/snapshot I'm gonna perform a full wipe?
Click to expand...
Click to collapse
mybe u can try other rom like cyanogenmodx..bcause i nver had this issue..
Sent from my GT-N7100 using Tapatalk
I was actually thinking about it, but as I said, when I used OmniRom few months ago, I recall that I had similar issues. Nevertheless thank you for your insight. Anyone have any slightest idea what might be causing such behavior?
I seem to have fixed the issue. Turns out the culprit was Business Calendar - Business Tasks to be more precise. I unistalled both and so far didn't experience those wake up lags.
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.."