yashsingh1/xdaforums huggingface dataset:
[X 2014 Original Android Development] mikeoswego:
Those should work. Google has gotten confused.

If you have a TWRP backup of your previous ROM, you might be able to restore that, go into settings->Backup and double check the settings are correct. Then go into Acounts->Google, make sure everything is set to sync and then use the 3 dot menu to sync now. Then flash CM13 and the GApps and see if Google then finds your old settings to restore when setup starts.
[X 2014 Original Android Development] salaesp:
It works everytime with the stock rom,
[X 2014 Original Android Development] leonardoafa:
Im having bluetooth issues.

I cannot lower or increase volume using device volume keys when playing through bluetooth. It happens on my Moto Deck, and on Tracks Air as well. when i lower the volume, nothing happens at all, when i try to increase it the audio almost blows the speaker!

Anyone else facing this issue??

Also when bluetooth is on, btsnoop_hci.log is created on my sdcard, and the bluetooth debug option isnt turned on in developers options.
[X 2014 Original Android Development] nandroidz:
It's a bug in AOSP 6.0.1. Linking volume control for Bluetooth devices in 6.0.1 caused this issue on some Bluetooth headsets. Hopefully it will get fixed by Google.
[X 2014 Original Android Development] netizenn:
When I rotate to my right the device, i got this issue on keyboard touchpad:

[IMG="rotateIssue"]http://s28.postimg.org/8wf32nxp9/rotate_Issue.png[/IMG]

[IMG="rotateIssue2"]http://s14.postimg.org/t66kmqspd/rotate_Issue_II.png[/IMG]

Is this happen to anyone? CM13 issue or my screen problem?

It doesn't happen in every rotation (to my right). In kodi see a movie everythig is fine, or even when I'm playing a game (exe RealRacing 3).

Anyone?
[X 2014 Original Android Development] Lebo-Wog:
If you read pages back, you would realize that it's an old bug, since day 1 actually, and since they ironed out most of the big things, I'm guessing this bug would be fixed soon.
[X 2014 Original Android Development] nandroidz:
This bug is present even on my Nexus 5. So i think this a bug across all CM13 devices.
[X 2014 Original Android Development] fleabus:
I'm running the latest nightly. The only troublesome issue I'm having is Hangouts isn't pushing notifications or updating until I open the app up, which is annoying. I'm not convinced this is a rom issue, but I wanted to ask anyway.

I did a clean flash and I'm using TWRP as my recovery.

Any suggestions?
[X 2014 Original Android Development] nandroidz:
Strange, i don't have any issues with hangouts. It works fine for me.

Which GAPPS package are you using.
[X 2014 Original Android Development] leonardoafa:
Thanks for the feedback my friend.
[X 2014 Original Android Development] fleabus:
OpenGapps stock version

Hmm. Sounds like I should reinstall something(s). What's the minimal way to "reinstall" what needs to be done? Do I need to clean flash the rom and gapps again? Just remove hangouts and reinstall? Install a more minimal gapps then add hangouts from the play store?

Thanks,

flea
[X 2014 Original Android Development] nandroidz:
I used the arm_6.0_aroma package. It has a sweet aroma installer. So just select hangouts in the setup and flash just that. Hope it works.
[X 2014 Original Android Development] Salo-S:
after using this ROM for a few days, I could conclude that:

- It is very fast! I thought I would have the same speed than the stock ROM but the experience was VERY BETTER

- I did not miss the Moto Voice.

-Thought that battery was better, but i have to charge my phone more times (maybe because now Moto X is more interesting?)

-The ROM is not fully translated. On PT-BR language you can see a lot of texts displayed in english.

-Camera seems OK to me (i use Moto Camera)

-Themes are a danger. I installed some in the play store and had a bootloop. I had to reinstall the stock firmware to fix this

Im going back to use The stock ROM, but i'll keep waiting to this ROM being more stable!
[X 2014 Original Android Development] nandroidz:
Cyanogen is working on translation. They said translation will be complete by the end of next month.
[X 2014 Original Android Development] Lebo-Wog:
Next time a theme causes a bootloop or system crashing, simply boot into safe mode and delete it.
[X 2014 Original Android Development] Salo-S:
Sorry for my noobish question, but there is a safe mode? Can be sound wierd but i never seen this on android.. How to boot on this mode? Thanks!
[X 2014 Original Android Development] nandroidz:
Just long press the Power Off option
[X 2014 Original Android Development] mrbock:
Has anybody have problems with the screen turning off? I mean, after the nightly from the 20151221 the phone will stay on forever if I don't explicitly turn the screen off.

