Wake up lag on latest nougat 7.0 what is the cause? - Galaxy S6 Edge+ Q&A, Help & Troubleshooting

I have this annoying lag when i try to use my s6 edge plus BTU it is the latest firmware.
When screen is off it takes ages to wake up, even after i reloaded rhe firmware with odin it fixes it for about 24 hours then it comes back.
I tried switching to 2.4ghz wifi same issue it seem to slow down whenever it connects to wifi then turns wifi off as i keep it on never.
I used package disabler pro so should be no lag.
Greenify i use.
It started last week after I dropped the phone but it didnt fall frim more than knee height.
What else can it be?
The only thing i done was delete files on it to make more space no other apps downloaded since.
And it used to be fine last week prior.
How can i fix this without factory reset
Because im using an old version business version of package dusabler pro that allows me to disable many packages which are now not allowed so i cant factory reset it under any circumstances.
What else can i try?
I have cleared cache
Rebooted
Closed all apps.
It always creeps up after about 8 hours charging screen off and using.
Could it be a bad sector on the storage that needs fixing?
It is weird how it happens from the time screen is off disconnecting from wifi and reconnectinf it seems like it accumulates the lag.

Related

Wifi issues - maybe TW related

Ever since I installed the Wifi based TW ROM I have had issues with the wifi stopping. The issue continues with the official rom (with root and deoxed). It is set to be on in software but says disconnected. If I reboot device it works fine again.
Anyone else have this issue? I am very close to going back to stock even though I like the new way of doing notifications.
Same problem here. Simple way to solve it to enable and disable Airplane Mode... But yeah.. its really annoying. So any fix would be very helpful.
I've had the same problem recently. Did either of you install the free wifi server app that the Amazon store offered a day or two ago? That's when it seemed to start so I just removed it so see if that fixes my issue... here's hoping!
Same problem here, but it just started the day before yesterday. I've had Touchwiz since a day or two after I bought the device (almost two weeks). Hadn't thought to toggle airplane mode, thanks for that tip. Beats power cycling every morning.
Sent from my GT-P7510 using Tapatalk
I had similar issue with the stock Galaxy rom. Since the TouchWhiz update however, it has been running extremely well.
So after uninstalling the WiFi File Explorer Pro my WiFi has worked fine without any connection issues. Just like before and after TW. I also had a weird issue that wouldn't recognize finger presses on the lockscreen after waking up once every 10 to 20 times.
If you installed this app or something similar it might be worth a shot to remove it.

mm-qcamera-daemon bug

This morning I noticed my phone getting very hot in my pocket. A quick check of gSam showed the phone temp at 105°. Battery had dropped from 100% to 60% in under two hours with no use. When I checked app usage mm-camera-daemon was running at 89% usage. I booted to recovery and wiped cache and that stopped it. Did a Google search and found that this was a bug with 4.4.2 and was fixed with 4.4.4. Now there are lots of posts on various forums about people having this problem with 5.0. It is the process that runs the camera and it apparently gets stuck running after using the camera or if any camera related apps are used. Clearing the cache fixes it, but I'm reading in different places that it may start again within a few hours. Just wondering if anyone else here has experienced this yet.
newmanx4 said:
This morning I noticed my phone getting very hot in my pocket. A quick check of gSam showed the phone temp at 105°. Battery had dropped from 100% to 60% in under two hours with no use. When I checked app usage mm-camera-daemon was running at 89% usage. I booted to recovery and wiped cache and that stopped it. Did a Google search and found that this was a bug with 4.4.2 and was fixed with 4.4.4. Now there are lots of posts on various forums about people having this problem with 5.0. It is the process that runs the camera and it apparently gets stuck running after using the camera or if any camera related apps are used. Clearing the cache fixes it, but I'm reading in different places that it may start again within a few hours. Just wondering if anyone else here has experienced this yet.
Click to expand...
Click to collapse
I would suggest checking to make sure you have Smart Stay turned off; it's not a complete solution but it eliminates a way the camera can turn on without you having directly initiated it. Since Smart Stay uses the camera to check if you are still looking at the phone before turning the screen off, it can cause the daemon to start even without a person realizing it leading to the overheating and power drain.
The morning this happened I booted to recovery and wiped the cache partition then left the phone off until it cooled down. I have not had this happen again since.
This is now happening 9 out of 10 times I open the camera or the gallery. With the original Lollipop update it was sporadic, but since OC4 it has become a regular problem for me. Is anyone else experiencing this?
newmanx4 said:
This is now happening 9 out of 10 times I open the camera or the gallery. With the original Lollipop update it was sporadic, but since OC4 it has become a regular problem for me. Is anyone else experiencing this?
Click to expand...
Click to collapse
It isn't just a lollipop problem. I'm on 4.4.4 NI2 and it happened to me. I deleted apps and still couldn't get it fixed. I had to go back to an earlier backup to get rid of it. Never figured it out.
Strange I never experienced this on KK. A cache wipe always fixes it but it's very annoying.
Probable Solution!
I had same problem on towelrooted 4.4.2 NE9 stock ROM. You can try this. I removed skype, rebooted and re-installed it again. And I never had this battery drain issue because of this again.

