yashsingh1/xdaforums huggingface dataset:
[X 2014 Original Android Development] alediniz:
Any way to install Supersu on Cm13?
[X 2014 Original Android Development] Vicalvi:
No need, the ROM itself already comes with native root, just activate in the developer options.
[X 2014 Original Android Development] alediniz:
I know and use that, but I prefer Supersu. Better control and interface. Any way to use Supersu instead cm root?
[X 2014 Original Android Development] thousandecibels:
Heads up, Snapshot release is up! ??
[X 2014 Original Android Development] t0per666:
Nice! It's up guys! Gonna download it for backup purposes still gonna use cm14.1.
[X 2014 Original Android Development] Vicalvi:
Nice, changelogs?
[X 2014 Original Android Development] Cybertron713:
Is there any way to change my cmupdater channel find snapshots AND nightlies?
[X 2014 Original Android Development] iron maiden:
Hello what gapps recomended? Very thanks

Regards

Enviado desde mi XT1092 mediante Tapatalk
[X 2014 Original Android Development] thousandecibels:
I use Stock 7.1 personally as I prefer vanilla Android.

For minimal setup you can use pico gapps. It's a bare bones package to support basic Google Play functionality and won't install Google bloat.

---------- Post added at 07:22 AM ---------- Previous post was at 06:50 AM ----------

No change-log released yet. I heard the CM logs for 13 branch got messed up.
[X 2014 Original Android Development] Vicalvi:
Some times when I do some video recording, when I press the stop the camera application hangs and the phone reboots, this does not happen every time, sometimes it works normally, someone with this problem?

This happened in the previous version and this happening in this new one as well.
[X 2014 Original Android Development] testkeys:
The CM13 Alarm is unreliable

Just heads up guys: do not rely on CM13's timer or alarms for anything important.

I've been using the alarm twice daily for the last 3-4 months and had no particular problem with it. Then suddenly today old, without any special system change, CM11-time alarm issues resurfaced.

I went for a power nap and set a time for 1h35min. When I finally woke up, I grabbed the phone and turned it on and then timer started ringing as the screen lit up. The screen was showing -6 minutes and a few seconds. So for that time, the alarm never woke up the phone and no sound was played.

Even worst, my regular daily alarm that was set for around 20 minutes later never gave me the usual pre-alarm notification (with the option of dismiss now) and also never rang like it was just turned off when it wasn't.

Finally, I performed a quick test just like many of us CM11 users at the time would do to prove the problem:

- set the timer for 6 seconds and press play;

- press the power button once to turn off your screen then quickly press it again to turn the display on and one last time to turn it off;

- wait for the remaining 3-4 seconds and see if the alarm will ring

--> well, it didn't and when I finally turned on the screen again, same as above, the ringer when of when the sceen lit up but the timer showed a negative (overdue) time again [pic].

This last quick test doesn't always fail, but believe me it does sometimes and really, just a single time is one too many.

This was observed running the last nightly build and has also been reproduced (sort test) on the newly released snapshot. VERY DISAPPOINTING.

