yashsingh1/xdaforums huggingface dataset:
[X 2014 Original Android Development] testkeys:
I tgink that you can download this directly from Github (although I remember trying for another package recently and couldn't figure out how to get to work w my PC..). But anyway, thanks to XdaLabs (very ease toattach any file type - as opposed to Tapatalk...) here it is.

Can't help you about location as G location services are not available where I live...
[X 2014 Original Android Development] enjoimadcow:
Another thing I found on 313. The alarm clock goes off but the ui crashes. I'm on a fresh install. I'm going to try the newest nightly when I get outta work today.
[X 2014 Original Android Development] pubcat:
I'm on cm-13.0-20160315-NIGHTLY and I'm having the same issues with the alarm clock. I was having the same troubles with the nightly right before this one as well.

Anyone else? Known issue?
[X 2014 Original Android Development] salaesp:
Something is killing my battery. Both wifi and Bluetooth location recognition are disabled. Any ideas. I'm on 20160314
[X 2014 Original Android Development] AhmedFaiz:
Is the M build of cm13 release 1 for victara.
[X 2014 Original Android Development] bornlivedie:
Sorry?
[X 2014 Original Android Development] kaktusmaier125:
Probably not there is no victra in cm first milestone device

---------- Post added at 08:56 PM ---------- Previous post was at 08:54 PM ----------

Cyanogen mod release first milestone of cm13 build

It means more stable than nightlys
[X 2014 Original Android Development] ming3r:
known.

Either set it to not be optimized by battery or...use timely.
[X 2014 Original Android Development] salaesp:
Sorry, what do you mean by "set it to not be optimized"? Inside battery options?

Thanks!
[X 2014 Original Android Development] salaesp:
Thats the thing that should be saving my battery. In previous versions, battery life was much better, now it seems like the phone es never entering Doze state.
[X 2014 Original Android Development] :
Alarm clock is still broken on 0317 nightly, setting it to not optimized doesn't work for me.
[X 2014 Original Android Development] AtLmd:
http://xdaforums.com/showpost.php?p=65308032&postcount=739
[X 2014 Original Android Development] testkeys:
You guys keep saying broken alarm /FCs over and over but no one even bother grabbing/attaching a log. This is a development thread, so when the cause and exact steps to reproduce something is known, it's the least one can do...

I don't really use the alarm, but I've tried it a few times lately (w the 2 or 3 last and recent nightly I ran on) and never had an issue with it...

Is the problem occurring only after long period of inactivity (morning alarm) or is it doing it for an alarm set 2 minutes apart? That makes a difference because Doze kicks in after some quiet time only.

And btw, I wouldn't expect the 'do not optimize' (battery) setting to help with this; it did not help with apps that could switch airplane mode on a short notice timer but that were failing to do it in the morning...

A dev finally provided me with a beta apk and it solved and confirmed that Doze was the culprit for THAT specific problem. But it doesn't mean it's related to your alarm issue though.
[X 2014 Original Android Development] BootloopedMillennials:
Did 3/18 update (today) break root for some apps?

Apps like Adaway and Doze Settings Editor. Root is working for Amplify though. Tried toggle in developer options and in app settings.
[X 2014 Original Android Development] zax10:
For me the FC happens after a nights sleep and when I try to turn the alarm off.
[X 2014 Original Android Development] :
It makes no difference if the alarm goes on after a night or if it's set for 2 minutes later. I cleared cache and app data, gave it all the permissions i could and it still crashed.

I took some logs, but have no idea if this is what a dev needs. Please tell me if you need anything else.
[X 2014 Original Android Development] testkeys:
Well I don't know for sure, but it's been hectic the last couple days here...

I was on 0315 I believe then suddenly, I realized that I couldn't browse many of my phone sdcard files from the PC through USB and among the, a recent 2.5GB nandroid backup (could see it on the phone but not from the PC). I then suspected that something got corrupt and I used Fastboot to go back to stock then restored another older nandroid then update to 0315 again.

I thought everything was fine for a while until earlier today, I decided to make another backup before updating. Reboot to recovery (2.8.7.0 - same as ever) then stuck on TWRP splash screen! Fastboot flash recovery and erase cache and user data (again lose all my files) then restored that same nandroid again, then update to 0318.

Knowing that the version of my 3rd party file manager from the nand is problematic, I uninstalled it. Then I used CM file manager wanting to install a different version : black screen on CM file manager and can't install it. Download that apk agaon and use the CM download manager to install it just to realize that the old and trusted 3rd party FM no longer works...

Someone mentioned to me that many have reported similar issues with CM this week (files not visible through USB, TB backup not restoring stuff properly, root issues, ...). So I'm now back to 0310 and I'll stay on it until I'm 100% sure I'm problem free...

So I'd susgest to people to either wait a bit to update or if you're adventurous, at the very least, backup first and keep your nandroid in a safe place...

I swear, this is the first and last phone I have w/o an ext-sd. Only internal memory is nice because file transfer is fast and it's easy to keep tidy and organized, but when problems happen, it's a real pain to lose your apps data that nandroids don't safeguard...

---------- Post added at 09:26 PM ---------- Previous post was at 09:18 PM ----------

I'm no CM dev, but giving a log is always the right thing to do as it is more 'respectful" to them than just saying it's broken....

If they need more info or a better log, at least they know that they can ask you.

Geez! almost 4:30AM... guess why I did not take logs while on 0318 as previously mentioned...
[X 2014 Original Android Development] Gus Ghanem:
I just noticed my CM File Manager is totally blank, just a white screen with status and nav bars, though I can access internal storage files and folders via USB to PC.
[X 2014 Original Android Development] aidanand:
Is anyone encountering WiFi and Bluetooth connectivity issues with the 3/18 nightly? No issues with my CM12.1 and iOS devices. Thanks!

EDIT: Resolved with the 3/19 nightly.
[X 2014 Original Android Development] jsgrrchg:
Someone know when the cm 13 snapshot will be release for this device?
[X 2014 Original Android Development] thousandecibels:
My wild guess based on past releases, in about 1-2 months min. :o
[X 2014 Original Android Development] Gus Ghanem:
I just updated to 19 March Nightly, and CM File Manager seems to be working fine, thank you.
[X 2014 Original Android Development] zax10:
Can you test alarm clock to see if it force closes. Set an alarm for like 1 min
[X 2014 Original Android Development] Gus Ghanem:
I never use alarms, so this is the first time I set one, and as everyone is asleep, I kept the phone silent... The alarm went off silently, and I kept the screen pulsing for over a minute, there was no crash, nor any error.
[X 2014 Original Android Development] :
Yes, alarm is working fine on the 0319 nightly.
[X 2014 Original Android Development] Starsurver:
works root for you with the latest nightly?

For me isn't working[emoji30]

Gesendet von meinem XT1092
[X 2014 Original Android Development] tanishque italia:
Yes
[X 2014 Original Android Development] thefroyo:
I am experiencing issues with Smart Lock since upgrading to CM 13. The phone randomly locks on trusted places. Is it just me, or is it a more common (well-known) issue?
[X 2014 Original Android Development] BootloopedMillennials:
This was fixed in 3/19 update.
[X 2014 Original Android Development] salaesp:
I had the same issue on 0317 build.
[X 2014 Original Android Development] thefroyo:
I have searched the forums more broadly, and it seems that Smark Lock has issues on other devices as well - even on stock. It works very well with bluetooth, but fails frequently when using the location to unlock, which is exactly my experience. So, maybe not a CM issue. I will try to add more locations surrounding my actual unlock location and see if that works better.
[X 2014 Original Android Development] awacker89:
Camera working for me in Moto Camera App with 11/28 build. Limited testing, but haven't gotten it to FC yet.
[X 2014 Original Android Development] Tommebaas:
The Whatsapp recording bug is also on 5.1. I'm still on Lollipop and it happens all the time.

Sent from my Moto X
[X 2014 Original Android Development] Lebo-Wog:
Moto camera is not working for me.

I didn't have any issue with it on 5.1
[X 2014 Original Android Development] mycontradiction:
For some reason my phone is not entering on Deep Sleep mode.

Anyone else having this problem?

Enviado desde mi XT1095 mediante Tapatalk
[X 2014 Original Android Development] awacker89:
Turn off "Wi-Fi Scanning Always Available"

---------- Post added at 02:19 PM ---------- Previous post was at 02:17 PM ----------

Yeah, mine isn't working now either. Took a couple photos without FC on first boot then it started doing it again.
[X 2014 Original Android Development] dunklesgemut:
somebody post antutu's points with cm13? i use 6.0 br
[X 2014 Original Android Development] philneo2:
Temporary solution for the camera use Snapchat and can take as many pictures as you want.
[X 2014 Original Android Development] Xdevillived666:
Not working for me. Camera i fc'ing no matter what
[X 2014 Original Android Development] Lebo-Wog:
Both the camera bug and the whatsapp bug are there in the 29 nightly...

Edit: i think at least the camera bug should be placed in the OP under the "known issues" section.

I will be doing more testing regarding the graphical glitching issues (double tap to like an Instagram picture causes glitching on the screen), themes not installing problem, and the landscape mode navigation bar mesh up.

Edit 2 : the graphical glitches are still there.

The navigation bar is still behaving weirdly in landscape mode.

And the themes are still having issues to install. (Example h2os theme, was working fine on the 24 nightly)

Edit 3: I found a new bug, if you plug in the charger while the phone is off, you only get a white screen with an empty battery icon in the middle (no animation, and no percentage), and the screen stays awake with no way to turn it off.

And here are a few geekbench 3 tests.
[X 2014 Original Android Development] Bl4ckX:
Instead of posting which bugs are still present, everyday again, you might want to check out cmxlog.com/13/victara/. If you can't find anything about any camera bugfix you can consider it not being fixed.
[X 2014 Original Android Development] halfsoul:
Anybody else having issues Chromecasting?
[X 2014 Original Android Development] Lebo-Wog:
This rom is in early development stages.

And it needs testers.

And i am a tester.

Testers report bugs.
[X 2014 Original Android Development] Lunatiic:
I don't want to be rude or anything, but I've been an XDA member for long enough to know that many people don't know how to see and comprehend github commits. Hell, a great deal of users barely know how to properly flash a ROM or a Custom Kernel... But I get your point. Also, many changes on github aren't directly related to a bug itself but they could indirectly cause it.. I remember last year when I was helping a dev. from the Xperia S forums to understand why music wasn't playing on both headphones and speakers, and it turned out to be the compilation method he was using, nothing at all to do with music or drivers or anything... another one was that the camera viewfinder would show up some messed up images even tho the pictures and recordings taken were normal, and turned out to be a bug in a Continguous Memory Allocation (CMA) implementation on his, again nothing to do with camera, drivers, etc..

I think that reporting bugs isn't actually a very helpful idea for the developer... logcats, dmesgs, last_ksmgs are much more helpful, but since he ain't here, they have no use but to discover what causes the bug and keep it for ourselfs. Reporting bugs, as the users above are doing, is helping regular users to decide either to flash or not CM13 (Including me). Also, the developer could commit a change on the cmxlog website but the bug could still persist.. so :silly:

I'm at Stock 6.0 and waiting for a more stable release to flash CM13 since the snapshot release should take a couple of weeks, so I've been following this thread and the one at X 2014 General to see if it's stable enough or not for my taste.
[X 2014 Original Android Development] Netux:
[MENTION=5090482]Bl4ckX[/MENTION] Thank you for saying this, and please, people, stop reporting problems and bugs because you have to remember that CM13 is still a NIGHTLY so many bugs are expected, even the CM team said that it is completely useless to report bugs with logs for nighties, don't loose your time.
[X 2014 Original Android Development] Lebo-Wog:
I don't understand why this thread exists then?
[X 2014 Original Android Development] Netux:
Everything but reporting bugs about nightlies, such as help, suggestions etc... :)
[X 2014 Original Android Development] crpalmer:
Despite what the last two posts say, please continue to report bugs and absolutely provide logs when doing so.

