Database Info

Flickering screen

Hey guys so I've got a huge issue. I'm on now my 3rd SGSIII and I'm getting very annoyed. My screen goes nuts randomly. I think I've found a fix, but I'm not sure what's causing it, as most people don't show the symptoms. My screen starts flashing and flickering, whether it's the lockscreen, the homescreens, within an app or in the app menu it does the same thing. I haven't taken a video of it yet, but will if someone wants to see what's happening. I've had it happen only on JB, both roms and stock doesn't seem to matter. The 'fix' is the same one as AOSP rom users use, which is to disable hardware overlay, however I don't know why a non-AOSP rom would need to deal with this. The roms I've used are: Vengeance, CleanRom, Synergy and The Executioner. I've gotten so annoyed that I've gotten Verizon to allow me to switch to the DNA if I want. I've taken a few Logcat's, if someone who can decipher them more than I can to figure out what's actually wrong would be great! I've taken a bunch of logcats, but only have one posted to pastebin. It was taken whilst I was having the issues. Thanks for the help guys!
http://pastebin.com/2SZkQGZJ

LlirasChosen said:
Hey guys so I've got a huge issue. I'm on now my 3rd SGSIII and I'm getting very annoyed. My screen goes nuts randomly. I think I've found a fix, but I'm not sure what's causing it, as most people don't show the symptoms. My screen starts flashing and flickering, whether it's the lockscreen, the homescreens, within an app or in the app menu it does the same thing. I haven't taken a video of it yet, but will if someone wants to see what's happening. I've had it happen only on JB, both roms and stock doesn't seem to matter. The 'fix' is the same one as AOSP rom users use, which is to disable hardware overlay, however I don't know why a non-AOSP rom would need to deal with this. The roms I've used are: Vengeance, CleanRom, Synergy and The Executioner. I've gotten so annoyed that I've gotten Verizon to allow me to switch to the DNA if I want. I've taken a few Logcat's, if someone who can decipher them more than I can to figure out what's actually wrong would be great! I've taken a bunch of logcats, but only have one posted to pastebin. It was taken whilst I was having the issues. Thanks for the help guys!
http://pastebin.com/2SZkQGZJ
Click to expand...
Click to collapse
is the show screen updates or something similar on in developer settings?

dragon1357 said:
is the show screen updates or something similar on in developer settings?
Click to expand...
Click to collapse
Nope, I don't run that stuff because all of the rendering updates and stuff can get annoying to look at while working. I'm able to get the same issues on a fully stock rom, and a pure flashed rom, with a few programs installed. But the fact that the hardware render seems to be the issue to me is just very odd on a non-AOSP rom.

I have been having screen flickering issues ever since I flashed the latest AOKP build (AOSP) I originally thought that it was because of the kernal and the under voting that I applied but even with a different governor and normal volt settings the screen still flickeres. After some poking around I figured you that it is only happening while I am trying to type and by uninstalling the Swype beta keyboard the screen flicker had been reduced to almost nothing. I do not know why the keyboard would amplify the effect but if I use the system keyboard the flickering becomes almost non existent.
Also, the screen flickers anytime a pop up menu is on screen, such as in the tapatalk app, the menu that pops up to allow you to quote someone..
Sent from my SCH-I535 using Tapatalk 2

Had been having the same issue on Baked Bean 6, flashed BB7 last night and it seems the problem is gone. BB7 being 4.2.1 I'm guessing whether intentional or not somewhere along the process of updating the "bug" if it indeed was as it appeared was squashed.
I'd be curious to know what was causing this, if by chance you find a definitive answer please post it.
Thanks

Lk
I had a very similar issue for a while, i flashed LEAN KERNEL
Rebooted twice, and problem went away.

For an update, I flashed kt's latest kernal and the flashing has ceased.
Sent from my SCH-I535 using Tapatalk 2

Phone freezes during a call on AOSP

I'm running Rootbox (v3.9.1) and a few times, the phone just freezes during a phone call, and battery has to be pulled.
Have you seen anything like this? Could this be related to the kernel?

ECrispy said:
I'm running Rootbox (v3.9.1) and a few times, the phone just freezes during a phone call, and battery has to be pulled.
Have you seen anything like this? Could this be related to the kernel?
Click to expand...
Click to collapse
I'm having the same issue running in baked

