Related
We have yet another possible remedy for those of us experiencing wakelock/battery drain issues still. Read about it from someone on the bugtracker.
Try leaving your GPS set to on, rather than toggling it. I switched mine on this morning (yesterday, now) and now for the first time in over a month I have now had my Evo unplugged for 13 hours and still have 31% battery remaining after moderate usage today.
It seems that CM may be managing it better or something (someone will have to look into it if this proves successful for more people)
Give it a try and post your results here!
I have never turned off my GPS once since I had the phone in like 6 months. GPS is not the issue for me.
I've always found that about 2 weeks after flashing a new ROM, I start getting wake lock issues which I can never track down. They always resolved themselves after I flash a new ROM, but reappear about 2 weeks later again.
Rinse and Repeat.
The GPS-on fix makes it look like there's an issue with the network location. This would tie in to earlier reports. In this case, it would be best to turn off "Use wireless networks" from Settings > Locations and Security until this bug is fixed.
The two most common causes mentioned so far are network location issues and SMD_RPCCALL wakelock issues.
Click to expand...
Click to collapse
Taken from bugtracker
What PRI are you guys running? This is likely unrelated, but PRI 1.90 seems to cause wake lock (100% wake) for some.
Edit: BTW, for every post I read, reverting to 1.77 PRI solves the 100% wake issue.
Not sure, haven't flashed a sense ROM in awhile... I'll try to check when I get a chance
kevinbear said:
We have yet another possible remedy for those of us experiencing wakelock/battery drain issues still. Read about it from someone on the bugtracker.
Try leaving your GPS set to on, rather than toggling it. I switched mine on this morning (yesterday, now) and now for the first time in over a month I have now had my Evo unplugged for 13 hours and still have 31% battery remaining after moderate usage today.
It seems that CM may be managing it better or something (someone will have to look into it if this proves successful for more people)
Give it a try and post your results here!
Click to expand...
Click to collapse
You do realize that this makes no sense, don't you?
Not if something keeps trying to call on the GPS when it's off causing some sort of wakelock while it loops trying to get a GPS fix. Leaving it on allows CM6 to manage it or something. But it does seem to help.
nabbed said:
You do realize that this makes no sense, don't you?
Click to expand...
Click to collapse
You know there's a well-known bug with Sense ROMs and the HTC 4G widget that forces 4g into a scan loop when you try to toggle 4G off that absolutely _kills_ the battery in a few hours...
I've not tested his suggestion, but the community has found stranger things before.
Side note: before two days ago I _never_ ran wifi on ... but also never ran into a wakelock ... I've left my wifi on just over the weekend as I was playing with something completely unrelated ... maybe with your suggestion Ill just continue to leave it up and see if i run into this wake-lock issue.
I've never turned gps off, it's been on since I got the phone this summer. I think it's funny that one of the settings we see for gps says something about "may cause excessive use of batter" or whatever and fact is - gps on 100% of the time doesn't do ANYthing until an app needs it. It's not used at all. No gps icon, no nothing.
The 4g problem is a PITA but it doesn't drain the battery within a few hours. It draws a little ut unless someone had shown me and proven it to me.....I wouldn't have known. And even now that I do know and I know to reboot my phone after I use 4g, I haven't noticed a big gain in battery life. Leaving 4g ON after you leave a 4g area or no longer need it WILL drain your battery within a few hours. fact
So I can't post in the Dev Forums so I thought I might create a thread here about the bugs found in floyo v0.15, and maybe somebody could help me on these problems.
1. The auto brightness works but it sometimes results in my screen completly fading black in 2~3 seconds. And then the phone will remain unresponsive for 20 or so seconds.
2.The SD-Card safe to remove reboot. Actually this is not a problem but What I want to say is in the time I've been using this rom I have only had two of these, which is really impressive compared to what I saw in the Dev Thread. All 2 occurred when I had about 10~15% power left. I don't think that is a coincidence so maybe someone could look into that and probably solve it.
3.Not a problem, I just want to say that, battery usage is superb.
4.I had a bit of a problem with the Google PINYIN IME, it would be disabled every time I restarted.I moved it back to phone storage and after one more problem it solved itself.
5.Compass crashes and results in reboot.
6.With PowerAmp and Default music player, the volume keys on the side do not work while screen is off.
7.The camera button is disabled.
That's all for right now.
8. can´t play .avi files with Rock player.
rock player really sucks on this rom
@UAL4588
dude somewhere in dev forums i read that there is a market app for camera. did u tried to use that one?? sorry forgot the name..
if you face any other issues please do mention it
*on the verge of installing floyo 0.15*
installed floyo 0.15 & ran quadrant, score 1070 , cpu 3389, memory 834
Woot, my first post. XD
I've been following racht's work, updating once I deem the ROM stable enough.
About the re-start thing. Yes, it's annoying. But I think it only happens when your system tries to close Root explorer. I'm guessing you're using some type of app killer. At times like these, I try to keep my phone as clean as possible, only installing apps that I need since lots of programs usually ends up messing with non-stable ROMs.
Auto brightness works fine on me. Not perfect but my phone doesn't freeze.
BuG: When battery level is at 10%, auto-brightness doesn't work if you put your phone to sleep. When you unlock it, brightness will be near the maximum level. To fix this, I just re-cycle through the brightness setting in the PowerWidget to quickly go to dim.
The camera here is definitely better than the stock one that Sony gave us. But I'd really want to be able to record videos.
I wonder why the camera button doesn't work to get pictures...
Oh and... Facebook crashes for me. I reinstalled but still, it crashed.
...
Hopefully, racht would be done soon. I'm checking on his thread everyday now. Support him, everyone. XD
fb work fine for me in 0.15 , but I want to remove some of the apps which comes pre-installed with floyo 0.15, like i dont want to keep the skype, but when i removed it with root uninstaller it showed up like a .com.skype...... file in the apps menu, though upon taping on it doesn't works.
Try removing it using Titanium Back-up. Worked for me.
Oh, and some apps leave those things. Check the filesize if it's 0 byte.
If it is, it should be safe to delete.
does ever try to wipe the data first? the Fb app wouldn't be crashed if the data wipe first(factory format)..fb app runs ok for me
kuwl
just use latest j room. first stable gbread on my x8. kuwl
Will switch to J006 in a few days. Jerpelea said there are still s few bugs that he forgot to take care of (like the > in the proximity sensor code)
They're so close!!
Sent from my X8 using XDA App
found some issues in racht's floyo 0.15, as im unable to detect mobile network through the wireless & network > mobile networks menu. My phone does connects to my operator network & it runs fine, but i can't manually search for a network operators available, it only displays an error as "error while searching for networks"
also when my phone gets starts up if i kept it idle then it gets restarted & thus it gets into a loop
anyone has faced these issues yet??
hotdude2411 said:
found some issues in racht's floyo 0.15, as im unable to detect mobile network through the wireless & network > mobile networks menu. My phone does connects to my operator network & it runs fine, but i can't manually search for a network operators available, it only displays an error as "error while searching for networks"
also when my phone gets starts up if i kept it idle then it gets restarted & thus it gets into a loop
anyone has faced these issues yet??
Click to expand...
Click to collapse
I didn't have any problems with Wi-Fi detection when I was using Floyo. Try full-wipe and re-install ROM. Though I think you should just update to racht's Gingerbread.
About the reboot loop, that's caused by xrecovery. There's a fix somewhere here in the forums but I suggest just updating to Gingerbread since racht took care of that already.
Sent from my X8 using XDA App
Not sure how to search on the XDA app, so please forgive me if this is already a topic... does anyone have any tips/tricks for avoiding the Sleep Of Death?
-XDA Premium on CM7 Nook Color
What version CM7 are you on?
Latest SOD fixes were put into a kernel which is available as separate zip but have not made it into a nightly build as the build has not been working since mid November.
You may be able to use the kernel update if you are on a fairly recent version or you could switch to the KANG MiRaGe ROM which does include the kernel fix together with other improvements which have not made it into a nightly. Look for the main MiRaGe thread in the development forum.
Other than that before applying this kernel fix people were using various techniques for switching wifi off rapidly when suspending which seemed to be a work-around.
I haven't had a SOD since using the new kernel when it first appeared and as now as embodied in MiRaGe.
I'm on cm7.1.0, I don't get SOD all the time just on occasion without pattern
-XDA Premium on CM7 Nook Color
Widgets...
Don't use Beautiful Widgets. That causes SoD's. Other widgets may cause the same problem.
I have found that every widget that has weather causes SOD for me. All others are okay.
Sent from my NexusHD2 using xda premium
I had to switch ROM's from MIUI to Phiremod to get this to stop. Works fine now even with Beautiful Weather Widget active.
The KANG ROM you describe is the one I have been on since it was introduced. I had the SOD fix but it still occured albeit infrequently. My "fix" is to just shut my Nook down every night. I haven't had one since.
Setting wifi to shut off when screen goes off also works for me (the issue seems to be wifi related). You can also use tasker to shut wifi off when the screen turns off.
Both beautiful widgets and the go weather widgets have caused the sleep of death for me. Without any widgets, my Nook would be up for weeks at a time.
stephen_liu said:
Setting wifi to shut off when screen goes off also works for me (the issue seems to be wifi related). You can also use tasker to shut wifi off when the screen turns off.
Both beautiful widgets and the go weather widgets have caused the sleep of death for me. Without any widgets, my Nook would be up for weeks at a time.
Click to expand...
Click to collapse
Indeed the tasker wifi fix worked for me
-XDA Premium on CM7 Nook Color
vessamj, could you explain what you did with Tasker to prevent SOD?
Quick Tasker fix for SOD
Thomas Droid said:
vessamj, could you explain what you did with Tasker to prevent SOD?
Click to expand...
Click to collapse
Certainly...
I'm assuming you have a basic understanding of how to use Tasker, if this is not so please let me know and I'll be more in-depth. I created a profile named WIFISLEEP with the condition being "Display Off". The first step of the internal task is to wait 5 minutes, with the "IF" box checked and the "IF" condition reading "%SCREEN ~ off". The second step is to set Wifi to off, with the same "IF" condition as the first step. The third step is to play a notification sound (not required, but nice to be assured that your profile actually executes), with the same "IF" condition as the first two steps. I already had a "Display On" profile (for setting the CPU governor and speed), so I just added the next part to the pre-existing profile. If you don't already have such profiles you can just create another profile (named something like "Display On"). The condition, of course, being "Display On", and the first task being "WiFi set On" with the "IF" condition being "%SCREEN ~ on". The second task being "WiFi Net Action Reconnect", with the same "IF" condition as the first task. Not only does this fix my SOD problems, but it will also save you quite a bit of battery when not in use for long periods of time. There will be a slight (10-20 sec.) delay waiting for the WiFi to reconnect after you turn the screen on (as long as it's been more than 5 min of course), but it's definitely worth it. The reason I have a 5 minute wait is so that downloads can finish before they are cut off, you can set the wait time longer if your downloading times take longer. Overall, this did the trick for me on SOD.
*EDIT* I did also get ahold of a much better WiFi management application called Green Power. Instead of having Tasker turn off the WiFi after 5 minutes of the screen being off no matter what, Green Power throws in a few more conditions to look for. Through Green Power I have it set to turn off the WiFi after 20sec of the screen being off IF WiFi traffic is at 1Kb or less. If it is not at 1Kb or less, the app will re-check the traffic every 10sec until it is at or below that level, then shut it off. Also, while the display is off, Green Power will re-enable the Wifi for 2min every 30min to allow data sync to occur. When the screen is turned on, WiFi will be re-enabled automatically. However, if the device can't successfully connect (after 30sec) OR if the strength at connection is less than 20% signal, the WiFi will be temporarily disabled so that there is no battery wasted continually trying to connect/stay connected. This setup is perfect for finishing a download after the screen goes off and then putting the WiFi to sleep, and quickly giving up on the reconnect if there is low/no signal and trying again later. This also fixes the SOD for me, with better overall management than what Tasker can provide as far as WiFi is concerned.
Hey guys, just wanted to post what I used to fix my problems related to SoD.
I was getting SoD all the time with any ROM that I used, no matter 7.1.0 or 7.2. So recently i started fresh on a 7.1.0 stable rom and moved the ROM from SD to EMMC, but the problems still persisted.
After seeing this thread, it gave me some insight regarding the root problem... For me, it seemed that wifi being on when the screen was off was the culprit. So I downloaded the free app called "Easy Battery Saver+ Task Killer" found here:
https://market.android.com/details?...SwxLG51bGwsImNvbS5lYXN5LmJhdHRlcnkuc2F2ZXIiXQ..
I set it to the "General Power Saving Mode" profile, which basically turns off the wifi whenever the screen is off.
That seems to have fixed the problem, now I never get a SoD! So I recommend giving it a try!
If you are interested in my opinion...
switch81 said:
Hey guys, just wanted to post what I used to fix my problems related to SoD.
I was getting SoD all the time with any ROM that I used, no matter 7.1.0 or 7.2. So recently i started fresh on a 7.1.0 stable rom and moved the ROM from SD to EMMC, but the problems still persisted.
After seeing this thread, it gave me some insight regarding the root problem... For me, it seemed that wifi being on when the screen was off was the culprit. So I downloaded the free app called "Easy Battery Saver+ Task Killer" found here:
https://market.android.com/details?...SwxLG51bGwsImNvbS5lYXN5LmJhdHRlcnkuc2F2ZXIiXQ..
I set it to the "General Power Saving Mode" profile, which basically turns off the wifi whenever the screen is off.
That seems to have fixed the problem, now I never get a SoD! So I recommend giving it a try!
Click to expand...
Click to collapse
The problems I see here are that there is no WiFi traffic check (at least from what you've explained) before it kills the WiFi, and the Task Killer part. Task Killers actually cause more battery usage because the Android System will have to use more battery to re-start many of the killed processes. This is because the OS is programmed to keep some/most of those background processes running and will continually re-start them no matter how many times a task-killer stops them. It is better to have apps such as Ram Manager Pro (http://forum.xda-developers.com/showthread.php?t=1111145) or V6 SuperCharger script (http://forum.xda-developers.com/showthread.php?t=991276) to optimize your RAM for much better smoothness and crisp response, with much better battery savings. Combine one (or both depending on what parts you use for different activities) with Green Power app, which will give a hand-full of extra conditions to look for before turning off the WiFi at screen off and thus fixing your SOD and providing better performance with extra battery savings. I hope this helps!
Now that I've got the Moto X Pure Edition activated, I've been able to work out some of the kinks inherent using it as a daily driver. One noteworthy issue that remains is an odd bug where the device will completely lose connection to the Internet on both a WiFi and cellular data connection, usually after transitioning between types of connections. When this happens, an exclamation point is displayed next to the icon representing whichever connection is currently active and nothing is able to transmit data to or from the Internet or even my local network.
Rebooting the device always fixes the problem, but this issue is materializing a bit too often for my liking, which is usually once every time that I return to a WiFi network after being disconnected from one for some time (more testing may have to be done to confirm exactly what triggers it).
The device is running the stock rom (rooted) and the stock kernel along with the usual tweaks (ad-blocking, Xposed framework, audio fixes, etc.). Anybody seen this before or know what might be causing it?
UPDATE (3/1/2017)
Figured it out! The problem appears to have been caused by my failure to whitelist certain applications in PowerNap. After following the instructions found in the Moto X Pure Edition power optimization thread, the problem appears to have vanished. I don't know if it was the Google Services Framework, JavaTcmdHelper, Android System, or some combination of those that needed to be whitelisted, but the problem has vanished. At least one of those must be responsible for verifying the validity of an Internet connection in sleep mode, which would cause the device to become confused when it would wake up with a different connection that it hadn't verified (that's my theory at least).
At any rate, it is no longer an issue.
Update (Later on 3/1/2017)
Well, it looks like it might not be fixed so well after all. A couple hours after arriving home today, I went to use the device and saw the dreaded "!" next to the network indicator. Still, two days is longer than it's ever lasted before. I've cleared the cache and dalvik/ART cache to see if something in there might be gumming it up and will add another post to this thread if the problem returns.
Still an issue
Looks like it might not be fixed after all. I lost connection again the other day in a parking lot and once more today after getting home. Any ideas as to what could be causing this?
I just recently got my x pure. I've seen this issue on mine too.
Another one!
inkdaddy66 said:
I just recently got my x pure. I've seen this issue on mine too.
Click to expand...
Click to collapse
Interesting. Are you running the stock Rom? Rooted? Amplify/Greenify/PowerNap?
Bill720 said:
Interesting. Are you running the stock Rom? Rooted? Amplify/Greenify/PowerNap?
Click to expand...
Click to collapse
I'm unlocked and rooted. Running validus 7.1.1 ROM.
does your configuration look anything like this?
inkdaddy66 said:
I'm unlocked and rooted. Running validus 7.1.1 ROM.
Click to expand...
Click to collapse
That too is interesting. I'm running the stock Rom, (rooted) so we can probably eliminate that as a potential cause. Given how little reference there is to this on the web at large, the problem is probably caused by a common app or setting (or some kind of unfortunate combination) running on both of our phones.
All we need to do is figure out what kind of "unusual" stuff our devices have in common. I'll rattle off a list of software and settings that might be out of the ordinary or network-related; you tell me if you're running anything like it on your phone.
AdFree
A.R.I.S.E. audio
FolderSync
Ice Box (Motorola Update Service is the only frozen app)
TOTAL Wireless My Account App
Pebble, MyTracks, and Pebble MyTracks
SlingPlayer (this one sometimes wakelocks)
Titanium backup (I tried restoring some WiFi access points once, but it didn't work)
Xposed Framework with Amplify, Greenify, and Power Nap installed and configured as instructed in the Moto X Pure Edition battery life guide thread OP. I've also got MinMinGuard and YouTube AdAway.
As far as settings go, I've not got much in the way of unusual configurations. I enabled the system UI tuner to get the battery percentage and the extended developer options to try out multi-window, (and to change the animation scales to .5X) but everything in there is still pretty much stock.
Does your configuration have anything in common with mine?
Close, but no cigar
It got almost 8 days this time before it happened again. I thought that maybe switching to the legacy DHCP client had done the trick, but that was apparently not the case. Any ideas as to what could be causing the issue or how to fix it?
Or, if you're having the same problem, can you look at my list in the previous post and tell me if any of the software or settings are similar so that we can narrow down the cause?
I have had this problem appear about three times over my 13 months of ownership and all three times was when my bootloader was still locked (obviously running stock not rooted). Never found a solution except to reboot.i only unlocked and rooted my device about a month ago.
Anything familiar?
aybarrap1 said:
I have had this problem appear about three times over my 13 months of ownership and all three times was when my bootloader was still locked (obviously running stock not rooted). Never found a solution except to reboot.i only unlocked and rooted my device about a month ago.
Click to expand...
Click to collapse
Interesting. Between that, my findings, and the fact that @inkdaddy66 was having the problem on a non-Motorola Rom, I want to think that we can eliminate the Rom software as a cause. Did you see any familiar software on my "potential troublemakers" list up in post 6? I'm thinking that if we can find a common program or workflow, then we'll be able to narrow down the cause of the problem.
In the meantime, I'll try posting in the general Android troubleshooting forum here on XDA and see if anybody there has seen the problem or has any troubleshooting tips.
Bill720 said:
Interesting. Between that, my findings, and the fact that @inkdaddy66 was having the problem on a non-Motorola Rom, I want to think that we can eliminate the Rom software as a cause. Did you see any familiar software on my "potential troublemakers" list up in post 6? I'm thinking that if we can find a common program or workflow, then we'll be able to narrow down the cause of the problem.
In the meantime, I'll try posting in the general Android troubleshooting forum here on XDA and see if anybody there has seen the problem or has any troubleshooting tips.
Click to expand...
Click to collapse
Nothing used from your list except system UI tuner when I experienced the problems. That would leave either a ROM and/or hardware issue IMO.
Cause and effect differential diagnosis
aybarrap1 said:
Nothing used from your list except system UI tuner when I experienced the problems. That would leave either a ROM and/or hardware issue IMO.
Click to expand...
Click to collapse
Hmmm... That's also interesting, but I just don't see how system UI tuner could be harming anything. Do you have any other apps or settings at all that you think could be causing the issue?
If this were anything other than my primary, I'd hard reset and troubleshoot that way, but I don't exactly have the time to pull the rug out of an otherwise-working setup right now, so this is going to have to be done the hard way (or, in the case of hardware glitch, lived with).
At any rate, I discovered a new symptom earlier in the week. This time, Internet connection was lost, but only for WiFi, so the connection would actually fall back to Cellular and still continue to work. As before, toggling the connection had no effect, but rebooting the device "fixed" it. I thought maybe it was a fluke, since we'd had an AP hiccup over the weekend, (I refuse to reboot that thing because I'm going for an uptime record) but it happened again on Wednesday, so I'm not sure what to make of it.
Side-issue aside, I'm beginning to wonder if it's some kind of combination of network behavior and usage pattern that brings the issue about. It seems like if I stay within range of the WiFi network, no issue develops, but if I move out of its coverage and don't touch the phone for a while, that allows for ideal conditions under which to replicate the problem (sometimes). I haven't nailed down a consistent pattern yet, but the problem does emerge more often when I'm returning home than at other times. Any thoughts?
Update (3/24/2017; 12:32PM)
Scratch that last part about the issue only being triggered upon "arriving home." The problem happened again this morning, in the same general area. First, no WiFI, then, after resetting the connections, no cellular either. I captured a LogCat before rebooting this time though. Anyone want to take a crack at sifting through that to see if it offers any clues?
I lose cellular data, from time to time, I don't kow if I'm losing WiFi capability also, because I'm on the road when this happens.
It takes a reboot or switching in and out of airplane mode to regain data.
I have had this happen on TruPureXMM ROM and stock-rooted Marshmallow.
I have not spent much time on stock-unrooted, so i don't know if it would happen then, also.
Possible fix
Just to follow up on this again, I have finally reached the eighth day of uptime without the problem materializing, which is the longest that I was able to go before without it happening. This time, I went in to the developer options and disabled "Cellular data always active." I'd give it another couple days to know for sure, but if this sticks, then I think we might've found the fix!
pizza_pablo said:
I lose cellular data, from time to time, I don't kow if I'm losing WiFi capability also, because I'm on the road when this happens.
It takes a reboot or switching in and out of airplane mode to regain data.
I have had this happen on TruPureXMM ROM and stock-rooted Marshmallow.
I have not spent much time on stock-unrooted, so i don't know if it would happen then, also.
Click to expand...
Click to collapse
If your trouble is isolated to just one connection and/or cycling the connection brings it back, then the issue you are experiencing is unrelated to the one described in this thread.
Bill720 said:
Just to follow up on this again, I have finally reached the eighth day of uptime without the problem materializing, which is the longest that I was able to go before without it happening. This time, I went in to the developer options and disabled "Cellular data always active." I'd give it another couple days to know for sure, but if this sticks, then I think we might've found the fix!
If your trouble is isolated to just one connection and/or cycling the connection brings it back, then the issue you are experiencing is unrelated to the one described in this thread.
Click to expand...
Click to collapse
Cellular data always active should never be on (it's disabled in stock rom), except if you have VoLTE only with no fallback to 3G or 2G (Jio is the only provider that comes to mind, but this phone doesn't support their service anyway) or otherwise unusual scenarios I can't really think of.
Huh, and CELLULAR DATA ALWAYS ACTIVE (for faster network switching) sounds like such a good thing.
Mine was selected on.
My loss of data happens in the same spot, usually, but is not leaving wifi. Perhaps it is a tower to tower handoff spot.
I turned it off. Time will tell.
Thanks, fellas!
pizza_pablo said:
Huh, and CELLULAR DATA ALWAYS ACTIVE (for faster network switching) sounds like such a good thing.
Mine was selected on.
My loss of data happens in the same spot, usually, but is not leaving wifi. Perhaps it is a tower to tower handoff spot.
I turned it off. Time will tell.
Thanks, fellas!
Click to expand...
Click to collapse
Always on is not necessarily a good thing. Reality is that when you lose or turn off WiFi, mobile data should only be delayed only by a second or two. There is no real benefit to having it on except for maybe VOLTE.
pizza_pablo said:
Huh, and CELLULAR DATA ALWAYS ACTIVE (for faster network switching) sounds like such a good thing.
Mine was selected on.
My loss of data happens in the same spot, usually, but is not leaving wifi. Perhaps it is a tower to tower handoff spot.
I turned it off. Time will tell.
Thanks, fellas!
Click to expand...
Click to collapse
Actually, it's a battery killer more than anything else... It keeps cellular data active even when on WiFi.
It is possible it's a tower thing though. I have noticed at this one hotel I stay at frequently people tell me they call and it rings or just goes to voicemail even though I have good signal. After investigating it a bit, I'm in a spot that has nearly identical signal strength from 3 towers and it's a metro area so there are 4+ bands accessible... I've seen times watching LTE Discovery where it keeps switching bands and towers for 30 to 120 seconds or so, like it can't make up it's mind what to talk to because it's confused, then it locks on for a while before it starts it's cycle again. During those cycles I think is when people can't call me, can't really say if it affects internet or not since I tend not to use my phone too much in the evenings when I'm on the road (usually on laptop).
Uptime record, but... it's back
acejavelin said:
Cellular data always active should never be on (it's disabled in stock rom), except if you have VoLTE only with no fallback to 3G or 2G (Jio is the only provider that comes to mind, but this phone doesn't support their service anyway) or otherwise unusual scenarios I can't really think of.
Click to expand...
Click to collapse
Interesting. I thought for sure that I had the default settings checked in there, but maybe I did change it early on and just forgot. Either way, waiting an extra five seconds to establish a data connection isn't that huge of a deal for me, so I'll leave it off anyway in exchange for battery life when the signal's poor.
At any rate, however, the problem has returned. I was just a few hours short of 9 days of uptime and really thought that I was out of the woods with this problem, but it has returned once again upon returning into range of the home access point. Looks like we're back to the drawing board on this one.
pizza_pablo said:
Huh, and CELLULAR DATA ALWAYS ACTIVE (for faster network switching) sounds like such a good thing.
Mine was selected on.
My loss of data happens in the same spot, usually, but is not leaving wifi. Perhaps it is a tower to tower handoff spot.
I turned it off. Time will tell.
Thanks, fellas!
Click to expand...
Click to collapse
So you're having the same problem too? That makes at least four of us now. Do you mind sharing what Rom and flashed tweaks (Xposed Framework, A.R.I.S.E. audio, root, etc.) you're using as well as any unusual software or settings? Anything in common with my list on page 1?
Bill720 said:
So you're having the same problem too? That makes at least four of us now. Do you mind sharing what Rom and flashed tweaks (Xposed Framework, A.R.I.S.E. audio, root, etc.) you're using as well as any unusual software or settings? Anything in common with my list on page 1?
Click to expand...
Click to collapse
I think we've established that my issue is different, but it has occurred on TruPureXMM and stock but rooted Marshmallow, both with Substratum, Xposed (Gravity Box only) and Viper Atmos.
Same as you =Titanium Backup
*another* new strategy (sigh)
For this week's shot in the dark, I'm going to try manually switching WiFi off before I leave anyplace covered by an access point. Since the problem seems to occur most often when connected to WiFi or when connecting to it, maybe this will make some kind of a difference.
pizza_pablo said:
I think we've established that my issue is different, but it has occurred on TruPureXMM and stock but rooted Marshmallow, both with Substratum, Xposed (Gravity Box only) and Viper Atmos.
Same as you =Titanium Backup
Click to expand...
Click to collapse
I see now; my mistake.
Hi,
I've noticed a UI lag when switching between apps or transitioning from an open app to home screen. This didn't happen in the Android 10 beta rom. Anybody have the same issue? I clean flashed the stable android 10.
I can confirm this issue in the stable release. But I would like to add that this lag was already in the beta release and is in my testing not app specific. I would clear the cache and make a reboot.
Go into developer options and disable the three animation types. Everything runs MUCH faster with them off.
Floridaplur said:
Go into developer options and disable the three animation types. Everything runs MUCH faster with them off.
Click to expand...
Click to collapse
I have, and while it does suppress animations, it actually feels less polished. And anyway, it does not resolve the UI lag which is really visible when using th app switcher. It's dropping below like 10fps. As if some gfx acceleration was disabled or the phone was completely overwhelmed
Anyone found a fix? I experience the lag every once in a while, though it's prevalent enough to be annoying.
I am having this literally every time i use the alt-tab like feature. Oneplus managed to **** up the one thing (butter smooth) Google has been bragging about for several versions ???
A simple fix would be toh format device once, as I have clean flashed and I don't face any lags
Dissable ram boost in system settings
fress said:
Dissable ram boost in system settings
Click to expand...
Click to collapse
I'm having random lag too. I'l try to disable RAM boost and is if it helps.
fress said:
Dissable ram boost in system settings
Click to expand...
Click to collapse
doesn't change a thing. (and am wondering it would. This feature is supposed to make smoothness (even) better, not worse)
Turn off auto brightness .. maybe it can help
I have been reading up on the A10 stable release posts and I saw a lot of people mentioning the issue that you are talking about here.
Many of them suggested a full format. So basically setting up your device as a new device.
I cannot confirm if this works for everyone but a lot of people are saying that after a fresh install they are not facing any issues.
All of the points mentioned above are just what I read from xda and op forum posts. I personally have not made the switch yet and probably wont be doing so soon.
Hey guys. I encountered the same problem on my Nokia 9. Not quite sure why this error doesn't get noticed by more people.
I think I fixed it for me though.
In my case it seemed that the OLED always on screen (which shows notifications and the time) was the problem in my case. It would always show that there are notifications even if there weren't any and that started adding up. So while the rest of my phone ran buttery smooth, the notification bar and lockscreen began looking like a Diashow. 2-5 fps sometimes. What I think is happening is that all these notifications are buggy and the always on screen can't get rid of them.
So my fix was turning that off and then restarting my phone. Since that everything runs smooth again.
If there is another thread I should post this to please tell me but I only found this one.
Hope it helped.
maxsak said:
Hey guys. I encountered the same problem on my Nokia 9. Not quite sure why this error doesn't get noticed by more people.
I think I fixed it for me though.
In my case it seemed that the OLED always on screen (which shows notifications and the time) was the problem in my case. It would always show that there are notifications even if there weren't any and that started adding up. So while the rest of my phone ran buttery smooth, the notification bar and lockscreen began looking like a Diashow. 2-5 fps sometimes. What I think is happening is that all these notifications are buggy and the always on screen can't get rid of them.
So my fix was turning that off and then restarting my phone. Since that everything runs smooth again.
If there is another thread I should post this to please tell me but I only found this one.
Hope it helped.
Click to expand...
Click to collapse
I think the issue is just : it's a ****show of awful coding, optimisation and non-existent testing. If manufacturers' programmers put in half the effort debugging their software we as "powerusers" at xda/reddit/... put twisting our brains in and out trying find correlating explanations and workarounds as to why we get UI lags or other absurd bugs (like 5GHz wifi not working anymore) on the 10th ****ing iteration of Android, we wouldn't have all of this. It all boils down to the general idea that because it is consumer grade product, quality check is just a non-subject. Apparent quality is just enough at product launch, and further updates (if they do get round to releasing them) can brake everything without manufacturers being held accountable.
The update showed up on my phone on the 25th, but, I'm NOT updating. 9 is too damn stable for me, & I don't see any "features" in 10 that will benefit me.
After reading all this i am not going to update to 10. Yet happy with 9.17.
Tmob unbranded dual sim op6t.
Narrowed down some parameters
I have the OnePlus 6, and have similar issues, that include swapping apps being slow, but not just the swapping of apps, any app that has typing in it, seems to DIE when I start typing. Maybe this is a google keyboard issue or something? I notice the issue most in the Microsoft Teams mobile app. It also tends to only happen when at least 2 apps are open, if it's on it's own, it seems to do fine.
This might just be coincidence but I went into dev settings and turned on "strict mode" and now I can't get it to lag like it previously did.
I just looked at my running services (dev options > running services) and saw that my Bluetooth was using 2.2GB of ram, and youtube was 1.7GB of that. I toggled bluetooth off, then back on and it reset this. I have not modified the strict mode setting above... still have not had any lag, will update this thread if I do get more lag.
MightySashiman said:
I think the issue is just : it's a ****show of awful coding, optimisation and non-existent testing. If manufacturers' programmers put in half the effort debugging their software we as "powerusers" at xda/reddit/... put twisting our brains in and out trying find correlating explanations and workarounds as to why we get UI lags or other absurd bugs (like 5GHz wifi not working anymore) on the 10th ****ing iteration of Android, we wouldn't have all of this. It all boils down to the general idea that because it is consumer grade product, quality check is just a non-subject. Apparent quality is just enough at product launch, and further updates (if they do get round to releasing them) can brake everything without manufacturers being held accountable.
Click to expand...
Click to collapse
Lagging issue I've seen many reporting in xda on the stock rom OOS 10.3.0. But 5GHz is working as expected. I can confirm it because I'm using 5GHz WiFI now and then
adondriel said:
I have the OnePlus 6, and have similar issues, that include swapping apps being slow, but not just the swapping of apps, any app that has typing in it, seems to DIE when I start typing. Maybe this is a google keyboard issue or something? I notice the issue most in the Microsoft Teams mobile app. It also tends to only happen when at least 2 apps are open, if it's on it's own, it seems to do fine.
This might just be coincidence but I went into dev settings and turned on "strict mode" and now I can't get it to lag like it previously did.
I just looked at my running services (dev options > running services) and saw that my Bluetooth was using 2.2GB of ram, and youtube was 1.7GB of that. I toggled bluetooth off, then back on and it reset this. I have not modified the strict mode setting above... still have not had any lag, will update this thread if I do get more lag.
Click to expand...
Click to collapse
After a night/day of normal testing with this, where I would normally have issues, I have not had and of the lag I mentioned above. This seems to have fixed some things. So, I would suggest that you first check to see what running processes are using all the ram, and then turn on strict mode in dev settings, if that doesn't solve your issues. I also have Ram Boost option turned off.
I experience the FPS drop quite often after the update. It's especially noticable when scrolling pages, switching between apps, pulling down the upper panel. The slowness seems to disappear temporarily after closing all apps. But I can't say that some particular app causes the lag.
UPD: A simple test to recreate the problem. I push the square button to switch between apps. Start swiping finger left-right and watch the animation smoothness. After 5-10 seconds comes the wave of low FPS, which lasts for a couple of seconds. Then the process repeats. The slowness doesn't seem to depend on some exact apps that are open.
UPD2: Well, I've just found out that the problem isn't constant throughout the day. There must be some connection to applications running in the background or something like this.