Develop Bugs

Random Extreme Lag on VZW GNex

So here's what I've discovered.
As of now, on stock 4.1.1, the phone runs smooth when audio is screwed up. The moment touch sounds work again (or the moment I install SoundAbout to fix it) it starts lagging like crazy. Is this a hardware thing? After switching roms, kernels, versions of Android, flashing stock and locking the bootloader nothing has worked.
_________________________________________________________________________________________________________
So I'm having this strange issue that I don't really see mentioned previously (based on my multiple searches)
My phone was running fine until I flashed Paranoid Android (The last Jellybean 4.1 Release). On this ROM i was getting some insane lag, sluggish performance. I'd swipe on the home screen and get a huge delay or the phone would read it as a long touch and bring up the wallpapers option. Opening folders and the app drawer had some serious slow downs. It was a real mess.
I assumed the phone just didn't play well with the ROM so I flashed over to Bugless Beast. The odd thing is that the problems persisted. I would get just as horrible performance and the same sluggish visual effects and stuff. Specifically I remember even the audio slowing down and being choppy (touch sounds) until they automatically disabled themselves and the ROM ran smooth for a bit but returned to the sluggishness again.
So last night I restored to stock flashing the stock image and relocking the bootloader. Rooted, unlocked, flashed recovery again and loaded up Bugless Beast and the issue is still happening. Even got my first random reboot on Bugless Beast today after it slowed down really bad. Now I've noticed that when touch sounds disable themselves so does media audio (while the ringer and notification sounds still work). This is pretty much why I'm convinced it's a software problem and not a hardware one.
Basically I just wanted to know if anyone's experienced something similar and found a way to fix it? Probably going to reflash to stock tonight
EDIT: Well it seems like the audio thing might be a hardware issue. SoundAbout fixed that but I don't see how my audio jack could have been damaged in between flashes.
EDIT 2: Current State:
- I tried flashing just the system img (multiple times) and the lag returned
- I just flashed a 4.2.1 ROM just to see what happened. Touch sounds are back which means my headphone jack fixed itself. Still EXTREMELY slow.
- And just like that headphone jack screwed AGAIN but no more lag? Any reason for these two things to be related?

Bump. Any help? Still happening, though not as common, when I flashed stock

Could it be a hardware problem? Though it would be odd for a hardware issue to show up after flashing a rom. How long have you had the phone before the issues started?

Have you tried the official 4.1.1 image?
If so, do problems go away?
If you are using ports you have to expect bugs.
Let us know
Sent from my Galaxy Nexus using xda premium

Try flashing just the system.img a few times in fast boot with a reboot boot loader between. I was having slow boot up and random performance issues on full stock until I flashed that partition with the stock image (3 Times to be precise). I no longer have the 5 minute wait for the Google logo to disappear, and overall much snappier. Apparently something was leftover from previous restores/downloaded OTA updates.
Sent from my Galaxy Nexus using xda premium

I'd suggest you stop messing around with multiple ROMs and start trying different kernels. Kernels will impact performance much more than any specific ROM will. Try either an updated version of leanKernel (assuming your sig is accurate) or a different kernel all together. Others have had luck with franco, trinity, etc, etc.

Had the same problem on my GSM GNex yesterday. Flashed a ROM combination (Xylon 4.2.1 + Lean Kernel 5.0) and had this lag.. everything would lag and FC.. tried a full wipe as well but didnt work..
Changed to another AOSP Rom (UDK 4.2.1 with linaro kernel) and its fine now..
Oh and i also changed recovery from 6.0.1.5 non-touch(that i flashed yesterday) to CWM 6.0.1.9 touch..
Not sure if this helps but thats what worked for me.. I suggest going back to a ROM that worked for you in the past.. and also try formatting your SD card and run the phone without putting back your data for a while..