ECrispy said:
I'm running Rootbox (v3.9.1) and a few times, the phone just freezes during a phone call, and battery has to be pulled.
Have you seen anything like this? Could this be related to the kernel?
Click to expand...
Click to collapse
It's happened to me on Carbon as well as Liquidsmooth. It's probably related to Cyanogenmod (since most (if not all) AOSP ROMs are based off of CM).
sent from my anthraxed GS3 with MOAR goodness

Thank you us for the confirmations. I've noticed this is other AOSP roms and have given up, I hope it gets fixed by CM team soon.

Yeah sadly for that exact reason I had to ditch aosp hope they fix it . usually j would talk on the phone but when I hit the 5min mark my phone would freeze and either stay on or stay off then a couple mins later the call would get dropped and u would have to do a battery pull and what not I was running carbon 1.6.1
Sent from my SCH-I535 using Tapatalk 2

its been fixed on slimbean for over a week if you want to try that out.
havent had that problem running paranoid android either.

[Q] Screen becomes unresponsive upon calls, help?

So to start, my phone is rooted and the bootloader is unlocked. I should also have the latest modem flashed. The problem is that the screen will freeze upon some calls, not all of them, and prevents me from doing anything. I can still hear everything that's coming through but the screen itself is just unresponsive. At that point, I usually just pull the battery and reboot and make the call over again. It hasn't happened to me immediately after a battery pull yet.
This problem has occurred to me on multiple roms. I initially noticed it on LiquidSmooth's 3/16/13 stable build and so I re-flashed it making sure to do a clean install. It kept on happening so I kept switching roms and am now on Carbon Rom and it hadn't given me any problems until just now (been on Carbon for over a week). All of my rom installs are done with clean flashes so I really don't know what's going on at this point.
Any help would be absolutely fantastic!

it's a known issue on AOSP roms

Try using the latest Official CM10.1 nightly. Best to do reset, clean install. That issue has pretty much been squashed on the latest builds.
Sent using Tapatalk

Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

I had no idea about it being a problem on aosp ROMs since it hasn't occurred for me on them until recently. But I'll definitely cm10.1 a try! Thanks!
Sent from my SCH-I535 using xda app-developers app

kupnooduls said:
I had no idea about it being a problem on aosp ROMs since it hasn't occurred for me on them until recently. But I'll definitely cm10.1 a try! Thanks!
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I am currently using Paranoid Android which is based off cyanogenmod, and I get the same thing. Phone freezes mid call. I was having general freezing problems across the board until I installed PA, I kept thinking is was my launchers, etc, but I am bare bones right now and it still does it periodically, and have once had it do it directly after a battery pull.
When mine does it, the call drops.

Two things..
First, I have been having the same phone freeze issues as everyone else, tried different roms, the dummy file fix, all kinds of different things going through this forum. I wanted to do everything I could possibly do before posting about it.
I am using Paranoid Android. I noticed the cyanogenmod version listed in the phone info is [email protected]#1 Tues March 19
Is this just a PA version number or actually the kernel number? What if I was to flash the newest stable kernel to my PA?
ALSO
I noticed when my phone does its freeze up thing, the battery has been at 53-57%. It does not seem to do it any lower or higher battery percentage. Is it possible that its actually a problem with the battery or the battery percentage programming??? It just seemed odd that it always seemed to be around the same % when it happened.
Any thoughts????

[Q] PA 3.60 Phone Calls Not Working

I downloaded the new PA 3.60 6/11 build from notta yesterday with KT747 Kernel and RErick universal setup. After using for a while, without attempting to call, I was more than happy. At work today I called my girlfriend and in the middle of our conversation the call dropped. Ever since then whenever I try to make a call I get a "com.android.phone has stopped" message or it will connect, close phone screen but keep call in status bar, show that same message, then drop the call. Sometimes it says "Mobile network not found" after trying to call then will reload my bars after. Can't receive calls either but my network shows I have bars and every IMEI & numbers alike are there. Restored nandroid and calls worked.
Thought it might be kernel combo so tried to wipe everything and reinstall but problem persisted. Any ideas on how to fix?
Thanks in advance!

Try the latest paranoid android gapps, i had that problem a few times but after i flashed those the problem stopped. And what's Rerick setup?
Sent from my SCH-I535 using xda premium

andrewk7750 said:
Try the latest paranoid android gapps, i had that problem a few times but after i flashed those the problem stopped. And what's Rerick setup?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I've flashed the 6/10 gapps both times I flashed the ROM, unfortunately. Maybe bad download? I don't know at this point.
Its RErick's from Team Kernelizers setup for the KT747 kernel. Can find him on the TK Mod thread. Great battery life supposedly but didn't get to try it for too long since calls didn't work.

