Develop Bugs

Strange Force Closes/Lag/Unresponsiveness

I'm pretty new to the root scene in general, only since about September when I got sick of not getting the GB update to my phone.
When I first started flashing roms, I started out with Nil's Business Gingersense 2.1/3.0 hybrid, and basically kept sticking to Nils roms from then on. I used a couple different Sense roms, but always came back to Nils with a gingertiny kernel.
A couple weeks ago, I decided to go with a CM just to get a taste of AOSP without Sense. I was using an incredikernel with it, and never seemed to have any problems.
Because I was a fan of the Sense 3.0 lockscreen, I was using MagicLocker on CM, and noticed it was somewhat of a battery hog. I was actually getting better battery life on sense roms with tiny over aosp with incredikernel.
I decided to switch back to Nils 3.0 ROM that I loved and used numerous times. It worked fine upon first flash. I let google restore download my apps *none from my time on CM autorestored?* and after it was all finished, I went back to Tinys 10/23 kernel. Upon flashing, it immediately started force closing everything, and it got to the point where my touchscreen was completely unresponsive, I couldn't even get the screen to turn on/off with the power button. I had to battery pull.
I eventually got the Nils 3.0 rom settled down with a Tiny 10/15 kernel, though only after using the v6 SuperCharger script in Multitasking mode.
I'm once again running into my power button no turning ont he screen, hitting an app and waiting for 3 minutes for it to force close before I can open it again.
What is going on here? I always factory wipe, clear cache, boot/system/davlik at least 3 times. And then battery stats at the end.
I've never had my phone become completely unresponsive when using the same ROM/kernel in the past. Any ideas?

TheManCalledX said:
I'm pretty new to the root scene in general, only since about September when I got sick of not getting the GB update to my phone.
When I first started flashing roms, I started out with Nil's Business Gingersense 2.1/3.0 hybrid, and basically kept sticking to Nils roms from then on. I used a couple different Sense roms, but always came back to Nils with a gingertiny kernel.
A couple weeks ago, I decided to go with a CM just to get a taste of AOSP without Sense. I was using an incredikernel with it, and never seemed to have any problems.
Because I was a fan of the Sense 3.0 lockscreen, I was using MagicLocker on CM, and noticed it was somewhat of a battery hog. I was actually getting better battery life on sense roms with tiny over aosp with incredikernel.
I decided to switch back to Nils 3.0 ROM that I loved and used numerous times. It worked fine upon first flash. I let google restore download my apps *none from my time on CM autorestored?* and after it was all finished, I went back to Tinys 10/23 kernel. Upon flashing, it immediately started force closing everything, and it got to the point where my touchscreen was completely unresponsive, I couldn't even get the screen to turn on/off with the power button. I had to battery pull.
I eventually got the Nils 3.0 rom settled down with a Tiny 10/15 kernel, though only after using the v6 SuperCharger script in Multitasking mode.
I'm once again running into my power button no turning ont he screen, hitting an app and waiting for 3 minutes for it to force close before I can open it again.
What is going on here? I always factory wipe, clear cache, boot/system/davlik at least 3 times. And then battery stats at the end.
I've never had my phone become completely unresponsive when using the same ROM/kernel in the past. Any ideas?
Click to expand...
Click to collapse
Are you using 128 as your min frequency by any chance? When i use 128 as my min frequencie my phone sometimes becomes unresponsive for seconds at a time, will hotboot it self, or just totally shut down and will require a battery pull to power on again. I ditched thr 128 and havent had the issue since.

That's the min for gingertiny right? If so, then yes. But I've literally never run into this problem since going from CM back to Sense. Never once had it happen during all my different Sense ROM flashes. Could it be something to do with the way CM does it's storage tree vs sense? I'm at a loss right now and just want some ideas on what to look into.

Just randomly got a notification upon reboot that says Package File is Invalid with the standard Triangle with the Exclamation Point in it. First time I've ever seen this error/notification. Is my Inc on the verge of death?

TheManCalledX said:
Just randomly got a notification upon reboot that says Package File is Invalid with the standard Triangle with the Exclamation Point in it. First time I've ever seen this error/notification. Is my Inc on the verge of death?
Click to expand...
Click to collapse
Flash amon ra recovery from rommanager. Then go into the recovery and select other anf fix apk uid mismatches, and fix permissions. You can flash back to clockwork when your done. I would also raise your min freq to 245000, and try that for awile.

