Related
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!
For the longest time I was on stock rooted EK02. I recently took the plunge and wiped all and installed CM10, which I love. The only problem I've had is that *all* sound suddenly decides to just go away whenever it wants to (ring/notif tones, touch clicks, app sounds, everything except in-call audio). It might last 5 minutes, or it might last an hour, but it always comes back on its own, and a reboot does not fix it. I can't seem to trigger the problem with a certain app or a certain action, but for example, I will be sitting here playing Angry Birds Star Wars, and the sound will just drop out completely. A few levels later, it comes back on its own. I put the phone down, go do something else, and the entire phone has muted itself again. Frustrating...
I'm on CM10 beta2 nightly 20121108
Kernel version says 3.0.15-CM-g8e7ed92, which seems appropriate since it references CM and this is the first CM I've ever had on the phone. Should I try other kernels though? AFAIK, no one else has mentioned this particular audio problem in the CM10 discussion thread. At least I don't think this is related to the "low volume in some apps" issue.
HOWEVER, something interesting, the baseband/radio version says EK02. I guess I should update that to get better comm, but it couldn't be causing an intermittent muting issue, right? I guess I assumed incorrectly that a ROM installed after a wipe would have to include its own modem. Argh.
This is frustrating, as I said. Thanks for any help.
Wow. 5 days and no replies. Can't someone at least tell me what you think? I've never understood why I can ask a legitimate, polite, and descriptive question after searching the forums as much as possible, and it gets ignored, while someone else can post something completely redundant that barely forms a coherent sentence, yet it sparks a 10 page discussion... frustrating.
I am not exceedingly familiar with cm10 but I would bet it is not the modem causing that issue. I would be inclined to think you have intentionally and / or accidentally changed the "quiet hours" or setup some form of silent profile. Otherwise it was perhaps a bad flash, you did not wipe CLEANLY (IE. calkulins format all or odin a full wipe/restore rim first) or maybe not install with what many revs believe to be a CWM safe kernel???
---------- Post added at 11:24 PM ---------- Previous post was at 11:19 PM ----------
also do you have anything (pc or stereo) connected to Bluetooth with the phone nearby?
trmitche2 said:
Wow. 5 days and no replies. Can't someone at least tell me what you think? I've never understood why I can ask a legitimate, polite, and descriptive question after searching the forums as much as possible, and it gets ignored, while someone else can post something completely redundant that barely forms a coherent sentence, yet it sparks a 10 page discussion... frustrating.
Click to expand...
Click to collapse
Nobody knows the answer to your questions. This is not a common problem and as mentioned above the modem has nothing to do with it. My only suggestion would be to flash a stock release one click, not a leak, and go from there.
Agree with above and mainly because I borked my build... it was perfect and then I tried a gps fix flash. Can confirm now that wipe in CWM and calks format all does not do crap for aosp, jb, or the like. So long story short, yeah you gotta one click or my guess is best served to clean slate with a stock ROM and in consequently factory wipe and just stay there.....
Wow thanks for the replies guys! I was really getting discouraged there for a bit.
I don't think it's a quiet hours setting, because all sound is cutting in and out *every 5-10 minutes*,
I will use Calk's wipe and start from scratch as suggested.
Although unrelated, surely EK02 is not a recommended modem for CM10, right? I guess I made a naive assumption that a full wipe followed by CM10 install would replace my old modem. I'm just curious what kind of problems might be caused by using such an old modem, even though I know sound is not one of them.
Can anyone recommend a modem for this ROM from personal experience? I understand from the main beta2 thread that the FK modems break 3G...
Just flash a one click, it will wipe everything and install a new modem. I'm using fi27 modem with codename rom, works fine. My current install method is run one click update prl and profile and get gps lock then do the install process of the rom.
someguyatx said:
Just flash a one click, it will wipe everything and install a new modem. I'm using fi27 modem with codename rom, works fine. My current install method is run one click update prl and profile and get gps lock then do the install process of the rom.
Click to expand...
Click to collapse
Yes. Do this. Then. Format all is still a good idea if you choose to revert to a GB ROM like el29 and progress.
UPDATE: I fixed this.... accidentally. What fixed it is hard for me to believe or accept, but Iv'e confirmed it by being able to reproduce it. The problem was being caused by the FRIKKIN' FACEBOOK APP. :/ I uninstalled the FB app for a totally unrelated reason: battery drain pointed out in another post. I realized the next day that the sound had not cut out once since then, I re-installed FB, and the problem returned quite predictably: all sounds started cutting in and out every few minutes. Uninstalled FB again, and sound has been fine ever since. My best guess is that the sound was cutting out/in each time a background sync of FB occurred. So now my sound is perfect and my battery life is much better to boot. I never used that damn app anyway.
Unrelated, but for what it's worth, I never installed a new modem as discussed above. Still running EK02 with CM10 nightly from 11/28. Have no problems to speak of. I didn't leave it on purpose, (noob mistake, thought CM10 installation would replace it), but I don't see any reason to change it as long as everything seems perfect, unless anyone can tell me what types of problems it could cause. Any further thoughts welcomed, but thanks again to you guys who already gave me advice.
trmitche2 said:
UPDATE: I fixed this.... accidentally. What fixed it is hard for me to believe or accept, but Iv'e confirmed it by being able to reproduce it. The problem was being caused by the FRIKKIN' FACEBOOK APP. :/ I uninstalled the FB app for a totally unrelated reason: battery drain pointed out in another post. I realized the next day that the sound had not cut out once since then, I re-installed FB, and the problem returned quite predictably: all sounds started cutting in and out every few minutes. Uninstalled FB again, and sound has been fine ever since. My best guess is that the sound was cutting out/in each time a background sync of FB occurred. So now my sound is perfect and my battery life is much better to boot. I never used that damn app anyway.
Unrelated, but for what it's worth, I never installed a new modem as discussed above. Still running EK02 with CM10 nightly from 11/28. Have no problems to speak of. I didn't leave it on purpose, (noob mistake, thought CM10 installation would replace it), but I don't see any reason to change it as long as everything seems perfect, unless anyone can tell me what types of problems it could cause. Any further thoughts welcomed, but thanks again to you guys who already gave me advice.
Click to expand...
Click to collapse
None, modems are interchangeable between builds with the exception of the fk-- and newer modems, they only work with Touchwiz based JB roms. If your modem is performing well speed and call quality wise then there's no need to change. However you could always test other modems to see if you get any improvement in your location. If you choose to change modems you should be on a touchwiz rom so you can update prl and profile after the modem flash. Modems are a YMMV item each one interacts with different devices and locations differently so to find the best modem for you you just need to flash and test them out if you so choose
Sent from my hand to your eyes!
Samsung: Intercept, Galaxy S2, Galaxy S3, Galaxy Note 2, Nexus10
HTC: EVO4g, EVO 3d
LG: Optimus G, Nexus 4
Asus: Nexus7
Motorola: Photon
Amazon: Kindle Fire, Kindle Fire HD
We are legion, for we are many!
Thanks KoN! Extremely helpful post, as always. All other replies in this thread have been thanked as well. I learned a lot.
Still wish I knew how FB could make my sound cut in and out every few minutes, but if no one else has seen that issue, it must've been a quirk, so I imagine I'll never know. Moving on....
I installed TWRP and a rom and the phone ran smooth. No issues. But after installing Wanam and Xposed a lag developed. I installed a analog clock and watched it. Every 3 to 4 seconds the clock will stop for 1 to 2 seconds. Videos freeze, while typing the keyboard freezes. I have tried the build prop edit, the wanam fixes with no help. I have even tried going back to stock. The lag is even there in the stock rom. I have not tried rooting the stock rom, just skipped that and installed TWRP then a rom. I have also notice when odining back to stock that the Sprint and the Sprint Spark logo does not come up. I am thinking that the stock logos should come back. Can anybody help with what could be going on with the lag.
dodgedurango said:
I installed TWRP and a rom and the phone ran smooth. No issues. But after installing Wanam and Xposed a lag developed. I installed a analog clock and watched it. Every 3 to 4 seconds the clock will stop for 1 to 2 seconds. Videos freeze, while typing the keyboard freezes. I have tried the build prop edit, the wanam fixes with no help. I have even tried going back to stock. The lag is even there in the stock rom. I have not tried rooting the stock rom, just skipped that and installed TWRP then a rom. I have also notice when odining back to stock that the Sprint and the Sprint Spark logo does not come up. I am thinking that the stock logos should come back. Can anybody help with what could be going on with the lag.
Click to expand...
Click to collapse
same story with me i installed Wanam and Xposed and after a few weeks its got crazy laggy even on a regular video it keeps skipping frames till i uninstalled exposed and im back fast as before
CMSTERN said:
same story with me i installed Wanam and Xposed and after a few weeks its got crazy laggy even on a regular video it keeps skipping frames till i uninstalled exposed and im back fast as before
Click to expand...
Click to collapse
Well I took the phone to best buy today and had them reflash the stock firmware. I finally got the sprint logo back on bootup, but it still had the same bad lag. I think the phone was not fixable. Ive done all the same things on wifes note 4 and it started working right after installing the stock firmware. Mine just wouldnt. So I will just buy another phone.
Are you past your return period? If so then I guess your stuck and will have to fix it yourself. It sounds like your problem can be fixed with a odin flash back to stock. Once you do that then immediately go to the activate phone option in settings and also update prl and profile. I think you'll get it sorted out by doing this. It definetely sounds software/firmware related so no worries.
tx_dbs_tx said:
Are you past your return period? If so then I guess your stuck and will have to fix it yourself. It sounds like your problem can be fixed with a odin flash back to stock. Once you do that then immediately go to the activate phone option in settings and also update prl and profile. I think you'll get it sorted out by doing this. It definetely sounds software/firmware related so no worries.
Click to expand...
Click to collapse
What is "PRL" and how can I check and change mine if i need to.
and change it to what?
im rooted stock.TWRP and wanam lag fix and build prop fix,but I still have a very slight lag.
thanks..
Settings, system update, first click update profile. When it finishes and your data come back, click update prl.
Xposed will always produce some lag based on how the additional framework functions upon boot. Its the nature of the beast I suppose. With the simplicity comes a price. Hopefully there will be some custom roms soon and you won't need the xposed framewor & modules.
tx_dbs_tx said:
Xposed will always produce some lag based on how the additional framework functions upon boot. Its the nature of the beast I suppose. With the simplicity comes a price. Hopefully there will be some custom roms soon and you won't need the xposed framewor & modules.
Click to expand...
Click to collapse
You're incorrect about xposed always producing lag. Do you even know the technical details of how xposed works? I'm inclined to think that you have no idea.
Anyway, for anyone experiencing lag after installing xposed, do this. It solved any lag I had:
http://www.droidforums.net/threads/...te-4-simple-tip-for-lag-after-rooting.275578/
-viperboy- said:
You're incorrect about xposed always producing lag. Do you even know the technical details of how xposed works? I'm inclined to think that you have no idea.
Anyway, for anyone experiencing lag after installing xposed, do this. It solved any lag I had:
http://www.droidforums.net/threads/...te-4-simple-tip-for-lag-after-rooting.275578/
Click to expand...
Click to collapse
This ^^^
Worked on mine.
Sent from my SM-N910P using XDA Free mobile app
My apologies for saying xposed framework always produces lag. I know it can be installed and run eith little to no lag, especially with these more powerful phones.. I also like the whole concept and the fact that it works for both deodexed and odexed systems. But I don't like a seperate running jar with a bunch of module (apk's) running in addition to the regular system files. (I know not all the modules are always loaded and unused ones sit dormant). For older devices that don't have enough ram etc this caused problems if you loaded it up too much. I guess this is what i based my opinion on. Then again you could be right and I have no clue about how xposed works. Lol. INo offense taken viperboy. I'm just used to doing everythong manually aka the hard way. Lol
tx_dbs_tx said:
My apologies for saying xposed framework always produces lag. I know it can be installed and run eith little to no lag, especially with these more powerful phones.. I also like the whole concept and the fact that it works for both deodexed and odexed systems. But I don't like a seperate running jar with a bunch of module (apk's) running in addition to the regular system files. (I know not all the modules are always loaded and unused ones sit dormant). For older devices that don't have enough ram etc this caused problems if you loaded it up too much. I guess this is what i based my opinion on. Then again you could be right and I have no clue about how xposed works. Lol. INo offense taken viperboy. I'm just used to doing everythong manually aka the hard way. Lol
Click to expand...
Click to collapse
Read up on it a bit. You define a method that you want to modify and you can do things such as modify that method before, during, or after it runs. That's why xposed is awesome and extremely versatile. The only time you typically need to update your xposed code is when the method you're modifying moves to a different class or the logic in it dramatically changes, which doesn't happen too often between software versions for most major things one would want to modify.
-viperboy- said:
Read up on it a bit. You define a method that you want to modify and you can do things such as modify that method before, during, or after it runs. That's why xposed is awesome and extremely versatile. The only time you typically need to update your xposed code is when the method you're modifying moves to a different class or the logic in it dramatically changes, which doesn't happen too often between software versions for most major things one would want to modify.
Click to expand...
Click to collapse
So does that mean xposed will get updated to work with lollipop/ART?
And I remember you from eVo 4g lte, will you be deving on this phone?
After doing literally everything to fix my phones lag, I took it too the Sprint store and they verified that they have had several Notes with the same issue. Apparently it is a motherboard issue that some of the earlier phones have had.
Mine wasn't so much lag, as the phone was perfectly fine, it was mostly that the phone would freeze upon flicking/scrolling/typing for 1 second randomly, and then it would mash all the commands you had entered in at once to catch up. Was VERY frustrating. I'm just glad it was hardware related, and not software like I believed..
I'll be getting a replacement free of charge on Tuesday.
Jeffbucc said:
After doing literally everything to fix my phones lag, I took it too the Sprint store and they verified that they have had several Notes with the same issue. Apparently it is a motherboard issue that some of the earlier phones have had.
Mine wasn't so much lag, as the phone was perfectly fine, it was mostly that the phone would freeze upon flicking/scrolling/typing for 1 second randomly, and then it would mash all the commands you had entered in at once to catch up. Was VERY frustrating. I'm just glad it was hardware related, and not software like I believed..
I'll be getting a replacement free of charge on Tuesday.
Click to expand...
Click to collapse
How long have you had the phone?
Preordered through Sprint and recieved it the day before release.
I'm having same issue. Every 3-5 seconds my phone freezes for a second. You can even see it recording a video. I tries the reset but still no go. Going to sprint Monday.
Same here and i never installed exposed
Sent from my SM-N910P using JellyBombed Tapatalk 2
Jeffbucc said:
Preordered through Sprint and recieved it the day before release.
Click to expand...
Click to collapse
Did they give you any problem being outside the 14 day return period?
jhill110 said:
Did they give you any problem being outside the 14 day return period?
Click to expand...
Click to collapse
None at all, but I also added the $10 insurance to my Note 4 upon activation. It covers 2 phone replacements no questions asked. They didn't even mention my knox being tripped.
Took my phone this morning to local store. Guy at store said he would order me a new one on Monday. Didn't want to give me a refurbishes one. He tried the phone for 2 minutes and said it needed to be replaced.
Hey guys! Since last week I've been experiencing some weird problems with my LG G3 d855 screen blacking out, everything was working OK, the last thing I remember installing was Opera Max,
don't know if this have to do something, BUT I've didn't dropped my phone or anything, It was working at all times, maybe it's time has come?
I've factory reset to see if solved but no luck. I attach a video so you can see what the problem is, it doesn't happen at all times, I can still use the phone normally and a few times a day the problem appears.
Can someone confirm I have to replace the whole screen? or is it something else?
https://youtu.be/JYbYg4cfqYE
gado45 said:
Hey guys! Since last week I've been experiencing some weird problems with my LG G3 d855 screen blacking out, everything was working OK, the last thing I remember installing was Opera Max,
don't know if this have to had something, BUT I've didn't dropped my phone or anything, It was working at all times, maybe it's time has come?
I've factory reset to see if solved but no luck. I attach a video so you can see what the problem is, it doesn't happen at all times, I can still use the phone normally and a few times a day the problem appears.
Can someone confirm I have to replace the whole screen? or is it something else?
https://youtu.be/JYbYg4cfqYE
Click to expand...
Click to collapse
it happened to me after putting the kernel with Android xceed 6, only solution is to remove the battery, is repeated by the browser think
davidez25 said:
it happened to me after putting the kernel with Android xceed 6, only solution is to remove the battery, is repeated by the browser think
Click to expand...
Click to collapse
don't know if It's a kernel thing, it also happened at recovery and when booting. Im on stock MM 30b since it got out without any problems and suddenly this.
Did you solve your problem?
davidez25 said:
it happened to me after putting the kernel with Android xceed 6, only solution is to remove the battery, is repeated by the browser think
Click to expand...
Click to collapse
There have been a couple of suggested fixes:
https://www.reddit.com/r/LGG3/comments/3j6puw/screen_flicker_and_fade_please_help/
This simple version of this one worked for me for a few days. I'm going to try the more involved version (still fairly simple)
http://forums.androidcentral.com/lg-g3/527306-why-does-my-lg-g3-screen-flicker-fades-darkness-8.html
And an existing thread here: http://forum.xda-developers.com/lg-g3/help/screen-fades-to-black-flickering-issue-t3255804
I chatted with LG's customer service and they basically denied the existence of any systemic problem.
OMG so many people with the same problem. I've readed all the posts on ac's forum, most of them complaining about LG customer service and how about they even know what the problem really is.. And in almost every case problem appeared after the warranty ended. Awful experience with LG.
Hey guys,
About 1 month ago the screen of my OP3 broke and I bought a replacement on eBay.
After the replacement I encountered problems, which only occured from time to time. Sometimes when waking up my device the screen stayed black.(Like on every 20th attempt it happened once). After pressing the power button some more times, the device finally unlocked. I am 100% sure that the device always unlocked on uneven attempts which means that the device at least woke up software-side.
I was totally sure that my replacement screen was kinda flawed and it is a not fixable hardware problem.
Then one week ago I switched from official LOS15.1 to the unofficial LOS16 rom and encountered big differences. The problem got noticebly worse. Waking up the device was a pain in the a**, it never worked on the first attempt on this rom. It's not unusual that it takes between 11 and up to 60 tries to wake up the device which makes it nearly impossible to use the phone. As before, the screen at least turns on software-side after every attempt. I can see this because the hardware buttons always light up.
Now after one week I switched back to official LOS15.1 and voilà, out of 20 attempts, the device instantly unlocked 19 times.
I know it is hard to understand and even to analyze such kind of problems, but there must be some solid solution for my problem.
Atm my clue is that original screens always offer more functions (e.g. gestures) than replacement lcd screens. Those functions are always connected to the software(rom). Is it possible that there is any other function (e.g. anything related to tap2wake or deepsleep) which is able to prevent my screen from turning on?
To deliver some more infos:
- I used standard system settings on both roms to test this out.
- "prevent" accitential wake up is turned off
- tried to disable gestures
- I tested my proximity sensor via an app, it seems to work flawless
- waking up screen in twrp is also very difficult and needs around 15-20 tries. Does anyone see any pattern?
gt-kingz said:
Hey guys,
About 1 month ago the screen of my OP3 broke and I bought a replacement on eBay.
After the replacement I encountered problems, which only occured from time to time. Sometimes when waking up my device the screen stayed black.(Like on every 20th attempt it happened once). After pressing the power button some more times, the device finally unlocked. I am 100% sure that the device always unlocked on uneven attempts which means that the device at least woke up software-side.
I was totally sure that my replacement screen was kinda flawed and it is a not fixable hardware problem.
Then one week ago I switched from official LOS15.1 to the unofficial LOS16 rom and encountered big differences. The problem got noticebly worse. Waking up the device was a pain in the a**, it never worked on the first attempt on this rom. It's not unusual that it takes between 11 and up to 60 tries to wake up the device which makes it nearly impossible to use the phone. As before, the screen at least turns on software-side after every attempt. I can see this because the hardware buttons always light up.
Now after one week I switched back to official LOS15.1 and voilà, out of 20 attempts, the device instantly unlocked 19 times.
I know it is hard to understand and even to analyze such kind of problems, but there must be some solid solution for my problem.
Atm my clue is that original screens always offer more functions (e.g. gestures) than replacement lcd screens. Those functions are always connected to the software(rom). Is it possible that there is any other function (e.g. anything related to tap2wake or deepsleep) which is able to prevent my screen from turning on?
To deliver some more infos:
- I used standard system settings on both roms to test this out.
- "prevent" accitential wake up is turned off
- tried to disable gestures
- I tested my proximity sensor via an app, it seems to work flawless
- waking up screen in twrp is also very difficult and needs around 15-20 tries. Does anyone see any pattern?
Click to expand...
Click to collapse
You most likely got a bad part. OEM like One plus and xioami are known for using something called product binning. Which means their parts have a higher failure rate then other oems. They also dont make extra parts really so what you got was most likely just a generic screen like you can buy at any shop in China.
Nothing you can really do about it except try a different screen but to be honest I would get a different device and this time dont skip on the price. You get what you pay for and when a good device is cheap there is always a reason. (why do you think most of the owners and mods of XDA run Iphones as their daily drivers and leave android for a hobby)
gt-kingz said:
Hey guys,
About 1 month ago the screen of my OP3 broke and I bought a replacement on eBay.
After the replacement I encountered problems, which only occured from time to time. Sometimes when waking up my device the screen stayed black.(Like on every 20th attempt it happened once). After pressing the power button some more times, the device finally unlocked. I am 100% sure that the device always unlocked on uneven attempts which means that the device at least woke up software-side.
I was totally sure that my replacement screen was kinda flawed and it is a not fixable hardware problem.
Then one week ago I switched from official LOS15.1 to the unofficial LOS16 rom and encountered big differences. The problem got noticebly worse. Waking up the device was a pain in the a**, it never worked on the first attempt on this rom. It's not unusual that it takes between 11 and up to 60 tries to wake up the device which makes it nearly impossible to use the phone. As before, the screen at least turns on software-side after every attempt. I can see this because the hardware buttons always light up.
Now after one week I switched back to official LOS15.1 and voilà, out of 20 attempts, the device instantly unlocked 19 times.
I know it is hard to understand and even to analyze such kind of problems, but there must be some solid solution for my problem.
Atm my clue is that original screens always offer more functions (e.g. gestures) than replacement lcd screens. Those functions are always connected to the software(rom). Is it possible that there is any other function (e.g. anything related to tap2wake or deepsleep) which is able to prevent my screen from turning on?
To deliver some more infos:
- I used standard system settings on both roms to test this out.
- "prevent" accitential wake up is turned off
- tried to disable gestures
- I tested my proximity sensor via an app, it seems to work flawless
- waking up screen in twrp is also very difficult and needs around 15-20 tries. Does anyone see any pattern?
Click to expand...
Click to collapse
As an experiment, try stock OOS and see whether the issue goes away.
i too have this problem cant find any solution anywhere been trying for about a week now arrggghh
ireaper4592 said:
i too have this problem cant find any solution anywhere been trying for about a week now arrggghh
Click to expand...
Click to collapse
tnsmani said:
As an experiment, try stock OOS and see whether the issue goes away.
Click to expand...
Click to collapse
Hey there again. I know my answer is kinda late but I wanted to share my experience. So I tried like 10 different custom ROMs with different Android version. The problem got even worse sometimes.
Anyway a few days ago I installed stock OOS and the problem is fixed now. I could not believe at first, but after excessive testing I am 100% sure now.
Anyone can tell why? Is the stock display driver proprietary?
TBH I always used to use custom ROMs (mostly CyanogenMod and now Lineage. Now on stock rom O feel like everything is better than ever before. Battery life, performance. Some features even offer more customization than custom ROMs.
I always thought the opposite is the case since custom roms advertise things like this. I will definitely stick with stock rom for now!
gt-kingz said:
Hey there again. I know my answer is kinda late but I wanted to share my experience. So I tried like 10 different custom ROMs with different Android version. The problem got even worse sometimes.
Anyway a few days ago I installed stock OOS and the problem is fixed now. I could not believe at first, but after excessive testing I am 100% sure now.
Anyone can tell why? Is the stock display driver proprietary?
TBH I always used to use custom ROMs (mostly CyanogenMod and now Lineage. Now on stock rom O feel like everything is better than ever before. Battery life, performance. Some features even offer more customization than custom ROMs.
I always thought the opposite is the case since custom roms advertise things like this. I will definitely stick with stock rom for now!
Click to expand...
Click to collapse
Thanks for the confirmation. The cheaper screens seem to have an issue which is not faced by the costlier ones. I have found while roaming the threads that sometimes flashing OOS helps. May be a driver issue.
My understanding from what I've read, third party displays needed kernel support.
I paid OP to replace mine - no problems.
Hi!
I'm having a similar issue with my Oneplus 5. Had my screen replaced (new one: OEM) and now it doesn't wake up most of the time either using power button or double tap or fingerprint scanner. I tried everything that I read on forums but nothing worked. Now I seem to have found a solution that I haven't read anywhere yet: I turned off night mode and now it's working as it should. Actually, whenever I want to use any screen adjustment feature like night mode, reading mode etc the screen doesn't wake up. But if I keep the default settings, there is no problem. The issue is definitely the new screen because before that I used night mode all the time (I mean after dark). Now I'm still thinking if I should return the phone to the repair shop and ask for another screen (they offer one year warranty after the repair) or just deal with it... I mean these OEM screen are cheap for a reason (as someone had written here before) and there is no guarantee that the next one will be good, and I don't feel like waiting weeks again for an uncertain outcome, also I can live without said features (gonna miss night mode tho'). Any suggestion? Should I give it a try? Maybe the repair shop made a mistake during assembly? Anyway, I hope this comment will be helpful for those lurking for a solution for a similar problem.
csabatoro said:
Hi!
I'm having a similar issue with my Oneplus 5. Had my screen replaced (new one: OEM) and now it doesn't wake up most of the time either using power button or double tap or fingerprint scanner. I tried everything that I read on forums but nothing worked. Now I seem to have found a solution that I haven't read anywhere yet: I turned off night mode and now it's working as it should. Actually, whenever I want to use any screen adjustment feature like night mode, reading mode etc the screen doesn't wake up. But if I keep the default settings, there is no problem. The issue is definitely the new screen because before that I used night mode all the time (I mean after dark). Now I'm still thinking if I should return the phone to the repair shop and ask for another screen (they offer one year warranty after the repair) or just deal with it... I mean these OEM screen are cheap for a reason (as someone had written here before) and there is no guarantee that the next one will be good, and I don't feel like waiting weeks again for an uncertain outcome, also I can live without said features (gonna miss night mode tho'). Any suggestion? Should I give it a try? Maybe the repair shop made a mistake during assembly? Anyway, I hope this comment will be helpful for those lurking for a solution for a similar problem.
Click to expand...
Click to collapse
Did you try OOS?
OEM screen is not cheap (atleast compared to what is offerred online).
May be you are better off with what you have since you have found a work around. Who knows what you will get next time?
Yea I have same problem it works totally fine on oos but on custom roms it is ****ed up
skymera said:
My understanding from what I've read, third party displays needed kernel support.
I paid OP to replace mine - no problems.
Click to expand...
Click to collapse
How much plz?
Shreeram02 said:
Yea I have same problem it works totally fine on oos but on custom roms it is ****ed up
Click to expand...
Click to collapse
Thank you also for confirming that on OOS there is no issue. Looks like the cheaper of the online replacements have this issue while the costlier ones don't.
Funniest thing is I have a slim ROM backup on 7.1. and that works fine so like what the f--- any ideas people?
gt-kingz said:
Hey guys,
About 1 month ago the screen of my OP3 broke and I bought a replacement on eBay.
After the replacement I encountered problems, which only occured from time to time. Sometimes when waking up my device the screen stayed black.(Like on every 20th attempt it happened once). After pressing the power button some more times, the device finally unlocked. I am 100% sure that the device always unlocked on uneven attempts which means that the device at least woke up software-side.
I was totally sure that my replacement screen was kinda flawed and it is a not fixable hardware problem.
Then one week ago I switched from official LOS15.1 to the unofficial LOS16 rom and encountered big differences. The problem got noticebly worse. Waking up the device was a pain in the a**, it never worked on the first attempt on this rom. It's not unusual that it takes between 11 and up to 60 tries to wake up the device which makes it nearly impossible to use the phone. As before, the screen at least turns on software-side after every attempt. I can see this because the hardware buttons always light up.
Now after one week I switched back to official LOS15.1 and voilà, out of 20 attempts, the device instantly unlocked 19 times.
I know it is hard to understand and even to analyze such kind of problems, but there must be some solid solution for my problem.
Atm my clue is that original screens always offer more functions (e.g. gestures) than replacement lcd screens. Those functions are always connected to the software(rom). Is it possible that there is any other function (e.g. anything related to tap2wake or deepsleep) which is able to prevent my screen from turning on?
To deliver some more infos:
- I used standard system settings on both roms to test this out.
- "prevent" accitential wake up is turned off
- tried to disable gestures
- I tested my proximity sensor via an app, it seems to work flawless
- waking up screen in twrp is also very difficult and needs around 15-20 tries. Does anyone see any pattern?
Click to expand...
Click to collapse
Yes, I have the same issue and I wanted to revert back to Stock OOS, but I just tried Caesium latest kernel, and the display wakeup issue seems to have gone. I'm using Havoc OS 2.3 based on Android Pie.
Guys the latest mad kernal reborn it wakes up all the time
At least for my screen
It used to be worse on all the other kernals
Finally found a solution
I had same problem on custom roms after replacement of display of my oneplus3...i was on oos 5.0.8 i had no issues in that but am a custom rom user and now the solution is flash any rom clean flash not dirty flash and flash gapps then flash any module if you want like magisk and then reboot setup the device and after first boot flash mcd custom kernel and yippeee enjoy... Present am on havoc os with no issues... Try and let me know...
Mohammed Raihan said:
I had same problem on custom roms after replacement of display of my oneplus3...i was on oos 5.0.8 i had no issues in that but am a custom rom user and now the solution is flash any rom clean flash not dirty flash and flash gapps then flash any module if you want like magisk and then reboot setup the device and after first boot flash mcd custom kernel and yippeee enjoy... Present am on havoc os with no issues... Try and let me know...
Click to expand...
Click to collapse
post link to one u have plz
Mail me i have that file..
[email protected]
There is issue while sending here
Mohammed Raihan said:
[email protected]
There is issue while sending here
Click to expand...
Click to collapse
got anyway working fine cheers dude
Even i have the same problem as mentioned above..even i changed my oneplus 3 display
I always prefer custom roms..but screen wakeup issue had made my phone worse...then i tried oos 5.0.8 and it works like a charm...yeah i know its very old android version but no other option though...
Others who have same problem and have no issues going back to oos oreo then go for it...your problem is solved..
---------- Post added at 01:47 PM ---------- Previous post was at 01:43 PM ----------
ireaper4592 said:
got anyway working fine cheers dude
Click to expand...
Click to collapse
Is this kernel working for you!??