I like this rom for customization, but I noticed the battery drain either.
[DEAD][ROM][8.1.0][UNOFFICIAL][MOTO-MODS][GRIFFIN]Resurrection Remix 6.2.1
- Thread starter Loader009
- Start date
What I found atm:
Seems it does't go to deep sleep mode. The big cores are in DS, but the little cores stay at 300mhz. This at least explains the miserable standby time.
(I'm reading the times with Kernel Adiutor atm.)
But Wakelock detector root doesn't give me any useful information.
Has anyone a good tutorial how to find wakelocks ?
Update 1:
So overnight, when I enabled airplane mode, the device goes into deep sleep and uses only about 3-4% charge over night (8h) - that's ok.
Update 2:
So I did some reserch. The BBS app seems to work nicely https://play.google.com/store/apps/details?id=com.asksven.betterbatterystats
(Here are some guides I've used
https://www.xda-developers.com/stop-wakelocks-android-without-root/
https://www.reddit.com/r/Android/comments/y7j8a/a_n00b_friendly_guide_to_betterbatterystats_please/
https://forum.xda-developers.com/showthread.php?t=1827676
https://www.android-hilfe.de/forum/tools.441/akku-how-to-better-battery-stats-support.501905.html)
and finally gives me some useful data:
The wakelock is caused 100% of the time by wcnss_filter_lock while I don't see some noticeable partial wakelocks.
Then searched for wcnss_filter_lock and landed here https://forum.xda-developers.com/an...drain-late-t3526313/post73792574#post73792574
but it's not that useful, as this app can't handle this type of wackelocks.
Then I found these links
https://plus.google.com/108819680684217517581/posts/SCkvYmd3jCp
https://www.reddit.com/r/LineageOS/comments/851ykg/op3t_kernel_kept_phone_awake_all_night/
which led me to this thread
https://forum.xda-developers.com/moto-x/moto-x-qa/moto-x-xt1060-issues-wifi-bluetooth-t2813308
So this is my current suspect and I'll go though this thread ...
Update 3:
I also went though dmesg logs and found this.
29326.045701] cnss_wlan_pci 0001:01:00.0: Refused to change power state, currently in D3
[29326.105816] cnss_wlan_pci 0001:01:00.0: enabling device (0000 -> 0002)
[29326.121629] cnss: runtime resume status: 0
[29327.057262] cnss: runtime suspend status: 0
[29327.069025] cnss_wlan_pci 0001:01:00.0: Refused to change power state, currently in D3
[29327.130226] cnss_wlan_pci 0001:01:00.0: enabling device (0000 -> 0002)
[29327.138145] cnss: runtime resume status: 0
[29327.975902] cnss: runtime suspend status: 0
[29327.988931] cnss_wlan_pci 0001:01:00.0: Refused to change power state, currently in D3
[29328.049836] cnss_wlan_pci 0001:01:00.0: enabling device (0000 -> 0002)
[29328.058689] R0: [swapper/0][17:07:18.332357] wlan: [0:F :WDA] WOW wakeup host event received (reason: PATTERN_MATCH_FOUND(9)) for vdev 0
[29328.061503] cnss: runtime resume status: 0
I haven't found any real errors of missing nv files like in the thread, but about 40% of the log consists of this stuff.
Now I'm unsure, if this is really wifi, or bt. Others seemed to have this problem as well https://review.aosiprom.com/c/AOSIP-Devices/device_oneplus_oneplus3/+/3128
So maybe this is this bluetooth drain bug after all ?
The weird thing is: Turning off BT and Wifi doesn't help. The cpu is still on 300mhz.
Only airplane mode helps to bring it to deep sleep.
Last edited:
I honestly respect your research on that but oreo is kinda old... I guess RR will drop support for oreo in a few months. I use erfans repo for LOS15.1 + RR patches, this means the devtree is on a current state and the last commit was on 3rd August. Any issue which came afterwards is on ROM side, out of erfans control and surely out of mine.
Let me repeat what I said already several times in this thread: I am not a dev, (in short) I only download the source, apply some patches and run the make command. This whole process is called: build.
If it fails to build, I might do some research and cherry-pick one or two commits. Beside this I am not able to solve bigger problems. For oreo ROMs only the ROM devs can change anything. (RessurrectionRemix devs in this case.)
Beside that, the main devs for our device don't work on oreo anymore, they work on pie.
Next thing about pie, I stronly recommend to switch to another ROM when you switch to pie. This ROM is not that great in my opinion, bugs can take months to be solved (if at all).
Let me repeat what I said already several times in this thread: I am not a dev, (in short) I only download the source, apply some patches and run the make command. This whole process is called: build.
If it fails to build, I might do some research and cherry-pick one or two commits. Beside this I am not able to solve bigger problems. For oreo ROMs only the ROM devs can change anything. (RessurrectionRemix devs in this case.)
Beside that, the main devs for our device don't work on oreo anymore, they work on pie.
Next thing about pie, I stronly recommend to switch to another ROM when you switch to pie. This ROM is not that great in my opinion, bugs can take months to be solved (if at all).
hello, i have the same problem.
With the app "wakeblock" i disabled
"phonewindowmanager.mpowerkeywakelock" and the phone goes in deep sleep mode without any side affects for me
Sent from my XT1650-03 using XDA-Developers Legacy app
Ok, interesting. I'll test that and update here. Thanks.
Update: Ok, very weird, I still have batterydrain, but I can't find "phonewindowmanager.mpowerkeywakelock" anywhere. And compared to last time the main wakelocks changed ...
I'll probably will have to change my approach here.
Last edited:
Hm, I somehow missed your answer the first time.
You just wrote the things which bugged me for a while in the back of my mind. I somehow felt, that I hadn't that much luck with the phone (many sw bugs, broken screen etc). I didn't like the motorola SW at all and that's why I switched.
To be honest, I didn't look that much into the sources and I skimmed the thread to look for the usual bugs, but downloaded it anyway.
I was just grateful to you all, that you provide the ROMs (and even "just building" is also more than I can to / have time & ressources for).
Anyway, I used RR just out of habbit. It was cool for some years now, and I'm used to the menus, and everything so I didn't thought that much about it. You are right that I should rethink this and it's indeed time to switch.
So as you have a better overview of the things: For headache-free usage, would you then recommend the "vanilla" LOS16 or which ROM do you use ?
The simple way is to switch to AICP. It is being build by their servers and I guess it has dozens of modification options too.
I will switch to another phone some time next year (look at readyfx.com from Livermorium), so I will probably not build RR pie later. Though, I might do the little adjustments to get it build.
(It also depends on Xposed, I need it and as long as it doesn't support pie, there is no interest on pie for me.)
I will switch to another phone some time next year (look at readyfx.com from Livermorium), so I will probably not build RR pie later. Though, I might do the little adjustments to get it build.
(It also depends on Xposed, I need it and as long as it doesn't support pie, there is no interest on pie for me.)
dunno, test it.
Ambient display works normally for me now.
What is the difference between the versions around the 3rd of every month and those around the 20th? I noticed the newest security updates come with the versions around the 20th, but what is then the change in the versions around the 3rd?
For my feeling, the versions around the 3rd are more stable, but why?
Kind regards and thank you again for this nice ROM
Rainer from Bonn
For my feeling, the versions around the 3rd are more stable, but why?
Kind regards and thank you again for this nice ROM
Rainer from Bonn
The builds at the beginning of a month are before security updates. This means that the most bugs which comes with the security updates (often because of new restrictions) are patched.
The builds at the middle of a month are mostly for those, who want the newest security update. In theory I could only build on every 15th of a month (I have seen some do that) but then we couldn't enjoy a stable ROM.
The builds at the middle of a month are mostly for those, who want the newest security update. In theory I could only build on every 15th of a month (I have seen some do that) but then we couldn't enjoy a stable ROM.
First i have to say... Great Rom... Only one Problem... i did not get back my navigation bar after opening an app in immersive mode(for example clash royale)
swiping up is not working
swiping up is not working
Will there be more updates in the future or do you plan to stop the support for this great ROM?
About the immersive mode problem, no idea. I guess it is a ROM issue, nothing device specific.
About the ROM support, I will build it as long as RR oreo is being supported. (Guess I won't stop building after I switch the device.)
If RR oreo won't be updated anymore, I will stop building it.
About the ROM support, I will build it as long as RR oreo is being supported. (Guess I won't stop building after I switch the device.)
If RR oreo won't be updated anymore, I will stop building it.
Last edited:
No mid month build this month, I borrowed my SATA adapter to someone else, which had connected the android source HDD with my self-built-NAS.
I will get it back probably on 2nd or 3rd February, then I will make a new build.
I will get it back probably on 2nd or 3rd February, then I will make a new build.
Hi , someone pls can confirm for me with twitter app is working on build 0601 ? Here is stop work after i install my apps
After the 2019-02-10 update my Moto Z became very slow. At the moment I do not know if its the update or s. th els.e Did s. o. see the same behavior?
I'm on 20190210 but didn't see any slowdown. However battery life is worse than in previous build - this may be some app related or this is a battery calibration issue - hard to tell...
New posts
-
Dasaita - Latest MCU and Updates for Rockchip PX5 Octa-Core 2G RAM 32GB
- Latest: pospisekfrantisek
-
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone