yashsingh1/xdaforums huggingface dataset:
[G 2014 Original Android Development] virenlr:
Go to Settings>Sounds>Vibrate On Touch

and Settings>Sounds>Other Sounds

to disable all your vibrations.

Moto Assist isn't on any of the CM nightlies. In fact, it's even been discontinued by Motorola in favor Marshmallow's built in functionality.

Download a theme from the play store (if you don't have any themes on your phone, already). Then switch to the 'style' of that theme. Then switch back to your system stock style. Then uninstall that theme. Basically, just switch theme style, and come back to original.
[G 2014 Original Android Development] brosmio:
Thanks for the reply but I was referring to notifications. I've disabled all that you've said and even set to 0% the vibrator intensity. Any ideas?
[G 2014 Original Android Development] virenlr:
If you're using xposed, then a module is probably causing you trouble. If not, then I have no idea- especially since you've set the entire System vibration to zero. Clean flash, I guess? No ideas besides that.
[G 2014 Original Android Development] Hetarth:
I tried to do that but It didn't work
[G 2014 Original Android Development] virenlr:
Okay, then try this. If you're using any other launcher other than stock, uninstall your launcher, and then reinstall it. If you're using stock launcher, then go to launcher settings, change the color of the app draw to the opposite color, and then change it back. And if that doesn't work (but it should, because that's how I got it to work), then just try a clean flash.
[G 2014 Original Android Development] Hetarth:
It worked ..Thanks alot man ?
[G 2014 Original Android Development] vayavalla:
Go to the settings on the specific app

Enviado desde mi ifive_mini_3GS mediante Tapatalk
[G 2014 Original Android Development] doppelhelix:
My device doesn't sleep too. Lost more than 60% in one night. I exported the BetterBattery stats. Maybe this will help.

https://drive.google.com/file/d/0B4HE-jMnIvEvdk5Xa2J4MTRMNm8/view?usp=docslist_api
[G 2014 Original Android Development] AlCaponeGG:
I'm sorry, but the 27.02.build is draining battery more than newer ones, at least for me.
[G 2014 Original Android Development] Hetarth:
Yes there is force close on the latest nightly??
[G 2014 Original Android Development] metalmoot:
I don't know if it's solved for others but with the latest nightly (20160305) and a clean flash, battery drain is back to normal, the phone can go into deepsleep and doze mode :)
[G 2014 Original Android Development] tntnt:
On the latest nightly 3/5, the phne doesn't sleep.

Massive battery drain, never had it....
[G 2014 Original Android Development] sagar846:
Guys you know it'll be nice if we can stop the excessive posts about battery drain. Its been made quite clear by a number of people (it happens to me too) that it is present. We'll just have to wait until it gets fixed. Also if a few people could please post a BBS dump of a good duration of the phone being in sleep would help luk and luca assess the problem properly (I cannot due to personal reasons), but someone else could, it would be very nice of you.
[G 2014 Original Android Development] luca020400:
Battery drain can't be fixed

It's android itself
[G 2014 Original Android Development] virenlr:
Excellent Battery Life

Guys, I know posts like this are useless and don't help anyone, but I'm posting to let you all know that I for one do not face any battery problems whatever. And I'm running the same CM as everyone else here. The purpose of this post is to say that if you're facing bad battery, then it's some problem on your side (maybe a common app that everyone uses that I don't) or Gapps issue, but not a problem with CM.
[G 2014 Original Android Development] luke!:
Every time I flash/update a rom I get terrible battery stats, after 2/3 days of normal usage everything is back to normal, the same happened with CM13. So, does this battery drain keep going for several days on the SAME nightly?
[G 2014 Original Android Development] doppelhelix:
what do you mean? That sounds like "ROM is broken, deal with it"

P.S. Just installed 20160305. Deep sleep it's working again.
[G 2014 Original Android Development] BealeStBluesBoy:
Is there any way to change lockscreen wallpaper apart from the ones bundled with a theme?
[G 2014 Original Android Development] mandar91:
Moto G 2014 Cyanogen Mod 13 Marshmallow Battery Performance

https://youtu.be/Hz4Ho8Exaik
[G 2014 Original Android Development] HunterMountain:
Duals sim call handling

A few days ago I posted a question about how assigning the sims was handled when making a call. Nobody replied, so I decided to try the 20160306 nightly.