@rlb81 - Starting to think it might be a hardware one but at this point I'm not sure of anything. Only had the device 3 months.
@tincbtrar - Yeah I flashed the official 4.1.1 image and the problems are still there. Ridiculously sluggish and the audio problems. In fact, on stock 4.1.1 I just had this issue where I'd turn the screen off, the animation would be really slow, and then I'd get a black screen and wouldn't be able to wake it up. Did a battery pull to boot it again and the same exact issue the second time it turned on.
@Winesnob - I'll be sure to give this a try. Thanks so much! This is a really odd issue and I've never experienced it on any of my previous android devices (Fascinate, Incredible, Thunderbolt, even the old HTC Vogue)
@Cilraaz - Currently just trying to get stock running properly so everything is locked right now. Can't remember but I'm pretty sure I tried the newer lean kernel when I flashed back to bugless.
@technogravy - Kinda the same response I have for Cilraaz here. Ideally I'd like to get stock running properly so that I can be sure there isn't something horribly messed up with my phone but I'll be sure to give both of your suggestions a try if things don't seem to work with stock.
Thanks so much to all of you guys. If you have any other input it'd be greatly appreciated.

+1 on try different kernels, my phone seems to love lean kernel. I switched to tiny kernel for a few days and every so often, a simple task like opening tapatalk would take up to 30 seconds, and everything would become unresponsive. Nothing but smoothness on lean, give some different kernels a try.
Sent from my Galaxy Nexus using Tapatalk 2

I tried Winesnob's method and I THOUGHT it worked. Was running smooth for a good amount of time and just now back to the really choppy mess it was before. In fact it just got frozen on the lock screen and went to a black screen again.
This is killing me. The headphone jack thing seems to be a hardware issue anyway so I emailed Wirefly about getting a replacement. I feel like they'll avoid that though and I'll be left with this.
Gonna try some other things tonight. Wish me luck
EDIT: The thing gets so choppy that notification sound get choppy and crackle. This is insane. I'm fully stock minus the unlocked bootloader right now
EDIT2: Flashed stock image and touch sounds came back. This is getting really weird. Lag is still here though. Really bad lag

Bumping again now that I've sort of pinpointed the issue. Lags with touch sounds enabled and headphone jack works / soundabout installed with touch sounds on.
Currently the phone's headphone jack is screwed up, I installed soundabout, disabled touch sound and no lag.

Over in the dinc2 forums a lot of people are having the same issue when going from vipers sense rom back to aosp. I know that's not the case here but they found it was due to a new lib partition that was introduced in jb. Again, not sure if I'm 100% on this, but it does sound like a bad wipe and something is getting left from previous roms
Sent from my Incredible 2 using xda app-developers app

Ahh thanks for the heads up
Would it be wise for me to try going back to the ROM that started the problem? Maybe that'll do *something?

Again, from what I saw, everyone had some luck going back to the rom that caused the problem.
There's a tool in the developer thread called "super duper wipe" that seems to have fixed the lag for ones having the issue. I'm not sure how it works, but If you can take it apart and look at the zip, it may point someone in the right direction.
Sent from my Incredible 2 using xda app-developers app
---------- Post added at 12:23 AM ---------- Previous post was at 12:22 AM ----------
The dev thread in the DROID incredible 2 forums.
Sent from my Incredible 2 using xda app-developers app

SkinnyT said:
Over in the dinc2 forums a lot of people are having the same issue when going from vipers sense rom back to aosp. I know that's not the case here but they found it was due to a new lib partition that was introduced in jb. Again, not sure if I'm 100% on this, but it does sound like a bad wipe and something is getting left from previous roms
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
I took a look at that super duper wipe script...looks interesting but not necessary on our phone.
Im starting to think you may have a hardware issue if you cant flash stock images and get everything back to normal. Maybe a relock and then unlock?
i just did this cause I had a SIM card issue...and naturally it wiped my data completely.

solarpolitiks said:
...
@technogravy - Kinda the same response I have for Cilraaz here. Ideally I'd like to get stock running properly so that I can be sure there isn't something horribly messed up with my phone but I'll be sure to give both of your suggestions a try if things don't seem to work with stock.
...
Click to expand...
Click to collapse
turns out my lag problems weren't gone completely until i wiped /System before flash.. Alot of ROM's out there have a /system wipe script, but the one causing my FC's and lag didn't, so it was installing the new system files on top of the old ones and possibly causing a conflict.
it could the same for you

