Ever since update phone is very slow and Bluetooth is terrible.cuts out while playing music on Bluetooth speakers.does anyone have a fix for this?
Sent from my LG-H900 using XDA Premium 4 mobile app
Have you done a factory reset since the update?
My phone has been very laggy and slow since I updated to MM. I do a factory reset about once a month to give the phone a fresh feel. However I've had so much lag that I've done multiple factory resets and its still present. As for the BT issue, I havent had any. I work in an assembly plant and listen to music 10 hours a day and never had a cut out or drop.
th3cavalry said:
My phone has been very laggy and slow since I updated to MM. I do a factory reset about once a month to give the phone a fresh feel. However I've had so much lag that I've done multiple factory resets and its still present. As for the BT issue, I havent had any. I work in an assembly plant and listen to music 10 hours a day and never had a cut out or drop.
Click to expand...
Click to collapse
Lag is a software problem, bluetooth can be either software or hardware. Just to be certain. You do close an app when your not using it right?
Related
My mother in law has a TF300 that has been really glitchy, so much so that it was basically unusable (the 4.2 update seems to have made it better, but still not perfect).
Her biggest issue has been sporadic touchscreen non-responsiveness. She thinks that this might be worse when connected to the internet (some app working in the background/updating?). Today she also had it where she couldn't use the screen while connected to the keyboard, but when she disconnected the keyboard it started working again, but that may have been a fluke.
In addition, there are times when it will act as if you've pressed an on screen button, even though your hand was nowhere near said button (almost like a ghosting effect on a keyboard, when the computer is running slow)
I've got the tablet with me for a few hours and I'd like to help her get it to the point where it's working normal again. Any thoughts or advice would be appreciated.
Almost as soon as I mentioned the on screen buttons, it started acting up.
Sent from my YP-G70 using xda app-developers app
Did it just start or has it been doing it since day 1? Go to settings, then Backup & Reset under Language & Input and do a Factory data reset.
That's the fist step in finding the problem. Bad side she will loose all saved data so save it to a pc.
4.2.1 update rolling out
hmm is that a galaxy player 5.0
I can't remember how long it's been giving her issues, but it has been a while. Multiple factory resets haven't fixed it. In the time I've been tinkering with it I've disabled some of the bloatware and turned off Auto Updates from the Play Store, so we'll see if those help in any way.
I've also noticed that the notification bar keeps getting stuck (either up or down). It looks like rotating it helps fix that, but still that's less than ideal...
Ah, the joys of being tech support :silly:
I've got it hooked up to my laptop in an attempt to use LogCat to help debug, but I'm not sure if I'm seeing anything consistent enough to label it as the cause of her troubles. Still, a resource available if anyone knows what I should be looking for there.
R3Z4545 said:
hmm is that a galaxy player 5.0
Click to expand...
Click to collapse
Yes, yes it is
If it's under warranty then send it back. Hopefully she hasn't had it over a year.
If it were mine it would've already been in the mail. Since its not unlocked and factory reset aren't working there's not much else that can be done without voiding the warranty.
Sent from my LG-LG855 using Xparent SkyBlue Tapatalk 2
is there a screen protector on it?
My TF300 always the same thing whenever there was background IO, even with Android 4.1.
Turning off the useless syncing and auto Play Store updates do help.
Also check to see if the storage has been filled. IO performance is also decreased by having a relatively filled flash.
So having disabled the Auto Updates from Google Play seems to have made a world of difference. I'm surprised background IO took so much out of the tablet, since it's running on a quad core, but oh well. Thanks for the suggestions everyone!
Several days ago I noticed I began missing notifications on my Gear. It took me a while to realise the reason for that. My watch vibration is now so weak to the point I don't feel it. It wasn't very strong to begin with, but now it deteriorated to the point it's useless. I have done a couple of factory resets, it didn't help. One thing I haven't tried yet is hard reset.
Anyone else experiencing this?
Sent from my GT-I9505 using Tapatalk
mpogr said:
Several days ago I noticed I began missing notifications on my Gear. It took me a while to realise the reason for that. My watch vibration is now so weak to the point I don't feel it. It wasn't very strong to begin with, but now it deteriorated to the point it's useless. I have done a couple of factory resets, it didn't help. One thing I haven't tried yet is hard reset.
Anyone else experiencing this?
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
I think yours is faulty and your problem is not common. Yes, the vibrate is weaker than it should be. I believe this "may" be correctable in firmware as I am not sure that even set to high, we are actually getting maximum vibration. But I don't recall anyone saying it is changing over time....just not strong enough to begin with. You may need to get yours swapped out.
mpogr said:
Several days ago I noticed I began missing notifications on my Gear. It took me a while to realise the reason for that. My watch vibration is now so weak to the point I don't feel it. It wasn't very strong to begin with, but now it deteriorated to the point it's useless. I have done a couple of factory resets, it didn't help. One thing I haven't tried yet is hard reset.
Anyone else experiencing this?
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
You could just be getting used to it. My old Sony Ericsson MBW-150 vibrated a lot stronger than my Gear 2, but after a few hours sometimes I didn't notice it either. Hopefully we get a fix to make it stronger either from Samsung or a rooted ROM.
Just wondering if anyone else has a similar issue - every so often it will just decide to reset, and get into the unpaired mode. On the phone I have to un-pair, and re-pair the device.
It happened to me only once. I think it is a memory issue. If it gets more than it can handle, it resets itself but this is just a wild guess.
Sent from my HTC One SV using Tapatalk
Happens to me every so often too! Very annoying.
Sent from my Nexus 7 using Tapatalk
I am observing this too, not very often though. I do lose BT connectivity sometimes, however, which is fixed by switching BT off and on again in the watch settings.
Happend to be me once too but was not such a big deal had to restart it and then wait untill the apps got back to the watch.
But might be that the watch runs out of RAM as thearif suggested.
So what would be the best way of resolving this - have less apps installed on the watch?
tangcla said:
So what would be the best way of resolving this - have less apps installed on the watch?
Click to expand...
Click to collapse
I have a hunch that this may happen when the watch has been out of Bluetooth range of the phone too many times. I have had this happen unpairing happen on several occasions, usually when I have gone up- and downstairs a few times without my phone, or if I leave my phone in my office at work and go to pick up print-outs....
For me this happens even when the watch lays next to the phone. It doing it few times daily. Goes off and then back on. It doesnt loose pairing or connectivity, well... only few times i have had to reboot the watch to get it ON (or turned off the Bt from the phone).
Sent from my phone - Note 10.1 (N8000)
I have this problem few times also. It happen often when I change or modify watchface on Sony app editor.
As we all know Pixels have this dreaded microphone issue. Sometimes it works, sometimes not. If you restart the phone, it temporary fix the problem and after few minutes/hours my mic doesn't respond again. I tried to flash different official rom released from https://developers.google.com/android/images but the issue is still there. I believe it's software issue because the hardware works. I'm now looking to root my phone and flash a custom rom, maybe they fixed the issue in their end.
I installed Sound Meter and Mic Tester to check once in while (you should too) if my mic is working. When I found that the mic don't respond the way it should, that's the time I restart my phone.
* Flashed different versions of: Nougat, Oreo, P (preview) ... but the issue is still there.
Can we list the Custom ROMs that fixes this annoying problem (is there any)?
Sound Meter(if mic is working)
https://photos.app.goo.gl/kcU0APX2pNPYjoG12
Sound Meter(No Response)
https://photos.app.goo.gl/a1lqNeyogTtuHRkE3
Mic Tester (if mic is working)
https://photos.app.goo.gl/K7oZYvSQDS2ndJHc2
Mic Tester (Flat)
https://photos.app.goo.gl/6BPoSryI3ECNJxwu1
chrizcrozz said:
As we all know Pixels have this dreaded microphone issue. Sometimes it works, sometimes are not. I tried to flash different official release from https://developers.google.com/android/images but the issue is still there. I believe it's software issue because the hardware works.
Can we list the Custom ROMs that fixes this annoying problem?
Click to expand...
Click to collapse
I had the problem in all oreo roms, but not in nougat or P. Been running the P preview since it was available and haven't had the issue once
jacobas92 said:
I had the problem in all oreo roms, but not in nougat or P. Been running the P preview since it was available and haven't had the issue once
Click to expand...
Click to collapse
Did you try to install Sound Meter and Mic Tester? If yes, is it stable (referring to mic Issue)?
chrizcrozz said:
Did you try to install Sound Meter and Mic Tester? If yes, is it stable (referring to mic Issue)?
Click to expand...
Click to collapse
No, I would just lose microphone functionality for a minute at a time, sometimes longer. It happened in phone calls a lot. I just thought my mic was going out but I'm glad I tried a few other roms before buying a new phone. I feel like my issue was far different from your current problems
If this was a software issue, everyone running android 8.1 would have this issue. This sounds like the audio codec manufacturing defect. Unless you have an app that is interfering with something, probably not software
That's weird,. I haven't encountered that issue not on stock but I never stayed on stock for long though as I flashed custom rom a couple of days after receiving my phone. Bought it new in March. I'm running Dirty Unicorns rom though, can be found from the link to Discord on my signature.
I'm definitely interested if you find anything. Installed the April update over the weekend and bam, no mic and random reboots. Factory reset didn't help. I would think it's firmware related since it happened immediately after the update, but idk. Both Sound Meter and Mic Tester show no response.
UPDATE:
I tried to load a custom ROM - Resurrection Remix 6
So far so good. I haven't experience the problem this day.
Usually, I restart my phone 6-8(or more) times a day just to temporary fix the microphone issue.
I will observe in a few days and update this asap.
UPDATE
Resurrection Remix 6.0 works great! I didn't have any problems! It seems fixes that microphone bug.
I have uptime of 36 hours and counting with out restarting my phone. I had few voice calls and few net calls (FB and Skype).
Super big thanks to all who's involved in making that project.
https://photos.app.goo.gl/60ABq4dUFnKNKAcE2
I installed Resurrection Remix 6 and I still have the same microphone issue. Can someone please confirm if by downgrading the problem will be fixed? Thank you.
chrizcrozz said:
UPDATE
Resurrection Remix 6.0 works great! I didn't have any problems! It seems fixes that microphone bug.
I have uptime of 36 hours and counting with out restarting my phone. I had few voice calls and few net calls (FB and Skype).
Super big thanks to all who's involved in making that project.
https://photos.app.goo.gl/60ABq4dUFnKNKAcE2
Click to expand...
Click to collapse
Do I need to downgrade before flashing Resurrection Remix 6.0?
I'm on 8.1.
jacobas92 said:
I had the problem in all oreo roms, but not in nougat or P. Been running the P preview since it was available and haven't had the issue once
Click to expand...
Click to collapse
Man, you can comfirm that you got no audio and microphone problems on android P?
If so, I will cry. :,)
zeth717 said:
Man, you can comfirm that you got no audio and microphone problems on android P?
If so, I will cry. :,)
Click to expand...
Click to collapse
problem persisting in Android P too..... i upgraded last night and works well for few hours, then today, starts again........
Thanks for the tip. Ever since I got the June 18 update (D1 android 8.1) I've had random reboots, mic and the odd speaker issue.
I rooted stock with twrp n magick no difference. Even b4 restoring apps. So this week have installed pixel dust. Such a great time BUT mic n speaker problems persist, and the random reboots have become complete crashes. Where I think my phone is bricked, but if you hold power long enough it reboots. That's where I'm at now. Barely got any apps installed, dealing with it. I think I'll give ressurection ROM a ago tomorrow. Thanks for the tip. I know easily when it's happening, because I use ok Google and voice typing ALOT.
I can't believe that only last month I was totally ignorant to this issue and loved my pixel a bit too much. Now it's like dancing with a dragon ?
Does anyone else have any more tips for dealing with this?
mattyyey said:
Thanks for the tip. Ever since I got the June 18 update (D1 android 8.1) I've had random reboots, mic and the odd speaker issue.
I rooted stock with twrp n magick no difference. Even b4 restoring apps. So this week have installed pixel dust. Such a great time BUT mic n speaker problems persist, and the random reboots have become complete crashes. Where I think my phone is bricked, but if you hold power long enough it reboots. That's where I'm at now. Barely got any apps installed, dealing with it. I think I'll give ressurection ROM a ago tomorrow. Thanks for the tip. I know easily when it's happening, because I use ok Google and voice typing ALOT.
I can't believe that only last month I was totally ignorant to this issue and loved my pixel a bit too much. Now it's like dancing with a dragon
Does anyone else have any more tips for dealing with this?
Click to expand...
Click to collapse
I was also pleasantly oblivious a week ago. And I've been running on the March 2018 security patch since...well...March. So I can confirm this issue isn't caused by the June (or April, as another hypothesized) security patch. I haven't updated because I've been using Magisk for root since day 1 (opted not to install twrp), and the one time I system-updated to March, it don't go smoothly with magisk.
My repeating symptoms:
Mic failure some number of hours after boot.
And yesterday (not sure if it's repeating):
Could not receive income phone calls
so I received a Hangouts call instead, and phone did not stop vibrating until the Hangouts call was finished.
Around the time these symptoms started I had:
1 never-before-seen phone brick while I wasn't looking at it. Picked up phone, black screen, no response. Held power button for ~10 seconds to reboot.
1 never-before-seen instance of super laggy scrolling. Freezing for a second before it would scroll. Rebooted to fix.
Claimed fixes:
some say uninstalling apps solved it
some say upgrading to P
some say replacing the motherboard
The frustrating part is not having any way to know what the problem is or what the solution is. And people are experiencing different symptoms, so we can't even be sure we are having the same problem.
This article https://9to5google.com/2018/02/08/google-lawsuit-pixel-defective-microphone/ explains the cause:
If you’ll recall, Google’s 2016 Pixel devices, the Pixel and Pixel XL, faced microphones issues not too long after launch. As Google explained in early 2017, this issue was attributed to “a hairline crack in the solder connection on the audio codec,” with a warranty replacement being the only reliable fix. Later on in the manufacturing process, Google refined this part of the device to reduce the chances of this problem occurring.
Obviously, that was a frustrating issue for Pixel users, as it essentially disabled all three microphones on the device. What made the problem worse, though, was that holding the device in a different way or even a change in temperature could make the problem come back after it had seemingly gone away.
Click to expand...
Click to collapse
Free Motherboard replacements are being offered http://piunikaweb.com/2018/05/03/untangling-google-og-pixel-motherboard-replacement-mess/ by UBreakIFix:
Google is providing free motherboard replacements, but only to those encountering bootloops due to microphone-related issues (lawsuit affect?). Some one who claims to be working for uBreakiFix have recently confirmed this on a Reddit thread discussing the matter.
Click to expand...
Click to collapse
abemore said:
I was also pleasantly oblivious a week ago. And I've been running on the March 2018 security patch since...well...March. So I can confirm this issue isn't caused by the June (or April, as another hypothesized) security patch. I haven't updated because I've been using Magisk for root since day 1 (opted not to install twrp), and the one time I system-updated to March, it don't go smoothly with magisk.
My repeating symptoms:
Mic failure some number of hours after boot.
And yesterday (not sure if it's repeating):
Could not receive income phone calls
so I received a Hangouts call instead, and phone did not stop vibrating until the Hangouts call was finished.
Around the time these symptoms started I had:
1 never-before-seen phone brick while I wasn't looking at it. Picked up phone, black screen, no response. Held power button for ~10 seconds to reboot.
1 never-before-seen instance of super laggy scrolling. Freezing for a second before it would scroll. Rebooted to fix.
Claimed fixes:
some say uninstalling apps solved it
some say upgrading to P
some say replacing the motherboard
The frustrating part is not having any way to know what the problem is or what the solution is. And people are experiencing different symptoms, so we can't even be sure we are having the same problem.
This article https://9to5google.com/2018/02/08/google-lawsuit-pixel-defective-microphone/ explains the cause:
Free Motherboard replacements are being offered http://piunikaweb.com/2018/05/03/untangling-google-og-pixel-motherboard-replacement-mess/ by UBreakIFix:
Click to expand...
Click to collapse
I never had bootloops but the mic and audio issue, with stockROM, pixel dust and CrDroid. Then I heard about the ubreakifix possibility and when to the next store and they changed the MB without hesitation. Since then it works like a charm. Just go there, they are very helpful. That's a hardware issue not a software one.
Long story short - the update triggers the behavior(s), but its actually a manufacturing fault. You can replace part or your full motherboard to fix it. I personally just flashed stock and took it back to EE and they replaced it no cost. I remembering reading its a common problem with a certain early batch of Pixels. I've lost the link but you can use your serial number to check if its an early version thats effected. Apparently its only effects less than 3% of phones but the problem looks bigger when i was searching lmfao.
Anyway software fixes might help, but ultimately its a hardware issue. Get it replaced. Yeah they sent me a new one with a locked bootloader so i have to start from scratch but thats better than living with the error.
mattyyey said:
Long story short - the update triggers the behavior(s), but its actually a manufacturing fault. You can replace part or your full motherboard to fix it. I personally just flashed stock and took it back to EE and they replaced it no cost. I remembering reading its a common problem with a certain early batch of Pixels. I've lost the link but you can use your serial number to check if its an early version thats effected. Apparently its only effects less than 3% of phones but the problem looks bigger when i was searching lmfao.
Anyway software fixes might help, but ultimately its a hardware issue. Get it replaced. Yeah they sent me a new one with a locked bootloader so i have to start from scratch but thats better than living with the error.
Click to expand...
Click to collapse
You're right. I ended up getting a free repair from uBreakifix. The guy said he wasn't allowed to tell me what he did to fix it. I noticed he had downgraded me from Android 9 to 7.1.2. I hoped that wasn't the secret fix. On closer examination, I noticed the serial number had changed, which means they replaced my motherboard...for free...on an out of warranty Pixel that I bought second hand. :good:
After I have done full factory reset, my P20 started to lag. I experience latency during opening apps, scrolling is not smooth as it was before. Basically I experience lag in general.
I tried to so factory reset again, it got a bit better, but lag still exists. Also, I have tried to compare app opening speed and performance with my friends new P20, so his phone works way more smoother.
What else I can do with my phone?
Maybe there is an update available for you? I have no idea tbh, try maybe rebooting like 3 times.
Sent from my EML-L29 using XDA Labs
I have only updated once, right after seting up phone first time. Right now there is no updates available
same problem with my p20
even in lineage rom, I have lag on it so it's not emui the problem
I have never seen a smartphone so slow
actupsp said:
same problem with my p20
even in lineage rom, I have lag on it so it's not emui the problem
I have never seen a smartphone so slow
Click to expand...
Click to collapse
Is it lagging after you done factory reset?
he always had lags since the beginning, with or without factory reset
with emui and with lineage os, so it's not software but hardware
Seems like these are some defective units or I am extremely lucky. Never had any sort of lag. Performance has been top notch for me.
Also there is no official lineage available for this device so I'm not surprised about the lag. Although I've read that 3 or so reboots usually fix the lag.
Sent from my EML-L29 using XDA Labs
Believe me I'm feeling really fusfrating.
Yeatarday I have installed new EMUI version so right now my battery started to drain super fast.
30 minuts of usage would take 10% battery, the f*** is this...
Getting really good performance as well. I have not experienced any sort of lag to speak of.