It runs great, shows no signs of battery drain and I would leave it on my phone without hesitation, but for one thing... call handling....

If you choose 'ask before making call' it asks once, and then changes the global setting to the sim you choose for that call. Assigning a sim to a number simply doesn't work... A great ROM ruined by something that seems simple enough. Pitty.
[G 2014 Original Android Development] apx@dwx:
which bad battery? like you can see in your own pictures, you have an absolute normal curve.

let me guess, the drop of capacity were exactly the time as u used your phone - saying, had your screen on.

while not, you can clearly see the deep sleep phases without any significant drain.

so i don't know what you all expect? a phone with his screen on will drain much energy, cause the screen is the most draining feature on it. on

every

phone!

like you also can see in your pictures. 39% drainage only cause of the screen.

so, thats no problem, this is how every battery-driven thing will work.

the only solution to extend your working time, at mobile conditions, is buying a powerpack.

like i and everyone else said, energy consumption has nothing to do with the rom itself. exception: if a kernel driven feature like the govs or deep sleep is broken cause of bug at the codebase.

further, my 2 cents: everyone want bigger screens, more cores and higher clock. but nobody realize this will consume much more energy. so stop complaining about the screen-on-time on phones with 5"+ screens and 4+ cores.

we all should be happy that our moto will last nearly 6-7 hours of usage and ~2 weeks of standby. that is much more time as my old phone!
[G 2014 Original Android Development] Jeannuel:
As I said, after I deactivated Ambient Screen, my Moto G now does go to deep sleep. 6-7 hours of screen is excellent for this phone. I dont have any complaint. This ROM is excellent.
[G 2014 Original Android Development] Rochambeau:
I can confirm this. Yesterday I flashed 20160305 and everything is back to normal. Kernel sleeps 99% of the time. :D
[G 2014 Original Android Development] tom002:
I completely agree with you. This ROM brings really a great duration - if standby works fine. But your last sentence is exactly the problem of the ones describing the battery problem: As soon as someone experiences it the standby time of the phone is not about 2 weeks but just 1,5 days. Not caused by a lot of display or app usage but because of standby/deepsleep/doze problems even in flight mode without any active connections. Just to clarify this - we are not complaining about regular battery consumption due to normal device usage.
[G 2014 Original Android Development] apx@dwx:
yea, but thats what i also said. if something is bugged at the codebase this can happen. but 99 of 100 replys refer to the behaviour that their phones won't last a week with display on. like my quoted ones.

and then people starting to advertise 'task killer' or 'battery extender'...

but like u said, u know what i mean.
[G 2014 Original Android Development] Simo1975:
No one realized that on this smartphone battery is underestimated compared to the size of the screen ?

It also heats up much...in the sahara desert it is discharged much more quickly than the Siberia. ^_^
[G 2014 Original Android Development] vishvavariya:
how to root on this rom i am not ble to root..whenevr i flash a supersu.ip file i get a bootloop..please help me
[G 2014 Original Android Development] Transdimensionalotaku:
......... It's already rooted, no need to flash anything. Go to development options and enable Root Access.
[G 2014 Original Android Development] Danilo-Sanchez:
It seems that this issue will be fixed in the next nightly build: http://review.cyanogenmod.org/#/c/135510/
[G 2014 Original Android Development] LuK1337:
Did you even read the commit message? This is fixing another thing...
[G 2014 Original Android Development] Danilo-Sanchez:
Yes, I read quickly. That's why I didn't understand correctly lol
[G 2014 Original Android Development] Jeannuel:
Do you have the latest twrp? I dont get bootloops when flashing super su.

http://xdaforums.com/showthread.php?t=1538053

By the way, the ROM is already rooted. You have to go to Dev options in Configuration to activate it.
[G 2014 Original Android Development] MarcosJungbluth:
Next build already based r17 (MMB29V)?
[G 2014 Original Android Development] luca020400:
Yup
[G 2014 Original Android Development] monojp:
Any noticeble or important changes?
[G 2014 Original Android Development] luca020400:
No, just march security
[G 2014 Original Android Development] rayz14:
Wifi conneting problem!!

I flashed cm-13.0-20160305-NIGHTLY-titan.zip on xt1068 as every thing worked fine and smooth WiFi shows up but doesn't connects to it so what will be the fix for this issue???
[G 2014 Original Android Development] vayavalla:
Check the router