---------- Post added at 06:55 AM ---------- Previous post was at 06:49 AM ----------

And when investigated, the settings look like this, where no option is selected.

https://drive.google.com/file/d/0B5m7qQiidOoxMWpLaWpWTjVQOTA/view?usp=docslist_api
[X 2014 Original Android Development] jooncheez:
Before I flash this, I have a question. Can anyone check if the livedisplay setting works in this rom?

It is a build in f.lux/twilight feature in Cm to protect your eyes at night.
[X 2014 Original Android Development] Lebo-Wog:
yes it is working ?
[X 2014 Original Android Development] lucasortlieb:
Hi, I made the compatibility test for manual camera, and it told me that my device isn't compatible. In some places I found that CM has the camera2 api implemented, but the incompatibility should be an issue in kernel level.

What I ask is if it would be fixed or implemented, since the camera in CM misses a bunch of possible features.

Enviado de meu XT1095 usando Tapatalk
[X 2014 Original Android Development] nanca:
hey mate. dig a little deep and you will see that camera2 api rely not only on CM but also on specific camera drivers (proprietary ones).

in other words, CM needs to have specific access to camera features and... only a few camera modules/devices supports that.

so, in conclusion: the camera module have to support those features and CM needs to have access to those "drivers".

i believe that it is not gonna happen to our device =/
[X 2014 Original Android Development] fredamsouza:
Solved. The problem is that if you just install it directly from Google Play, it doesn't installs the system libs needed to work flawlessly. But I managed to solve it by installing the zip found here:

http://xdaforums.com/moto-g-2014/th...ola-camera-t3187927/post62536982#post62536982
[X 2014 Original Android Development] Tommebaas:
I'm not getting notifications for my email and Whatsapp. I have tot manually open Inbox and Whatsapp go get messages.

Latest nightly, stock settings, clean flash with open gapps.

How can I fix this?

Sent from my Moto X
[X 2014 Original Android Development] lucasortlieb:
Some of the features are not working for me. I disabled double tap in status bar to sleep but it keeps activated, as well as double tap on power button for camera. The increasing ringing volume are not working too... All this little things are happening since I first installed CM13 last week.

Are this problems with the ROM and everybody is getting this? Or it's a problem only with me and I have to fix?

Enviado de meu XT1095 usando Tapatalk
[X 2014 Original Android Development] nandroidz:
Double tap to sleep works even when turned off. Rest of the things are working perfectly for me.

---------- Post added at 11:11 PM ---------- Previous post was at 11:08 PM ----------

Notifications are working fine for me. Try a clean install again.
[X 2014 Original Android Development] Lebo-Wog:
Slow mo camera doesn't work,

anyone has that working?
[X 2014 Original Android Development] nandroidz:
It's not working for me either
[X 2014 Original Android Development] :
We're almost there!

https://github.com/MotorolaMobilityLLC/kernel-msm/tree/marshmallow-6.0.0-release

OK, it's...

"Linux Kernel for Motorola devices using MSM-based chipset" MarshMallow source code.
[X 2014 Original Android Development] Tommebaas:
So Motorola is going to release the full source for the X 14?

That's good right?

Sent from my Moto X

---------- Post added at 01:00 AM ---------- Previous post was at 12:59 AM ----------

I'm noticing a strange bug on the 12/23 nightly.

I can connect to my wifi downstairs and to my wifi extender upstairs which are both password protected.

But when I want to switch between the two networks using the quick settings, it asks my password again for the network I already had my password entered for. This happens in the lockscreen and also when the phone is unlocked.

It does not happen when you go straight to the wifi settings.

Hopefully you understand!

Sorry for my English.
[X 2014 Original Android Development] abhay6547:
Why hasn't the landscape notification shade glitch been fixed yet? For those who don't know, if you go into landscape in most apps and pull down the notification shade, you will see a duplicate of it in the nav bar on the right.
[X 2014 Original Android Development] nandroidz:
It will get fixed eventually. Now that Moto has released the kernel sources.
[X 2014 Original Android Development] core720:
dont fix bug whatsapp hour?
[X 2014 Original Android Development] chazeon:
VSCO cam filter keeps loading even on latest CM ROM. Anyone get any ideas?
[X 2014 Original Android Development] nabor:
Hi developer, I found two bugs today:

1. Screen won't turn off if "User-aware display" is switched on. This bug happened in 5.x as well.

2. When quick switch a wifi ap(pull down the status bar and select a wifi ap through the drop list), always prompt password since it is already saved.

Besides, please add raw usb-otg support, thanks.
[X 2014 Original Android Development] fredamsouza:
Everytime when I finish a call pops up a message on my screen saying "Invalid number". But the call didn't had any problems. Anyone else with the same problem? It does not interferes in anything, it's just annoying...
[X 2014 Original Android Development] nandroidz:
It's a know bug.
[X 2014 Original Android Development] FreVDP:
That's not a Whatsapp bug, the phone just resets it's timesettings and Whatsapp reacts to it because the information is incorrect.
[X 2014 Original Android Development] core720:
Fix????
[X 2014 Original Android Development] FreVDP:
No, I don't know how to fix that, I'm just an idiot who knows how to install new roms.
[X 2014 Original Android Development] G4 Man2:
Am I the only one here that's not able to dirty flash any build past 12/22? TWRP gets stuck at "detected filesytem". Possibly due to this bug "https://jira.cyanogenmod.org/browse/NIGHTLIES-2155". Tried TWRP 2.8.7.0, 2.8.7.1, and the 2.8.7.0 available on invisblek's server and still no go.
[X 2014 Original Android Development] mikeoswego:
I just dirty flashed the 12226 nightly with no problems. I use invisiblek's 2.8.7.0 version of TWRP.
[X 2014 Original Android Development] G4 Man2:
Well, at least it's not an issue for most people. If anyone else has this issue a workaround is available here.
[X 2014 Original Android Development] MichelBorgess:
hey guys , i trying make a custom kernel for vic , but a having some random reboots .. i compile a test build without any features , just pure from source .. andd reboots .. whats happening .-.

Last kmseg

http://pastebin.com/uVvXwgZw
[X 2014 Original Android Development] salaesp:
Is anyone having a crash when trying to enter "data usage" option in settings menu? Im on 1226
[X 2014 Original Android Development] fleabus:
Just tried on same version. Even messed with various options. Worked for me. Dirty flashed to 1226 a couple days ago fwiw.
[X 2014 Original Android Development] salaesp:
I just did a fresh install without any gapps in order to test, and when I first enter, it works, but then I moved the limit bar and started crashing. The logcat is attached
[X 2014 Original Android Development] Tinchoska:
The problem is system hour, it's not whatsapp problem.... If system hour is bad whatsapp will tell you that something is wrong so you have to reset hour

Enviado desde mi XT1097 mediante Tapatalk
[X 2014 Original Android Development] Amisuta:
Is there such thing as a feature request here? I'd like a minor thing to be added to prevent the flashlight from turning on in the pocket.
[X 2014 Original Android Development] mikeoswego:
Here is an unofficial build of CM13 for Victara.

It includes commits up to "stagefright-plugins: Fix shutdown deadlock"

cm-13.0-20151230-UNOFFICIAL-victara.zip
[X 2014 Original Android Development] fleabus:
Thank you for doing this.

On a slightly related topic, is there a way to figure out why the nightlies have stopped? I found the status page with what is in the next one but no idea what is going on build wise.

Ty
[X 2014 Original Android Development] mikeoswego:
The devs for our device are aware of the problem. I don't have an official answer for why this happens but right now there may be 2 different problems.

First, the boxes that build these nightlies are compiling 12.1 versions for the devices that don't have CM13 yet and CM13 for those that do; it is probably fairly easy for the process to get messed up; then nobody gets a build until someone with the right skills can log into the build computers and fix things. A combination of one bad apple spoils the whole bunch and sh** happens.

Second, we are seeing other devices get CM13 builds in recent days but it is failing for the Victara nightlies. It may be that the latest commit titled "mkbootimg: don't use -e for lzma compression" fixes the problem with the Victara nightlies failing to build. (The build seems to be failing around the point where this change could have an effect.)

Due to the holidays, people aren't around as much so it can take longer to fix any problems that might come up.

Some helpful links:

CM13 Changelogs

Build History of Jenkins
[X 2014 Original Android Development] mikeoswego:
In addition to all the kernel commits visible in the changelog posted by invisiblek, he has also updated the "proprietary blobs" for our device that Motorola just released a few days ago. There are over 250 new files including various 6.0 binaries, libraries and other things to go along with the new Android M kernel files. Think of the blobs as being somewhat like drivers for Windows and we finally have right ones for Android 6.x!