HELP REQ - Stock Lollipop Note 3 N9005 - Random Reboots/Wifi-BT Clashes

Hi all,
Having a problem here.
Had my N9005 for about 18 months, never really had any problems with it - or rather, never really required anything of it which might manifest any problems.
I've always used Stock ROM's, soft-rooted.
Never triggered KNOX.
I'm currently running Stock Lollipop (latest Switzerland Open). Everything I'm about to elaborate is also the same using Stock Lollipop (latest UK Open).
I'm rooted on Lollipop using the method compiled by The TAMAS on XDADEV.
I root because my phone is work-critical, and so I use Titanium Backup to keep my data/calls/APN/SMS backed up and to make restoring easy, as well as to disable stock bloatware etc.
The problem may have pre-existed in pre-Lollipop ROM's, but the sequence of changes which caused it to be manifested included my need to update to Lollipop, about 5/6 months back.
THE PROBLEM - First and foremost, the damn phone reboots randomly. I become aware of it because it will vibrate for startup and play the Samsung startup tone and splash screen before booting to normal functionality. It can do this day or night, maybe 3-4 times a day. I have no error messages or warnings, it's done it while in my hand, while plugged in charging, while out and about, in the car, on wifi, on data. MOST times it reboots. SOME times it just shuts off and I don't realise it's off until I go to use it, or get a call on a second phone to ask why I'm not responding to calls or messages.
When it reboots itself, if I go to the Samsung Battery control panel pane and take a look at the battery chart it will show a gap which is longer than the time it took to reboot, and a shift in the battery meter level.
But, that's not the only possible symptom or problem with the phone.
I've noticed also that my WIFI does a lot of crapping out, or slowing to a crawl, even on my home AP. I've reset AP's, reset networks, reset the phone, forgotten and then reattached the AP in WiFi Settings. So I downloaded the Ookla Speedtest App, to see this issue in black and white, and sure enough, even though any other Android or iOS or Windows or OSX device in my place can connect via Wireless AP to my fibre connection and get great consistent throughput, the Note 3 can often appear crippled...
At it's best, it responds to ping quickly on the Speedtest app, and leaps up to the 30-40Mbps range with consistency for download, and up to 17-20Mbps for upload. This is the least I would expect it to do, my target standard.
At it's worst (which can be 'most of the time') it responds slowly to ping, and either struggles to get over 250Kbps download and maybe a crazy Meg or two for upload, consistently, a slow grind; or it may oscillate extremely wildly between slow and high speeds before eventually settling to unacceptably low transfer rates.
Up to press, I've been trying to chase these problems in isolation, believing them to be unconnected.
No success.
I've reflashed several times. I've Factory Reset. I've wiped data and cache. I've reinstalled and restored from Titanium. I've reinstalled and restored nothing but my SMS's and Call Logs. I've reduced my installed apps to bare minimums. I've tried it with a MicroSD installed, and without. I've bought another battery and replaced it. I've tried it in its case and without its case.
Then I started thinking that the problems were all the same thing, and stemming from the same root.
It suddenly occurred to me that my use of the phone changed significantly at the same time as I moved to Lollipop.
I need to be on Lollipop because apps and hardware that are critical to me are Lollipop dependent.
All at the same time, I began using a Moto360, a Bluetooth Receipt Printer and a Bluetooth Credit Card Reader, all of which are deficient in functionality or in some way hamstrung by not using Lollipop.
So I had gone from occasional BT user (maybe PlayerPro plus a BT link to headphones or my stereo occasionally; when needed, BT speakerphone in car) who usually turned BT off manually to preserve battery life, to a constantly connected BT user...
So I went back to Speedtest app, and tried to test the WIFI connection again. Sure enough, it was pitiful. Then I simply disabled BT on the N9005 and ran the test again, and had full 'through the roof' speed ratings.
I've tried this back and forth hundreds of times now, and it is predictable and established. BT is somehow crippling WIFI on my N9005.
I've tried running the phone on either wifi or data only, with BT off, and had a couple of days use at a time without any restarts. Put BT back on permanently, and the restarts resume within hours.
I'll be honest, I've even been cursing and swearing at my BT devices, because BT sometimes struggles to even maintain a continuous connection. I get vibrations all the time on my Moto360 indicating that the phone, which is on my person, has disconnected from the watch again, perhaps just for moments, sometimes for minutes, resulting in the watch eating battery life, trying to get reconnected.
I'm convinced now that all these things are related, and the problem lies somewhere in the interaction between BT and WIFI in my N9005.
It seems likely that I never noticed the problem before because I never required continuous BT connection before the point where I installed Lollipop.
Downgrading the ROM isn't an option. Leaving BT off isn't an option (nor should they have to be, on an 18 month old £600 smartphone).
Does anyone else have experience of this? Has anyone else had problems that they now suspect might be this same problem? Does anyone understand what's going on hardware/software wise, or have experience of a solution to these issues?
I'd appreciate your input urgently, even if only to affirm that I need to go to the inconvenience of temporarily buying another phone to replace this, while I send this away for a warranty repair.
Is this even a recognised hardware fault, or would I just get back an identical unit which is crippled from being able to perform as I expect it?
Please help.

T-mobile S7Edge stock, after Sept. 1st Security patch update, battery drain

I do not know whether it is coincidence, but I updated couple of days ago and all of sudden, starting this morning, the Android system is draining battery at alarming rate. It does appear that this happens only when I am on cellular network and not on wifi.
I have been off the charger about 2 hours and my battery is down to about 50% already.
The phone is running very hot. (I took it out of the case) It does not appear that turning off cellular data affects this at all.
Rebooted the phone couple of times to no avail, at this point, I am considering factory reset of the phone, but would like to get some opinions on what may be the cause.
I saw the thread on the "android system battery drain", but this does not appear to be related to what majority of people are reporting as this slows down the phone significantly enough that the phone is almost unusable at this point.
Cleared cache but don't think is helping. That said, when I was trying to get to the recovery, the system said "Installing update" and then "No command", before getting me to the cache, I am wondering whether the "update" did not clean up itself...
Thanks.
EDIT: Looks like the system cache clearing did help after all.... System appear to be working normally now. Will have to see..
Ok, well, back to the drawing board. The phone behaved ok all day long. Came home, I did 2 things, turn on wifi, and then turned on bluetooth to test out a headphone and then shut off the bluetooth. High battery drain again. Phone got hot and everything is VERY sluggish.
Shut down, cleared the cache again. Will see what happened.
Is there a way to go BACK to previous stock ROM WITHOUT factory reset?
Found out the issue, it was Oculus update which caused the issue. Looks like the bug caused the "Oculus Room" to install it self over and over again. I manually ran the Oculus home app, and it prompted me to update, which I did and it appear to have fixed the issue.
Flash your decice with version from sammobile.com
I have this exact same problem, posted about it yesterday but had no help.
I don't have Oculus on my phone though. But phone behaves for a most of the day, then does as the OP describes, still cant see why, but its only since the update.
Steve

Getting stuck on boot screen every month

Since about July 2017 my G-900v has gone bad and gets stuck on the Verizon loading screen. I am talking this has been at least 4 times. This last time yesterday a factory reset would not get it going again and I had to find a firmware (G900VVRS2DQA1_G900VVZW2DQA1_G900VVRS2DQA1_HOME) and load that with Odin. Admittedly it really seems to be working better than before and I think it was running the previous firmware when it was freezing up. Was there known issues with the other firmware? I am not certain what the build version was.
I have 2 batteries and have tried both during the freeze up. Neither make a difference. And the freeze up always happens at night during charging. After the update earlier this year it was prone to sudden reboots and applications stopped working errors. Also the emoji icons had stopped working and would cause keyboard crashes on all keyboard apps. Can having a large amount of photos saved on the SD card lead to such issues?
What is the best known way to back up and restore my handset if this continues to happen? I am tired of having to DL and customize my apps every time this happens.
Some but not all of my apps
Go SMS Pro
My Work Clock
Instagram
FB Messenger
Facebook
SnapChat
C4Yourself
DoubleMaps
Beautiful Widgets
SeekDroid
Western Union
LookOut Mobile
Screen Off Lock
Removed
WiFi Advisor
Network Analyzer
AVG
What default apps should I disable?
Thanks for any help or insight on this.
Do you have the link to the firmware you used? Mine is stuck on the Verizon logo screen after doing a factory reset and I want to flash a good stock firmware on it via Odin.
Pretty sure it was from here.
https://samsung-firmware.org/model/SM-G900V/region/VZW/
I followed the guide here http://www.**********.com/install-stock-android-6-0-1-marshmallow-on-verizon-galaxy-s5-sm-g900v/
There WERE bugs in the Samsung keyboard back in the day, that have supposedly been patched up in recent times. Depending on the age of the installed firmware, it could be an issue.

Categories

Resources