yashsingh1/xdaforums huggingface dataset:
[X 2014 Original Android Development] testkeys:
Yes (about Gello) and a bit of a warning here:

May 4th nightly 'kills' led notification light for me.

And I've tried to install it twice (1- coming from May 1st and 2- after restoring a April 28th build nand and verifying led) and both times the phone soft rebooted after the app optimization and displaying something about Calendar sync..

First install optimized 100apps, after nand restore optimized just 75...

SHA1 has been verified.

Restored nand again, booted up and then flashed May 1st: led notification works still.

How to waste an hour and third of battery charge.

So my advice: stay on May 3rd for now.
[X 2014 Original Android Development] Gus Ghanem:
I clean flashed May 4th with Delta Gapps Base only (Play Store/Framework only). Optimizes about 98 apps, but after a CM Update, usually 70 apps. I haven't done much with the phone since, didn't get any notifications to check the LED, but it does light up from the LED settings. So far no reboots or crashes.

I understood from the changelog that we were getting this brand new (Chromium based?) browser; it looks like not yet. I usually replace the CM browser with Chrome.
[X 2014 Original Android Development] testkeys:
I find it very strange that simply installing a nightly build (no gapps package needed again) over an older build -which I've running on for 3 days- would likely create more issues than a clean flash. Then restore a clean installed setup nandroid from 3 days prior to that and try again same latest nightly, same soft reboot and led problems... ....

I know that it happens (I've experienced it more than my share) but strange as to why should it? Anyhow, past 3AM... I don't want to think about it really, but ...

Gello: that's what I meant by yes; I thought it was going live this time around, but no luck.
[X 2014 Original Android Development] testkeys:
[Q]: would that be silly for me to try to:

- make a nandroid backup from my current 0501 setup;

- wipe everything except internal sd;

- (clean) install 0504 again and let it boot up;

- go back in recovery and restore only data from my nandroid (and would I need to mount data first or it does it on its own?)?

- -

And one strange observation: after restoring a nandroid, boot up then install 0501 yesterday, only 75 apps were optimized at boot. I could swear that I've rebooted normally afterwards (although it was in the middle of the night and a bit foggy now) but this morning, when I rebooted, 10 additional apps were optimized without any special chages made to my system... ?! ?! ?
[X 2014 Original Android Development] bornlivedie:
You think dirty flashing and overwriting files is safer than clean flashing? [emoji47] [emoji47] [emoji47]
[X 2014 Original Android Development] testkeys:
I think that there must something wrong somewhere because flashing a newer build over another should not be an issue. I've read it in nany devices/CM threads and from many maintainers before.

It must be the word "dirty" that scares some, much like "stable" or "snapshot" makes others feel so much safer...
[X 2014 Original Android Development] testkeys:
May 5th nightly installed...

- unlike may 4th, no soft reboot on first boot (92 apps optimized and none on next reboot: all good!);

- Although the LED notification light lights up when choosing to adjust its intensity in settings, it is now again no longer lighting up when receiving a sms;

:crying:

- still no Gello;

- good news: the loud "thump" that I've mentioned previously that was occuring when pausing/resuming audio playback now seems to be gone. - oh yeah!

So [MENTION=244209]Gus[/MENTION] Ghanem: did you finally verify if your led was working fine on May 4th? You can always do like I do and send yourself a message...

Cheers.
[X 2014 Original Android Development] Gus Ghanem:
Updated to May 5 as soon as it was available (dirty update). I don't use SMS, but the LED seems normal, lights up on Whatsapp notifications. I doubt there were any LED issues before; I don't remember ever experiencing any.

No, I guess the LED is not lighting up for SMS (sent to myself).

I'm still wondering about Gello, maybe there are still some bugs to be fixed.
[X 2014 Original Android Development] lucasortlieb:
I'm facing issues with my battery. When I first flashed CM13 (3 months ago) the battery life was arround 6h of SOT, during all day long. Now the battery drains very very fast from 30% to 0% (seems normal from 100 to 30), and sometimes the phone just turns off with 10, 15%... Also, sometimes the battery have "cuts", like being in 60% and suddently falling to 45%....

What could be causing this issues? What can I do to fix it? (I'm still a bit noobie)
[X 2014 Original Android Development] salaesp:
I've noticed the same issue. I also couldn't get close to the battery life of stock ROM. I found out that if I wipe all the recent apps after using them, the battery life improves a lot, ( it decreased 20% in 6 hours with 30minutes of screen time)
[X 2014 Original Android Development] xavi23:
I've installed May 6th nightly and the LED light is working fine again. Everything seems to be working OK.

Cheers!
[X 2014 Original Android Development] sonsum:
Finally updated to the 5/6 build after running 1/26 since I first flashed CM13. I'll report back if I experience any issues.

Has anyone had any luck with alternative kernels and CM13?
[X 2014 Original Android Development] [] AL []:
..

---------- Post added at 03:54 AM ---------- Previous post was at 03:50 AM ----------

Sorry, I've deleted my previous post by mistake...

Could please tell us:

- when did it stop working

- if you clean flashed (wiped data) or just installed over?

Thanks!

Downloading....
[X 2014 Original Android Development] xavi23:
I've been reading in previous posts that the notification led wasn't working, I never had that issue though.
[X 2014 Original Android Development] testkeys:
Yeah, well sorry it was me and my system apps messing around and dirty flashing....

Your comment gave me hope that I could fix my LED with 0506, but that didn't fly and I still had soft reboot after flash...

So I bit the bullet again and did flash it clean and now LED is fine... So I don't know what I'm messing with that eventually (after maybe 5-6nightly builds) make the update process get bugged...

Notes on 0506:

I tried the new Yahoo! weather provider:

- very nice that unlike WU, there is no need to register and set a plan... much better: let's hope it stays that way;

- like it was the case at the beginning with WU, I think that some weather conditions might need fixing because I got a big "?" as forecast for Tuesday... (pic);

- I really wonder why no one in the CM team took a few minutes to fix the forecast panel's layout... As I reported before, weather condition overlaps with RH/wind and also having hi and lows on 2 rows might make sense, but they could have centered them under all the weather images. That looks pretty weird as it is;

- the yahoo provider app takes something like 8MB of RAM on it own; a little much for something that used to require nothing extra of LockClock... That was the final nail that got me revert to the old one once more...

The rest seems fine for now....
[X 2014 Original Android Development] kaktusmaier125:
Camera crashes when auto and flash light is on

05/04
[X 2014 Original Android Development] josfr4ncisco:
Audio seems a bit slow and sluggish on games, is there a fix for that?
[X 2014 Original Android Development] Zikote:
HELP! cm-13.0-20160507-NIGHTLY-victara status bar pulldown not working...
[X 2014 Original Android Development] wttb470:
Been getting good results using snapkernel for cm. Although display settings still crash for me, on may6 nightly.

Update: ran my 27.4 backup, updated via cmupdater, and display settings now works. What gives?

Update2: Busted after some rebooting. Display settings crashes again.
[X 2014 Original Android Development] Bryandu13:
Display crash for me too with Snapkernel, and with Real One X too.
[X 2014 Original Android Development] wttb470:
You think the kernel has something to do with display settings not working g?
[X 2014 Original Android Development] Bryandu13:
Yeah because display work with stock cm13 kernel
[X 2014 Original Android Development] wttb470:
Ahhh that's a bummer. Good to know.
[X 2014 Original Android Development] bornlivedie:
those kernel are extremely outdated and buggy

don't even consider them
[X 2014 Original Android Development] lucasortlieb:
Is Snapchat working in last nightlies? I mean video recording, also with filters applied. I want to update from an old nightly but I need to know if it's working properly.

Enviado de meu XT1095 usando Tapatalk
[X 2014 Original Android Development] Bryandu13:
Snapchat fully working since some weeks ! You can record ;)
[X 2014 Original Android Development] lucasortlieb:
ok Google is not working for me. the app just shows the option for detection in the app, not in home screen or somewhere else...

Enviado de meu XT1095 usando Tapatalk
[X 2014 Original Android Development] raptir:
OK Google has never worked for me on CM on the Moto X, and Google Now voice detection does not work on the stock software either.
[X 2014 Original Android Development] R55770:
To everyone that is having problems with their quick settings and notifications:

I found that if I flash a newer OpenGapps package, the notifications and pulldown and settings panel work.

For example, I was running the latest CM nightly but I was using a Gapps package from March. Apparently, that messes with the setup process. After I used the latest Gapps package, all was well.

Tell me if this worked for you.
[X 2014 Original Android Development] dwiedunia:
Change the gapps solved my problem
[X 2014 Original Android Development] Gerriitw:
screensettings fc on the newest build. i did a clean flash
[X 2014 Original Android Development] mikeoswego:
On 20160512-nightly, at least when calling *86, it makes the call and then an FC saying phone has stopped. Call is still connected and I accidentally started a conference call. Am able to go back to call in progress and hang up.

Reverted to 0511 and problem does not exist. I know I'm not providing logs, etc. but will if no one can replicate this.
[X 2014 Original Android Development] mikeoswego:
Problem with outgoing calls continues with 20160513-nightly.

Dial a number, messages pops up saying "Unfortunately phone has stopped."

I used the built in report problem dialog that pops up to submit the report that way.

Attached is a log with 2 calls.

The calls go through, you can "Return to call in progress" , it appears to be just the UI that stops

20160511-nightly and prior did not have this problem.
[X 2014 Original Android Development] Tinchoska:
Hu guys, have you tried L speed?

Enviado desde mi XT1097 mediante Tapatalk

---------- Post added at 06:12 PM ---------- Previous post was at 06:10 PM ----------

And, have you test snap camera with stock firm camera

Enviado desde mi XT1097 mediante Tapatalk
[X 2014 Original Android Development] mikeoswego:
Looks like one of the commits for tomorrow's nightly fixes the "phone has stopped" problem I was reporting. :good:
[X 2014 Original Android Development] tanishque italia:
Does screen mirroring with Chromecast work cm13?

I can't test myself because once I switch to cm13 from stock I do face some issues while going back to stock.
[X 2014 Original Android Development] pedp4000:
On nightly 0512 getting cm actions failed notification when trying to chop chop for flash. Anyone else get this? This was working fine on 0503 for me.
[X 2014 Original Android Development] ayusharad:
can I flash this on XT1092 Indian model? and what all are the known bugs? sorry if it's answered before.
[X 2014 Original Android Development] bwcall:
I'm pretty sure as long as you already have the means to boot into your custom recovery like TWRP and have unlocked your device's bootloader, you'll be able to flash this. However, if you've not yet unlocked your bootloader and installed a custom recovery, then you won't be able to use this CM13 ROM yet.
[X 2014 Original Android Development] ayusharad:
Yeah I have unlocked my bootloader and flashed TWRP recovery, its just the model number I was worried about
[X 2014 Original Android Development] bwcall:
My ATT XT1097 works fine, shows up as a XT1095 now in System Info.
[X 2014 Original Android Development] Tinchoska:
It's normal. But made no effects on phone itself

Enviado desde mi XT1097 mediante Tapatalk
[X 2014 Original Android Development] lauren:
hey guys

latest nightly 20160517 i am having an issue where pushing to power button is not waking up the device - never happened before - anybody else seeing this?
[X 2014 Original Android Development] adap11:
Seems to be working fine. Is ur power button intact?
[X 2014 Original Android Development] Gus Ghanem:
May 21 Nightly: Gello Browser

Why is this still at version 42 when Chromium is now 50.
[X 2014 Original Android Development] alediniz:
Fellow how is the question of stability and battery consumption in relation to MM stock rom? Any significant bug? Do you use one of the alternative kernels or standard CM13? Thanks a lot.
[X 2014 Original Android Development] testkeys:
Yep true, but well.. I got more than the version number bothering me about it...

I was anxious to try it when I saw your ss showing night mode settings... But it turns out that it is in fact an (everything) inverted mode. Hello strange colors on web pages!

Couldn't find anywhere how to switch Desktop user agent. Big thumb down if it isn't possible or not on roadmap for a later option.

Another bummer: the browser doesn't let you take screnshots. (pic 1). I don't know if it's a new legal thing, but that's quite a little freedom lost here... [EDIT: as mentioned 3-4 posts below, this was because I had the browser's "LookLock option turned ON]

Last nail in the coffin from this very quick test/review: apk size (pic2 speaks by itself here...). Hello gello! the wobbly stuff just made our nightly builds downloads more than 10% bigger. Quick math: a nightly a day for a month: about a GB more to transfer. I hope that delta updates are on the roadmap as well...
[X 2014 Original Android Development] adap11:
1. Battery lasts a few hours(3-4) longer than stock ROM.

2. CM13 is functionally very stable, but is still under progress. Hence a few minor bugs are encountered e.g. Notification LED not working for a particular nightly( NOTE: not everyone is affected by the bugs. I haven't encountered even a single bug yet and have had a smooth ride so far). These small bugs are fixed almost immediately. All in all its worth the upgrade. CM is faster, smoother and has a better battery life.

3. I'm using the stock CM13 kernel. I have previously tried snapKernel but had a bad experience with it (random restarts, apps freezing and idle overheating)

You'll not be able to use moto voice. But most of us don't miss it either. And yea, CM themes are mesmerizing?

---------- Post added at 07:46 PM ---------- Previous post was at 07:32 PM ----------

Why is the size of May 21st nightly 331.08mb? Any additional packages?(Usually they are 297-297mb)
[X 2014 Original Android Development] Gus Ghanem:
Gello lets you save webpages? I'm not sure what you mean by screenshots, other than "power + volume down"? That works for me on web pages.
[X 2014 Original Android Development] testkeys:
Ok, found it: had the" LookLock" option ON.... Dang!

Thanks
[X 2014 Original Android Development] wispoffates:
I had this problem as well as spontaneous reboots while charging. Then just as suddenly as it started it stopped. No idea what happened.
[X 2014 Original Android Development] testkeys:
Just in case you haven't figure out yet or read the post above yours.. well, go and read it. hehe

I've never seen this although, I use the volume rocker to wake the device 95% of the time.. [Settings/Buttons/(Volume buttons) Wake up device --> switch ON].

This might somehow be related to an issue I've reported long ago (which still happens occasionally [on each nightly] and which others have confirmed as well) where we could not turn off the display with the power button. The work around is to press the volume rocker one shot up and one shot down (or opposite I guess, but only one direction doesn't do it for me). So I'd suggest you to try this out (and let us know the result) before setting the volume rocker to wake the device.

Cheers!

- - -

O-T part:

I got a little tired of blinding white or that uggly blue-green color boot logos, so I made a simple one a little more sober and thought I could trow it in here...

I couldn't figure out a update-binary/updater script with to put it in a flashable zip. But I think that it is even easier and faster with adb/fastboot anyway...

Here's a quick how-to:

If you don't have it yet, search for and install something like 'Minimal adb/Fastboot' or '15 seconds Fastboot installer' [and you Moto drivers that you should already have installed on PC by now...]

- unzip my attachement and copy the .bin file to your adb/fastboot folder;

- Turn ON adb debugging in the developers options of your phone;

- plug the phone to the pc (no need to turn off) and run adb/fastboot and in the command window type: adb reboot bootloader

- now type: fastboot flash logo testkeys_cm_moto_bootlogo_3.bin

[tip: you don't have to type the whole filename of the bin file: type 2 or 3 letters then the "tab" key]

- fastboot reboot

- enjoy!

edit: preview png is resized and lower quality than actual bin
[X 2014 Original Android Development] kaktusmaier125:
corrupted zip error when ota update on latest nightly but works when manually flash it
[X 2014 Original Android Development] testkeys:
I hope that you've verified the Md5 or SHA1 check sum at least...

Otherwise hats off for being braver than me to install something flagged as corrupted - lol
[X 2014 Original Android Development] kaktusmaier125:
No i haven't verified :)))

Can you tell me what the issue is it ? Is It twrp problem?
[X 2014 Original Android Development] testkeys:
I don't know and even less so because you don't really gives us clear info.

1- "Latest nightly" never means anything to me, because they get released at different time of the day and I don't feel like going to the download site to verify info not given...

2- what exactly gives you "corrupted zip error"? the CM updater? If so, then like I wrote, I would never flash that build without verifying the checksum --> think about it; why would the updater warn you otherwise...?

3- you wrote "manually flashed" worked, so I'm guessing you're referring to TWRP... So why would it be a problem with the recovery then?

4- OR long shot here: did you press the ~ "press ok to reboot and install" ? <-- because that doesn't work with TWRP

So explain more if you want more... It's never fun for anyone trying to help to do all the guess work; ask and write more than what the person with the question did....
[X 2014 Original Android Development] kaktusmaier125:
1) cm-13.0-20160521-NIGHTLY-victara.zip

2)In twrp

3)...............................

