Related
Edit: Problem might be solved, thanks to kennyglass123.
I never thought that my battery could be the problem, since I got a replacement phone, but I had forgotten the battery was transferred from the original, malfunctioning phone. I'll be trying this solution as soon as I get paid.
Original Post:
For starters, I've had the Epic since it was originally released. I'm on my second Epic, as the first one needed to be replaced after the speakerphone speaker went out. (I hardly even used it outside a moderate ringtone.)
Here's my issue with both:
Every time the phone get's warm to the touch, while I'm in a warm environment, and I'm using the phone heavily, everything starts to force close like crazy. This includes completely bone-stock ROMs, and I definitely don't overclock, as I'm having issues already. This has happened to me on Froyo and Gingerbread, leaked, official, and custom ROMs, to include RFS/EXT4, and journaling on or off. This has happened to me 5-10+ times over the course of a year.
Every time it happens, my first instinct, after having to pull the battery, since so much is crashing, I go straight into CWM and I wipe dalvik cache or even cache/dalvik. Sometimes, I'll even wipe completely and reload everything from ground up, to include not recovering with Titanium and downloading every app one by one.
No matter how stable I get any ROM working on my phone, this problem occurs when I'm in a warm environment (server room, restaurant kitchen, or summer day), and I'm using the phone very heavily (heavy multitasking, installing lots of apps in market, etc).
Is this me being way too demanding on an older phone, or is this my hardware needing to be replaced? I'm curious, because I would have already gotten a faster phone to suit my needs, but I just now found a better job, and I haven't had extra spending money to throw down another $700; not to mention, I can renew my contract Jan 1, 2012.
Out of all the random issues I've had with all the different ROMs, especially leaks, this problem seems to be very consistent in the conditions I stated, across all ROMs. When I reload my phone from Odin to CWM flashing, now, I do it very slowly, in a cold room, with cool air being blown over it from a fan. I then slowly reload all 40+ apps from the market, one by one, and it takes forever.. every time. I hope some of you can imagine how frustrating this is, being I paid the $650 out of contract price for a top-of-the-line phone, and I've had issues like this over the past year. My phone organizes my whole life, including a full-time job, a part-time job, full-time school, my social life, and everything else. I can't have it crap out on me every time I need it most; and, it does.
Is this my Epic, or is this just all of them? I'd like to not think so, since I see so many people running them overclocked. I really hope I'm not just going crazy.
Thanks in advance for any constructive input in my situation. I'm not sure if it's because I'm at school, but my searches weren't pulling up any results at all.
If it's happening consistently with different ROMs, I would say it is a problem with your hardware. I have an annoying issue with my phone, 'Stay Awake' in Development doesn't keep. Such a minor annoyance compared to what you have to deal with.
If you can document it, you have a case for a replacement phone. But then, your contract renews in two months.....
Have you tried other batteries? I say definitely hardware given the info you provided. It may be a flaky battery causing some intermittance then the FCs. Although that shouldn't happen on completely stock RFS. So probably phone memory is bad.
I'll be trying this possible solution.
kennyglass123 said:
Have you tried other batteries? I say definitely hardware given the info you provided. It may be a flaky battery causing some intermittance then the FCs. Although that shouldn't happen on completely stock RFS. So probably phone memory is bad.
Click to expand...
Click to collapse
You know, when I got my replacement phone, the original battery and cover were moved over to it. I can't believe I never thought to buy a different battery.
I've been wanting to try the suggestion I read about a new Epic Touch battery which is slightly higher capacity, and it still works great. I'll be sure to read up on exactly which one it was before I purchase.
Either way, I suppose it's going to be try a new battery and cross my fingers for two months, because I know how fun the local Sprint store always is. Thanks for the input.
toolegit said:
If it's happening consistently with different ROMs, I would say it is a problem with your hardware. I have an annoying issue with my phone, 'Stay Awake' in Development doesn't keep. Such a minor annoyance compared to what you have to deal with.
If you can document it, you have a case for a replacement phone. But then, your contract renews in two months.....
Click to expand...
Click to collapse
The stay awake when charging not working was changed back in one of the first Gingerbread releases, if I recall correctly. It's unfortunate, because it bugs me too, but that was something I thought Samsung did on purpose in the newer ROMs.
Hi does anybody reading this have the similar issue? If so do you know the solution or how to fix this issue?
1. Adobe Flash. A small little issue I've been also having that Adobe flash on my Android gives me issues, when I play a video on the browser it usually takes a couple of seconds for the video to show, sometimes it doesn't so I have to reload the page
2. Ever since I've flashed and rooted my device, on the screen I've been getting a little bit of this wavy thing at the bottom of my screen, almost as if it's loosing power down at the bottom of the screen....If that makes sense.
If you know a solution or is facing this problem, please let me know. Or post the solution?
It'll be a great big help! Thanks and thanks for your time! Much appreciate!
my opinion is:
the flash player, it playing streaming software player flash.....it may lag just a little but its not that big a deal is it really?
the wavy lines, i would say look into of a its a defective tab and if you have receipt take it back for a replacement
i wouldnt say defective tab, have had mine for a year, and after flashing over to tabonney's ICS i get an odd flicker too, as for flash, its trying to render what computers play, with just much less hardware resources to use. Its slow and thats the way its going to be.
My video issues aren't like yours Mkami... But if I might suggest making a full backup, then reflash your rom. Maybe you'll get lucky and the issue will go away.
BrianDigital said:
i wouldnt say defective tab, have had mine for a year, and after flashing over to tabonney's ICS i get an odd flicker too,
Click to expand...
Click to collapse
You know, I've been waiting on someone to mention the odd flicker. Does your tab do it when either, a 3d game or app is running, or maybe on a home screen that has an email widget? And does the tablet seem to still be reacting normally to touch input other than the fact that the screen doesn't show any change? I am thinking about sending my tab in over this for warranty work. I got mine over a year ago too. Sure am glad I paid with plastic, got an extra year warranty for doing it. I just wonder what they are gonna say about the bent corner where it hit the pavement...
JdgM3NT4L said:
My video issues aren't like yours Mkami... But if I might suggest making a full backup, then reflash your rom. Maybe you'll get lucky and the issue will go away.
You know, I've been waiting on someone to mention the odd flicker. Does your tab do it when either, a 3d game or app is running, or maybe on a home screen that has an email widget? And does the tablet seem to still be reacting normally to touch input other than the fact that the screen doesn't show any change? I am thinking about sending my tab in over this for warranty work. I got mine over a year ago too. Sure am glad I paid with plastic, got an extra year warranty for doing it. I just wonder what they are gonna say about the bent corner where it hit the pavement...
Click to expand...
Click to collapse
oh flickering? i think thats a ics problem as most of the ics based roms have the flickering plus stock,. but the guy said he had wavy lines at the bottom of the screen. never heard of that before.
chismay said:
oh flickering? i think thats a ics problem as most of the ics based roms have the flickering plus stock,. but the guy said he had wavy lines at the bottom of the screen. never heard of that before.
Click to expand...
Click to collapse
With pached bootloader and any rom on this site and stock I got
screen flicker, very poor battery, not so smooth scrolling and host of other gliches. (all compared to ota). Flashed back to stock ota and not looked back. No problems. It seemed to me that the problems are not in the roms because stock had the same problems, it the act of changing the bootloader. Just what I have seen, try it just to get rid of the screen problem, go to ota stock no mods and it will be gone.
shaun298 said:
With pached bootloader and any rom on this site and stock I got
screen flicker, very poor battery, not so smooth scrolling and host of other gliches. (all compared to ota). Flashed back to stock ota and not looked back. No problems. It seemed to me that the problems are not in the roms because stock had the same problems, it the act of changing the bootloader. Just what I have seen, try it just to get rid of the screen problem, go to ota stock no mods and it will be gone.
Click to expand...
Click to collapse
You know, that's kind of what I've been thinking. I've been testing by going back and forth between bootloaders. So far that is the best explaination. I'll likely go back to stock again soon. But it seems like I remember it doing it at least once on the stock bl...
When I first updated to ICS, all was well. Within a couple weeks, Flash video got laggy, the browsers got laggy, and I got the occasional screen flickers. I backed everything up and did a hard reset and it's been great ever since.
I haven't heard a really good explanation for all this, but a good theory is leftover files remaining on the system, or possibly file fragments, are interfering with the OS. A hard reset purges the old crap out... regardless of the explanation, it's known to fix these problems.
sRDennyCrane said:
A hard reset purges the old crap out... regardless of the explanation, it's known to fix these problems.
Click to expand...
Click to collapse
Awesome, glad that you were able to get to normal. It didn't help me tho... I might start a different thread for this if it keeps up. I don't want to hijack Mkami's thread with a different problem. Thank you for the help.
Hey everyone thanks for the advices and different problems you guys are facing.
Sorry for my poor explanation... When I mean screen "wave" what I really meant is screen flicker
I found a semi cure for this...Though I don't know about other peoples tablets, all I did was raise the brightness of the screen and the flicker seemed to not show, I must say though that flicker doesn't really much bother me as it does with the flash, but I guess I have to live with it, just a heads up, my tab isn't defective. Truthfully when I do go to stock ROM everything on the device including the flicker goes away, it's only when I flash my device that I notice that, but I am pretty sure there might be a solution for that one or another, because a buddy of mine has the same tablet, which is why I got that a500. I love it and I love android way much more than any other.
Anyways, I hope Flexreaper releases a new rom soon, really am excited with anticipation. Can't wait to see what he has in store for us.
I am going to try that hard reset and fully restoring the device after a nandroid backup and test and reflash and check if anything works with a good
result I shall post up the steps and how to fix this little issue.
I thank you all! Please post if anybody else has this issue or solution down! Much appreciated! Thanks! :laugh:
Hey guys, I was wondering if anyone may know if the new 4.4 Kit Kat will fix all of the Nexus 7 2013 touch screen problems.
Maybe Asus and Google knows it fixes the issue. That's why they didn't rush to help us in the last few months.
Cross your fingers people and hope this fixes all of our issues. That would be sweet.
Oct 28 4.4 I'm thinking.
I hope that... it's been a headache, and that's the only flaw mine has, the fix here fixes it just temporally.
Can't say whether it will or won't but I can say I really doubt they have the fix already in hand and are holding it back waiting for kit kat.
They've never been shy about putting out releases to fix things and a touchscreen fix is very contained and isolated, not something that touches many areas requiring long code reviews.
Can I just ask what kinde of problems you are reffering to? Multitouch problem has been fixed with the latest update. At least mine was. With a multitouch program I placed all 10 fingers on screen and was moving it arround, and it registrated all fingers and arrows were moving very very smoothly. 60fps+. Also, there is no problem with GPS anymore. The only problem which is actually not a problem, is smal buzz from speakers when watching of listening to something at very low volume, but that is reported for all nexus 7 devices because that is how the speakers are made.
You are saying like nexus 7 2013 is forgotten and this 4.4 is our last hope for the device otherwise its useless to use. Which is far from truth. I have absolutely no problems with it.
I don't know, maybe I use the device too much? But I can definitely say ghost touchs and some multi-touch issues are there and persistent. In fact right now as I was writting this the keyboard went crazy, it's really annoying and I don't even want to start with the horrible experience I'm getting with PS Touch(which I use a lot) thanks to this problem. Sometimes I have to reboot the device when it goes crazy zooming while navigating the internet.
For you guys that your tablet is "perfect", fascinating, good for you, but that doesn't mean the problem doesn't exists anymore, you just got lucky.
I personally have no more touchscreen issues since JSS15Q, but if there is another touchscreen fix in KitKat that would be good to the few unlucky ones still having issue with theirs..
neo5468 said:
Can I just ask what kinde of problems you are reffering to? Multitouch problem has been fixed with the latest update. At least mine was. With a multitouch program I placed all 10 fingers on screen and was moving it arround, and it registrated all fingers and arrows were moving very very smoothly. 60fps+. Also, there is no problem with GPS anymore. The only problem which is actually not a problem, is smal buzz from speakers when watching of listening to something at very low volume, but that is reported for all nexus 7 devices because that is how the speakers are made.
You are saying like nexus 7 2013 is forgotten and this 4.4 is our last hope for the device otherwise its useless to use. Which is far from truth. I have absolutely no problems with it.
Click to expand...
Click to collapse
The few that had touchscreen problems initially were fixed. 75% of working units were broken in the process. Its a big issue. We have a fix but nothing from Google. There are several screen variances which make it impossible for a single 1 fix all solution.
Google will have to detect each variance and patch accordingly. Probably why it hasn't been released yet because it probably will take a larger testing period then previously mentioned. Even using the XDA fix, some versions can cause several FCs and bugs. Similar to the specific pattern freakout.
With 4.4 on the horizon, it would be best to include it in that. Google probably isn't going to create an OTA and then another one in a few weeks.
Just cross your fingers and hope for an official fix.
GPS was fixed though. I'm not sure about the kernel reboots though. I haven't used the stock kernel nor had reboots since I flashed CM Kanged.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
player911 said:
The few that had touchscreen problems initially were fixed. 75% of working units were broken in the process. Its a big issue. We have a fix but nothing from Google. There are several screen variances which make it impossible for a single 1 fix all solution.
Click to expand...
Click to collapse
Any source for that 75% number? Without a proper source it is hard to not consider that as a case of the loud minority.
If it were that serve of a problem we would hear the tech press clamoring about it by now. But nothing was said about N7 touchscreen by the tech press since JSS15Q.
I can't tell you what the real percentages are, but the touchscreen issue is definitely a much bigger problem than your standard problems.
Standard run-of-the-mill issues get a thread with maybe 20 posts. Touchscreen is producing 1000 post threads. So relative to normal problems it is a big problem, but whether that is a 5% vs 1% problem or a 75% vs 1% problem I could not tell you.
There are at least 3 huge threads on Google support forums about this problem:
Multi-touch - reports of improvement, no improvement, and some worse
Multi-touch (continued) - more reports of fixed / not fixed for JSS15R
Multi-touch (continued 2) - more reports of touchscreen issues
BTW I created the xda fix for touchscreen so I'm very familiar with the fixes Google put out and whether they have fixed the issue. JSS15R fixed it for some screens but made it much worse for others.
That's the main reason I haven't sent my Nexus for repair, is not hardware related, or at least that's what I think, please someone correct me if I'm wrong.
NekroWolfen said:
That's the main reason I haven't sent my Nexus for repair, is not hardware related, or at least that's what I think, please someone correct me if I'm wrong.
Click to expand...
Click to collapse
Well, actually it is hardware related, but you can't tell if your hardware is one type or another without using Sfhub's process.
Well, thanks for confirming
I personally don't think that all of the touchscreen issues will be fixed with Kit Kat. I feel that Google will he focusing more on a fully operational OS, and that we'll need a dedicated fix to solve our problems.
But I surely hope that I'm wrong.
______________________________
HTC Evo 4G LTE
any word of usb audio coming via kitkat. ive been waiting for this feature to come to the nexus 7 forever because its keepingme outof my car
Lockeskidney said:
any word of usb audio coming via kitkat. ive been waiting for this feature to come to the nexus 7 forever because its keepingme outof my car
Click to expand...
Click to collapse
At this point, questions to me are almost meaningless to ask. We night as well wait for tomorrow. It took long enough to arrive.
It just sucks that I don't have my tablet. I went back to Radio Shack and ordered the 32gb through them, since none of their stores had that version on their shelves, and 16gb was not working out for me. At least I'll get to download it as soon as I get my new device!
______________________________
HTC Evo 4G LTE
GPS isn't solved to me.
diogobuique said:
GPS isn't solved to me.
Click to expand...
Click to collapse
That's a hardware issue, I suggest you to send it back to Google.
Kitkat gave me phantom touch issues, have none before kitkat. :-\
Sent from my SM-N900P via TapaTalk PRO
Elite Tester
This process doesn’t wipe the tablet, so your settings, apps and everything else should stay in tact whenever you get back to the system. Remember that you will have lost root at this point, but it’s easy enough to get that back.. Cool resource!
But before kitkat my GPS worked very well
I wonder if anyone is also experiencing sensitivity issues with the new 38R OTA.
In my case It is evident when scrolling (homescreen, twitter, whatsapp....) and typing. Also the capacitive buttons seem a bit unresponsive from time to time.
What about you guys?
Edit: here you have the prove (bad scrolling and multitouch problem) i think i am going to RMA
Multitouch and sensitivity issues in 38R: http://youtu.be/KSAl1Uh_Src
Edit:
Suddenly the issue has been gone for a week, no problems at all since 15 October... I am so confused
Edit 2:
The sensibility issue is back on 24/10/2014 without changing anything
QuBeX said:
I wonder if anyone is also experiencing sensitivity issues with the new 38R OTA.
In my case It is evident when scrolling (homescreen, twitter, whatsapp....) and typing. Also the capacitive buttons seem a bit unresponsive from time to time.
What about you guys?
Click to expand...
Click to collapse
Yes, I also still have troubles with it. I especially notice it when typing.
gr4nchio said:
Yes, I also still have troubles with it. I especially notice it when typing.
Click to expand...
Click to collapse
Do you think it could be hardware problem? I am not sure, because sometimes it works perfect, but it is the 10% of the whole time
QuBeX said:
Do you think it could be hardware problem? I am not sure, because sometimes it works perfect, but it is the 10% of the whole time
Click to expand...
Click to collapse
I am really not sure... the last couple days I was on 33R CM11S with AK kernel and did not notice the problem at all. But it is not something that happens often in my case. So it is possible that I just did not wait long enough for it to appear.
I will stay on stock cm11s 38R for a few more days and then probably switch back to AK kernel to see if my previous experience is reproducible.
Did you even try to use a different kernel? Did you still have the issue?
gr4nchio said:
I am really not sure... the last couple days I was on 33R CM11S with AK kernel and did not notice the problem at all. But it is not something that happens often in my case. So it is possible that I just did not wait long enough for it to appear.
I will stay on stock cm11s 38R for a few more days and then probably switch back to AK kernel to see if my previous experience is reproducible.
Did you even try to use a different kernel? Did you still have the issue?
Click to expand...
Click to collapse
Just flashed AK, It seems that the unresponsiveness is still there
I am really dissapointed, i though this OTA would solve sensitivity problem...
QuBeX said:
Just flashed AK, It seems that the unresponsiveness is still there
I am really dissapointed, i though this OTA would solve sensitivity problem...
Click to expand...
Click to collapse
Sorry to hear it did not help.
I have also just noticed this post http://forum.xda-developers.com/showpost.php?p=55195972&postcount=62 which suggests macgyvering an improved grounding for the phone. I have to admit that I don't understand exactly what to do. But it might become clearer if I get frustrated enough to actually open up the phone
Please let me know if you try it and it works.
Touch screen is still going to be an issue. You can check the original bug which was reported here (still says in progress) https://jira.cyanogenmod.org/browse/BACON-55
gr4nchio said:
Sorry to hear it did not help.
I have also just noticed this post http://forum.xda-developers.com/showpost.php?p=55195972&postcount=62 which suggests macgyvering an improved grounding for the phone. I have to admit that I don't understand exactly what to do. But it might become clearer if I get frustrated enough to actually open up the phone
Please let me know if you try it and it works.
Click to expand...
Click to collapse
It could work but i don't want to touch inside the phone very much, I don't want to void my warranty. I think I will RMA with this video I just made. Multitouch and sensitivity issues in 38R: http://youtu.be/KSAl1Uh_Src
QuBeX said:
It could work but i don't want to touch inside the phone very much, I don't want to void my warranty. I think I will RMA with this video I just made. Multitouch and sensitivity issues in 38R: http://youtu.be/KSAl1Uh_Src
Click to expand...
Click to collapse
You should just know that OPO's customer service while polite, will give you the run around a while. Took me about a month before they finally granted the RMA.
jlevy73 said:
You should just know that OPO's customer service while polite, will give you the run around a while. Took me about a month before they finally granted the RMA.
Click to expand...
Click to collapse
Will they RMA for a refund or just a new phone? I'm not convinced this will ever be fixed in software, and I'd rather go back to a mainstream manufacturer at this point.
dipdewdog said:
Will they RMA for a refund or just a new phone? I'm not convinced this will ever be fixed in software, and I'd rather go back to a mainstream manufacturer at this point.
Click to expand...
Click to collapse
Not sure since I just requested a new phone.
dipdewdog said:
Will they RMA for a refund or just a new phone? I'm not convinced this will ever be fixed in software, and I'd rather go back to a mainstream manufacturer at this point.
Click to expand...
Click to collapse
They will, at least, replace your phone. I did and am waiting for my new one to arrive. If multitouch issues remain (and most likely will) i'll ask for a refund. I don't really care if the phone is "cheap for specs", this flaw is unacceptable.
My S3 is much worse hardware wise and feels SO much better while typing or anything else touch related. I did have to open a ticket and later show up a few videos of multitouch malfunctioning to oneplus. They decided it was a malfunctioning unit and i was eligible for a replacement. They never mentioned bacon 55 or a "known issue" common to every phone that would be solved at some point later on.
It's taking forever too. It's been over a month and it's mainly their fault because they take so long to reply to every single email. They did ask my VAT number before hand so they could send an invoice with it to my customs that would facilitate the returning process. Despite that, my phone got stuck on my country's customs precisely because they sent them an invoice without it and was up to me to ask it to oneplus. I waited about a week for what seems an poorly excel made document (compared to my country's invoices this is a joke of a document ). I sent it to the courier who picked up and they forwarded it to customs. Stuff went smooth from that point on. Oh yea, i'm from Portugal and even though my phone was sent to me from the UK the first time, to return a phone, you're going to send it to Hong Kong. All free of charge. I did have to print loads of pre made documents (about 10 pages?), because apparently sending anything with a battery is a big deal safety wise.
Even though they are, like someone said, polite, they do take a good while to reply to anything and aren't very keen to answer to anything that falls a bit out of their "process". For example, I've asked them several times if they would send me a new phone before or after a return mine. They never really cared enough to answer. Their English also seems translated by google sometimes. Several different people may take care of the same case. I've had about 5 or 6 different names reply to me and they all just use their first name like "Wilona". It made me stop to think i was sending my already paid phone to some place across the world because this randomly named guy told me so by email - in any other different scenario this would scream of a scam. But I've placed my RMA through an official ticket on their website, they actually made a new order request from their store on their website, they use very well known couriers with tracking numbers and it's the only way i'm ever getting a chance of having a properly working phone.
I did warn them before sending my "faulty" unit back they can expect me asking for a full refund if this new one isn't working any better.
I have been on liquidsmooth rom since I got the phone, no problems with touchscreen whatsoever, Installed new 38 CMS today and started to experience that problem. Also, cms lags compare to AOSP, this is pretty weird
QuBeX said:
Do you think it could be hardware problem? I am not sure, because sometimes it works perfect, but it is the 10% of the whole time
Click to expand...
Click to collapse
Flashing ColorOS for me gave a much better touchscreen experience, things worked flawlessly in all apps for me(Amazon is my biggest issue, any scrolling over a description/review would select it and move you to that section to read it, does not happen at all in ColorOS), so im thinking its software
This issue is so exaggerated...
Sent from my A0001 using Tapatalk
What is the touchscreen issue that people are referring to? Mine seems perfect? The only issue is the slight yellow at the bottom but you only notice it if you actually go looking for it.
jojohnson250 said:
This issue is so exaggerated...
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Not really. It's bothersome.
Sent from my OnePlus One using Tapatalk
Mines slightly yellow at the bottom, appears to be getting a bit better though, unless thats just my eyes playing tricks on me. I haven't noticed touchscreen issues except i can't seem to press the spacebar properly
My touchscreen seems to be very picky as to where I touch. Sometimes it takes a few attempts. Since 38 I have had random reboots. I m stock rooted without anything else flashed.
jojohnson250 said:
This issue is so exaggerated...
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
If you can say that you're a lucky one. It can render your phone completely unusable. Imagine your phone randomly assuming touches when you're not even touching it, non stop (stuff opening, key input, etc). You can't do anything else while it happens and the only way to stop is by rebooting. 5 to 10 times a day, everyday. Also, just about anything multitouch like simply zooming on a webpage has a 50% chance of working or send your phone spazing on a zooming in/out frenzy. So I'd say it isn't exaggerating, you just aren't experiencing the worse of it.
So I picked up a 6P again after I got rid of my original a couple years ago. It arrived yesterday and I got it all setup, but then it started having issues that night. So I did a factory reset. I should mention that the very first thing I did when I got it was root it and install elementalx. Didn't bother with a ROM since Pure Nexus hasn't been supported for awhile (which is what I installed on my old 6P) and I was already running Oreo.
Today was going great until about an hour ago. I unplugged it from charging and the same symptoms as last night happened. When this happens I have to hold the power button until the device reboots.
What happens is that severe lag happens. The screen turns on after a few seconds when I use the fingerprint scanner or power button, but it's very slow and glitchy. Like it'll show half the notification bar and below that there will be a 2 inch long by 1 inch long rectangle in the upper left corner that shows the bottom of my wallpaper. The rest of the screen will show my wallpaper but it'll be glitched, where like the bottom is actually a section of the top. And trying to pull down the notification shade is just impossible. It glitches big time but after lagging of course. I really wish I had pictures to better explain. If it happens again I'll be sure to take some.
From what I've said though, does anyone have any idea why this is happening?
I have a few days where I can still return the device, but I really would like to keep it since it's in mint condition. Battery life is great still and there doesn't seem to be any performance issues when it's working properly. I really don't want to keep doing resets, which if I'd have to then I don't see any point in keeping it since it basically won't be usable.
Edit: 9:37pm
Just had it happen again so I took some pictures. It got to the point the screen wouldn't come on at all, so I had to hold the power button again to reboot. But I found out it still registers the fingerprint to unlock (I hear the sound) and hitting the power button twice still launches the camera (the phone vibrates). When this first started happening this time, after waiting for a little bit with the screen on, I got the popup that the System UI wasn't responding.
Just wanted to update that I flashed the stock ota from Google's site for the October 2018 update. Since doing so the phone has been working fine *knocks on wood*. So right now I'm thinking there was an issue with rooting, elementalx, or magisk. I'll make a backup and do those things one at a time and see when/if my issues return.
Just another update for those who stumble across this topic from Google or whatever.
Things were working great for a few days so I decided to go ahead and root but not install elementalx or anything. Did so last night and upon waking up this morning the phone was having the lag issue again. So it seems rooting is causing my problem. I used magisk, so I'm going to try SuperSU and see if that causes my problem as well.
Switching from magisk to SuperSU did not solve my problem. The phone started freezing up and lagging bad again, requiring me to hold the power button and reboot. So I guess I'll just unroot again and leave it that way.
Unless someone seeing this has any other ideas.
I dont recommend oreo. Im having a lot of issues like the worst of all not being able to install TWRP, lag, screen stutters and excessive battery usage
I love Oreo. Have zero problems with it, my problems are this specific phone. Don't root it and it works flawlessly. Oreo runs better for me than any previous version of Android ever, especially on older lower spec devices. There is zero reason something as powerful as the 6P can't handle it.
TWRP installed without issue, never had an issue with it and Oreo shouldn't affect it anyways. I've got the phone running kind of stock. I installed TWRP and ElementalX and left it at that. Using other apps and adb commands I was able to install a bunch of "Pixel only" stuff and get what I wanted without root. So I'm happy.
The thing's just a side project next to my Note 9 anyways. So long as the hardware issues stay at bay that render the 6P worthless, I'll stay happy.
Sounds like to me you need to do a full re-flash from the stock files on Google's Nexus site and start fresh. Or yours is starting to show signs of the hardware defects.
Either way, this topic is moot to me now I guess. Mainly just left it here in case others find it through Google searches. Good luck!
Whenever I do a major android version upgrade I wipe internal storage. I found that if I didn't do this would get all kinds of little issues. Internal storage carries over files from one android version to the next.
My 6P is doing very similar as yours is. Extreme lagging, basically totally freezing and sometimes half the screen is visible just like on your pictures. I haven't find a solution to it, but you are saying not rooting it fixed it for you? Seems far-fetched but I guess I have no other option. I have been using Lineage OS.
Yeah, removing root instantly fixed the issues for me. I made sure to clear cache and everything like that from recovery too. I'm still unlocked and using TWRP with Elementalx, setup however I like. I just can't root. Soon as I do I can actually feel a little slowdown in using the phone, and then after a day or so the horrible lag with freezing and stuff starts.
Not sure about using a custom ROM since like I said I didn't try it on this phone. My original 6P didn't have any of these issues and I could root, ROM, and modify my heart out.
So to recap, currently and since my last actual update here basically, I've been unlocked, using elementalx and TWRP, but running stock October 2018 Oreo ROM and all that. I used adb commands to get Greenify setup as close to root settings as possible, and to install some Pixel stuff to get night light and whatnot. Got immersive mode by using systemuituner app. And a couple other things to get it as close to how my original 6P was on Pure Nexus.
Hope this helps. I'll be glad to provide anything else I can.
Oreo is crap on the nexus 6p. Seems.like google is slowing it down. Not only on the operating sysyem but also on its latest apps. The latest version of maps is too laggy but the one that comes with nougat is smooth. Thats why i went back to nougat is lile heaven and hell. Shame on goole being thay oreo runs very good on the 5x but not the 6p
survivor_evil said:
Oreo is crap on the nexus 6p. Seems.like google is slowing it down. Not only on the operating sysyem but also on its latest apps. The latest version of maps is too laggy but the one that comes with nougat is smooth. Thats why i went back to nougat is lile heaven and hell. Shame on goole being thay oreo runs very good on the 5x but not the 6p
Click to expand...
Click to collapse
Take your conspiracy theories elsewhere. Oreo runs smooth as butter on perfectly (or even in my case, not perfectly since it won't root) fine 6P's. Everything works as it should and I have zero issues and zero lag. All you're doing is cluttering up my topic on something that has absolutely nothing to do with Oreo. This topic is about the issues I'm having after rooting, nothing else. If you don't like Oreo, fine. If you think a device that's several years old at this point isn't running the newest OS as smooth as it ran older ones, that's fine too. Especially since Google has at this point completely disowned the Nexus nameplate. Just don't come into someone else's topic and run your mouth. I told you before I had no issues with Oreo and that it sounds like your device is showing odd behavior, if you didn't like that... well that's fine too. Why subscribe to this topic and keep coming back if it has nothing to do with you. Go away or contribute helpful info to the issue at hand here; rooting complications not Oreo.
Although at this point I'm not having any issues. My 6P has been running buttery smooth since I removed root on what, October 18th... that's about two weeks ago. And this includes installing and tweaking stuff on it that it's supposedly too obsolete to run and only Pixel devices can handle. It goes toe to toe with my Note 9 in daily activities, all while running Oreo.
RockwellB1 said:
Take your conspiracy theories elsewhere. Oreo runs smooth as butter on perfectly (or even in my case, not perfectly since it won't root) fine 6P's. Everything works as it should and I have zero issues and zero lag. All you're doing is cluttering up my topic on something that has absolutely nothing to do with Oreo. This topic is about the issues I'm having after rooting, nothing else. If you don't like Oreo, fine. If you think a device that's several years old at this point isn't running the newest OS as smooth as it ran older ones, that's fine too. Especially since Google has at this point completely disowned the Nexus nameplate. Just don't come into someone else's topic and run your mouth. I told you before I had no issues with Oreo and that it sounds like your device is showing odd behavior, if you didn't like that... well that's fine too. Why subscribe to this topic and keep coming back if it has nothing to do with you. Go away or contribute helpful info to the issue at hand here; rooting complications not Oreo.
Although at this point I'm not having any issues. My 6P has been running buttery smooth since I removed root on what, October 18th... that's about two weeks ago. And this includes installing and tweaking stuff on it that it's supposedly too obsolete to run and only Pixel devices can handle. It goes toe to toe with my Note 9 in daily activities, all while running Oreo.
Click to expand...
Click to collapse
It wasnt for you but in general, there are more users complaining about it. I tested oreo without rooting and it lags as hell. You can even check comparison videos too... this topic is about having lag issues so I gave you an answer, go back to nougat.
survivor_evil said:
It wasnt for you but in general, there are more users complaining about it. I tested oreo without rooting and it lags as hell. You can even check comparison videos too... this topic is about having lag issues so I gave you an answer, go back to nougat.
Click to expand...
Click to collapse
I told you the first time you mentioned that "solution" , Nougat isn't an option for me and shouldn't be because I'm pretty sure I made it clear Oreo wasn't the problem. I even made it clear I basically solved my issue before your first foray into this thread.
I made it clear again in my last post.
I really don't care if there are comparison videos, I have absolutely zero lag if I'm unrooted. That is what this topic is about, lag caused by root. Those who actually spend the time to read more than the topic title can understand that. I've been working with electronics for a long long time, I know how to diagnose everything and I think I made that pretty clear by providing updates as I did things. If not for the fact the thing is all setup and running great, I'd wager I could go back to Nougat and still have root lag issues. The 6P and the 5X for that matter, are ticking time bombs. They both have hardware defects that basically turn them into fancy paperweights. Those defects could be causing my issues, your issues, and edda's issues. No real way to tell that until the bootloops or early shutdowns start. I'm of course hoping this late in the game that maybe those of us with still functioning units don't have those issues, but my gut tells me it's always a "time will tell" issue.
RockwellB1 said:
I told you the first time you mentioned that "solution" , Nougat isn't an option for me and shouldn't be because I'm pretty sure I made it clear Oreo wasn't the problem. I even made it clear I basically solved my issue before your first foray into this thread.
I made it clear again in my last post.
I really don't care if there are comparison videos, I have absolutely zero lag if I'm unrooted. That is what this topic is about, lag caused by root. Those who actually spend the time to read more than the topic title can understand that. I've been working with electronics for a long long time, I know how to diagnose everything and I think I made that pretty clear by providing updates as I did things. If not for the fact the thing is all setup and running great, I'd wager I could go back to Nougat and still have root lag issues. The 6P and the 5X for that matter, are ticking time bombs. They both have hardware defects that basically turn them into fancy paperweights. Those defects could be causing my issues, your issues, and edda's issues. No real way to tell that until the bootloops or early shutdowns start. I'm of course hoping this late in the game that maybe those of us with still functioning units don't have those issues, but my gut tells me it's always a "time will tell" issue.
Click to expand...
Click to collapse
If that was a hardware issue Id be having it with other versions of android but no, only oreo. And everything points out that oreo is the issue. Not only me but all the users posting videos and on forums
survivor_evil said:
Oreo is crap on the nexus 6p. Seems.like google is slowing it down. Not only on the operating sysyem but also on its latest apps. The latest version of maps is too laggy but the one that comes with nougat is smooth. Thats why i went back to nougat is lile heaven and hell. Shame on goole being thay oreo runs very good on the 5x but not the 6p
Click to expand...
Click to collapse
I agree with you on that. I have had much better luck running Pure Nexus over any other rom.
Chris
RockwellB1 said:
Yeah, removing root instantly fixed the issues for me. I made sure to clear cache and everything like that from recovery too. I'm still unlocked and using TWRP with Elementalx, setup however I like. I just can't root. Soon as I do I can actually feel a little slowdown in using the phone, and then after a day or so the horrible lag with freezing and stuff starts.
Not sure about using a custom ROM since like I said I didn't try it on this phone. My original 6P didn't have any of these issues and I could root, ROM, and modify my heart out.
So to recap, currently and since my last actual update here basically, I've been unlocked, using elementalx and TWRP, but running stock October 2018 Oreo ROM and all that. I used adb commands to get Greenify setup as close to root settings as possible, and to install some Pixel stuff to get night light and whatnot. Got immersive mode by using systemuituner app. And a couple other things to get it as close to how my original 6P was on Pure Nexus.
Hope this helps. I'll be glad to provide anything else I can.
Click to expand...
Click to collapse
I had problems similar to this and found out it was the immersive mode causing it, activating it with any app caused problems. If you download terminal emulator and use some commands that can be found elsewhere in the Nexus 6p part of the forum it works fine. Hope this helps. Currently on Resurrection remix with magisk installed. Running smooth as butter. Just waiting for pie to be more stable now
faybarn said:
I had problems similar to this and found out it was the immersive mode causing it, activating it with any app caused problems. If you download terminal emulator and use some commands that can be found elsewhere in the Nexus 6p part of the forum it works fine. Hope this helps. Currently on Resurrection remix with magisk installed. Running smooth as butter. Just waiting for pie to be more stable now
Click to expand...
Click to collapse
Thanks but I wasn't even messing with immersive mode at the time. Or are you saying just having it present because I made uituner visible in settings that it might have been causing it?
My issue very much seems to be straight up linked to rooting. If I used magisk or SuperSU (really the only two I'm willing to trust) I'd notice the phone felt sluggish soon as it would reboot after rooting with them. It wasn't a huge slowdown though so I thought nothing of it, until the horrible lag/freezing issues started usually within the day. Remove root, and everything went back to normal.
I've since been using immersive mode without any issue, but of course I gave up on root.
And yeah, I hear ya on Pie. Soon as it becomes stable enough I'll be testing it out. I had 8.1 running on my Note 4, just sold it about a month ago, and it was running great. Only minor issues that were still being worked on. Being a Nexus though I have high hopes this'll be a bit easier to port to.
buchananchris said:
I agree with you on that. I have had much better luck running Pure Nexus over any other rom.
Chris
Click to expand...
Click to collapse
Im talking about pure oreo on the nexus 6p. Ive installed it many times thinking coukd be a bad installation but its just that oreo is crap on the nexus 6p. I went back to nougat and its working like a charm again.