Yeah I've recently tried unlocking again, formatting system before a ROM flash and I still get lag. Now it's more that it will last a day without the lag and just magically come back the next day. Headphone/speaker issues still exist. Wirefly completely ignored my first email so I sent them another one. Hoping for the best.
Completely lost on what this could be

anyone see this thread?
http://forum.xda-developers.com/showthread.php?t=2029246
I have random lag on my vzw nexus and i think its io related and nothing to do with the kernel.
Sent from my Galaxy Nexus using Tapatalk 2

I'll check out that app but like I've mentioned. Lag seems to be coming from sound. After installing soundabout to get the speaker working again I get some nasty lag. Disable touch sounds and I have no lag. Disable the sound effects on twitter - no issues with the app. WireFly said I'm still under manufacturer warranty through my carrier and it sounds like I should be covered. If Verizon tries anything to get around that they'll be willing to do a three way call to make sure I get the replacement. I'll probably end up with a refurb but hopefully it'll beat this stupid issue.

Just stopping in to say thanks to everyone that tried to fix the issue but Verizon is sending out my replacement device today and I'll be sending this one with the faulty headphone jack back.
Problem solved!

[Q] Graphic glitches and other problems

So I've been having a bit of trouble with my t989 lately, when I try unlocking the phone I will either get a black screen (the lock screen will appear for a split second before going blank if I hit the lock button again) or it won't track my finger movements on the screen. If I manage to unlock the device I end up seeing numerous graphic glitches ranging from the bar at the top w/ the clock/battery meter just gone and the keyboard not working.
I'm runing CM9.0.0 because I had issues with 10.2 (battery wouldn't charge) and 10.1.3 (similar to my lock screen issues but not as severe, still agitating) and also 9.1 which had the same exact issues as I'm having now. I've tried installing with different gapps but the same thing happens. The phone will work for a day or two, then the glitches come. After resetting, everything is normal for a day or so, then it's normal a few hours, etc. The time is getting narrower between reboots and it's a bit frustrating.
Does anyone know what I could be doing wrong, if anything? I flash via twrp and wipe, then install the rom, then install gapps, then reboot, wait 20min, reboot, and go about my business w/ the setup and such. I would be fine going back to 10.1.3 but jellybean roms and snapchat don't really like to work together on this phone for some reason. It's really the only app I use because it seems like the only way my friends want to communicate nowadays, so I'd prefer to stay on ics if possible...
If anyone can give any insight I'd really appreciate it

greenghoul said:
If anyone can give any insight I'd really appreciate it
Click to expand...
Click to collapse
Have you tried using Odin to flash back to stock? That is usually the recommended step if you are having problems with custom ROMs.
And the newest stock is 4.1.2, so at least you wouldn't have to be on ICS.

meekrawb said:
Have you tried using Odin to flash back to stock? That is usually the recommended step if you are having problems with custom ROMs.
And the newest stock is 4.1.2, so at least you wouldn't have to be on ICS.
Click to expand...
Click to collapse
I'll give that a try. Odin is just the program used to root originally, correct? Also, I want to stay on ICS if possible. So after doing that I'm going to try CM9 again and see how that works.
Anyway, the past few days I've been using AOKP mr2 milestone 1 and it's been okay. For some reason the battery life is bad even with juice defender and a task killer taking care of things. In a matter of minutes after clearing tasks I'm down from ~350mb of ram free to 60. Is that normal with that rom?
I'm not sure what to do at this point. I'm not the best with technology but i figured i was smart enough to figure this out...

bump.
I still haven't tried flashing w/ odin yet. Does anyone know where I can find a gingerbread stock rom? I've been looking for a while and can only find the jellybean one. Since I want to stay on ICS what I want to do is go from gingerbread and up to that rather than downgrading from the jellybean stock rom if that makes sense.

[Q] Random reboots and lock ups (memory leak?)

Hey all,
I've had this issue with everything but the stock rom. After a certain amount of time the phone either locks up to where I have to pop the battery, or will graphic glitch on the screen for a second and then auto reboot. Happens maybe 2-4 times a day depending on the day.
I've done a full wipe and full factory reset. I've been modding phones for ages and this is the first time I've encountered this issue. Everything else seems to run completely fine.
I'm running resurrection rom, but it's done this on several other roms I've tried. However all roms are AOKP/AOSP based if that's relevant.
If there is anymore information I can offer please don't hesitate to ask. I searched the forums and couldn't seem to find anyone else really talking about this. It can be a giant headache so hopefully I can get it sorted.

heartspains88 said:
Hey all,
I've had this issue with everything but the stock rom. After a certain amount of time the phone either locks up to where I have to pop the battery, or will graphic glitch on the screen for a second and then auto reboot. Happens maybe 2-4 times a day depending on the day.
I've done a full wipe and full factory reset. I've been modding phones for ages and this is the first time I've encountered this issue. Everything else seems to run completely fine.
I'm running resurrection rom, but it's done this on several other roms I've tried. However all roms are AOKP/AOSP based if that's relevant.
If there is anymore information I can offer please don't hesitate to ask. I searched the forums and couldn't seem to find anyone else really talking about this. It can be a giant headache so hopefully I can get it sorted.
Click to expand...
Click to collapse
If this has just started recently in would say it is indeed apart of the cm base, and related to kernel issue. Since the kernel devs are using cm and their kernel base most ROMs kernels have the same base, which means in a round about way they may react the same way on your device. To me, you said graphic glitch, then reboot. I would bump up your voltage little by little and see if it stops, I also would change govs in the kernel.. I'm assuming it happens on any cm kernels you've tried? Yank555 has an awesome cm kernel I would highly recommend, or even imoseyon always has a solid stable cm kernel as well.

How are you transferring the firmware? The heavy cable with the heavy plug? If so, it might have damaged your device's USB port and is causing intermittent disconnections which are corrupting the data as it is transferred. Try a lightweight cable and make sure it is firmly seated, then don't let it move during the transfer.
If this solves it then maybe look into replacement due to faulty design.
Frank

It is happening on all roms, however the only custom roms I've tried are CM based. I'll take a look at these other kernels and see if that resolves. Thanks for the help and idea's so far guys.

I've been having the same issues. Hellish reboots though. 10+ a day... Keep me posted. Thanks
Sent from my SM-N900T using XDA Premium 4 mobile app

Screen Glitches,Stock Rooted S3.

I've been getting these glitches/artifacts/tearing on any 4.4+ rom on my T-mobile S3.
It's like the status bar will glitch down to the bottom of the screen.
I'm currently on a 4.3 stock rom (ENC2), It's been rooted with the samsung toolkit and has knox disabled (at least according to the app).
I've tried most current d2lte roms, PA, spirit, ACIP...ect.) and they all have it.
I know for a fact I'm missing something. I just can't remember what it is for the life of me. I know it has something to do with the bootloader/binary. I seem to remember when 4.4.1 came out there was something with the bootloader we had to do and no matter what I search nothing is coming up with the correct solution.
I'm hoping someone could tell me what i'm missing because it seems painfully obvious and I'm missing it, . I really don't enjoy using TW.

We don't ever mess with the bootloader or other parts of the base firmware, so maybe you're thinking of a different device?
When did it start? What was the last thing you did (flash)? Tbh, to me it sounds like a hardware problem. Maybe a connector got loosened, or some moisture/water damage, or even heat damage could cause what you are describing. Especially if its happening on every ROM.
Flash the stock NC2 firmware via Odin and factory reset. If it still happens after that its almost certainly hardware related.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

Does it also happen with touchwiz?

So. I ran the knox removal thing from the samsung toolkit and now I don't see them on the latest CM nightly.
I have to test a few other roms but I don't know, it's somehow fixed, thank you for the responses.

Glad to hear it. Be careful with the toolkit though. It is not supported and has bricked devices.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