Okay, I flashed a Nandroid backup from the very first day I rooted my phone. Then a couple others from other sense ROMs I have run. Every once in a while I'm still dealing with a little lag loading something, and I'm trying to let things settle in for a couple days before I flash a new kernel.
But, a friend at work also has an Inc, and after going from Sense to CM back to Sense, he's experienced similar problems. So I have a vague idea of what the problem is, but literally no idea how to fix it.

cmlusco said:
Are you using 128 as your min frequency by any chance? When i use 128 as my min frequencie my phone sometimes becomes unresponsive for seconds at a time, will hotboot it self, or just totally shut down and will require a battery pull to power on again. I ditched thr 128 and havent had the issue since.
Click to expand...
Click to collapse
You think its the 128 min causing the freeze issue? I don't have the issue on cm with incredikernel. So it must be something with the GB kernel but i'm not sure what yet and don't want to release a new one until that's fixed.
Sent from my ADR6300 using Tapatalk

tiny4579 said:
You think its the 128 min causing the freeze issue? I don't have the issue on cm with incredikernel. So it must be something with the GB kernel but i'm not sure what yet and don't want to release a new one until that's fixed.
EDIT: I thought i would also mention that this happens on all governers except performance, not just on sa or sa2.
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
I believe it is. I have tried a couple of times to use 128 as the min, and every time i have issues with it. Usually a random long freeze followed by an automatic hotboot, or just a freeze that requires a battery pull. I have tried raising and lowereing the voltages for 128 with the same results. It usually happens when using system intensive apps like games, google earth, or watching videos on the net. When i go back to 245 i get no issues at all, no freezing and no reboots.
EDIT: I also thought i should mention that this happens with every governor except performance, not just in sa and sa2.

cmlusco said:
I believe it is. I have tried a couple of times to use 128 as the min, and every time i have issues with it. Usually a random long freeze followed by an automatic hotboot, or just a freeze that requires a battery pull. I have tried raising and lowereing the voltages for 128 with the same results. It usually happens when using system intensive apps like games, google earth, or watching videos on the net. When i go back to 245 i get no issues at all, no freezing and no reboots.
EDIT: I also thought i should mention that this happens with every governor except performance, not just in sa and sa2.
Click to expand...
Click to collapse
I never had the problem using 128 before I switched to CM and back to Sense.

TheManCalledX said:
I never had the problem using 128 before I switched to CM and back to Sense.
Click to expand...
Click to collapse
Well i have never used CM, i have always used sense roms.

Try smartass governor (not smartass v2) and see if it helps. I don't know about reboots but there is no wake lag or virtually none.
Sent from my ADR6300 using Tapatalk

Ok, I posted a test release in the kernel thread. Please test it if you're having lag issues.

to themancalledx
I had the exact same problem going from aosp to sense. For me it was a pretty simple fix. I hope it works for you. Go into recovery select advanced and then fix permissions. Good luck.

New kernel released. Try that one.
Sent from my ADR6300 using Tapatalk

Screen flicker issue in all CM10 based roms!

Is anyone else having an issue with their screen flickering randomly (& constantly) when they flash a CM10 based rom? I've never had the issue once in stock ice cream sandwich based roms. As soon as I flash a CM10 rom, the issue starts. Anyone else having this issue & is there a fix for it? I love the speed of Jelly Bean, but the screen problem is so annoying that I keep going back to TW/ICS. It's happened on all 3 CM10 based roms I've flashed.

What kind of flickering? A dark to light repeated flicker when it's dimming as the screen is still on? or a flicker where the screen flashes off and then back on?
---> Brought to you in part by my T999 / T-Mobile Galaxy SIII

Kinda like flashing off and back on. Almost like a strobe. The screen doesn't actually turn off. It just flickers real quick. I've been playing around with different settings trying to fix it. No luck yet. I noticed that a new kernel was released today. I'm going to install that to see if it fixes the issue. It's worth a shot.

There was no point in making a thread. U obviously use cm10 or aokp and if u read the threads it is a known issue. Its definitely being worked on. Turn off force GPU rendering in developer options for now ....it helps

this happens on stock rom as well. known issue :/

It's a HW overlay issue. Qualcomm is still updating their drivers for vsync (Butter).

mrmako777 said:
this happens on stock rom as well. known issue :/
Click to expand...
Click to collapse
I'm on team sonics freegs3 RC 6 which is based off the stock rom and have yet to experience this... running the adama v3 kernel as well.
The only thing I notice is when the screen is dimming, sometimes it flickers dark to light a few times before staying dim then turns off.
Are you doing anything specific when this occurs or is it random?
---> Brought to you in part by my T999 / T-Mobile Galaxy SIII