Enviado desde mi Moto G 2014 mediante Tapatalk
[G 2014 Original Android Development] HouseBreaker:
I flashed the 05/Mar/2016 nightly and had 99% awake time. There were like 120k wakelocks of the same kernel feature/process and stuff like that, which is obviously not normal. I went 4 days with this issue and today it resolved by itself lmao android is ****ed up
[G 2014 Original Android Development] SuperSimian:
C- apps "theme chooser" FC.

https://cyngn.com/c-apps

FC since 2016.03.05 build.

Ill report this to CM later
[G 2014 Original Android Development] luca020400:
Since you're using capps for cm12 on cm13 it makes totally sense[emoji14]
[G 2014 Original Android Development] SuperSimian:
Good point. I thought those capps were good for cm13 since they functioned as intended all the way up to march 4th build.
[G 2014 Original Android Development] yuyoelmero:
Hi, where are the performance settings?
[G 2014 Original Android Development] LuK1337:
Nowhere.
[G 2014 Original Android Development] sagalfisz:
So, what do that pair of lines mean?
[G 2014 Original Android Development] LuK1337:
Nothing. They just add the cmsdk permission lol.
[G 2014 Original Android Development] nikunj.baheti@gmail.com:
[MENTION=5075128]LuK1337[/MENTION] [MENTION=5778309]luca020400[/MENTION] i noticed a bug in the latest nightly. That is the 9 march nightly. i have set the notifications to hide the sensitive info from the lockscreen. but even after unlocking the phone the notification still shows as "content hidden". pls look into the matter
[G 2014 Original Android Development] H@wK11:
Same here please fix this.
[G 2014 Original Android Development] zakaziky:
Edit: same here ?
[G 2014 Original Android Development] sagalfisz:
Is there a way to solve the theme chooser fc? I clean flashed this ROM a couple months ago, but I guess i have c-apps theme chooser because I flashed them when I was on CM 12.

If someone knows the solution, idk like flashing another theme chooser or something.. Please tell us! More than one will be thankful for it.
[G 2014 Original Android Development] Lenarios:
I read over some old posts but I failed to see if the battery drain was fixed. It's been over a week on my device...
[G 2014 Original Android Development] hawkshot:
I am experiencing vibrations at random times. It would appear that the phone is vibrating whenever a change in connection occurs (Wifi, BT, 3G). I've looked around the menus and searched the internet for info, but I appear to be the only one experiencing this and there does not appear to be a way to disable it.

13.0-20160224-NIGHTLY-titan

What can I do to disable this? Feature request? Bug?

The vibrations are like Chinese water torture. I am starting to hear voices...
[G 2014 Original Android Development] Lenarios:
Update your rom
[G 2014 Original Android Development] BealeStBluesBoy:
No, it's not. The thing is that BBS doesn't show any wakelock.
[G 2014 Original Android Development] Lenarios:
BBS? Wakelock?
[G 2014 Original Android Development] hawkshot:
Yeah, I guess that would be the first step. Was it a known issue? I can't find any info on it.
[G 2014 Original Android Development] monojp:
Don't you maybe have profiles that are triggered on WiFi/data changes? Those would explain the vibrations I guess ;)
[G 2014 Original Android Development] luke!:
On latest nightly I'm experiencing static/crackling noise from the speaker only during calls, not while listening to music. Today I've also flashed the latest cm 12.1 snapshot and I did't have any problems so I assume that's not related to the hardware/provider/ambiental interferences. Has someone any ideas?

More info: this seems to happen only when I use 2G network.
[G 2014 Original Android Development] Lenarios:
Since early this morning the cm download site is off... something happened?
[G 2014 Original Android Development] luke!:
http://get.cm is up and running
[G 2014 Original Android Development] Lenarios:
Had to use a proxy, but I can't download anyway...
[G 2014 Original Android Development] Jeannuel:
Same here. All the notifications are hiding. This should happen only when the phone is locked. Also, I cant remove some notifications until I click them.

For example: Do a screenshot, pull down the statusbar and try to remove the screenshot notification by swiping to the left or right. I cant remove it.
[G 2014 Original Android Development] super-drone:
It's just me or voice audio on whatsapp got worse after today's update?
[G 2014 Original Android Development] sagalfisz:
.....anyone?
[G 2014 Original Android Development] Aliston Pinto:
Capps doesn't support cm 13 yet
[G 2014 Original Android Development] sagalfisz:
I already know that! I don't want to force it to work, I want to know if there's a way to flash a compatible theme chooser, idk like the original one, so I can get rid of the c-apps one. Unless somehow the ROM can recover its compatibility to that theme chooser, you know, it worked nice until 03-05 build.

