Flickering screen - Verizon Samsung Galaxy S III

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

Related

[Q] Questions about Cognition Custom ROM

So I upgrade my Captivate to the leaked 2.2 and came to the conclusion that everyone else did after using it for a couple of days. I've been missing a few apps from the market (i.e. New York Times) since I've upgraded and stuff has been crashing so I decided to go with a custom ROM for it, especially because everyone says the phone becomes amazing once you do it. I decided to go with Cognition since its the one I've heard of that everyone seems to think is the best.
One question I have about Cognition is how does it run with LauncherPro? I really don't like TouchWiz 3.0 which is one of the bad things about Cognition. I'd prefer Vanilla Android with some HTC Sense capabilities, so LauncherPro is really important to me. Can anyone tell me how well it runs on Cognition?
Also, do you need to apply a lag fix to the Captivate once you install Cognition, or does it just run better overall?
Thanks to anyone that can help.
Cognition comes with the stock launcher, not the touch wiz launcher.
I've never been a fan of launcherpro, so I don't know how it runs. There us no reason to believe it wont run awesome, as cognition is silky smooth, fast and stable.
Cognition loads a voodoo lagfix upon flashing, so you don't need to. Keep that in mind, as you need to disable the lagfix before you flash anything else.
For what it's worth I like DesignGears other ROM better, perception. They are very similar, but perception lets you pick your lock screen.
Sent from my SGH-I897 using XDA App
I use LauncherPro on Cognition. It runs fine.
You won't regret switching to Cognition. It's a great ROM and is much faster than stock. And everything works.
I haven't tried any other ROMs yet but was thinking about flashing Perception thus weekend.
Sent from XDA App
Can anyone tell me the risk factor of bricking my phone? I believe I mostly understand the process, I first need to go back to original 2.1 and go from there, but I'd rather not do it if there is a large chance of me bricking my phone.
Also, any forum tutorial would be nice, I like to have something to read up on it alongside a video. Thanks
I've always trusted dg for my roms. If you want to know how to install. Just go to the page and every step is laid out for you there. I have never had a problem with installing it. Even though it says to go back to stock I never do. But please do what it says untill you are ok with what you are doing. With that said. Flash and enjoy.
Sent from my SAMSUNG-SGH-I897 using XDA App
jojomoulder said:
I've always trusted dg for my roms. If you want to know how to install. Just go to the page and every step is laid out for you there. I have never had a problem with installing it. Even though it says to go back to stock I never do. But please do what it says untill you are ok with what you are doing. With that said. Flash and enjoy.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Searched for the page on this forum, the latest is 2.3 b8 correct? I remember reading somewhere that 2.41 was released, or something newer than 2.3
Nvm, ignore my last question, I figured out what that was. But I've been reading that Cognition and Perception are made by the same dev, so which one is the better, more updated one? I mainly want it to be fast and have app support for a couple 2.1 Galaxy S apps.
The chances of (fully) bricking it are pretty slim. I've actually never had a bad flash, and I've quite a bit of roms, including a few I cooked up on my own. In the absolute worst case scenario (you pulled the plug during a flash - though this is also not guaranteed to fully brick it - in an attempt to deliberately break it, and now your phone just shows a black screen), you may still get it into download mode by building yourself a jig (it's just a 301k resistor across pins 4 and 5 of your microusb slot).
Also, if you want my two cents on DG roms, Perception is a bit better than Cognition. I had some weird stability issues in Cog 2.3b6, and it was definitely slower than my current rom - Perception 10.1. There are a few annoying things in Percep, but they're mostly minor. The haptic feedback on the home button doesn't work, the lock screen unlock audio cue doesn't work even though the locking audio cue mysteriously does, and the browser still has the annoying issue of not being able to save large images in a higher resolution than 305x203. The phone call audio quality seems to be a bit crappier too, but it's not dreadful.
Edit:
Also, the NY Times app not appearing in the market on 2.2 devices is the fault of the developer. The developer can set a max sdk version in android apps, so if your version of Android is higher than the max version specified in the program's manifest, it will not appear in the market for you.
- It seems like they're now supporting 2.2. Check for "NYTimes for Android" or get it with the QR code here:
http://www.appbrain.com/app/nytimes-for-android-phone/com.nytimes.android#
modest_mandroid said:
The chances of (fully) bricking it are pretty slim. I've actually never had a bad flash, and I've quite a bit of roms, including a few I cooked up on my own. In the absolute worst case scenario (you pulled the plug during a flash - though this is also not guaranteed to fully brick it - in an attempt to deliberately break it, and now your phone just shows a black screen), you may still get it into download mode by building yourself a jig (it's just a 301k resistor across pins 4 and 5 of your microusb slot).
Also, if you want my two cents on DG roms, Perception is a bit better than Cognition. I had some weird stability issues in Cog 2.3b6, and it was definitely slower than my current rom - Perception 10.1. There are a few annoying things in Percep, but they're mostly minor. The haptic feedback on the home button doesn't work, the lock screen unlock audio cue doesn't work even though the locking audio cue mysteriously does, and the browser still has the annoying issue of not being able to save large images in a higher resolution than 305x203. The phone call audio quality seems to be a bit crappier too, but it's not dreadful.
Click to expand...
Click to collapse
If anything, the main thing that I would probably get annoyed with about Perception is the haptic feedback for the home button and the call quality if there is a noticeable difference.
A few more questions, is Cognition still updated or was 2.3b8 the last one to be released? Also, with any of these ROMs, do I have to do anything special to gain the ability to side-load apps?
YoungBloodz said:
If anything, the main thing that I would probably get annoyed with about Perception is the haptic feedback for the home button and the call quality if there is a noticeable difference.
A few more questions, is Cognition still updated or was 2.3b8 the last one to be released? Also, with any of these ROMs, do I have to do anything special to gain the ability to side-load apps?
Click to expand...
Click to collapse
I probably wouldn't have noticed the difference in call quality if I didn't see other people complaining about it first. I think it's because it's based off of an i9000 rom, and to my understanding, the i9000 doesn't have a hardware support for noise cancellation (so it's done in software), whereas the Captivate does.
The haptic feedback on the home button "kind of" works. You get a haptic buzz when you do a long press, but you don't get a buzz if you just tap it.
The update question is a question for the dev, but I haven't seen Cog updated in a long time. I think DG is mostly focusing on Perception now.
Edit: err woops, forgot to answer part of your question. Both Cog and Percep permit sideloading by default, with Percep being slightly nicer because it restores the "Unknown sources" toggle under settings>applications.
I am running cognition now for three days, and couldn't be happier! Launcherpro is fine also. I flashed 2.3b6 (my roomate had it already and we didn't see that 2.3b8 was out)
I Followed an AWESOME video guide on youtube from a user on here named connexion2005
HERE is the link if you'd like it. Follow it to a tee and you will be a happy camper!
modest_mandroid said:
I probably wouldn't have noticed the difference in call quality if I didn't see other people complaining about it first. I think it's because it's based off of an i9000 rom, and to my understanding, the i9000 doesn't have a hardware support for noise cancellation (so it's done in software), whereas the Captivate does.
The haptic feedback on the home button "kind of" works. You get a haptic buzz when you do a long press, but you don't get a buzz if you just tap it.
The update question is a question for the dev, but I haven't seen Cog updated in a long time. I think DG is mostly focusing on Perception now.
Edit: err woops, forgot to answer part of your question. Both Cog and Percep permit sideloading by default, with Percep being slightly nicer because it restores the "Unknown sources" toggle under settings>applications.
Click to expand...
Click to collapse
Alright, I guess I'm probably gonna end up going with Perception then, and since DG should be still working on it, hopefully some of those problems get fixed. If I do find anything particularly annoying about it, I guess I can just flash to Cognition. Everyone has been saying how once you start flashing that you can't stop, so I'll see . Thanks a lot for your help!
Also, I found this for the haptic feedback for anyone who wants on a fix for Perception that's reading this thread
http://forum.xda-developers.com/showthread.php?t=903227