OTAw said:
I'm on team sonics freegs3 rom which is based on stock and have yet to experience this... running the adama v3 kernel as well.
The only thing I notice is when the screen is dimming, sometimes it flickers dark to light a few times before staying dim then turns off.
Are you doing anything specific when this occurs or is it random?
---> Brought to you in part by my T999 / T-Mobile Galaxy SIII
Click to expand...
Click to collapse
typically does it when the keyboard is open. somewhere around here theres a thread about it

I just pinpointed the problem. It's SwiftKey. I just went a half hour with no issues. As soon as I installed SwiftKey, the screen started flickering again. My issue had nothing to do with GPU rendering. I hope this helps anyone else who has been having the same issue.
Sent from my SGH-T999 using xda premium

Ok I think I see something similar to what you guys are talking about. I usually have been seeing it in the Google chrome app when I go to open a new tab.. the tab(s) slots will start flickering and go haywire for a moment.
----
And I'm not using swift key as mentioned above.
---> Brought to you in part by my T999 / T-Mobile Galaxy SIII

I used to have the flicker too til I updated to xquizit v16 ...
Sent from my SGH-T999 using xda premium

Did you try turning off "Force GPU rendering" as sarni suggested? Maybe that's where your particular issue lies. I'm just glad it's software related. Shouldn't be long before we see a fix.

Fuse8499 said:
Did you try turning off "Force GPU rendering" as sarni suggested? Maybe that's where your particular issue lies. I'm just glad it's software related. Shouldn't be long before we see a fix.
Click to expand...
Click to collapse
Seems to be automatically turned off, at least on mine :/
---> Brought to you in part by my T999 / T-Mobile Galaxy SIII

yea its definitely software related. you see it big time in aosp/ jb roms mainly such as cm10 or aokp jb. im running aokp jb build that whitehawkx has out and I do see it. If i keep gpu rendering off it flickers a lot less. basically qualcomm is updating vsync almost everyday and the devs are adding it in as it comes i assume. it will get better over time....anyone running jb aokp go to settings/about phone/android version tap that ten times or so to get the easter egg and u will see a lot of flickering

OTAw said:
Seems to be automatically turned off, at least on mine :/
---> Brought to you in part by my T999 / T-Mobile Galaxy SIII
Click to expand...
Click to collapse
You have to manually check it every time you reboot.

Normally I wouldn't harp on someone for posting a thread that could be answered with a simple search but this is just ridiculous. The flickering issue is probably the largest current bug on all CM10 ROMs and has been discussed countless times in all of the CM10 ROM threads as well as the new kernel threads.
You need to read a little before posting in a panic.

I wasn't in the panic, pal. Thank you for your constructive response!
Sent from my SGH-T999 using xda premium

Fuse8499 said:
Did you try turning off "Force GPU rendering" as sarni suggested? Maybe that's where your particular issue lies. I'm just glad it's software related. Shouldn't be long before we see a fix.
Click to expand...
Click to collapse
It's not "Force GPU rendering" that stops the flickering. You have to check "Disable Hardware Overlay" every time you reboot to stop the flickering at the moment.
Also, to the one individual who said Swiftkey is the issue, it's definitely not. The issue occurs some time after you flash the roms - even if you don't install any third party apps. Like someone else already said, it's more likely to be an issue with the constant driver updates Qualcomm is releasing. Eventually, it should go away.

Hayhay said:
It's not "Force GPU rendering" that stops the flickering. You have to check "Disable Hardware Overlay" every time you reboot to stop the flickering at the moment.
Also, to the one individual who said Swiftkey is the issue, it's definitely not. The issue occurs some time after you flash the roms - even if you don't install any third party apps. Like someone else already said, it's more likely to be an issue with the constant driver updates Qualcomm is releasing. Eventually, it should go away.
Click to expand...
Click to collapse
You are correct sir, it is the HW Overlay, disable it, flickering goes away...

has anyone experienced a tiny flicker when pressing the power button to turn the screen off? i seem to be having this issue with CM10

(Thread Closed)

Thread Closed !!

New Google's Android 4.2.1 Features
-> Photo Sphere
-> Gesture Typing
-> Multi-User Support (Tablets Only)
-> Miracast Wireless Display Support
-> Daydream
-> Notification Power Controls
-> Google Now Improvements
For More Information on Which of the above features available in CyanogenMod, Come to My New Thread T989 Official CM10.1 4.2.1 Discussion (Coming Soon)
Enjoy !!! :good:

This is very useful! I am currently running AOKP JB and I will pay attention to this thread as it geets updated so I can see which ROM has less bugs, AOKP JB by TLS, or CM10.

theandroidrooter88 said:
This is very useful! I am currently running AOKP JB and I will pay attention to this thread as it geets updated so I can see which ROM has less bugs, AOKP JB by TLS, or CM10.
Click to expand...
Click to collapse
This is why i started this Thread, So we can discuss Bugs in the latest versions. :highfive:
I heard AOKP JB is stll having SODs and RRs. Do u find anything like these?

Why do we say there are no more SOD or RR? are we just taking guesses? Haven't seen any changes that would be anywhere near relevant for fixing those.
Sent from my SGH-T989 using Tapatalk 2

algorhythm said:
Why do we say there are no more SOD or RR? are we just taking guesses? Haven't seen any changes that would be anywhere near relevant for fixing those.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
First we have to fix our flashing methods and recoveries used. I for one haven't experienced one single RR or SoD since I started flashing official nightlies. People are probably causing these issues themselves to begin with. Expecting a fix for an issue that has no identifiable cause.. I wonder if any other phones outside the t989 forums are experiencing RR and SoDs with Jelly Bean..
Sent from my SAMSUNG-SGH-T989 using xda premium

algorhythm said:
Why do we say there are no more SOD or RR? are we just taking guesses? Haven't seen any changes that would be anywhere near relevant for fixing those.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
running 10-10. I experienced one soft reboot after restoring apps and then running all of them (I don't blame my phone). no sod yet. i don't know if they fixed rr or sod completely but i believe they made an impact. I think people are making assumptions since the 4.1.2 update claimed "better performance and stability fixes" and the bbq log shows a lot of framework and system updates

algorhythm said:
Why do we say there are no more SOD or RR? are we just taking guesses? Haven't seen any changes that would be anywhere near relevant for fixing those.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
We are not guessing. I said there are no SODs or RRs because I installed each update and i am pushing hard my device to get a RR. Also as i observed that there are no SODs. CM10 09-Oct Nightly is more stable than previous Nightlies. I know there are still some issues like as i stated above. We can find solutions for common problems but not major problems.

garth719 said:
running 10-10. I experienced one soft reboot after restoring apps and then running all of them (I don't blame my phone). no sod yet. i don't know if they fixed rr or sod completely but i believe they made an impact. I think people are making assumptions since the 4.1.2 update claimed "better performance and stability fixes" and the bbq log shows a lot of framework and system updates
Click to expand...
Click to collapse
Great to hear that your running latest 10-Oct Nightly. A Simple advice to you & all other users, is to restore app without data if your are using any backup tools such as TitaniumBackup etc., Restore Apps with data cause Problems.

srikanth.t989 said:
We are not guessing. I said there are no SODs or RRs because I installed each update and i am pushing hard my device to get a RR. Also as i observed that there are no SODs. CM10 09-Oct Nightly is more stable than previous Nightlies. I know there are still some issues like as i stated above. We can find solutions for common problems but not major problems.
Click to expand...
Click to collapse
Sorry, I don't mean to crap on the thread but unless you can confidently say that SODs and RRs have been fixed (changelogs, yourself writing the code, etc.), going by your own experience shouldn't be the end-all-be-all to say whether something is fixed or not. Just like with call echo, some devices are worse than others.

I see that supposedly the issue with audio and docking has been addressed. However, the docking option is still grayed out for me when docked. Just looking for audio pass-through while docked...

Been running CM10 for the past few days and updating nightlies. My issues so far:
1. No sound with Alarms, just vibrating
2. I have been told by caller that I sounded weird using phone mic, but fine with headset
3. Had phone freeze once this morning on 10/9 with touch keys lit, but screen black, had to pull battery
I am now on 10/10 and plan on doing a clean install of it this afternoon, so I'm not sure how many of these issues with persist yet

SOD RR is not fixed for me, ran latest cm10 as well as aokp nightlies
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

eight_heads said:
Been running CM10 for the past few days and updating nightlies. My issues so far:
1. No sound with Alarms, just vibrating
2. I have been told by caller that I sounded weird using phone mic, but fine with headset
3. Had phone freeze once this morning on 10/9 with touch keys lit, but screen black, had to pull battery
I am now on 10/10 and plan on doing a clean install of it this afternoon, so I'm not sure how many of these issues with persist yet
Click to expand...
Click to collapse
1. There are issues with all of the volume settings. To fix your alarm volume open the clock settings, go to volumes and chnge the volume level. It should work. You can fix all volume settings with a simple toggle. 2. Make sure you have noise suppression enabled in call settings. 3. To avoid pulling the battery hold down the power for 10-15 seconds and it will reboot.
running 10-10 with TWRP and clean install (no tdj scripts). No rr/sod for 6 hrs so far. just a soft reboot after loading a ton of apps and running them all to push my phone to the max. No issues except the ones above and a tiny camera app issue thats already been reproduced (switching from camera mode--> video mode-->panorama-->camera will cause fc). I'm starting to think this is dd material. will let you know of any rr/sods.

I'm on recent CM10 Oct10 nightly and the BLN lights stay on, even with the Oct 7 nightly.
Update: fixed my own problems. This post helped: go to menu - systems - advanced settings - sensor and uncheck and check enable keys notifications and then send yourself a text or email. It actually should work out the box mine always has. Make sure you have notifications checked off in the apps like sms and gmail.
Also check display - notification light to make sure it enabled and you can add the apps you want to have the light enabled to work
Sent from my SAMSUNG-SGH-T989 using XDA Premium HD app

on CM10: 10-10. Google Now still no voice. ( prompt voice ). also, Google Now Initializing takes forever after press on mic. I am using GAPP 0726.

garth719 said:
1. There are issues with all of the volume settings. To fix your alarm volume open the clock settings, go to volumes and chnge the volume level. It should work. You can fix all volume settings with a simple toggle. 2. Make sure you have noise suppression enabled in call settings. 3. To avoid pulling the battery hold down the power for 10-15 seconds and it will reboot.
running 10-10 with TWRP and clean install (no tdj scripts). No rr/sod for 6 hrs so far. just a soft reboot after loading a ton of apps and running them all to push my phone to the max. No issues except the ones above and a tiny camera app issue thats already been reproduced (switching from camera mode--> video mode-->panorama-->camera will cause fc). I'm starting to think this is dd material. will let you know of any rr/sods.
EDIT:
Just ran the music player for 45min on a run. no skips, nothing.. ran a 90 mb mp3 file too which usually gives my ipod trouble.. good sign
Click to expand...
Click to collapse
So is that how we're saying we don't get random reboots anymore? We just call them something else??

algorhythm said:
So is that how we're saying we don't get random reboots anymore? We just call them something else??
Click to expand...
Click to collapse
well there was a difference in this reboot because my phone didnt actually fully shut off. the "cyanogenmod" boot animation came up and the phone was ready to go in about 20 seconds. there was no usual vibration indicating that the phone has shut off and no "samsung" boot image as a regular reboot would do. call it what you will

Quote:
[email protected]: on CM10: 10-10. Google Now still no voice. ( prompt voice ). also, Google Now Initializing takes forever after press on mic. I am using GAPP 0726.
Try updating it on the market
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

Laazyboy said:
SOD RR is not fixed for me, ran latest cm10 as well as aokp nightlies
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Run only One ROM. Do a clean reflash. We are not experiencing any SODs or RRs. Use only one ROM because Flashing different ROMs one after the Other will Make your device weak. The data left by the AOKP causes some errors to CM10. Thats why i said that don't restore the apps with data.

4.2 is making me angry

So yeah all the 4.2 Roms are making me very angry because I'll turn my screen off and it doesn't want to turn back on. Is anyone else having this issue? Does anyone know how to fix it?

dakota.breeden said:
So yeah all the 4.2 Roms are making me very angry because I'll turn my screen off and it doesn't want to turn back on. Is anyone else having this issue? Does anyone know how to fix it?
Click to expand...
Click to collapse
its called sod, sleep of death. its a common problem with 4.2.1 kernel source. just about everyone has experienced them, some a lot more than others, root and not rooted, custom rom/kernel and stock. google needs to fix it in its source. there are some anecdotal fixes, some claim work, others say dont work.

I'm running a 4.2 ROM (Beta at that) and am amazed at how much better my device is working. Everything is smoother and I haven't had a single issue. I honestly don't see how everyone is having so many problems with it.

063_XOBX said:
I'm running a 4.2 ROM (Beta at that) and am amazed at how much better my device is working. Everything is smoother and I haven't had a single issue. I honestly don't see how everyone is having so many problems with it.
Click to expand...
Click to collapse
im loving 4.2.1, cant say that i have any real issues with it. but, i do get sod occasionally, about once every ten days or so. if you around the forums, just about everyone has experienced them. some get them several times an hour, some several times a day, some several times a week, some just have had sod once or twice total. every device is different, they will have differing experiences.

dakota.breeden said:
So yeah all the 4.2 Roms are making me very angry because I'll turn my screen off and it doesn't want to turn back on. Is anyone else having this issue? Does anyone know how to fix it?
Click to expand...
Click to collapse
just go back to 4.1.2 if you are having issues.. 4.2.1 is a hit or miss IMO, some ppl get issues while for others it works great

Just a thought, how many of you had bt on when sod occurs?
Sent from my i9250

bk201doesntexist said:
Just a thought, how many of you had bt on when sod occurs?
Sent from my i9250
Click to expand...
Click to collapse
Interesting idea. I never use it and have never had any issues.

i never use bluetooth, but have had sod.

Same here.

063_XOBX said:
Interesting idea. I never use it and have never had any issues.
Click to expand...
Click to collapse
I've had issues with BT on 4.2.1 (OTA), turned it off after a) sending first file OK b) second file fail, and it stuck on " turning off".
Read below.
simms22 said:
i never use bluetooth, but have had sod.
Click to expand...
Click to collapse
dakota.breeden said:
Same here.
Click to expand...
Click to collapse
I've experienced a "black screen" on 4.2.1 (OTA), due to what i think was a crash from XDA app, probably from using it with an ad blocker, at least from what i could see. I could adb shell to the device, remount system, no problem. I've removed the ad blocker from the system, while still on 4.2.1 (OTA), and have not experienced the "black screen of death" again.
I have not experienced a "sleep of death" yet on this device. Note: definition of sod from my galaxy s days: device is in a state (after going into deep sleep) in which the only way to get it back is pulling the battery out. System is unresponsive.
I've flashed JOP40D through stock images, and haven't seen black screen/sod scenarios, recreating the same system, more or less.
As i rarely use BT, i haven't tested it again, but we shall see.
Op, what apps do you have installed? Do you use SR/AVS? If not, please raise voltages by 50mv at each step, or at least the lowest and highest step, for mpu, core and iva.
While the device is in this state, no communication is possible? Can you logcat? dmesg? Can you receive calls?
Sent from my i9250

I have not had that issue or any SOD and I am running CM10.1 with LeanKernel, my wife runs the same setup and she also has not had any issues.

I've seen SoD's on Jellybro CM10.1 with ZenSERIES kernel v14.1, but only when using the ZenX governor. If I change to Pegasusq, the SoD's stop. I guess ADA is still working out some of the kinks in ZenX. Ooo, and it looks like v15 was released a few days ago. Something new to flash.

[Q] lag cm12 flo black screen of death

Well ATM its working.. But lately the lag on my device makes it stutter so bad it freezes up then slowly comes back. Then sometimes the screen goes black and my device won't do anything.. The screen doesn't come back on. I have to hold the power button and sometimes volume buttons together to get it to restart to be usable.
I have only experienced this on 5.0.x roms 4.4.4 never did this
Ideas? Suggestions? Thanks
Sent from my Nexus 7 using XDA Free mobile app

I've never had those issues on any lollipop ROMs (at least not for this device).
Personally I'm not a big fan of CM, have you tried any other ROMs and/or kernels? Have you flashed a custom kernel or adjusted any kernel settings that could be causing this? Are you using any mods (like Xposed)?
I'd suggest trying out some other ROMs (possibly even just rooted stock) and starting out with a clean flash, with no mods/kernel changes initially, and see if you still have the issue.

PrizmaticSmoke said:
I've never had those issues on any lollipop ROMs (at least not for this device).
Personally I'm not a big fan of CM, have you tried any other ROMs and/or kernels? Have you flashed a custom kernel or adjusted any kernel settings that could be causing this? Are you using any mods (like Xposed)?
I'd suggest trying out some other ROMs (possibly even just rooted stock) and starting out with a clean flash, with no mods/kernel changes initially, and see if you still have the issue.
Click to expand...
Click to collapse
I'll give that a try.. I haven't done anything to it because upgraded the bootloader to like 4.04 and installed CM12 on it. It ran so good till like a week or so ago and now its just trash. A case with a magnet for sleep mode wouldn't have anything to do with this would it? But first things first, I'll try a simple 5.0.2 rom and see what happens.
Thanks