[MENTION=5778309]luca020400[/MENTION] or [MENTION=5075128]LuK1337[/MENTION], is there a way you can recover that? Believe me, I've been looking and reading and you'll be helping a lot of people with this issue.
[G 2014 Original Android Development] monojp:
Formatting system, reinstalling cm and gapps should fix you up. This gets rid of the script that restores c-apps. Just be sure to NOT format data or do a factory reset.
[G 2014 Original Android Development] doppelhelix:
Sure thing. But since kernel and rom are distributed as one package, and the average user doesn't care (and rightfully so) which is wich, this is the place to post unnormal battery consumption.

And this (clean install 20160309 without gapps) is not normal:
[G 2014 Original Android Development] himsin:
I think problem is in source code of cm. I switched to xenonHD (AOSP based) and there is no battery issue. Deep sleep is better than it was ever on cm13. Like all AOSP based roms for our device, XenonHD also uses cm's device tree, so we can say it's not device specific problem.
[G 2014 Original Android Development] luca020400:
Lol every ROM is cm based even if they say aosp based

The battery drain is caused by android it isn't a cm/whether fault
[G 2014 Original Android Development] virenlr:
https://wiki.cyanogenmod.org/w/Cyanogen_Apps

Scroll to the end and read the uninstalling instructions.

Basically, remove the Capps file from addon.d in System. Followed by dirty flashing CM to get back your original theme chooser.
[G 2014 Original Android Development] himsin:
I would suggest that you give it a try. Use the same setup you are currently using in AOSP based rom and you will see the difference. There surely is some bug in cm which is not letting device sleep and such high drain without even using the device is totally not normal at all.
[G 2014 Original Android Development] katikati93:
how do i disable offline charging? Because my power button is gone and when it runs out of juice completely(which ill try to avoid max).i want it boot it up by itself when connected to a charger.
[G 2014 Original Android Development] luca020400:
When you are going to install a custom ROM that is based on aosp , you're going to install a cm with more features
[G 2014 Original Android Development] himsin:
I agree every one of them uses a lot of cm code but they are also not using a lot cm code too e.g. cm's worthless statistics service etc...

That is why I suggested to try, experience is the best way to clear doubts.

Also, I am not doing publicity of some rom here, I am just saying there is some bug and by saying "it's android" is not a justification (no disrespect to devs here)
[G 2014 Original Android Development] luca020400:
I don't see how cm can be the cause to a well know android issue ..

Just my 2cents
[G 2014 Original Android Development] himsin:
What is that well known android issue here which is causing approx 10% drain per hour without even using the phone?
[G 2014 Original Android Development] luca020400:
No it isn't , it's your configuration

But without proper information I don't really know what is happening
[G 2014 Original Android Development] luke!:
Bad flash-timing for snapcamera: the photos in low-light conditions are darker compared to stock camera or Opencamera.

Would a logcat be useful in this case?
[G 2014 Original Android Development] luca020400:
Should be fixed in yesterday/today build
[G 2014 Original Android Development] Vidhanth:
You can't disable offline charging, but you could do this. Keep your vol down key pressed as you plug in your charger, and it'll take you into BL mode. From there press vol up to boot up.
[G 2014 Original Android Development] apx@dwx:
yea, it should look like this (build from 27.2.16). but why does those wakelocks happen on a clean install, when luc said it's not the fault of cm? cause i've never had wakelocks just cause of android itself.
[G 2014 Original Android Development] super-drone:
If this is not a cm problem I don't know what the heck is, cause I was at 20160214 build and wasn't facing this battery drain while sleeping (and I use same configuration as 02/14 build) I think I'll just go back to it, but please try to figure out what is this problem...
[G 2014 Original Android Development] luke!:
Just to let you know: I've flashed the 20160310 build and snapcamera has the same problem :/
[G 2014 Original Android Development] Aijen:
Yeah its no a Cm or Android problem....I notice the Battery Drain since December 22 2015, before that Cm13 was excellent in battery performance, I report it and since that date its the same answer :/
[G 2014 Original Android Development] H@wK11:
Huge battery drain on stand by mode.
[G 2014 Original Android Development] sagalfisz:
Thank to you both! I removed the file from /system, then installed the latest nightly and it worked!
[G 2014 Original Android Development] monojp:
Battery drain could be because of your magical build from the future :D
[G 2014 Original Android Development] skaveelicious:
Clear the data of snap cam. Is this happening on titan or thea? Nightly, self built? Need some more information. Also issue with snap should be fixed since like 10 days. Other cams since yesterday.
[G 2014 Original Android Development] luke!:
After the umpteenth reflash of the nightly and after clearing cache and dalvik, I got it working fine right few minutes ago, thanks. Btw, I downloaded the nightly from get.cm and clean flashed it.