[Q] andriod.phone crash when adding image widget -with Gummy ROM 1.01

First off, I just want to say Hi to everyone on the forums, this is my first post, but I've been lurking for quite a while, waiting for the right time to flash my phone –Should have done it sooner
Also, I want to thank everybody involved here, especially devs, for all of their hard work! -- I’m really not trying to suck up here… Just trying to portray sincere gratitude --
Anyway, I tried searching the forums here for related issues, as well as, the interwebs, but didn’t find anything relevant. So I apologize in advance if this is a known issue or a repost… Also, I tried posting this issue in the Gummy 1.01 release thread, but I’m a newbie so, I have to post it here:
This past weekend I finally got fed up with the buggy STOCK ROM for my SCH-i500 (Fascinate) and took the plunge and installed the latest Gummy build available for it (1.01). Everything is running very well so far, and I only have a few minor gripes, but all in all, it’s pretty awesome! Except for one big issue that I found…
If I try to add a photo widget to any of the launcher home screens, the screen goes black, and the bootup animation starts up, followed by a window that states “android.phone has stopped”. This is how I did it:
Menu>>Add>>Widgets>>Photo Gallery>>Choose an image>>[select an image]>>Crop.
This does not happen when I choose the other two options (“Choose an album” or “Shuffle all images”). I think this is either an issue with ICS 4.04, or Apex launcher. I think this because the same thing happens with my friends Galaxy Nexus; he is running Liquid ROM - not sure what version - based on ICS 4.04 with Apex launcher. It’s a completely different phone and he has a different kernel, which makes me assume it might be related to ICS 4.04 and/or Apex. … I’m not sure though because I’m not a dev…
Is anyone else having this issue?
*Update: Tried it again, and it completely crashed the phone this time. I had to pull the battery out to boot. Also, the phone started in “Safe Mode”. I just rebooted one more time, and everything seems fine again…
I'm having the same problem with my Verizon G NEX, Ive searched online and haven't found anything except for this post its a pretty strange bug if you ask me. anyone know of a fix ?
Just an update for anyone who comes across this thread... The issue has been resolved in the updated version Apex that just came out (v1.1.0).