Invisiblek and I do both read this thread and we work to fix the bugs (mostly him, but I try to steal a little credit too).

Android M has been rather a challenge unless you have a vendor release of M, along with the corresponding kernel source code. The good news is that by being on the bleeding edge we are actually making significant contributions to almost all CyanogenMod supported devices and making them better for M!
[X 2014 Original Android Development] vpxf:
I'm also waiting for a more stable release as I need my phone to be 100% all the time. But as I was going to say, where did you get stock and is it for xt1095? Rooted?
[X 2014 Original Android Development] Lunatiic:
I'm from Brazil and the 6.0 OTA has already rolled out here for retail models (XT1097). I think you can flash it, but you have to flash the correct modem later, check the Marshmallow thread on X 2014 General. I'm not rooted, yet, but there is a way to get root access. Beware tho, the firmware is packed with bugs (small ones, but still annoying) and has decreased in performance: scrolling lags a lot on certain apps, like whatsapp and play music, and some animations are considerably slow, like on the dialer. Those small bugs and performance issues, coupled with CM13 dope features like Color Calibration, Theme Support and Multi Window Mode are making me want to flash CM13.
[X 2014 Original Android Development] Amisuta:
Anyone know anything about the minimized Google search bar?
[X 2014 Original Android Development] Lucas Lucena:
Root

The root does not work for me. even turning on developer. Message missing binary
[X 2014 Original Android Development] theblakdavid:
Are you trying to use SuperSU by any chance?
[X 2014 Original Android Development] Lucas Lucena:
No. Some applications show me this message. But I read a Past comments and has been corrected in the night 03/19.

---------- Post added at 11:54 PM ---------- Previous post was at 11:53 PM ----------

A doubt. By placing the brightness on the screen minimum is a little "Purple". Because?
[X 2014 Original Android Development] theblakdavid:
Check if night mode is on in settings or in notification drawer.
[X 2014 Original Android Development] Lucas Lucena:
It's deactivated.
[X 2014 Original Android Development] JnNn98:
I think its just the hardware, on stock lollipop the screen also had a purple tinge at extremely low brightness
[X 2014 Original Android Development] Lucas Lucena:
I have FC missed calls
[X 2014 Original Android Development] :
On 03/19 nightly whenever I unplug or plug headphones the cm music app crashes. Even if I am using a different app. And on Verizon my connection seems to be getting worse and worse with every nightly
[X 2014 Original Android Development] bornlivedie:
not here

wipe and reflash
[X 2014 Original Android Development] misterkickass:
The persistent Skype camera problem seems to have been solved in recent nightlies.

However, it appears that my phone thinks it is stuck in Do Not Disturb mode. The icon indicates the option is switched on and whenever I change the volume it also offers to disable Do Not Disturb, but neither selecting "End Now" nor pressing on the icon in the status bar quick settings does anything. At the same time, the phone is not in Do Not Disturb mode, since I receive all calls and notifications normally. Anybody encountered this before? 3/21 nightly, but started with 3/19. Reflashing did not alleviate the problem.
[X 2014 Original Android Development] bornlivedie:
Not here. Just tested.

Do you use themes/xposed modules?
[X 2014 Original Android Development] testkeys:
I might very well misunderstand the commit's intent, but from reading the strings and other bits, it truly seems like there will now be a built-in firewall in CM!!

http://review.cyanogenmod.org/#/c/135445/

Woohoo!

Well..., maybe not full-blown FW, but the ability to control individual app's data/WiFi connectivity will/wouldl be a VERY nice addition indeed...
[X 2014 Original Android Development] testkeys:
Yes it is!

On March 22nd nightly, longpress any app from the main PrivacyGuard list - Internet section at the bottom:

Nice!
[X 2014 Original Android Development] thefroyo:
After a few days of playing around, I could not get Smart Lock to work hassle free. Even when I add more nearby locations, I have to unlock the phone approx. every second try. Maybe the next android version will improve the situation.
[X 2014 Original Android Development] ATaRiii:
I would like to know if the screen cast function is ok in recent nightlies. On 03/12 nightly, i see a error mensagem every time i try. To me, this is fundamental to update my system.
[X 2014 Original Android Development] Gus Ghanem:
No, screen cast still does not work from the CM options, nor from the Google Cast app. Mrach 24 Nightly.
[X 2014 Original Android Development] ATaRiii:
Thank you man. I really need this function. Still waiting.
[X 2014 Original Android Development] R2D2-AKU2:
I'm out of storage memory (16gb version). I'm using about 2.5 GB in /sdcard/. Something in the system must be taking up the rest. Any idea what that might be?
[X 2014 Original Android Development] C-Ph87:
I'm geting some serious lags in Google Plus app.

My device is XT1097 (brazilian) but in settings is listed as XT1095. Is that right?

All the rest is just fine.
[X 2014 Original Android Development] theblakdavid:
Do you have any backups?
[X 2014 Original Android Development] R2D2-AKU2:
Twrp backups are on USB otg.
[X 2014 Original Android Development] nandroidz:
Guys any of you have Ok Google from any screen option. Mine seems to be missing. BTW i flashed Open Gapps Aroma package (over a clean install).
[X 2014 Original Android Development] kaktusmaier125:
First freez and then reboot

Doe's someone has same on 24 nightly s
[X 2014 Original Android Development] Tinchoska:
Guys which nightly Is better on battery and performance?