-------------------------------------------

Has anyone noticed that the activation of doze doesn't correspond to a deep sleep state of the device? Shouldn't the two things be correlated? Is this a normal behaviour?
[G 2014 Original Android Development] super-drone:
Lmao sorry I mean 02/14
[G 2014 Original Android Development] DepressedDead:
https://github.com/MotorolaMobilityLLC/kernel-msm/issues/62

[MENTION=5778309]luca020400[/MENTION] [MENTION=5075128]LuK1337[/MENTION]

As the github issue is now closed, have you had luck with the touch issues, or there were no changes in the kernel sources? Just asking.
[G 2014 Original Android Development] luca020400:
Touch is 100% the same as stock

No changes were made by us or moto

So I don't know what's going on ( and if it still happens )
[G 2014 Original Android Development] hawkshot:
Yeah, right after updating yesterday I noticed that it went into vibrate mode. I have a Tasker script set up to put my phone into vibrate if connected to my watch. It didn't use to do this with LP, so I will have to tinker around to see if I can get it to go into vibrate mode without vibrating using either Tasker or Profiles. Thanks.
[G 2014 Original Android Development] luke!:
[MENTION=5778309]luca020400[/MENTION] I've to ask you some clarification about the so called "doze mode" because it's been driving me crazy for hours and I have to understand this xD So, I've noticed the usual battery drain and bla bla bla, reading the stats I've seen that the time spent by the device in doze mode (idle) is not the same amount of time spent in deep sleep but it's exactly the same time the processor spent running at 300 mhz. I attach two images when you can see better what I'm talking about. Now, why does the processor run at 300 mhz (no time spent in deep sleep) if doze mode is active? I'm just freaking out while reading everywhere trying to understand this xD Thanks in advance.
[G 2014 Original Android Development] josfr4ncisco:
So, there's nothing else to do? If touch is still buggy, we'll have to deal with it?
[G 2014 Original Android Development] H@wK11:
Battery draining like hell

Drop from 29% to 5% in just 7 hours at night time. before i go to sleep I put it into flightmode still huge drain and also not getting good SOT :( :crying:

[MENTION=5075128]LuK1337[/MENTION] [MENTION=5778309]luca020400[/MENTION]
[G 2014 Original Android Development] josfr4ncisco:
Devs, is there a way to get info about touch input like a logcat? I've tested CM13 and 12.1 (also recorded my tests) and seems like the digitizer isn't picking light touches. Hoping there's a way I can help with logs
[G 2014 Original Android Development] ethanbmnz:
At least I'm not the only one experiencing this issue.
[G 2014 Original Android Development] ealejandr0:
As other people I'm also experiencing a huge battery drain when I'm not using the phone, the first screen shows my battery usage overnight yesterday. You can clearly see the graph went nearly flat thanks to doze(this was after clean flashing March 4th buid). Without changing any configuration it suddenly went to losing 1-2% overnight to losing 10%(you can see the today's graph is a steady decline) and Wakelock detector shows my phone was awake 60% of the time(and this wakelock doesn't correlate to any of my apps). This is not normal.

Is there any log that I should get for the devs to clear up this issue? I love CM13 but for the time being I guess I'll have to go back to stock :(
[G 2014 Original Android Development] monojp:
So, dose is working fine at night, but you are loosing battey during the day, right? "Google App" seems to be making the most wakelocka, maybe due to GoogleNow or other location history stuff when moving around?

You could also try to get the other and especially the kernel wakelocks from WLD
[G 2014 Original Android Development] rgnicholas:
Hello, I am just curious... you mention that you clean flashed the 03/04 build, but have you applied the last 3 OTA updates? I wonder if the last build may have corrected this issue. I was about to try to 03/10 build, but if the battery issue persists, I will wait a bit. TIA