4)yeah i pressed the press ok to reboot and install, it has just worked till 20160521
[X 2014 Original Android Development] testkeys:
Then this is news to me because I've only tried that option once a while ago and it didn't work. And everything I've read thereafter said that it wasn't possible with TWRP. (Not that pressing the power button and choosing reboot in recovery so much harder to do...)

So what version of TWRP are you using and if you're still determined to find out what happened, why haven't you checked if the nightly Md5 match yet?? (again: first thing you should have done really)
[X 2014 Original Android Development] Tinchoska:
Guys, fast question, how's battery on latest nightlies ?

Enviado desde mi XT1097 mediante Tapatalk
[X 2014 Original Android Development] kaktusmaier125:
Much better than stock M
[X 2014 Original Android Development] dwiedunia:
is audio glitches on Real Racing 3 had fixed?
[X 2014 Original Android Development] thousandecibels:
Running May 22 Nightly, after reboot, I see blank lock screen wallpaper. Does it happen with anyone else? Any fix?
[X 2014 Original Android Development] vinydasilveira:
Nope
[X 2014 Original Android Development] salaesp:
Any particular configuration for that battery usage? My phone runs out of battery after 16hs with 1 hour of screen time
[X 2014 Original Android Development] CanitoLagos:
Anyone know when will the stable version? as a snapshot
[X 2014 Original Android Development] adap11:
That's strange. Many possible reasons.

Do you have background apps which eat up your battery?

I had a similar problem once. I thought the battery had lost its life(it ran for ~14hrs). I did a clean flash, installed bare minimum 3-4 apps.

And volla it ran for one and a half days straight with around 2 hrs of screentime.

I would recommended you to do the same. If your battery is dying, get it replaced.
[X 2014 Original Android Development] joseph_1802:
Running May 24 nightly.

- CM Camera crashes when using the flash. Without using it, works fine. Any solutions to this? Is it possible to use the double-twist gesture to launch another camera app?

- Notification led per app doesn't work. For example, I've set it to notify me when I get a message from Whatsapp, but nothing happens. Also, is there a way to customize the led, like make it blink instead of being on all the time?

Other than this, everything seems to be working fine. By the way, any good dark theme to recommend?
[X 2014 Original Android Development] julian.c28:
***UPDATE ISSUE SOLVED***

It seems that the issue persisted because when booting up first, the Setup Wizard for Cyanogen didn't open correctly. Only the Google setup wizard worked. I just reflashed, and it was all good.

--------

Long story short: my phone went through some issues so I factory reset it, and reinstalled CM13 and Gapps.

I'm running the 5/24 nightly. The bug I'm experiencing? I can't swipe down a second time from the notifications bar and it also doesn't show ANY notifications I get. I feel like this is a common problem, and it's NOT just this build.
[X 2014 Original Android Development] vok01:
Somebody knows about "Battery Save" bug on CM13?