After giving it a few days the issue came back.
I've tested this on a stock nc2 touchwiz as well as your (doc) latest likewise release with no issues with the screen or anything.
For the non touchwiz I tried aicp latest 4.4.4, the latest cm11, the latest aospa weekly and a 4.3 AOKP release (milestone2).
The glitch issue wasnt in the cm release for a day or so then showed up, all others showed up instantly.
I also emergency recovered via kies. Then rerooted. I'm also using the latest twrp
Here is a logcat of the ROM I'm currently on, the 4.3 AOKP. I wish I had more of an understanding of logcats so i knew if I posted the right section.
http://pastebin.com/UyZFHriB

I was curious so I booted up a nandroid of aicp and then restored a backup of the boot from likewise. Results were minimal glitching but no connectivity at all. APNs didn't load and WiFi is broken. I'll post a video shortly of the screen.

The only thing that jumps out on that logcat is where you have this kind repeated several times in a row:
09-18 13:35:38.752 W/ActivityManager( *761): Permission denied: checkComponentPermission() owningUid=10060
But I honestly don't know what its referring to. But I will say that since it appears to be happening on every rom, even stock, it sounds more like a hardware issue. Display problems usually are to begin with, but almost any problem that persists across multiple ROMs and wipes can usually be blamed on a hardware malfunction.
Watch a disassembly video on youtube, then open it up and reseat all connectors. (Don't mess with the antenna. Its fragile and not related to the issue at hand.)
Sent from my SAMSUNG-SGH-T999 using Tapatalk

DocHoliday77 said:
But I will say that since it appears to be happening on every rom, even stock, it sounds more like a hardware issue.
Click to expand...
Click to collapse
That's the odd thing, On both 4.3 and 4.4.2 versions of touchwiz I don't get the glitching. Only on AOSP based roms. I could just go stick with a touchwiz based rom and be done with it but my personal preference is not using touchwiz. I'm just confused as to what is actually causing this.
I'm guessing it has to have something to do with the bootloader and baseband.
I think i did forget to mention this is a "refurbished" warranty replacement, i regret that I don't recall which specific version it had as stock, I'd guess it has to be enc2?
Here is a poor quality video to show whats happening, on the home screen you see the glitching where the status bar glitches down to the bottom. I tried to get it to do what it sometimes does in both the MLB app as well as the reddit app but it decided not to be as noticeable this time.
http://youtu.be/ZsZL1Okio-A (sorry about the added music )
Just a side question, I couldn't seem to find a definitive answer, but was it ok to downgrade within the 4.3 bootloaders? I thought I remember reading that as long as you don't go from 4.3 to 4.1.2 it was fine.

Soryy I misunderstood before about it happening on stock. Have you tried any different kernels? I'd suspect that before bootloader. But since it's a refurb, there's just no telling for sure.
Once on 4.3 you cannot downgrade your firmware at all. You can flash older roms, but that's it.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

My device freezes in a black screen

Hey all!
This is happening to me for 2 months now, I was running official 12.1CM and now official 13CM
I tried to also use some stock based rom but im pretty sure it happened there too.
Whats happening to me is that randomly throughout the day my phone's screen turns black and I cant reboot it by any home button combination, only by getting out the battery.
When this happens the phone just totally freezes and I cant get it to respond or make a sound.
I don't think that the phone dies because sometimes when its freezes I can still see the notification led blinking.
Does anyone know why this might happen? or where can i copy some logs that might help you guys figure it out?
Thanks in advance!

sounds like you have the sleep of death issue? Personally I haven't been on CM roms much on my G3 so I haven't really encountered this issue but on my previous phone I've encountered this a few times on CM.
EDIT: Though it shouldn't happen on stock are you sure it happens on stock as well?

I have this issue as well using the Exodus rom. I never had it while using a stock rom, so I think this is a cyanogenmod issue (Exodus is a CM based rom in 5.1).

I have the exact same issue with my vs985. Seems to happen the most when viewing any sort of video, but I have had it happen at other times as well. Pretty dang annoying, probably 3-4 times a day. Using CM 13.0-20151217-nightly-vs985 but it started when I first flashed CM. Never had the issue on stock rooted rom.