I was running the latest pa with their gapps and calling was fine for about a day then I got the phone crashing every time I tried to make a call and couldn't receive any.
Did nothing different. I didn't try to fix it or anything, I just restored my tw backup.
Unfortunately, I've been running tw mostly these past few months. Occasionally I try out aosp, be it cm or another iteration, but go back due to the annoying deal breaking glitches. I've pretty much given up on running anything other than bone stock on this phone. Not sure if it's just my phone or what, but anything else always has obnoxious bugs that never seem to get squashed.
Shame, too. The developers do great work. Probably just my particular phone as plenty of others seem to run with zero problems.
Stock bloated tw with nova for me. Even the debloated roms run wonky on my phone after a couple days. Always full, clean wipe.

antiseen said:
I was running the latest pa with their gapps and calling was fine for about a day then I got the phone crashing every time I tried to make a call and couldn't receive any.
Did nothing different. I didn't try to fix it or anything, I just restored my tw backup.
Unfortunately, I've been running tw mostly these past few months. Occasionally I try out aosp, be it cm or another iteration, but go back due to the annoying deal breaking glitches. I've pretty much given up on running anything other than bone stock on this phone. Not sure if it's just my phone or what, but anything else always has obnoxious bugs that never seem to get squashed.
Shame, too. The developers do great work. Probably just my particular phone as plenty of others seem to run with zero problems.
Stock bloated tw with nova for me. Even the debloated roms run wonky on my phone after a couple days. Always full, clean wipe.
Click to expand...
Click to collapse
The same things HaS been happening to me with alot of asop ROMs. Only way to fix is not use custom kernel and the roam setting have something to do with it. It sucks cause I like the asop ROMs . Its been doing to me for two weeks just wonder if they have changed anything with these ROMs cause it don't matter if its cm PA AOKP or unofficial versions of these I just can run them anymore
Sent from my SCH-I535 using xda app-developers app

kenbrownstone said:
The same things HaS been happening to me with alot of asop ROMs. Only way to fix is not use custom kernel and the roam setting have something to do with it. It sucks cause I like the asop ROMs . Its been doing to me for two weeks just wonder if they have changed anything with these ROMs cause it don't matter if its cm PA AOKP or unofficial versions of these I just can run them anymore
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Since I've been having so much trouble with any rom I haven't used a custom kernel since my thunderbolt days. I run whatever kernel the rom comes packaged with.
But like I said, it's probably my phone. It has defective bluetooth that I didn't figure out until well after I purchased the phone. It's got constant loud crackling and popping on stock (ironically, non existent on aosp roms). I doubt that's related but just illustrates the weird differences between phones.

Had the same problem less than an hour ago when i really needed to make a phonecall. Had to restore to my backup i made before flashing PA. Hell of a time for it to stop working.
Sent from my SCH-I535 using xda app-developers app

Well after first believing it was just my phone, after reading these comments as well as the PA thread I've come to the assumption that its something with the ROM and how it behaves with the phone app. Hopefully the details will get resolved soon cause I was really enjoying the new PA. Until then, sticking with hyperdrive.
Thanks guys.

had this problem since upgrading to the 6/11 build.
i could make calls out as long as i didnt press the ok button to dismiss the process stopped message.
i could not receive calls hwoever. it does ring like it should, but it does not allow me to answer.
using latest gapps package.

I've had this problem on both 6/12 and 6/14, using the 6/10 gapps.
Any chance anyone has come up with some way to resolve this?

for ppl with this problem, i moved to pacman to get all my newest PA features setup with pie, expanded desktop and halo.
not having htis problem on there.

ddurandSGS3 said:
for ppl with this problem, i moved to pacman to get all my newest PA features setup with pie, expanded desktop and halo.
not having htis problem on there.
Click to expand...
Click to collapse
Good suggestion. Really liked PACman for a while, but eventually my call got dropped and I ran into the exact same issue from that point on. At this point I've just decided to go with a TW based rom. With hyperdrive you can still have pie and download Floating Notifications app that is practically the same thing as halo but also has themes available too.
Until that bug can be fixed, going to stick with Hyperdrive. Sweet rom anyway.

AOSP Random reboots