My battery have less that 10%, I change Battery Save mode to off and then to "Activate at 5%" and my screen starts to flash and the touchscreen stop working

CM13-20160524 build.

Clean installation with stocks GApps from Opengapps (stock)
[X 2014 Original Android Development] nandroidz:
Try Swift Dark https://play.google.com/store/apps/details?id=com.brit.swiftdark
[X 2014 Original Android Development] testkeys:
Same nightly + recent Open Gapps pico got to 15% Battery SaveR kicked in, went in settings and changed it for 5%: screen (statusbar and navbar) went back to normal until battery saver turned ON again at 5%... So not having that issue here.

Same with notification double-swipe down and all notifications work fine here. No battery drain and did not test the camera yet since I mainly use Moto Camera.

But:

anyone has used to speakerphone recently and experienced any issue?

I've noticed while running May 21 build that I couldn't use the speaker phone because although it sounded relatively normal on my side (some strange intermittent static noises, but not that much), the other caller though could barely hear me and was hearing loud noises and echo of his/her own voice and could not bare communicating like so; it's was that bad. To test and hear it for myself, I called a automated answering system, chose speakerphone and recorded the call while listening to the recorded message and making selections; sound and echo was pretty bad. There! I found one of those recordings; zipped and attached - and one of the person that I called heard it and said it was even worst than that on her side.

Later installed May24th on top: same issue. Then reverted to a May 17th nandroid: still same issue... Could it be hardware or anyone has also experienced this in the last 7-10 days?

I don't use speakerphone that often, but I know that it did used to work fine not that long ago.