Related
I've search high and low but it seems like any thread related to this was closed when the forums were split up. In any case, please report any screen flicker issues here and what keyboard you might be using and whether or not you're rooted. I bought this phone new and had a screen flicker before I rooted it. I figured it might be software related so I rooted and installed another ROM. I still notice it from time to time when typing. I don't think this flicker will ever go away. I'm now on CM10 and still notice the problem. I've been using Swiftkey from the start but I'm not sure yet if that's what causing it.
Thanks to TechSavvy2, I think this problem has been fixed.
Originally Posted by TechSavvy2
Go to settings - developer options - and check the box disable hw overlays. It should drastically fix flicker or at least help till the fix is merged (who knows when)
Click to expand...
Click to collapse
Known problems when selecting this option.
-Swiftkey FC's. (link to vote to fix problem - http://support.swiftkey.net/forums/116693-2-swiftkey-bugs-/suggestions/3143605-disabled-hw-overlays-due-to-screen-flicker-galaxy-
I have experienced it too on my s3
AndroidGraphix said:
I've search high and low but it seems like any thread related to this was closed when the forums were split up. In any case, please report any screen flicker issues here and what keyboard you might be using and whether or not you're rooted. I bought this phone new and had a screen flicker before I rooted it. I figured it might be software related so I rooted and installed another ROM. I still notice it from time to time when typing. I don't think this flicker will ever go away. I'm now on CM10 and still notice the problem. I've been using Swiftkey from the start but I'm not sure yet if that's what causing it.
Click to expand...
Click to collapse
Aren't you on CM10??? Go to settings - developer options - and check the box disable hw overlays. It should drastically fix flicker or at least help till the fix is merged (who knows when)
Sent from my Galaxy S3 using Tapatalk 2
TechSavvy2 said:
Aren't you on CM10??? Go to settings - developer options - and check the box disable hw overlays. It should drastically fix flicker or at least help till the fix is merged (who knows when)
Sent from my Galaxy S3 using Tapatalk 2
Click to expand...
Click to collapse
I'm pretty sure this has fixed the screen flicker problem for the galaxy s3. Thanks a million. What exactly does this option do
Sent from my SCH-I535 using xda premium
AndroidGraphix said:
I'm pretty sure this has fixed the screen flicker problem for the galaxy s3. Thanks a million. What exactly does this option do
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Not sure what it does, but you will need to tick the same option every time you reboot if you're on CM10 official at least(I can't speak for the other AOSP ROMs.)
You got a screen flicker BEFORE you did anything to your phone tho? That's the first I've heard of the flicker anywhere except an AOSP ROM. Hmmm. And was/is it only when you used Swiftkey? If so, gotta be some conflict between Swiftkey and our phones. (I really don't care for swiftkey since it doesn't have any kind of swipe option. I use Touchpal, which is pretty good on the autocorrect/predictions especially for a freebie)
I've also had the screen flicker on my phone since I activated it. I am on stock touchwiz and the thing that kepts it from occuring every time i opened the keyboard was installing thumb keyboard. I really wish Samsung would send a fix sometime in the near future. I am hoping this is just a software issue and not hardware.
shangrila500 said:
I've also had the screen flicker on my phone since I activated it. I am on stock touchwiz and the thing that kepts it from occuring every time i opened the keyboard was installing thumb keyboard. I really wish Samsung would send a fix sometime in the near future. I am hoping this is just a software issue and not hardware.
Click to expand...
Click to collapse
Ya, I know for a fact, I had the flicker before I rooted or even changed the bootloader. I've tried every rom out there and still have a real bad flicker every now and then. It does go away when I turn hw overlays off but by turning it off I can't use SwiftKey which really bites. Isn't this an indication its software related?
And I'm not sure if it's just SwiftKey related. I guess, I'll experiment with the other keyboard to test.
By any chance could it be kernel related?
Sent from my SCH-I535 using xda premium
It happened to my GF's S3, lets call this S3 A, screen fickers and with series of lines vertically, phone freezes, had to do hard boot, then the battery dropped to 3% instantly. We think it's the battery, lucky us, we have another S3, we'll call this S3 B, in which has no flickering issue, and we exchange the battery and the flickering did not happen on S3 A anymore but it did happen to S3 B in which has no flickering issues at all from the start.
And we noticed the S3 A battery is beginning to bloat (it is getting fatter than the battery of S3 B) maybe due to wear and tear or over charging.
So our conclusion, the battery is culprit, we've replaced it and we'll observe for about a week.
I can also experience flickering and very crappy battery life. Guess I need to buy a new batter then? I don't want to waste money if changing batter doesn't work so please tell me if I should buy or not.
Is there any reason why this would happen?
Another one here experiencing the same issue
Another one here experiencing the same issue.
It didn't happen to my device until I upgraded to 4.0.4 Android and HTC Sense 4.1 (Spanish Orange network HTC One S version 2.38.75.4).
When it switch on while on a pocket it is very annoying as the phone "tries" to make an emergency call.
Faulty power button?
Sent from my locked, tampered ville
jaywhy13 said:
Is there any reason why this would happen?
Click to expand...
Click to collapse
This will say:
AirPush Detector. You find this app on the Play Market.
usaff22 said:
Faulty power button?
Sent from my locked, tampered ville
Click to expand...
Click to collapse
Only detected after a firmware update? I don't think so.
I was flashing the new Viper on my nieces phone and didn't quite get everything set up the way she likes it before she had to go home so I had to restore her nandroid of Viper ICS and now she is texting me telling me she is having this issue. Can anyone tell me if they ever had this issue and resolved it and if so i guess i might resolve it when i see her next weekend by reflashing the ROM? Or is it a serious issue or maybe one she can resolve? thanks for any info pertaining to this, my niece is quite picky and i am sure any of us crackflashers here know what it is like when you promise a woman the best for her phone then screw it up for her, never hear the end of it! lol. thanks for any help!
LibertyMonger said:
I was flashing the new Viper on my nieces phone and didn't quite get everything set up the way she likes it before she had to go home so I had to restore her nandroid of Viper ICS and now she is texting me telling me she is having this issue. Can anyone tell me if they ever had this issue and resolved it and if so i guess i might resolve it when i see her next weekend by reflashing the ROM? Or is it a serious issue or maybe one she can resolve? thanks for any info pertaining to this, my niece is quite picky and i am sure any of us crackflashers here know what it is like when you promise a woman the best for her phone then screw it up for her, never hear the end of it! lol. thanks for any help!
Click to expand...
Click to collapse
All i can really think of is that in the viper rom you have the option under tweaks to let the screen turn on when a message arrives. Mine used to do the same thing every once in a while but it was somehow connected to my data connectivity jumping all over the place so i re-flashed and wiped caches which did the trick.
Hope you get the problem resolved for your nieces sake!
I'm having the same issue with my Evo LTE
The same problem with SGS2 / ICS 4.0.3. Any idea how to fix that please ? It is VERY annoying, cuz it drains my battery !!!
aquinoe said:
Only detected after a firmware update? I don't think so.
Click to expand...
Click to collapse
In my original post I was talking to the OP.
It's not a software problem on the One S, look at everyone else with the same problem.
Sent from my HTC One S using Tapatalk 2
jaywhy13 said:
Is there any reason why this would happen?
Click to expand...
Click to collapse
If there are still people with this kind of issue,
I would recommend to check for "wakelock" usage.
As third-party apps can use "wakelock" to turn on the screen, there might be some buggy app which is using the feature improperly.
I had the same case before, turned out that "Naver Mail" app was using Screen wakelock to turn the screen on randomly.
As a solution, there is an app in Google Play called "Wakelock detector" which has a feature to show statistics of Screen wakelocks.
GooD luck
Random Screen On caused by faulty power adapter
I changed my power adapter for charging, and the problem went away immediately. I assume it was the result of either drawing too much power, or not enough to charge the phone. Anyway, there you go. Hope it helps! :silly:
touch screen sensitivity is so low, sometime it gets stuck when typing or just miss a few keys and very very annoying. is there a way to fix this ATM ? i'm not sure its software problem or my phone is defected. i flashed like 5 6 roms already but the problem still there, change to another keyboard and samething . any help ?
Software. Have to wait for an official fix
Sent from my A0001 using Tapatalk
sjhotwings said:
touch screen sensitivity is so low, sometime it gets stuck when typing or just miss a few keys and very very annoying. is there a way to fix this ATM ? i'm not sure its software problem or my phone is defected. i flashed like 5 6 roms already but the problem still there, change to another keyboard and samething . any help ?
Click to expand...
Click to collapse
I feel your pain. My situation is absolutely the same. I beleive it could have started after I used the chinese car charger and power bank on vacation. Did you use something like that?
sjhotwings said:
touch screen sensitivity is so low, sometime it gets stuck when typing or just miss a few keys and very very annoying. is there a way to fix this ATM ? i'm not sure its software problem or my phone is defected. i flashed like 5 6 roms already but the problem still there, change to another keyboard and samething . any help ?
Click to expand...
Click to collapse
The problem is in the touchscreen firmware and the fix have to be released from synaptics and not frome Oneplus.
The fact is that it may take a few or a long time based on the issue and it may be enven never be fixed, who knows.
As now i am really disappointed. They should have never release da device knowing of such a major bug.
ky3bmu4 said:
I feel your pain. My situation is absolutely the same. I beleive it could have started after I used the chinese car charger and power bank on vacation. Did you use something like that?
Click to expand...
Click to collapse
No, nothing related to the charger tho haha. the problem started as soon as i turn on the phone for the first time and it went crazy like that since then. i flashed almost every rom on here still no good. i flashed fusionjack slimsaber rom earlier and it really improved alot . you might want to check that rom out.i'm gonna stick w/ slimsaber for a while now i guess
sjhotwings said:
No, nothing related to the charger tho haha. the problem started as soon as i turn on the phone for the first time and it went crazy like that since then. i flashed almost every rom on here still no good. i flashed fusionjack slimsaber rom earlier and it really improved alot . you might want to check that rom out.i'm gonna stick w/ slimsaber for a while now i guess
Click to expand...
Click to collapse
Thx for the advice. For me the issue seems to be solved randomly when I restored the 33R in Twrp. However some other problems remain: like not getting back to the mobile Internet after leaving the wifi area or loseing the network at all ( curable by switching on and off the airplane mode or rebooting respectively).
My phone is cursed really xD
ky3bmu4 said:
Thx for the advice. For me the issue seems to be solved randomly when I restored the 33R in Twrp. However some other problems remain: like not getting back to the mobile Internet after leaving the wifi area or loseing the network at all ( curable by switching on and off the airplane mode or rebooting respectively).
My phone is cursed really xD
Click to expand...
Click to collapse
try slimsaber , it worked very good for me . and hope it work for you too
sjhotwings said:
try slimsaber , it worked very good for me . and hope it work for you too
Click to expand...
Click to collapse
I'm not sure if this is the same issue, but when you run a touch screen test, does it work with more than one touch? IE is multitouch working? I had an issue the other day and I resolved it by turning off the phone, attaching it to the charger and then turning it back on (read it on the oneplus forum). It is a known issue and they are working on bringing us the fix.
Hope this is helpful.
I have this issue too, although it's been mitigated somewhat by the most recent software patches they pushed in 30O and 33R. I'm on a CM nightly at the moment and it's certainly usable. I made the issue a lot better by disabling haptic feedback in the SwiftKey settings - it almost feels like that extra effort to run the vibrating motor causes the screen to respond badly or something.
Is it doing this?
http://youtu.be/XsGPsDP4V0U
If so this is what mine is doing and it's soooo annoying trying to type.
http://www.androidheadlines.com/201...ti-touch-issues-oneplus-one-fix-incoming.html
Some-not me, have been able to mitigate the problem by running a code through terminal emulator.
This has been brought up in CM bug log as Bacon 55.
You don't have to be rooted to do this.
Type: su (if you're rooted)
Type: cat /sys/class/input/input0/baseline_test
Press enter.
Note that you will need to do this every time you reboot your phone.
Credits to a member on jira cm. Forgot to name! Hope it works for you
I've tried everything and everything failed.
Let's hope synaptics pushes out a fix soon. I can't stand this issue. Basically two different touches near each other are recognized as a swype -_-'
i did a test using multitouch test app. i use 1 finger touch on the phone and got a red dot, finger #2 gave me a blue dot . as soon as my 2 fingers get close together 1 of the dot disappear, also test w/ 4 5 fingers same result .thats why if you text really fast , you get alot of missing words and sometime it lag and get stuck.
I think that until this gets fixed the phone will be not ready to be sold,too...
Sent from my Oneplus One
Here is a fix I have tried and it has helped me a lotttt.
https://play.google.com/store/apps/details?id=br.shop4apps.touchscreenbooster.com
DuckMcQUack said:
I think that until this gets fixed the phone will be not ready to be sold,too...
Sent from my Oneplus One
Click to expand...
Click to collapse
Is this phone worth purchasing since customer service is not readily available. I'm not sure if I want to spend my money and not be able to get quality customer service. What are your thoughts?
alhadee12 said:
Is this phone worth purchasing since customer service is not readily available. I'm not sure if I want to spend my money and not be able to get quality customer service. What are your thoughts?
Click to expand...
Click to collapse
As long as the touchscreen issue is not fixed the phone has to be considered to be bugged and faulty. I would not spend my money on a defective phone at a very few weeks from N6 release that will be a superior terminal by far.
Even if it gets fixed it will be not worthy the same as N& is near to come anyways.
I wish i didn't buy mine.
DuckMcQUack said:
As long as the touchscreen issue is not fixed the phone has to be considered to be bugged and faulty. I would not spend my money on a defective phone at a very few weeks from N6 release that will be a superior terminal by far.
Even if it gets fixed it will be not worthy the same as N& is near to come anyways.
I wish i didn't buy mine.
Click to expand...
Click to collapse
Thanks, I started becoming more concerned because users have been paying long wait times for service and possibly having to ship back to China at the customers cost. That's a bad deal.
alhadee12 said:
Thanks, I started becoming more concerned because users have been paying long wait times for service and possibly having to ship back to China at the customers cost. That's a bad deal.
Click to expand...
Click to collapse
Definitely. I would stay away from this thing.
And by the way who knows if the ghost touches/swypes problem is not even a software issue just as the multitouch not working when placing the phone on a non-conductive surface...
Hi there,
(Im opening a new thread as the old one was completely off the topic of the original post)
So on CM11S, my phone screen was working fine. After the CM12S update, my phones screen sometimes doesn't respond correctly when I go to unlock my phone with the unlock pattern. (The timing of the update and the problem occurring may just be coincidence) Its as if holding your finger on the screen isn't registered as staying on the screen, its like the phone thinks I am lifting my finger off and reapplying it very quickly, I cant draw my unlock pattern and unlock my phone. It also affects the 'swipe down' I must do to get the unlock pattern prompt.
If I restart my phone, it usually fixes the problem. Although in the past few days, it has started happening more frequently and sometimes restarting the phone doesn't solve the issue. It is becoming more of a frustration now because of how frequently I have to restart my phone just to unlock it.
I first believed that using a glass screen protector was the problem, I thought the glass was causing ghost touches, so I removed my glass protector and replaced it with a film protector, at first it seemed that this was the problem, but I have just encountered the problem again. I'm not sure if its a hardware or a software issue, because restarting the device is fixing the problem most of the time, but its also switching off all power to the digitizer during a reboot so I cant tell what is the culprit.
I've opened a support ticket with OnePlus but it says it can be up to 10 days before I get a reply, I figured I'd post here too to see if anyone else has had similar issues or even found a fix.
Thanks in advance!
I had the same problem
I was having the same issue, although I never updated to CM12S. Instead, this happened to me when running Exodus Lollipop ROM and the SlimLP ROM. Since then, I have switched to Paranoid Android Alpha2 and have not had the issue recur in the last few days running PA. So to me it seems like a software glitch in many of the Lollipop ROMs. Try PA if you like and see if it's fixed.
welcome to ghost touch
google "oneplus one ghost touch" and join the hundreds of other known cases
I had a feeling this was the ghost touch issue, but my phone hasn't really had actual ghost touches, its just that most of screen stops working. I've got a few videos of it happening. First the screen goes a bit unresponsive, then after a short while, about 1/3 of the screen is completely unresponsive, I switched on show touches in development options and you can see that from the middle to the bottom of the screen there is no response unless I use the very edge on the right side, then it works, its like it has a dead spot. If I reboot my phone, that usually fixes the problem for a while, sometimes up to a whole day, but the problem comes back with time.
I was given a patch by the OnePlus automated support message, and it says my case has been forwarded to a specialist. I have just applied the patch which has rolled me back to CM11, I'm guessing it did more than just that, but the patch and notes don't really explain what it does. Either way, I'm in the process of receiving OTA updates so I can get back on CO12 so I can hopefully restore my data with my ADB backup (never done this before, not rooted my One yet)
Has anyone had any success with this patch?
Thanks
EDIT: So my ADB Backup isn't restoring on my phone. I am using Holo Backup (formerly Simple ADB Backup) and when I chose restore and select the backup, it just show the output for the help command from ADB and then doesnt appear to do anything else. Are there any manual commands to restore my backup or have I done something wrong?
Try going back to cm11s and then check...
Sent from Android (a google product)
Hi there,
So heres an update, I applied the first patch and it rolled me back to CM11S and the issue was still present on CM11S, I then got OTA's back up to CO12 and the issue still happens. I have turned off the off screen gestures and the ambient wakeup thing. It doesn't happen as often but when it happens, 2 restarts are needed to get it running smooth again.
My support ticket with OnePlus has gone quiet and I don't really know what my next step is? I have heard there is a second patch but I couldn't backup properly last time with ADB so I don't know if I want to go through all of the wiping and reupdating again when people report the 2nd patch is also ineffective.
Does anyone have any suggestions? I feel a bit cheated now knowing that my phone has what I can tell to be a manufacturing defect / hardware issue.
Another update here.
So after a week of silence from the OnePlus tech support, I have a new person handling my ticket and he has told me that I need to apply another display patch. I'm guessing this is the 2nd patch and not this final patch which was mentioned by Carl on Facebook.
Either way, I ran into a problem applying the 1st patch, I couldn't make a proper backup of my phone before I did the patch. I used SimpleADBBackup which I thought would work well but it took a very long time to create the backup and then when I applied the backup back onto my newly flashed phone, It missed many apps, only did app data for a few apps and didn't take any of my pictures or SD storage, so all my SMS and Call log backups were also lost. I would like to take a proper backup this time but I don't know how to do it? I don't trust this ADB backup method, even on the Simple ADB Backup program, it admits that ADB backups are hacky and untested.
I have been trying to use Helium but for some reason, my phone wont get past connecting it to the computer companion app, I have all phone drivers and ADB drivers installed correctly, but helium on the android side cant seem to see the computer app, the computer side of the app says that helium is enabled, but on my phone it is stuck on "waiting for the helium desktop app".
I feel like I'm having the worst luck with this phone, and its frustrating because I really like this phone and this flaw is really getting in the way of using this phone, I counted 8 restarts in one day due to the screen not working.
I hope someone can help me out, I don't want to fully wipe my phone again and I cant seem to back anything up correctly!
One more here... when everyone had the probelms, my screen works almost good... now trying the nightli from Cm... the problems become mroe and more big... ( than soon it is oneplus two? xD Its not in my mind waste more money on OPO company... jajajaja Any solution? we waiting for the miracle update they promised?
naghtan said:
One more here... when everyone had the probelms, my screen works almost good... now trying the nightli from Cm... the problems become mroe and more big... ( than soon it is oneplus two? xD Its not in my mind waste more money on OPO company... jajajaja Any solution? we waiting for the miracle update they promised?
Click to expand...
Click to collapse
I'm not sure if a full solution has been found yet. I read on Facebook that they are working with Synaptics to make a final patch which should solve the issue.
I've given up on trying to backup my phone without root, it just seems impossible to do right. I've just applied the 2nd display patch and got my phone running again, I think I may stay on CM11 and just forget lollipop until this issue gets resolved. I'm pretty sure last time I was on KitKat, the issues were there still but it may be less frequent, who knows?!
Do I have a better chance of seeing this screen issue less on KitKat or should I just update to CO12 for the 3rd time?
Another update here,
I have been instructed and have booked a remote session with OnePlus. I'm guessing they are going to be flashing CO12 or OxygenOS and hopefully some kind of display patch or calibration fix. I really hope this solves my problem, the issue has become a daily occurrence and I have also finally seen a ghost touch, it looked like it was trembling . I really love this phone apart from this issue but it happens way too often to ignore it. Ill post what happens after the session.
donk165 said:
Another update here,
I have been instructed and have booked a remote session with OnePlus. I'm guessing they are going to be flashing CO12 or OxygenOS and hopefully some kind of display patch or calibration fix. I really hope this solves my problem, the issue has become a daily occurrence and I have also finally seen a ghost touch, it looked like it was trembling . I really love this phone apart from this issue but it happens way too often to ignore it. Ill post what happens after the session.
Click to expand...
Click to collapse
You may can check this while you wait for support..
https://www.reddit.com/r/oneplus/comments/361dr7/how_to_fix_your_touchscreen_issues_if_you_are_on/
vickykolari said:
You may can check this while you wait for support..
https://www.reddit.com/r/oneplus/comments/361dr7/how_to_fix_your_touchscreen_issues_if_you_are_on/
Click to expand...
Click to collapse
Thanks for this, I'm not going to root yet though because I think I'm finally at the stage where I can start the RMA process, I have a new video of the touch screen being unable to maintain a touch and drag gesture, and then another video doing the same action but just after restarting my phone - it works fine after the restart.
During this support session, I was flashed onto Oxygen OS and I really miss CO12 now, so many features that I grew accustomed to are not present in Oxygen. Oxygen does seem quite solid, but I've gotten way too used to all the features of Cyanogen.
Oh well, ill live with it until I get another reply from the support team.
I write with the assistance for 10 posts at today and I declare them to STOP sending me those bug non fixing ROMS/ZIPS...
I will replace by myself the screen (they don't change it in warranty because I've on the frame some dents... )
It's a clear HW issue, on any software, if the display degrade to a "fail stage" you wan't come back never to a total solve situation.
I loved my Oneplus, but they buy some batches of too cheap display, and after some month, I see clearly the results.
donk165 said:
Thanks for this, I'm not going to root yet though because I think I'm finally at the stage where I can start the RMA process, I have a new video of the touch screen being unable to maintain a touch and drag gesture, and then another video doing the same action but just after restarting my phone - it works fine after the restart.
During this support session, I was flashed onto Oxygen OS and I really miss CO12 now, so many features that I grew accustomed to are not present in Oxygen. Oxygen does seem quite solid, but I've gotten way too used to all the features of Cyanogen.
Oh well, ill live with it until I get another reply from the support team.
Click to expand...
Click to collapse
I wish you all the luck mate..
vickykolari said:
I wish you all the luck mate..
Click to expand...
Click to collapse
Thanks man,
It went well, I have been issued an RMA and will be sending it back soon. Just waiting on the postage label.
Ive just received my new OnePlus One today, very chuffed as it hasn't cost me anything. RMA and Support with OnePlus may be a bit slow but at least they do the right things!
To anyone facing screen issues, create a support ticket and persist with it, it should pay off!
Flash the latest CM 12 nightlies and you're good to go
Sent from my A0001 using Tapatalk
anugrah n3xu5 said:
Flash the latest CM 12 nightlies and you're good to go
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Your a bit late here man, that phone has been sent back and I'm on my 2nd OPO now, using the latest official CO12 build with these touchscreen fixes. No touchscreen problems on this phone.
donk165 said:
Your a bit late here man, that phone has been sent back and I'm on my 2nd OPO now, using the latest official CO12 build with these touchscreen fixes. No touchscreen problems on this phone.
Click to expand...
Click to collapse
Congrats! Enjoy the beast
Sent from my A0001 using Tapatalk
Hi , I have a h830 with latest firmware 30c (Oreo) it's completely stock no root no custom recovery , at the first time I notice some bugs to the Oreo build ...
Always on display some times it's stucked at 12 o clock..
Bluetooth connection is unstable....
Some time lags too much....
just wondering if anyone had the same issues with his phone...
Sent from my LG-H830 using Tapatalk
not sure about bluetooth as i haven't tried it since the update but my always on display will change to 2:00 for no reason and then back to the correct time and the phone runs so sluggish with any app unless its already in ram from a previous attempt. Sad an update this nice basically ruined the phone while others not on tmobile seem to be fine. Sure hope someone looks into this so we can get a fix.
Hard reset the device. It will fix most weird issues from the upgrade.
cradelikz said:
Hard reset the device. It will fix most weird issues from the upgrade.
Click to expand...
Click to collapse
Sometimes when it's locked pop's up the lock screensaver like someone calls or send message and then go to sleep again..
Sometimes when it's unlocked open google assistance for no reason maybe as you said i have to make a hard reset
Sent from my LG-H830 using Tapatalk
Not sure about anybody else but I'm experiencing a lot of random app crashes. Most specifically messenger, instagram, and YouTube. Its almost making me wanna downgrade back to nougat until this is fixed. Almost every time I go into messenger, if I begin to scroll through a message it crashes. Also crashes if I begin to type a message to someone. I noticed that for some reason if I do these actions slower it seems to crash less... It's very annoying.
Whats up everyone!? Im not new to XDA- I usally sit back and read what everyone has to st because ....well honestly ....I dont know **** compared to you guys!! Lmaoooo ! But ive been wondering Now that you guys have oreo....would you recommend upgrading from 7.0? I havent upgraded because im comfortable with 7- and all I keep seeing are complaints about oreo- ive even seen a few who downgraded back from oreo.
Is it worth it?
Also im on t-mobile have a LG-H830. Not rooted.
It took t-mobile forever to catch up.
My worry is -ok I upgrade to oreo, I experience all the bugs and issues everyone talks about....how long til they put out a fix for the bugs!?!?
I don't know.if I should or shouldn't
I appreciate any feedback.
And if im on the wrong thread /forum for this question.......I apologize.
Thanks