I've been having a lot of random reboots when using AOSP based roms. So far I've used CM10.1.0, 10.1.3, 10.2, and liquidsmooth 2.10. As long as it is AOSP, the phone randomly reboots. Sometimes while it's just sitting on the charger or in my pocket.. After digging through this site I tried installing the firmware from here:
http://invisiblek.org/d2firmware.html
but I'm still having random reboots. I have a stock battery, and a later model brown S3 phone. TW roms work flawlessly.
Any advice?

As far as I am concerned CM is not very stable. Plus if you flash nighties that could be your issue. I read other people having random freezes and hot boots on LS 2.10. My suggestion to figure out if it's really AOSP (seriously doubt it) try LS 2.9. probably the most stable AOSP ROM out there. Also I have heard good things about older Slim Bean Builds. Do NOT do anything 4.3 related. 4.3 ROMs are still considered unstable.
Sent from my SCH-I535 using Tapatalk

Sandman-007 said:
As far as I am concerned CM is not very stable. Plus if you flash nighties that could be your issue. I read other people having random freezes and hot boots on LS 2.10. My suggestion to figure out if it's really AOSP (seriously doubt it) try LS 2.9. probably the most stable AOSP ROM out there. Also I have heard good things about older Slim Bean Builds. Do NOT do anything 4.3 related. 4.3 ROMs are still considered unstable.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Ive been using several 4.3 roms without one issue. Dirty Unicorn and Carbon have been prefect so far. Using latest twrp, full wipe and stock kernels.

Noremacam said:
I've been having a lot of random reboots when using AOSP based roms. So far I've used CM10.1.0, 10.1.3, 10.2, and liquidsmooth 2.10. As long as it is AOSP, the phone randomly reboots. Sometimes while it's just sitting on the charger or in my pocket.. After digging through this site I tried installing the firmware from here:
http://invisiblek.org/d2firmware.html
but I'm still having random reboots. I have a stock battery, and a later model brown S3 phone. TW roms work flawlessly.
Any advice?
Click to expand...
Click to collapse
What revision is your phone? Rev4? Rev5? My phone is a Rev0 and I'm not having any problems with running AOSP based ROMs.

I did too. I'm not sure WTF was going on, but ASOP/CM would be great for about a month, and then it'd start random rebooting. After it'd start random rebooting, the way to stop it would be to ODIN back to stock, and start over. Clean installs, nandroid restores, full formats.. None of it worked.
So here I stay on a crappy 4.1.2 TW ROM.. itching to return, but not really seeing enough improvements to warrant another go.

How are you restoring apps and data? I had problems after restoring via titanium backup, but when I restored selectively (just apps and data I really needed) with helium it's running fine.

this has to be a very late revision of the phone because it comes in the brown color that Verizon didn't start offering until recently. Even so, how do I determine the revision?

Noremacam said:
this has to be a very late revision of the phone because it comes in the brown color that Verizon didn't start offering until recently. Even so, how do I determine the revision?
Click to expand...
Click to collapse
I believe it states the version when in download mode. (Vol down + home + power at a powered off state)
Sent from my SCH-I535 using Tapatalk

Sandman-007 said:
I believe it states the version when in download mode. (Vol down + home + power at a powered off state)
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Check in terminal emulator.
Su (enter)
cat /proc/cpuinfo (enter)
This will give you the revision number and a lot more about your phone.

I have "rev 4" on my brown GS3 and have been running CM10.1.3. The only time my phone crashes/reboots is when I attempt to use the front facing camera with a third party camera app.

Is it possible to get some logging of what's triggering the crash, so someone can take a look at it? Also right now, to the person who asked, I am reinstalling my apps from scratch from the play store. Since I haven't built up a lot of custom data for this phone to make it worth backing up.
I miss AOSP something fierce.

Noremacam said:
Is it possible to get some logging of what's triggering the crash, so someone can take a look at it? Also right now, to the person who asked, I am reinstalling my apps from scratch from the play store. Since I haven't built up a lot of custom data for this phone to make it worth backing up.
I miss AOSP something fierce.
Click to expand...
Click to collapse
Download aLogCat from the play store and start the app. Then trigger the crash
Sent from my SCH-I535 using Tapatalk

What do you do if you can't cause it to crash? Mine are always totally random. It'll crash during a call, it'll crash while web browsing, it'll crash while locked in my pocket.. The only time it won't crash is when you want it to!
Do you just end up with a giant log file then or what?