[and btw, no need to tell me to switch to CM14 because I won't. And if you were going to say that; I tell you: go on and open a specific CM14 thread]

I don't know if it is related at all and if this could be helpful for our maintainers, but I saw this page on which someone was mentioning similar issues with CM13 and a 3rd party app. One guy submitted a commit for a fix in this regard:

https://github.com/citiususc/calendula/issues/52

With regret, I will now have to rely on a third party alarm.
[X 2014 Original Android Development] ordnas888:
Hello I would need a kernel to 13 cm with the possibility of lowering CPU frequencies ... thanks
[X 2014 Original Android Development] [] AL []:
Sad times...

R.I.P. CyanogenMod.

Long live LineAge OS
[X 2014 Original Android Development] Sdobron:
Tried to reproduce the timer problem. Could not be duplicated once in ten tries. Note I use the gapps mini package which replaced the CM clock app with stock Google clock app. Maybe you should do the same to avoid using a 3rd party alarm.
[X 2014 Original Android Development] Sdobron:
Ambient Display is broken on the snapshot build. Clean flash. Anyone that can confirm?
[X 2014 Original Android Development] Cybertron713:
Working fine for me, so it's not necessarily your ROM.
[X 2014 Original Android Development] Sdobron:
Strange. Thanks! Didn't work in 12/04 build either but works fine in CM 14.1...
[X 2014 Original Android Development] testkeys:
Well thanks for trying to reproduce this and thanks for the suggestion: it is a good idea.

The problem is not always present and like often for bugs, something or some special condition must trigger it - I just can't pinpoint that yet.

Anyhow, I didn't feel like downloading and installing a new gapps package, so I just downloaded Google Clock from the Playstore (and disabled CM one by renaming its file extension) and will give it a spin. I'm not sure it is much different, but at least from the version number, it seems newer. It is also using almost 3 times the space once installed, but being a Google app, this ain't too surprising (and obviously, it is also made to accommodate more phones/dpis/rom versions which explains the size difference).

Since I'm here, I'd just like to mention that I've noticed that the snapshot went backwards on two things from the latest nightly builds: 1- it uses the old DSP manager and not the (IMHO) much better AudioFX for Cyanogen OS and 2- it uses the older theme chooser version - but which I MUCH prefer.

And yes it was a very sad news to learn that CyanogenMod is now a thing of the past. Even if its legacy will survive under the new Lineage OS name, it's been a great 8 years and it will be hard to wrap my head around the fact that CM is 'no more'.

[emoji22] [emoji23] [emoji32] [emoji25] [emoji30] [emoji31]
[X 2014 Original Android Development] hrncs:
hello, im install the snapshot cyanogen 13.0 20161221 but the LTE is not working, anyone with this problem, can be fixed?

Thanks! and happy new year!
[X 2014 Original Android Development] danielcepa:
Delete and create new APNs according to your network provider. CM default APNs are notoriously unreliable !
[X 2014 Original Android Development] hrncs:
Wow, in first time looks ok, but i delete all APNs and create new and LTE is OK!

Thanks!

Happy new Year!!!

please, help me, the videocamera is not working, only record one video, and the next try to open the cam freeze and restart the android all time.

Thanks
[X 2014 Original Android Development] NikitaUKR5:
Where can I download this rom?
[X 2014 Original Android Development] xabr3:
https://drive.google.com/open?id=0B9-A7RHWsaU-M01tWFpnek1jVkE
[X 2014 Original Android Development] NikitaUKR5:
Thanks
[X 2014 Original Android Development] dego_:
I'm not sure someone can help you. This video recording bug persists on all custom roms for this device (both CM 13 and CM 14 based). My moto x runs Lineage 14.1 and I'm still waiting for this annoying bug to be solved. Maybe I should start learning android development skills if I want it done ... haha
[X 2014 Original Android Development] [] AL []:
I've never had any issue with my camera.

Been running CM13 from day 1 and tried maybe 6 or 7 -all fully functional- camera apks also....

So maybe instead of waiting for someone to fix this for you, you should first learn to grab a logcat and/or flash a stock firmware. Because if clearing everything and returning stock doesn't solve your Canberra issue, that mostly means that your problem is with your hardware....

I think you'd better practice your reading skill before contemplating acquiring development skills.

[emoji57]
[X 2014 Original Android Development] dego_:
Talking about Motorola Camera (also sometimes called stock)?
[X 2014 Original Android Development] [] AL []:
You're on a CyanogenMod rom discussion thread.... So by default, you'd be talking about Snap camera.... How were we supposed to know which camera you were referring to?

Anyhow, I have both CM's (Snap) and Motorola Camera operational and equally used for the longest time on my phone...

Read my last response again: I was not talking about returning to stock camera only; you have to completely erase your phone's system and data and then flash the stock bootloader, recovery, radios and system. ...as they would have been on a brand new pbone.

Good luck.
[X 2014 Original Android Development] dego_:
I appreciate how you care about my reading skills. Actually I referred to a bit different rom. You can read it above, can’t you?

Yes yes, my bad… I’m leaving this neat thread now, since it’s not a Lineage 14.1 space.
[X 2014 Original Android Development] [] AL []:
I can read very well; even between the lines - thanks.

Yes, yes please go find another fine thread where you'll be able to keep hoping someone magically solves the problem you carry over from rom to rom. And keep on not describing anything and lecturing people that actually suggest you stuff to go try and learn. You'll go far, I'm sure.
[X 2014 Original Android Development] dego_:
lecturing? lol

anyway, I'm out of here. stay awesome.
[X 2014 Original Android Development] NeriL:
Anyone has a working link?
[X 2014 Original Android Development] papsr6:
Nobody a working link?
[X 2014 Original Android Development] Cybertron713:
Latest release of CM 13: https://mega.nz/#!j50FVQpA!FMH6Yf-kBiDfQc7l_DefbF6K-8idJ3e-C3s86zp5TYg
[X 2014 Original Android Development] papsr6:
Thank you ...

I try the rom and i cant install gapps.

I have FC and reboot when i change the camera 16.9 and have touch delay.

I dont know why.

Have you a solution?
[X 2014 Original Android Development] Cybertron713:
Unfortunately, I do not. I never experienced any of those issues. Best I can suggest is to try flashing it, again. If that doesn't fix it, I'm sorry, I don't have the knowledge to be of further help...
[X 2014 Original Android Development] papsr6:
Its ok...thank you very much .
[X 2014 Original Android Development] thousandecibels:
Which version of GApps?
[X 2014 Original Android Development] papsr6:
Arm 7.1 pico...
[X 2014 Original Android Development] thousandecibels:
Lol you're on Android 6.0 and you're using Android 7.1 GApps?
[X 2014 Original Android Development] papsr6:
Ah sorry 6.0 pico i want to write.

I am nor beginer and i came from LG G4 2 years mods with all custom roms.

This device have a lot of roms but all custon roms i have touch delays except LITE STOCK ROM.

I dont know why.
[X 2014 Original Android Development] LexX-V:
The last official build mirror - Snapshot 20161221
[X 2014 Original Android Development] netizenn:
something strange happened to my MX 2014, I losted the root acess. :-/

I cannot work in recovery (TWRP or CWM) in order to install anything. CWM tell "can't mount the scard"

I rooted the device with multool moto x2015 with 5.1. And now How can I get rooted again, in CM13? :(

Thanks
[X 2014 Original Android Development] nandroidz:
Do a fresh install of the rom
[X 2014 Original Android Development] netizenn:
I can't, because even I wipe system/dalkiv/cache and data, when I choose install, CWM send me that message, and TWRP I can't explorer cmupdater directory. It's stuck in the directory downloads, and the option go back (up level),just disappeared.

The solution is flash with fastboot to 5.1?

:(:confused:
[X 2014 Original Android Development] nandroidz:
Yup boot into fastboot and use adb to push 5.1 img
[X 2014 Original Android Development] netizenn:
Mann :( All that work again??

There is not even another way? Dammm

How the hell It lost root acess and get all messed up in recovery? The system/device is workin flawless... :(
[X 2014 Original Android Development] nandroidz:
Go download the latest TWRP and flash it using adb. It should work
[X 2014 Original Android Development] netizenn:
Nothing! Its stuck in any version in directory Downloads, and there is files of the last CM13 and the gaps, but in recovery that directory is empty, and stuck.

Dammm
[X 2014 Original Android Development] surrealjam:
Ahh OK - I'm only trying with the standard version from the Play Store (2.x). I guess 3.x has only been released for Nexus phones as it has not been tested with anything else.

---------- Post added at 01:16 PM ---------- Previous post was at 01:14 PM ----------

Yeah, I think some people reported this on CM 12.1 as well but I have only begun to notice since CM 13. Obviously the network updates the time after about 30-60 seconds but I get an error on WhatsApp to tell me my time needs to be adjusted.
[X 2014 Original Android Development] drwhitney:
I got stuck without the option to go up a level in TWRP explorer once; I worked around it by going into terminal within TWRP and renaming the directory. (for example: "mv Downloads Downloaded") and then explorer couldn't find "Downloads" when I opened it again, so it defaulted to its parent directory. I realize this only helps one of your issues, but thought I'd chime in.
[X 2014 Original Android Development] nanca:
It's easy to flash 5.1 if you use a script. Instead of issuing a command for each line, type all of it on a bat file and the process can be automated. But the ADB, 5.1 image files and this script should all be placed in the same directory.
[X 2014 Original Android Development] mikeoswego:
I wrote at length about this problem in 12.1 and the base issue is that the Qualcomm chipset in our phone does something with the timestamps that isn't properly documented. The time and certain data files that help the phone set the correct time at boot are not being created correctly. CM is using the time_daemon program from the Moto rom that creates those files but for unknown reasons they aren't correct. I've spent a few hours trying to figure this out with no luck. I suspect our device devs have more pressing issues to work with for the time being.

On 12.1, I commented that if a copy of the file /data/time/ats_13 to /datat/time/ats_2 is made, the time would then be correct in TWRP and upon a reboot. This has changed with CM13, having that copy seems to be no longer used by the ROM at start up (the last time I checked this was over a week ago.)

For the devs: I notice that now the time_daemon is only creating ats_8 and ats_13 files (most of the time.) TWRP apparently uses ats_13 when no ats_2 or ats_1 file is found and gets the correct time. Every once in a while (randomly, once in the last couple weeks), the time_daemon creates an ats_1 file that causes the TWRP time to be incorrect.

---------- Post added at 11:26 AM ---------- Previous post was at 10:51 AM ----------

This isn't an issue with root, recovery always has what we call root access to the file system.

The sdcard on our phones is actually a part of the /data filesystem and is also called internal storage.

When recovery can't access the internal sdcard, something has gotten messed up in the files that tell the phone where to look for various parts of the filesystem. Often flashing a different rom will fix the problem.

Do you have a USB-OTG drive? If so, put the ROM zip on it and flash it from there. The reflash might fix it. If not, do a complete a backup to the USB-OTG drive, then wipe data, then flash cm12.1 or a TWRP flashable stock rom for your phone, let it boot up. Then go back into recovery, presuming the access to sdcard problem is fixed, restore the backup you made (only boot, system, data, not efs) and with luck you'll be all restored to where you were with CM13 and the access problem in recovery will continue to be fixed.
[X 2014 Original Android Development] netizenn:
Still on the recovery

I do not know if it's something strange about the recovery, but at least this had never before happened to me. I notice that there are three folders that get stuck : Android, Notification and Downloads. File manager to navigate between the various folders, you find the option "Up on Level"; in these three folders this option will disappear. The only way to get out of there, it's back to "advanced" and press "Reload Theme" and so out of these folders that get stuck and beginning to navigate to other folders. But whenever I return to enter one of the three folders that said, always get stuck and have to return the option "Reload Theme". Strange

But the recovery apparently works ok. Let me back up and Restore

At least I can install any update (folder cmupdate) and install gapps.

P.S The CM13 highly rolls both on this device, as in my XT1092.
[X 2014 Original Android Development] gianboy:
That happened to me once

It was because I dont know why some .nomedia files got corrupted, even on my computer I couldnt access those folders.

Wipe data didnt work, i had to reinstall TVE stock rom through adb
[X 2014 Original Android Development] netizenn:
Well I think just somehow find a solution. In ES explore I just copy a txts files and logs (some junk) to the folders I mentioned that gave problems in recovery. I boot into recovery, and no longer the case the problem of getting stuck. This speaking in TWRP, as the CWM I don't know if the problem remains (while trying to install from sdcard, was given to me a message that could not mount sdcard), but honestly, I'm just a littletired of walking around on the device because of this issue. At least for now everything appears to be working properly.

That's all for now :)
[X 2014 Original Android Development] Tommebaas:
Weird. Maybe the rom needs to settle for a few days.

Sent from my Moto X
[X 2014 Original Android Development] surrealjam:
http://review.cyanogenmod.org/#/c/123097/

As of the next nightly, over counted stats will be ignored.
[X 2014 Original Android Development] Tommebaas:
"Quadruple battery lifez"

That's all I need.

Sent from my Moto X

---------- Post added at 11:01 PM ---------- Previous post was at 10:06 PM ----------

Has anyone found a solution for the wifi battery drain?

I found this http://xdaforums.com/google-nexus-5/general/guys-call-wifi-battery-drain-6-0-t3219870.

They go to location -> tap settings and disable wifi scanning.

But it still drains pretty bad.

EDIT:

The people in the same thread say that the latest Google connectivity services app fixes the wifi drain.
[X 2014 Original Android Development] Tommebaas:
6.0.1 got released today!

Sent from my Moto X
[X 2014 Original Android Development] nanca:
And seems to have been merged. =D
[X 2014 Original Android Development] lifty95:
Is the flashlight gone in 12/07 or is it just me?

Gesendet von meinem XT1092 mit Hilfe von XDA Forums
[Galaxy Note 3 Q&A, Help & Troubleshooting] Jcamden420:
Hi I have a note 3 sm 9005 on t-mobile network unlimited 4g data.

When I tether with cm 12.1 to my laptop websites go super super slow yet on same laptop if I do a speed test once the website loads I get 30 megs and on same laptop on utorrent I get 3 Meg a second download speeds. Why would I get super fast download speeds and my websites Barly load and go super super slow

Thank you guys

My first post I like this place got cm 13 here

Any ideas?
[Nexus 6 Android Development] fhem:
This is my own custom ROM for the Nexus 6 called noobbuilds. It is an AOSP 6.x based ROM with a few added useful features. I am an old retired guy who enjoys the hobby of builiding and using his own roms. I'm just sharing my rom not competing with the big the boys. I intend to add features and update ROM as AOSP updates.

​

.

N6 Noobbuilds initial M release date 2015/11/24

NOTE: See Changelog in Post #2 below for susequent releases.

Initial Release Features

*Based on AOSP Android 6.0_r26

*Pre-rooted with SuperSU 2.52. Thanks [MENTION=631273]Chainfire[/MENTION]

*SuperSu backported to Settings

*Bionic Busybox

*Advanced reboot power menu

*Native clear all/recents enabled

*Adawy 3.1 (55) built from source

*Kernel Adiutor tester version

*Stock M boot animation

*Stock M default wallpaper

*Stock M blobs -- thanks [MENTION=4395895]BeansTown106[/MENTION]

*Show apps being optimized during initial boot

*Added build date to about phone

*Developer options enabled by default

*Added option to hide adb notification

*Allow apps from unkown sources enabled by default

*Enabled battery charging LED.

*Layers 4 support

*Misc tweaks

*Stock kernel built from source.

*Forced encryption disabled and verity warning removed.

*SELinux enforcing. Thanks to [MENTION=4395895]BeansTown106[/MENTION] and [MENTION=3357040]Imoseyon[/MENTION]

CREDITS

Primary credits and thanks to [MENTION=4395895]BeansTown106[/MENTION] and [MENTION=1978554]zephiK[/MENTION] for their great work.

Also, there are far too many other people for me to thank and give credit here.

Please see my GitHub links below to see all who deserve credit.

Source:

1. Manifest

https://github.com/fwhem/noobbuilds_manifest

2. All repositories

https://github.com/fwhem?tab=repositories

Requirements:

1. Unlocked bootloader

2. Recommend installing the latest bootloader image from from here. FASTBOOT FLASH ONLY.

3. Recommend installing newest twrp (Ver. 3.0.2)

Install Instructions:

1. Download noobbuilds rom and recommended gapps. Thanks [MENTION=2915683]BaNkS[/MENTION]

2. Boot into twrp, make backup, and wipe (system, caches, data)

3. Flash noobbuilds rom and recommended gapps.

4. Boot up and enjoy!!!!

5. I restored the data partition from my twrp backup w/o any issues.

NOTE: The first boot and sign in can be a little laggy but all will be good. :good::good:

KERNEL NOTE: I have been using the ROM kernel but if you are going to flash another kernel please make sure it has been updated for aosp-6.0.1

Google camera note: I suggest flashing this for working camera. Flash camera w/ rom and gapps before first boot.

ROM Download:

https://www.androidfilehost.com/?fid=24588212152304934

My many thanks to those whose commits I used in my ROM.