Enviado desde mi XT1097 mediante Tapatalk
[X 2014 Original Android Development] kaktusmaier125:
Latest
[X 2014 Original Android Development] Tinchoska:
20160325 right?

Enviado desde mi XT1097 mediante Tapatalk
[X 2014 Original Android Development] mikeoswego:
Same here. I've been away from CM for awhile; did OK Google from any screen ever work even when you could select it?
[X 2014 Original Android Development] testkeys:
At Chris or Dan,

( [MENTION=3857343]crpalmer[/MENTION] or [MENTION=2385005]invisiblek[/MENTION] )

Do you guys know what happened to the ic_settings_gestures.xml vector drawable on our rom? I'm currently running on 0322 and it is nowhere to be found in the Settings.apk.

Do you guys know what now replaces it - if that was intented?

I've diff-merge'd March 10/March 22 and it's obviously now missing. I've looked at all the Settings.apk commits list since March 10 on Github, but couldn't find anything related to this.

I've ask on another xda thread and someone with a Oppo 1+1 (also having Gestures available on his device) still has that drawable included.

Here's why I ask:
[X 2014 Original Android Development] vinydasilveira:
I'm having this problem in Ridge Racer Slipstream and Real Racing 3
[X 2014 Original Android Development] bluscript:
Android Auto on XT1092 working for anybody?

I'm experiencing serious problems with Android Auto. For some reason, under CM13 the app says that my XT1092 (RETDE) is not compatible and refuses to work. No such problem with either CM12.1 or official Marshmallow-ROMs: it worked perfectly fine both with the last CM12.1 snapshot as well as with the official VICTARA_RETDE_XT1092_6.0_MPE24.49-18. Something must be different about CM13...

Can anyone confirm this problem or knows of a work-around?

I've been searching for similar reports for a couple of weeks now but couldn't find any mention of it. Am I the only one trying to use Android Auto on the XT1092 and CM13? I'm through multiple clean re-installs, having tried everything I could think of including different GAPPS bundles. Whenever I flash the official ROM or CM12.1 it works, CM13 however is a consistent no-go.

Any hints or simply info on the technical background would be massively appreciated! Thanks in advance!
[X 2014 Original Android Development] Tinchoska:
Guys I'm still having this problem with time, every time I reboot clock goes 4 hrs back, if it's 6pm it goes to 12pm and when it connects to Internet clock set to right hour... any idea how to fix it? And still can't get super su working

Enviado desde mi SM-T700 mediante Tapatalk
[X 2014 Original Android Development] vinydasilveira:
Hermano. I think everyone here has this problem since Cyanogen12. They say it is something related to the Cyanogen ROM and TWRP recovery, however I have used other Custom recovery and the problem persisted. But when I use the stock rom does not happen that, even using the TWRP.
[X 2014 Original Android Development] lauren:
20160326-nightly boot loop

hey guys

anybody else getting problems with this? just did normal dirty flash with wipes and all, rebooted and just got stuck at the lil dudes face for at least 10 mins before i restored from yesterdays flash

no custom anything - just stock CM13 nightly

thanks

[edit]

ok even restoring from yesterdays backup caused the same bootloop - it does the "optimizing apps" thing then goes back to the lil dudes face and just sits there for at least 10 mins

any ideas?

[/edit]
[X 2014 Original Android Development] Tinchoska:
Yeap, on stock con y do not happened... I thought they've fixed that, LOL. Another thing, WiFi do not connect until I unlock Sim and screen, on stock it connects just after phone boot up. I don't know if its a bug or not, but I comment....

Enviado desde mi XT1095 mediante Tapatalk

---------- Post added at 08:57 AM ---------- Previous post was at 08:56 AM ----------

Did you tried clean flash?

Enviado desde mi XT1095 mediante Tapatalk
[X 2014 Original Android Development] testkeys:
Here's a regression [well, it's one for me anyway since I've been using LockClock's Yahoo weather since basically CM7 era..]:

i noticed about 24 hours ago while running 0322build that the weather stopped updating. I thought it was just a temporary fluke w Yahoo, but I tried to refresh many times today with and withoit using a VPN: it won't refresh at all. Installed 0326 build on top a few hours ago, didn't help. Removed widget, reset city,... same.

Partial log + my now permanent fair weather conditions and forecast...

:(
[X 2014 Original Android Development] lauren:
no i ended up restoring my backup from 20160322-nightly and that works fine

has something changed since then that requires updated TWRP or something?