I had to do a build for myself to check it out and it is posted here: cm-13.0-20151231-UNOFFICIAL-victara.zip

Happy New Year!
[X 2014 Original Android Development] salaesp:
Does the new kernel fix the clock problem?
[X 2014 Original Android Development] amd_h4x0r:
My Antutu benchmark scores went from 49k on your 20151230 build to 52k on this build :D
[X 2014 Original Android Development] fleabus:
Your last two posts are filled with great information. From one random internet user to another, thanks for being awesome!

Fleabus
[X 2014 Original Android Development] surrealjam:
Do the new kernel commits fix the graphical glitches in the navigation bar?
[X 2014 Original Android Development] Tommebaas:
So the new official rom from today also has all the commits?

Sent from my Moto X
[X 2014 Original Android Development] mikeoswego:
Unfortunately it does not fix that one although the "blob" that is responsible for keeping/saving the time was one of the ones updated. I presume you're talking about when you put the phone in airplane mode (or don't have service) and reboot, the time will be wrong.

---------- Post added at 10:13 AM ---------- Previous post was at 10:12 AM ----------

I just got 53k on Antutu and best before was 49-50k so that is quite an improvement!

---------- Post added at 10:14 AM ---------- Previous post was at 10:13 AM ----------

Just tested this with Trebuchet in landscape mode and the navigation bar is still messed up when you pull down the notification shade.

---------- Post added at 10:17 AM ---------- Previous post was at 10:14 AM ----------

Yes it does, in fact it has one more that was posted after the build I made involving a minor improvement to audio recording.
[X 2014 Original Android Development] surrealjam:
Thanks for checking. I am currently running stock Marshmallow due to the graphical glitches and some Bluetooth audio skipping. Think I'll stick with that till we get a stable CM13 :good:
[X 2014 Original Android Development] Tommebaas:
The newest nightly is pretty stable. Only the new Google Camera isn't working when sliding to video mode, but that was a known bug.

Sent from my Moto X
[X 2014 Original Android Development] chazeon:
The newest nightly eventually fixed vscocam loading forever problem.
[X 2014 Original Android Development] ATGardner:
I get random reboots on 1.1

I upgraded today from 12.21, and already had 3 random reboots. Anybody else encountered that problem?
[X 2014 Original Android Development] chazeon:
I do.
[X 2014 Original Android Development] cogie:
I've had 2
[X 2014 Original Android Development] mikeoswego:
Just had a random reboot, first one since crpalmer's post on 12/19/2015 about updating kernel and wifi driver from CAF (post 286)

Phone was idle, charging and hotspot was active.

This was on my build, I'll install the latest official to remove that variable.

Last_kmsg attached.
[X 2014 Original Android Development] nanca:
-Still not able to switch network mode.

-One random reboot.

-Smooth and fast.

-Still not able to make movies.

-Battery OK.

Overall: we are almost there. =)

Thank you guys.
[X 2014 Original Android Development] Heroeagle:
3 random reboot here too using latest nightly 1-1-16
[X 2014 Original Android Development] Tommebaas:
I also just got a random reboot.

Plus I still have to manually open Inbox and Whatsapp to get messages.
[X 2014 Original Android Development] mikeoswego:
Your last_kmsg is showing different problems than mine.

Did you wipe cache and dalvik after flashing the latest nightly?

