Related
A few people here and there have been starting to have this problem pop up- including me.
My phone was perfectly fine with absolutely no problems with the touch screen but about three days ago, my phone started acting weird.
At that time, I was running CM 5.1 nightly and then dirty flashed over to the latest. I thought that this was the problem and so I did a clean flash but still the problem was there.
Went back to the original CM nightly that I was previously on and problem is still there.
Tried many different ROMs but the problem is still there..
I can't type out a sentence without my phone failing to register a touch and sometimes registering rapid touches as one - the same problems before Synaptic released a 'fix' for this issue.
At this point, I don't really know what to do but it's aggravating that a phone can't do it's basic tasks such as type.
The phone seems really sluggish when I type - which I haven't encountered before this which slightly leads me to believe that input lag is the crux of the problem however, I can't say for certain.
Can anyone with more expertise help me with this?
Same issue
You_got_owned123 said:
A few people here and there have been starting to have this problem pop up- including me.
My phone was perfectly fine with absolutely no problems with the touch screen but about three days ago, my phone started acting weird.
At that time, I was running CM 5.1 nightly and then dirty flashed over to the latest. I thought that this was the problem and so I did a clean flash but still the problem was there.
Went back to the original CM nightly that I was previously on and problem is still there.
Tried many different ROMs but the problem is still there..
I can't type out a sentence without my phone failing to register a touch and sometimes registering rapid touches as one - the same problems before Synaptic released a 'fix' for this issue.
At this point, I don't really know what to do but it's aggravating that a phone can't do it's basic tasks such as type.
The phone seems really sluggish when I type - which I haven't encountered before this which slightly leads me to believe that input lag is the crux of the problem however, I can't say for certain.
Can anyone with more expertise help me with this?
Click to expand...
Click to collapse
Im having a similar problem. I cant type a single sentence without errors. It doesnt register the touch as well few times. Using a device is so sluggish.. hate it. Tried many roms with clean wipe but without any success. Would be nice if anyone could help with the above issues.
I have similar issues and I don't think it's a software issue - I have never flashed a ROM. I think it's hardware problem, probable the earthing suggested in this post:
http://forum.xda-developers.com/oneplus-one/general/fixing-ghost-touch-grounding-issue-hint-t2951000
There is an app that re-calibrates the touchscreen every time you turn it on, but it doesn't completely solve the problem for me and also prevents unlocking until it has completed, which is annoying. The fact that a re-calibration is needed to even achieve a little stability is consistent with an earthing problem.
If mine gets any worse, and I think it will, I'm going to investigate a warranty claim, but that sounds like a few weeks with no phone, which I can't tolerate.
hi, i'm experiencing the same problems. you can test this when registering 2 touches on the same Y axis (try with anyone of touch test apps).
I think that this is popping out to a lot of people in this moment because of the hot days kicking in. in fact, if your phone is cold (try to put in a fridge for 5 minutes) it will work perfectly, but when it will become hot again in your hands the touch will start to freak out again
What sucks is my phone was perfectly fine a few days ago and we've only had an increase of about 5 deg F over the week.
Occasionally the capacitive buttons don't register either.
Same thing here. Perfectly working screen, flashed 5.1 unofficial some weeks ago and no matter wich versión of cm or what kernel, randomly ghost touches happens.
Now with official 5.1 and ak 200 works better, but it's still there. There must be some kind of firmware/software problem, It's too curious that this issue begin to happend to many people at the same time.
My bro has the same problem, some days after flasing CM12S the screen doesn't feel as responsive anymore.
The screen isn't able to handle multiple touches anymore what makes typing really annoying, scrolling through settings also goes really slow.
Tried flashing latest 12.1 nightly but I don't think any ROM will be able to fix it.
No idea what caused it and if there is a way to fix it.
ZuLa said:
Same thing here. Perfectly working screen, flashed 5.1 unofficial some weeks ago and no matter wich versión of cm or what kernel, randomly ghost touches happens.
Now with official 5.1 and ak 200 works better, but it's still there. There must be some kind of firmware/software problem, It's too curious that this issue begin to happend to many people at the same time.
Click to expand...
Click to collapse
This is exactly what happened to me and it seems like it happened to a good number of people around the same time. Either 1)It's a huge coincidence 2)OnePlus rigged our phones to go haywire around this time or 3)Something in one of the nightlys got messed up for a few people however like you said, flashing new roms for kernels doesn't help anymore which makes me want to do a complete wipe - Internal data included.
Same issue
I was sure it's the heat some time back but then this touchscreen fixer app in the Themes and Apps section is actually helping. That makes me wonder if its the firmware, coz the problem only kicked off after the CM12.1 update. A few of my classmates purchased the OPO at the same time as I did and they dont have this issue (they didnt go to CM12.1).
Any tips on what firmware/ROM to revert to?
Edit: I also flashed the Oxygen OS firmware.
It's not a change in the firmware, mine did it spontaneously. It's hardware. OnePlus will do everything they can to spin a software story and indeed it will often be possible to partially mitigate in software, but ultimately everyone with this problem should be getting a replacement. That could be a lot of people.
patp said:
It's not a change in the firmware, mine did it spontaneously. It's hardware. OnePlus will do everything they can to spin a software story and indeed it will often be possible to partially mitigate in software, but ultimately everyone with this problem should be getting a replacement. That could be a lot of people.
Click to expand...
Click to collapse
I'd love to see how you jumped to such a definite conclusion. I live in a warm climate to begin with, temperatures are actually lower now than they were a month and a half ago, and the CPU of my OPO has definitely risen above the 41-45 Celcius range that people seem to quote for this current wave of issues (and I have corroborated with my own testing). However, if I go to the recovery, the touchscreen seems to have normal responsiveness, regardless of the CPU temperature. Unless it was a built in hardware malfunction set for a specific moment, the probability of a sample, even of this size, where a series of individuals can all see the exact same lineup of hardware-based issues occurring at the same time, is too ugly for me to try and imagine calculating. But I would fare to bet it isn't high.
However, if a set of users are all changing their software as new versions and builds come out, just as the release occurs... At least then you have a series of events occurring all at the same time. Not causation, but at least there's a stronger correlation than "it's warming up so now we see the hardware defects".
The temperature range this "defect" is being attributed to can be reached quite easily in normal use in temperate areas, but even in colder climates, it should be simple to reach such temperatures if the phone isn't underclocked, as the phone is set to charge, or even if the phone is running a software update of some kind, and countless other things.
TL;DR - Don't jump to conclusions that fast, weather changes aren't a strong correlation.
hyshion said:
I'd love to see how you jumped to such a definite conclusion. I live in a warm climate to begin with, temperatures are actually lower now than they were a month and a half ago, and the CPU of my OPO has definitely risen above the 41-45 Celcius range that people seem to quote for this current wave of issues (and I have corroborated with my own testing). However, if I go to the recovery, the touchscreen seems to have normal responsiveness, regardless of the CPU temperature. Unless it was a built in hardware malfunction set for a specific moment, the probability of a sample, even of this size, where a series of individuals can all see the exact same lineup of hardware-based issues occurring at the same time, is too ugly for me to try and imagine calculating. But I would fare to bet it isn't high.
However, if a set of users are all changing their software as new versions and builds come out, just as the release occurs... At least then you have a series of events occurring all at the same time. Not causation, but at least there's a stronger correlation than "it's warming up so now we see the hardware defects".
The temperature range this "defect" is being attributed to can be reached quite easily in normal use in temperate areas, but even in colder climates, it should be simple to reach such temperatures if the phone isn't underclocked, as the phone is set to charge, or even if the phone is running a software update of some kind, and countless other things.
Click to expand...
Click to collapse
The outside temperature being warm would keep the screen hot for a prolonged period of time as compared to the phone heating while charging or intense usage. However, your recovery argument is spot on! The touch works flawlessly in recovery!
goldengargoyle said:
The outside temperature being warm would keep the screen hot for a prolonged period of time as compared to the phone heating while charging or intense usage. However, your recovery argument is spot on! The touch works flawlessly in recovery!
Click to expand...
Click to collapse
Well I guess it's good that it's not hardware damage.
Has anyone tried going back to android 4.x to see if it helps- if it really is software?
Surprised there hasn't been more people experiencing this issue given the number of people going to android 5.x
I have the same frustrating issue
Same here, works fine in recovery. Also had this issue arise after the first bout of touch issues: https://www.youtube.com/watch?v=yoFYcFawTI4&feature=youtu.be
(clearing cache seems to alleviate that particular problem)
I think it's a software issue. I mean possibly there is hardware problems too but mine started appearing only after I installed the 5.1 update... also some things for me feel like a software issue for example when scrolling instagram back up to the top. as soon as it gets to the top it bounces back down again.. seems like software problem to me.
This is definitely a hardware issue. My phone was working perfectly. Until I went on a 5 days trip and used it for navigation, and went very hot. Up until then I was on the same CM12 rom for weeks without a problem. Since then, I've flashed many roms and the problem persists. It's definitely a hardware problem. For me it occurs whenever the phone runs a little bit hot. Practically all the time when I'm on 3G. When the phone has been in my pocket with 3G on, it's almost impossible to unlock it when I try to use it.
I contacted Oneplus a week ago and I still try to get them to RMA the phone. They've sent me all sorts of crap emails, I wiped the phone and now they ask me to shoot a video to showcase the problem. This company has the worst customer service you can find. As much as I like the pricing, I won't be bothered again with their devices. I only hope they'll RMA it otherwise I'll open it myself and try to fix the grounding issue. There is a detailed how to which also explains what's the problem.
I always had it but it was so minim that maybe couple of times a day weren't that big problem!
Just yesterday and today the issue is now intolerable! I removed the screen protector and used the stock lollipop keyboard (bcz swiftkey is kinda slower the issue was there more).
It's still very annoying and I can't type easily! I had to remove flow/swype feature to minimize it further!
Seriously considering buying another phone although I wanted to keep it for a year at least! But the hate is growing on me...
HAha exact same problem here happening since 3days.
I was on Euphoria 29/3 build. I flashed ak kernel, after reboot i couldn't type properly anymore. I was like damn, maybe its bad kernel setting or so. Didn't help.
Cleanflashed 3 roms since then, didn't solve anything. All tho touch works fine in twrp for me. So im really clueless. Swiping does seem to work better for some unknown reason to me!
The ghost swipes while typing is driving me crazy. Thinking of going back to 5.0.2 to see if that helps. Do I need to flash an old firmware to go back to a previous Android version
Alright,
Phone: Nexus 5 2013
Android: 5.1.1
Country: Canada
So I've started to get a lot of issues on my Nexus 5 that I ordered back in November 2013 (when it was released) and they are too big to be left alone. If I cannot fix them, I'll have to buy a new cellphone and there's none that interest me right now, nor that I want to change my current Nexus 5.
Issues:
My Nexus 5 doesn't connect to my cellular network anymore. I'll stay on "No service" and refuse to connect to any Operator Network stating that the network is unavailable at the moment, even thought it is. Sometimes, it'll connect to the network for 15 to 30 minutes, before losing it for the next 8 hours.
It becomes hot really, really quick randomly. The upper back part of it becomes hot, and according to the Nexus 5 architecture, the battery isn't even located there so I don't know what could make it heat up like that. This happens even without it being charged, and without me using it a lot (games, apps, etc.)
The phone will randomly restart for no reason, and sometimes stay stuck on a "boot loop" (Starting apps X of Y... before restarting).
The vibrate mode is messed up. It'll vibrate every 30 seconds for a notification (email, Facebook, SMS, etc.) despite the fact that there's nothing, absolutely nothing. Right now I disabled the vibration/sound mode to avoid that issue.
The battery gets drained really, really fast. Like overnight, while not being used it'll fall from 100% to 5%. It never used to do that. When I don't use it overnight, it would lose maybe 20%, even less than that. It started recently as well.
All these issues were present in past versions of Android, starting at 4.4 so I doubt the version is in cause here, but it's still a possibility I guess.
I got my SIM card changed for a brand a new one, troubleshooted the phone with everything I could find online before giving up and restoring it to it's default settings, but the issues are still present. I don't know what I should check anymore. If you have any comments, experiences or solutions I could try to solve my issues, please let me know since at this point I'll most likely try all of them. Also, if you need more information on my phone, system, etc. let me know as well.
Thank you.
Is your phone stock/rooted etc?
Sent from my Nexus 5 using Tapatalk
There is a recognised problem with the Nexus 5 that a dead battery can kill something in the radio functionality. Since you have so many problems your best bet is to start with the software - a full refresh of the ROM. It might be worth waiting a few days for the release of Android 6.0 which is supposed to be coming in the next week (anything from 29th September to 5th October, but who knows...?). If you can't wait, save whatever you want from the device and install preview 3 MPA44I - it works very well on my N5, and since I'm not using it as my daily phone (I have a Nexus 6) the standby battery life is amazing. At the moment it shows 76% with 13 days 12 hours left.
firemaned said:
Is your phone stock/rooted etc?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It used to be rooted, but it's not anymore. Any way I can make sure that it's rooted or not? When I used the SuperSU app back then I realized at some point that it wasn't rooted anymore (it was telling me that this app can only be used on rooted devices). I think the bootloader is unlocked because when I open my device, it shows me the little lock icon, but it's open (unlocked). Also, it's freshly reset to factory default (from yesterday).
dahawthorne said:
There is a recognised problem with the Nexus 5 that a dead battery can kill something in the radio functionality. Since you have so many problems your best bet is to start with the software - a full refresh of the ROM. It might be worth waiting a few days for the release of Android 6.0 which is supposed to be coming in the next week (anything from 29th September to 5th October, but who knows...?). If you can't wait, save whatever you want from the device and install preview 3 MPA44I - it works very well on my N5, and since I'm not using it as my daily phone (I have a Nexus 6) the standby battery life is amazing. At the moment it shows 76% with 13 days 12 hours left.
Click to expand...
Click to collapse
I already did a Factory Reset on my phone yesterday, so I guess I don't have to do another one? Right now, if I follow what you just told me, I should wait until the release of Android 6.0 (M) and upgrade to it then see if it solves my issues. I just hope that it won't take a long time to be pushed to my phone like it was with Android 5.0. Or your other solution is to flash the latest preview for Android 6.0 (M) on my phone and see how it goes, right?
If you've restored a ROM and lost root, and are back to 100% stock Android, then as far as I know the Android 6 upgrade will be provided over the air (OTA) and will work fine. Whether it resolves your problems is a different question. I myself tried everything to make my radio work again after the battery died, and eventually contacted Google, who were honorable enough to send me a replacement (refurbished, but effectively as good as new) which works perfectly.
dahawthorne said:
If you've restored a ROM and lost root, and are back to 100% stock Android, then as far as I know the Android 6 upgrade will be provided over the air (OTA) and will work fine. Whether it resolves your problems is a different question. I myself tried everything to make my radio work again after the battery died, and eventually contacted Google, who were honorable enough to send me a replacement (refurbished, but effectively as good as new) which works perfectly.
Click to expand...
Click to collapse
That was my original plan. I called the Play Store support this week and they told me that my phone was elligible for a replacement till April of 2016. I found that weird because it would make it a 2 years and a half guarantee but at least I had my backup plan in mind. Then I called today to order a replacement and the guy told me that my guarantee expired back in November 2014 (1 year after I bought my Nexus 5, which made sense) so now I'm stuck with this one. I don't know why, but since this morning (after creating this thread), the cellular network cameback. It still drops sometimes but only for a few seconds and if not, I enable/disable the Plane mode to make it connect again. However, the battery drain, phone heat, random restart and messed up vibration issues are still present. I can deal with them however until Android 6.0 (M) gets released. The most important thing was the cellular network. We'll see tomorrow how it goes. Still awaiting tips and tricks for my other issues if anyone have some.
For the battery draining issue, I think I have the paid version of Greenify somewhere and was thinking of using it to see if it helps, even though I didn't have that issue at the beginning.
Instead of a factory reset you should try using fastboot to flash the factory image for a fresh start.
Sent from my Nexus 4 using XDA Free mobile app
CalculatedRisk said:
Instead of a factory reset you should try using fastboot to flash the factory image for a fresh start.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
And I imagine that the factory image is still present on the device? This is what I find weird, because when I "reset" my factory to defaults, it restores it to Android 5.1.1 even though the device came with 4.x. I come from the computer field, and a Factory Reset on a computer uses the manufacturer's image present on the CD, DVD, USB or partition given with the computer to reinstall the original OS that was present on it and the OEM software as well. If the computer was eventually upgraded to Windows 8.1 and came with Windows 7, Windows 7 will be restored, not Windows 8.1. So I can understand now that a "Factory Reset" doesn't really return the device to its factory state, right?
I would guess that you've had an OTA update to 5.1.1? You would have had to actively accept it - it doesn't install itself automatically. The factory image isn't (as far as I'm aware...) on the device, it just resets components back to default values - I may be wrong about this. There's obviously no way that a Kitkat device could mysteriously upgrade itself to Lollipop in any other way than a deliberate flash or an OTA update.
I use Greenify myself and it appears to do what it claims, but I wonder if it will become unnecessary when the new Doze function comes in with Android 6. Maybe the two will complement each other for optimum battery life. Any experts out there that can comment?
You mention that it's the upper back that becomes hot - I'm guessing that this is where the processor is. Mine does the same if it's running under load - for example when taking a TWRP backup. And anything that's creating heat has to get its energy from somewhere, hence the battery drain. If there is a rogue app that's running even when you're not using the phone Greenify might kill it - worth a try.
And final comment (for the moment... ) - the padlock with the gap means that your bootloader is unlocked, but doesn't mean that the phone is rooted. It does however mean that the phone can accept new ROMs and can be rooted.
dahawthorne said:
I would guess that you've had an OTA update to 5.1.1? You would have had to actively accept it - it doesn't install itself automatically. The factory image isn't (as far as I'm aware...) on the device, it just resets components back to default values - I may be wrong about this. There's obviously no way that a Kitkat device could mysteriously upgrade itself to Lollipop in any other way than a deliberate flash or an OTA update.
I use Greenify myself and it appears to do what it claims, but I wonder if it will become unnecessary when the new Doze function comes in with Android 6. Maybe the two will complement each other for optimum battery life. Any experts out there that can comment?
You mention that it's the upper back that becomes hot - I'm guessing that this is where the processor is. Mine does the same if it's running under load - for example when taking a TWRP backup. And anything that's creating heat has to get its energy from somewhere, hence the battery drain. If there is a rogue app that's running even when you're not using the phone Greenify might kill it - worth a try.
And final comment (for the moment... ) - the padlock with the gap means that your bootloader is unlocked, but doesn't mean that the phone is rooted. It does however mean that the phone can accept new ROMs and can be rooted.
Click to expand...
Click to collapse
I did have an OTA update to 5.1.1, yes.
And I talked to one of my friend who's really into phones (used to work for Bell and he's usually the person I go to whenever I have issues with my cellphone), and he suggested me to wait until Android 6.0 comes out, and then to fastboot it on my Nexus 5 since OTA updates can be buggy sometimes. I could actually fastboot the phone right now (well tonight) with Android 5.1.1, but if Android 6.0 is to come out next week (or the one after), it might worth the wait, depending on whether or not I can keep the cellular network working. Otherwise I would have to go through 2 flashboots in 2 weeks and I can't really be bothered to do that
And I don't know where the CPU is in the Nexus 5 (I could look it up) but the zone where the heat is isn't where the battery is so there's that. However, my friend told me that the fact that my cellular network isn't working could explain why the battery is being drained so fast, but can't explain the vibrate mode and random restarts issues.
I was having battery issues on Stock ROM, but now I am using CM12.1 so battery is not draining very fast.
When I am inside my home or in some other house or building, the network disconnects very often. However, if I am outside, the network works pretty well.
The notification LED, when being configured using CM12.1 settings, shows blue color on green color selection and green color on blue color selection.
I had some of the same problems with my phone, it would reboot randomly throughout the day. With mine if I charged it overnight with it off when I turned it on in the morning it would only be at 85%. I ended up contacting LG and I paid $170 to get it fixed, they have replaced the mainboard twice so far. After the second time it had no issues, and that lasted a couple months but I have sent it back again to be fixed. If you bought the phone on a credit card they usually extend the warranty by a year, that's what I did, filed a claim and they sent a cheque for the repair cost, very simple actually. But I suspect it might be the same problem as mine, some hardware issue, especially if you've reset the phone.
Just for info, the CPU is indeed at the top rear of the phone, so this is undoubtedly where the heat is coming from.
https://www.ifixit.com/Teardown/Nexus+5+Teardown/19016 - see step 11 saying "The Quad-core, 2.26 GHz Snapdragon 800 SoC is layered beneath the RAM".
I reckon it's a rogue app, which I hope isn't a system app, running wild - a system app will be hard to cure.
A ROM refresh is probably a good place to start, and if you can wait for Android 6.0 then why settle for less...
Wiped my os on nexus 5 trying to install nethunter only comes on in twrp. very new to this be easy on me ive previously installed a vm lab with kali linux.
I have downloaded adb and fastboot
Using winace . Before this my pc would not recognize my device, "no drivers". But now it shows up on the pc control panel as active and found
However snap pea still cant find drivers although now it says are you fornatting your phone with only one option "yes" then it just dissappear. ... but before I downloaded adb, fast boot ... snap pea was simply saying no drivers found.... Please help. ..thank you.
Sent from my GT-I8190 using XDA Free mobile app
Here's an update on my situation: the cellular network is back at both my house and my workplace. The way it works, it seems that it takes it a day to "adapt" itself to the location and then gives me network. So at first after the Factory Reset, I didn't have network at my house, the day after I did. Now, when I went to work on Monday I didn't have network, but when I did on Tuesday, I did. My job is an hour of road away too, and at some places on the road I don't get any network, but it happens less and less as I travel back and forth.
The random restart and overheating issue are still present however. I didn't test the notifications (on vibrate) but I will soon. As long as I have my cellular network, I don't care about the other issues, until Android 6.0 (M) gets released and I fastboot it on my phone.
Now, since I bought my Nexus 5 using a MasterCard, I remembered that they have a promotion which double the guarantee on electronics (up to a 1 year), which means that I have a 2 years guarantee on my phone. So I called LG, and they have a promotion right now, $150 to get my phone repaired by their tech center IF it can be repaired. If they can't, they send it back and gives me a 50% refund (around that number).
My current plan of action is to wait for Android 6.0 (M) to get released, flashboot it on my phone and see how it goes from there.
Thank you for all the replies so far, they really helped me and still help me today
Good luck man. Keep us updated.
Sent from my Nexus 4 using XDA Free mobile app
Alright so, I fastbooted Android 6.0 on my Nexus 5, and it seems to have done the trick. I have network everywhere now, even on the road. I still lose it from times to times (a few seconds only), but this is a "normal" behavior considering the carrier I have. The notification issue is also gone, and so does the restart issue since I didn't have it once so far. But I only fastbooted it yesterday evening so it might be too soon to say that.
Now, I still have the "overheating" issue, but it could be from me playing Fallout Shelter, I really don't know. I used to play Clash of Clans alot, and graphically speaking, I think it's more demanding than FS, but I never had that overheating effect before. One thing I noticed however is that after fastbooting Android 6.0, my battery drops real fast, even when idle. I thought that Android 6.0 was supposed to improve the battery life. I'll try to see what process, app or activity is taking the most juice out of it, but I'm sure this isn't normal.
Alright so it took me an hour to go from my house to my workplace, and my battery went from 34% to 12%, while being on standby. This isn't normal I guess. I'll need to charge it to 100% once, and then use the Battery setting to see what's taking all the juice.
Might have spoke too soon. When going to work today, I went in a room where there's usually no signal (or the signal is very weak), and lost the network. It's normal in that room so I didn't pay much attention to it, but now I'm not able to get back on the network. Even searching for the Network Operator fails. Sigh, it really looks like I'll have to send it to LG for repair. I guess I need to fastboot it first to erase all my data, because they need to use my phone to test the repairs they make?
My Note 10.1 is extremely slow recently. I mean it can work normally for half an hour and then hang for a minute or not allow me to turn the screen on for 30 or more seconds. Is this because of age? Is the flash inside degraded to a point it slows everything down or maybe clear new ROM will fix this? I am asking because I am not exactly sure I will be able to load a new ROM on it (the recovery is a bit broken, but it will probably be possible through Odin). If it is happening to other old, heavily used Note 10.1's I will just leave it as it is, instead of risking of breaking it completely. So, how are your good old Note 10.1's behaving lately?
One replace battery if you think thats at fault .
Two wipe and install stock rom via Odin .
Nand / flash should not degrade in such a short time .
It took me a while, since I use the tablet very rarely and have gotten used to it's slow downs but I have solved the problem - it was caused by the kernel it had. Changing the kernel to a new, stable one solved the issue. The tablet is still a bit slow, but no longer hangs for 30 seconds like it used too. Thanks everyone for help.
Magnesus said:
My Note 10.1 is extremely slow recently. I mean it can work normally for half an hour and then hang for a minute or not allow me to turn the screen on for 30 or more seconds. Is this because of age? Is the flash inside degraded to a point it slows everything down or maybe clear new ROM will fix this? I am asking because I am not exactly sure I will be able to load a new ROM on it (the recovery is a bit broken, but it will probably be possible through Odin). If it is happening to other old, heavily used Note 10.1's I will just leave it as it is, instead of risking of breaking it completely. So, how are your good old Note 10.1's behaving lately?
Click to expand...
Click to collapse
I experienced the same problem until recently with my GT-n-8010, when it still was under the official 4.4.2 firmware. I also thought about an age problem, but it was definitely not. I've been trying for the last four days the CM13 BETA developped by senior member Lirokoa - everything is explained in this thread : http://forum.xda-developers.com/galaxy-note-10-1/development/rom-lollipop-t3269375 - and it's just as if I had gotten a brand new device, so it really was a software problem, not a hardware one. I advise you to try it too, you should not regret it
so my galaxy s7 phone did it recently
exactly after one year warranty just expired the phone became painfully slow
it was a brand new phone sent from samsung as a replacement for my broken phone replaced under warranty
had zero problems for a whole year and i mean zero like no issues with speed or freezing at all
never dropped or dipped in the water to test the water resistance
always in a case since day one. no crazy apps. actually same exact apps that i have on all my phones.
no new apps were installed before slowdown
i already deleted some apps. cleaned up app cache individually and reset cache from boot screen
tested in safe mode and still slow
im not sure if the update was installed recently or not but the slowdown happened about 2 months ago. was there a tmobile update at that time?
im not really sure.
but this is the third phone that did this.
galaxy s5 that i also bought brand new for a year was well maintained and had no problems
that phone actually started lagging really bad and shutting down multiple times a week or restarting....
before that galaxy s3 did same thing. after exactly a year it became ridiculously slow for absolutely no reason
i install all the apps i use right out of the box. change all the settings to what i want and dont really make any changes after and it usually very stable for about a year
is there an app that i can use to troubleshoot?
or an app that will show me what component is slowing down the system in real time?
obviously something is slowing down the OS, theres gotta be an app that can trace the faulty app or file or component
i cant be the only one who noticed that
is there really no way to pinpoint what is slowing down the phone?
why do i have to reset everything every time it gets slow
isnt there an app that can diagnose what is loading up the system?
this phone is painfully slow suddenly with no apparent reason
Have you been able to view the CPU activity and the RAM allocation?
I am not sure how to do this, but if possible, it might reveal what is happening.
I would try disabling some of the applications one by one. First suspects would be:
1. Facebook
2. Google Play Store.
3. Youtube.
Disable one, then try the phone. If still the same, disable second and try etc.
Jim.
How is your device storage. Once you use more then 50% device storage android starts to lag. It's an issue with the OS.
device storage has always been about the same since brand new. which is about 80% on average.
doesnt safe mode disable all non stock apps? i tried safe mode with same result
windows has a resource monitor that helps alot but i dont know if android has any monitoring app that could help troubleshoot this
Samsung devices are known for getting laggy over time, try a different phone next time, in the meantime, do a factory reset and start fresh.
fuzzysig said:
device storage .......................... about 80% on average.
............................................
Click to expand...
Click to collapse
This is very suspect to me, but I am only a beginner.
Given zelendel's post about (re 50%), I would investigate further. Did you note his credentials?
What does all that data consist of?
What is the total storage capacity of the phone?
Perhaps some of that storage capacity is used as "swap" memory? Just guessing...........I am extrapolating Linux terminology here.
about 10-15 gigs of that is music/videos for airplane or when i have no internet. its been there since i got the phone
other things come and go like downloads documents videos images
im surprised theres no apps to troubleshoot the phone lagging when theres so many people having that problem and the best solution is to just reset the phone. which should be the last resort
if resetting the phone works most of the time then there should be an app that could look for conflicts as it runs in the background.
fuzzysig said:
about 10-15 gigs of that is music/videos for airplane or when i have no internet. its been there since i got the phone
other things come and go like downloads documents videos images
im surprised theres no apps to troubleshoot the phone lagging when theres so many people having that problem and the best solution is to just reset the phone. which should be the last resort
if resetting the phone works most of the time then there should be an app that could look for conflicts as it runs in the background.
Click to expand...
Click to collapse
Depending on the amount of storage in your device that could be a lot.
Resetting the device wipes things. You really can't find an issue if the only issue is storage space. So here is a test. Remove stuff from your device. Give yourself a clean start and then go from there. Adding stuff slowly until it slows down.
I have had dozens of devices and the only time they ever got slow was due to getting low on phone storage.
This even encludes a 5 year old Samsung that I have that is as fast as the day I got it. Mind you there is nothing on it but some games for a kid. I even disabled all of Samsungs crap they install that slows a device down.
Could also be stuff acting up in the background
Run a log cat and see if anything is hanging.
cool thanks ill try that
got my internal memory to under 50%
reset cache again
deleted few apps and moved alot of them to SD card and cleared cache for those too
heres exactly whats happening
theres a delay for every action
2 wifi seems to drop in and out now since it got slow
3 facebook and browser wouldnt load anything on wifi
but as soon as i switch to data it works
i have to restart the phone alot now and close all apps multiple times a day to get them to work
also running safe mode had no effect on speed
i dont know when the last update was from tmobile but it might have been due to crappy update im not sure at this point
i got the phone last end of summer and it worked flawlessly every single day up until last 2 months exactly when warranty expired
how does samsung find faulty hardware when i send it in for service?
do they use an app?
ok this is getting ridiculous.
the phone wen to complete ****
facebook doesnt load posts unless i restert it by closing the app
phone just feels very slow overall.
constantly lags hangs. and in general just completely crappy performance slowly degrading.
i dont know why suddenly it started happening just like my last 3 phones
after about a year theres always a sudden decrease in performance and things start bugging and lagging etc
so theres no way to figure out why its slow?
isnt there some hardware tests or system scan or something that can help point to the problem?
Sorry to read that you are still having this problem Fuzzysig.
Did you try any of the suggestions in my post #4 and/or in Zelendel's post #10?
If so, which ones did you try and what resulted from those changes?
fuzzysig said:
so theres no way to figure out why its slow?
isnt there some hardware tests or system scan or something that can help point to the problem?
Click to expand...
Click to collapse
Hi, I was a Samsung user too and faced the same problem.
I went through various threads which gave me multiple solutions: rooting, removing bloatware, cpu monitoring and many more.
None of that worked. The phone was so slow that it was not usable.
Ultimately I had to throw it and buy another phone.
Then I noticed this is not just me, all Samsung users face the same problem even the flagship users.
I swear I'll never buy a Samsung phone and never let anyone buy one.
So I've had a T-Mo S7 for about a year and a half now. It's incredibly slow/unresponsive and I've spent a really long time troubleshooting.
I've done full factory resets, and direct ODIN OS installs with data wipes. Whenever I do this, the phone starts out, with all current apps installed, extremely fast/responsive. I have a somewhat limited app library, and I haven't added anything since the phone slowed down noticeably.
About two months ago, the Samsung Device Maintenance app, which until then only reported battery draining, said "Some apps or processes are overloading the system (CPU)" and the app it reported was something like com.android/google.searchbar" which I assume is the google search bar widget. I thought, "awesome, the device app is actually doing something." I told it to kill the app and my phone sprung to life. My phone was super fast for a long time, but is now back to being super slow again. I searched "Apps" in device settings and can't find any apps/processes that sound anything like search bar. Also, how is there not a system resource monitor in system settings!? Clearly, an app is hogging resources, because I've experienced periods of responsiveness. Is there no direct way to figure this out without doing the safe mode process of elimination?
Can someone help shed some light or suggest further troubleshooting steps? Thanks in advance.
I got mine on black friday 2 years ago and I've been having the same issue. Of course my battery doesn't last very long being it's over 2 years old. I'm guessing it may have some.thing to do with the battery voltage being so weak after so long. I'm due for an upgrade obviously but I'd be fine using my S7 for another year if a battery replacement did the trick. I believe I was told in chat that I could go into the store and they'd only charge me $5 but I assume they'd have to send the phone out unless they just swap it out for a refurbished one. I've had no other problems with mine at all so not really the route I want to take.
Anyone else familiar with this process? Has anyone else had their battery replaced or phone swapped and notice if the fresher battery helps or is it just a symptom of it "can't" handle the newer OS properly? Any feedback would be appreciated. Hopefully it helps us both out. Didn't mean to hijack the thread!
tony yayo said:
I got mine on black friday 2 years ago and I've been having the same issue. Of course my battery doesn't last very long being it's over 2 years old. I'm guessing it may have some.thing to do with the battery voltage being so weak after so long. I'm due for an upgrade obviously but I'd be fine using my S7 for another year if a battery replacement did the trick. I believe I was told in chat that I could go into the store and they'd only charge me $5 but I assume they'd have to send the phone out unless they just swap it out for a refurbished one. I've had no other problems with mine at all so not really the route I want to take.
Anyone else familiar with this process? Has anyone else had their battery replaced or phone swapped and notice if the fresher battery helps or is it just a symptom of it "can't" handle the newer OS properly? Any feedback would be appreciated. Hopefully it helps us both out. Didn't mean to hijack the thread!
Click to expand...
Click to collapse
So I promise it's not the battery because I had it factory replaced by Samsung. To answer your question, yeah you have to send it in. With the waterproofing they have to do it at a repair center. However, for me it was 100% worth it. I think I was without the phone for about 10 days. But having a brand new battery life was incredible.
Also, as I was working with the phone slow for a while, it immediately and dramatically became quick after device maintenance killed that process. But a few months later, I'm back to suuuuper slow.
The S7 is getting old. Old things slow down. It's planned obsolescence. I've gotten to the point of turning notifications off for all apps and only using badge numbers to tell me when to check something. I also use do not disturb a lot when gaming instead of game tools because game tools is another app but do not disturb is more of an internal process. As soon as my taxes come back I'm probably going to get a S8+