Jellybean (CM/AOKP/Virtuous) Maps/Photoshpere Bug (Report Here)

Hello,
I have the following problem:
I experience visual artifacts when using two-finger rotate in Google Maps, also Photoshpere is really acting up... the images flicker...
Not all devices have it, as a matter of fact there are few of them (reported). Let's try to collect as much data as we can in order to find the cause of this and maybe a fix. I'll start.
HTC One S
Color: Gradient Blue
HBOOT:1.14.0002
Radio:1.06es.50.02.31
Jun 11 2012, 14:36:28
It's recommended to attach a logcat with the problem.
The problem allways happen when try to rotate Gmaps with two fingers, and photoshpere gets crazy especially after taking 1st photo.
It seems like an accelerometer problem, but accelerometer utilities seems to report the sensors working fine, so maybe a GPU driver problem.
C'mon guys, let's get this fixed
For the flicker have you tried changing debug.composition.type=dyn to debug.composition.type=gpu? I also had the same issue with that camera but only tried it when it come out, have you tried other packs that have it?
Darknites said:
For the flicker have you tried changing debug.composition.type=dyn to debug.composition.type=gpu? I also had the same issue with that camera but only tried it when it come out, have you tried other packs that have it?
Click to expand...
Click to collapse
I've tried many packs... i will try those and report back. The thing that scares me is that this happens on Virtuous Rom also (which is almost stock build with HTC jb libs), and this may mean that i will never have fully working jb not either from HTC.
adi4motion said:
I've tried many packs... i will try those and report bach. The thing that scares me is that this happens on Virtuous Rom also (which is almost stock build with HTC jb libs), and this may mean that i will never have fully working jb not either from HTC.
Click to expand...
Click to collapse
What you get both issues on Virtuous? that can't be good.
Darknites said:
What you get both issues on Virtuous? that can't be good.
Click to expand...
Click to collapse
yes... that's also what i'm afraid of...
Keep in mind the camera is for 4.2, not 4.1, and I doubt we'd ever get stock camera on official Sense.
PcFish said:
Keep in mind the camera is for 4.2, not 4.1, and I doubt we'd ever get stock camera on official Sense.
Click to expand...
Click to collapse
ok, that's not a problem, i can live without photoshpere, but the fact is Google Maps also have this problem and I need GMaps...
I know that at least 3 others reported this problem (and i'm sure that are many others who didn't test for it) I wonder where are they now...
I started this thread hoping that if other users reported it, the devs would try to solve this, but i think i'll just have to wait for HTC to give us JB and see if i still have the problem (but I am really concerned that I might have it). What's wrong with this One series? so many bugs (and not minor): cases chipping, helicoptering bug, sound issues, performance issues (one x), this problem....
I reported in another thread that I have this problem and I do, when using photosphere, I've seen it, although if I keep my movements nice and slow and steady, it seems to hold together.
I haven't seen any problem in Google Maps though, what happens to you in there?
Cheers
wheeliemonster said:
I reported in another thread that I have this problem and I do, when using photosphere, I've seen it, although if I keep my movements nice and slow and steady, it seems to hold together.
I haven't seen any problem in Google Maps though, what happens to you in there?
Cheers
Click to expand...
Click to collapse
when i rotate the map with two fingers i get visual artifacts
I have the same problem on photospere, on maps I have no graphical problems, but the magnet sensor seams to change it's direction sometimes. Had this on CM10, and now on 4.1 Sense+.
Edit: I mean I have the orientation problem on photosphere. My screen does not flicker.
I have this same exact problem with an HTC One XL. I have not found a fix for it.
I've tried flashing every flavor of jellybean there is. It oddly seems to not happen if I use a sense version of jellybean. But I hate sense and want vanilla android.
AOKP, AOSP, modded, unmodded, doesn't matter. I get this annoying graphics glitch when I try to scroll around using maps or photosphere.
I hope it's not purely hardware related, and that there's an easy software fix for it.