If not, I'd give that a try.
[X 2014 Original Android Development] Heroeagle:
No i didn't wipe cache nor dalvik after flash , but I made full wipe before flashing latest nightly
[X 2014 Original Android Development] salaesp:
My phone resets the clock every time it is rebooted (doesn't matter if it has service or not) or when I set the option to automatically update the clock using the network. At least that's what happened to me on 1226.
[X 2014 Original Android Development] crpalmer:
Nothing should ever make the kernel panic. Wiping doesn't matter either way to the kernel. Aka, not wiping could make your phone useless, but it should never cause the kernel to crash.
[X 2014 Original Android Development] mikeoswego:
Ok, that is good too.

---------- Post added at 05:07 PM ---------- Previous post was at 05:02 PM ----------

On mine the time is always wrong after a reboot but only for the time it takes the phone to get service and get the time from the network; this shouldn't happen but it doesn't hurt anything (for me) and I'd probably never notice if I weren't paying attention.

---------- Post added at 05:12 PM ---------- Previous post was at 05:07 PM ----------

Good to know! I saw all those lines about the cache being below limit and thought that might have something to do with it. Turns out he had wiped the cache anyway proving that I'm no expert on kmsg files.
[X 2014 Original Android Development] mikeoswego:
Was leaving a place where I have the wifi password saved, got in vehicle , connect to charger, noticed a few seconds later that phone was rebooting.

20160101-nightly - last_kmsg attached
[X 2014 Original Android Development] nandroidz:
The same happened to me. Just turn off WiFi and lock the mobile for a few seconds. The device will reboot on it's on.
[X 2014 Original Android Development] crpalmer:
Thanks to both of you. Posting steps to reproduce is incredibly useful. After seeing these posts, it only took me a couple of minutes to see something that is likely the problem. At the very least, I can't reproduce it any more with a change I just pushed.

Let me know if you are still getting crashes on tomorrow's build or later.
[X 2014 Original Android Development] testkeys:
Yo!

Well, the last few pages of this thread just convinced me to stop digging through reviews and xda threads about the Moto X 2014 and go on and order one. I'm a die-hard fan of CM and it's been since CM7 time that I didn't see devs/maintainers actually listening to user feedback and chip in as crpalmer does - really nice to see and a big thumbs up. I can't wait to get back to the daily GitHub's CM commits reading and nightly flashing.

Again, a big thanks to Mr. Palmer and users helping out to make CM13 better for the X.

:good: :highfive:

Edit: and oh!, isn't there an included script in CM to clear cache after falshing? Don't we always see the updating apps... And sorry for being noob here also, but now that everything runs with ART, is clearing dalvik any pertinent?
[X 2014 Original Android Development] mikeoswego:
You seem well read and probably already know that on some 2014 Moto X models you can't unlock the bootloader meaning no TWRP. The Verizon xt1096 model if it already has the latest Verizon OTA installed is one example of that.

After flashing a new version of CM, you will see the updating/optimizing apps dialog. Even though it is ART, there are still optimization files created and they are stored in the old dalvik-cache directory. After flashing/install zips in TWRP, there will be a button to clear cache & dalvik before rebooting; I don't always use it but sometimes there can be problems if you don't and it only takes a couple seconds. The updating/optimizing apps process does pretty much clear out the dalvik-cache but in some cases junk can be left behind.
[X 2014 Original Android Development] enjoimadcow:
Hey does anyone know if the newest nightly has the random reboots fixed yet? I saw he said he couldn't reproduce it but I just want confirmation before I flash. Thank you =)
[X 2014 Original Android Development] mikeoswego:
The 20160102-nightly does not have the fix, that was posted a few hours before crpalmer made the change. The fix will be in the next nightly to be posted probably tomorrow morning.
[X 2014 Original Android Development] testkeys:
Thanks for the precisions [MENTION=5849464]mikeoswego[/MENTION]

I still have much to learn... I spent a long time on CM7, then jump to dalvik_CM11 and now getting excited to go Full ART (but maybe encypted-less -if I can find that thread again- in time, once the which old app is still working time...)

hehehe

Backtracking here after filling yet another page:

<! - -

- - - pure Off-Topic below - - -

(sorry and please skip to next post at ease :-p)

Well, the "which are the BL unlocked available models" will surely be on top of my questions to the chinese seller tomorrow. Online translations services have margin to improve I tell you...

Because here on the chinese eBay, I can't get a XT1095; just the (3 state-owned carrier's) 4G-friendly XT1085 and some other (mainly US) models.

I don't care much about 4G here in China atm (but might eventually) and GSM is fine with me. But I don't know much about what they do to unlock sim/carrier/network locks either? I'm just a little worried that my first full nandroid + separate EMS (imeid/modems) backups will fully bring me back to the received state if I ever need to get fast data...

There seems to be an unlocked XT1093 for sure (w bands 38 + 41) but unsure about their XT1096 and XT1097 and nothing is too clear about which one best match my carrier's 4G bands (which are within these six I believe 1,3,7,38,41).

So lot's of hard ball Q&A left for my poor translator wife...

And on the other hand, I have to figure out which model is best fitted for Moto's craziness (most rom [CM13 really]/sbf/root....../and user -compatible).

Anyhow, let's see what the store has to say first but I'm a bit puzzled, but more so like a kid in front of too many hard candy jars in front of him, so I won't complain too much...

[emoji14]

gn and

end of OT

-->