[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.

[Q] Various potential hardware/sensor related issues

Hey guys,
I have a VZW HTC One M8 with the following version details:
Cyanogenmod 11-20141112-snapshot-m12-m8
Unlocked bootloader
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT-3.16.0.0000
RADIO-0.89.20.0222
OPENDSP-V26.2.2-00538-M8974.0106
OS-
eMMC-boot
This phone came to me with a clean Cyanogenmod install on it. I wiped it anyway to be sure. I have an S3 that I've been running CM11 on up until I got this phone so I'm no stranger to Cyanogenmod.
My issues appear to be randomly occurring and I cannot seem to pin down what is causing it or when it actually happens. Here are the various issues I'm seeing:
1. Screen fails to reorient when being turn - this happens system wide, even the home screen fails to reorient. Perhaps a problem reading the gyro sensor?
2. Lux values get stuck, usually at 45. Ambient light sensor?
3. Double tap to wake stops working - need to use the sleep/wake button to turn the screen on. Can still double tap the status bar to turn the screen off
4. Incorrect battery reporting - The battery appears to drain normally and at a consistent pace, however if the phone is shutoff or rebooted I will sometime see a huge drop when the phone boots back up.
I have a screenshot from the phone this afternoon but cannot post it (attachments fail to upload on this forum). I can probably PM it to you though.
I noticed if the phone gets to 5%, sometimes ~15% it will just turn off because the battery has actually died but the OS thinks differently.
The first 3 issues fix themselves after reboot.
Oh and I've noticed that the profiles feature doesn't work properly. If the ring mode is set to vibrate on the work profile, it will stay in vibrate even when it switches back to the default profile which is set to ring mode. The phone will not let me set custom notification sounds with Profiles enabled either. Example: Hangouts uses the notification sound as set by the default in Settings. I cannot change this. I can turn off Profiles and I can change the notification tone on Hangouts all day long.
Not quite sure what I should be looking at here so any guidance or suggestions would be much appreciated. Let me know if you need any more details.
You answered the question yourself in the second sentence of your post.
beaups said:
You answered the question yourself in the second sentence of your post.
Click to expand...
Click to collapse
beaups,
Was really hoping for a more descript answer. Can you please elaborate?
cstokes86 said:
beaups,
Was really hoping for a more descript answer. Can you please elaborate?
Click to expand...
Click to collapse
You are running cm. Probably known cm bugs or possibly you need different firmware. Either way, there's no such thing as a hardware problem until it exists on stock software.
beaups said:
You are running cm. Probably known cm bugs or possibly you need different firmware. Either way, there's no such thing as a hardware problem until it exists on stock software.
Click to expand...
Click to collapse
I forgot to mention in my original post:
I already searched around for the various issues I'm having but was not able to find any mentioning of them in any known issues lists. Was hoping to see if any devs on here had suggestions on things to try.
cstokes86 said:
I forgot to mention in my original post:
I already searched around for the various issues I'm having but was not able to find any mentioning of them in any known issues lists. Was hoping to see if any devs on here had suggestions on things to try.
Click to expand...
Click to collapse
Search better. This took me less than 5 minutes:
http://forum.xda-developers.com/showpost.php?p=56813202&postcount=3167
http://forum.xda-developers.com/showpost.php?p=56733227&postcount=3140
http://forum.xda-developers.com/showpost.php?p=56719654&postcount=3130
and many, many more all in that thread, which happens to be the CM thread for your phone.
Oh, and welcome to XDA
beaups said:
Search better. This took me less than 5 minutes:
http://forum.xda-developers.com/showpost.php?p=56813202&postcount=3167
http://forum.xda-developers.com/showpost.php?p=56733227&postcount=3140
http://forum.xda-developers.com/showpost.php?p=56719654&postcount=3130
and many, many more all in that thread, which happens to be the CM thread for your phone.
Oh, and welcome to XDA
Click to expand...
Click to collapse
Thanks for those links. I was looking in the official known problem lists for Cynogenmod for these issues to see if they actually confirmed anything. I will look at possibly installing a nightly and testing with that, but I'm a bit reluctant to go that route since this is my daily driver.
cstokes86 said:
Thanks for those links. I was looking in the official known problem lists for Cynogenmod for these issues to see if they actually confirmed anything. I will look at possibly installing a nightly and testing with that, but I'm a bit reluctant to go that route since this is my daily driver.
Click to expand...
Click to collapse
If you are looking for stability, flash a sense based ROM. Its just the way it is.
beaups said:
If you are looking for stability, flash a sense based ROM. Its just the way it is.
Click to expand...
Click to collapse
^ Can't disagree with that, but I loathe the bloatware and manufacturer UI and skins they put on their devices, not to mention the freedom and functionality I lose out on by going back to a more or less stock experience. If I want stock non-CM, I'll just flash 5.0 GPE and see how that goes, but I've already tested with that as well and missed the functionality that CM brings. :/
Win/Lose.
Do you think the firmware (not the ROM/OS) is highly out of date and should be updated by now?
cstokes86 said:
^ Can't disagree with that, but I loathe the bloatware and manufacturer UI and skins they put on their devices, not to mention the freedom and functionality I lose out on by going back to a more or less stock experience. If I want stock non-CM, I'll just flash 5.0 GPE and see how that goes, but I've already tested with that as well and missed the functionality that CM brings. :/
Win/Lose.
Do you think the firmware (not the ROM/OS) is highly out of date and should be updated by now?
Click to expand...
Click to collapse
Yes you should update that firmware. There's an emmc controller firmware update amongst other things included you should have. Have you tried gpe or stock with some of the xposed modules now available?

Categories

Resources