yashsingh1/xdaforums huggingface dataset:
[X 2014 Original Android Development] mikeoswego:
16 minutes?!? That must be a really, really fast box!

Do you have a ~/android/system/.repo/local_manifests/roomservice.xml file?

If not, create it with the following content:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_motorola_victara" path="device/motorola/victara" remote="github" revision="cm-13.0"/>
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-13.0"/>
<project name="CyanogenMod/android_kernel_motorola_msm8974" path="kernel/motorola/msm8974" remote="github" revision="cm-13.0"/>
<project name="TheMuppets/proprietary_vendor_motorola" path="vendor/motorola" remote="github" revision="cm-13.0"/>
<!--
Following lines added to roomservice.xml by 'breakfast victara'
-->
<project name="CyanogenMod/android_external_stlport" path="external/stlport" remote="github" />
<project name="CyanogenMod/android_external_sony_boringssl-compat" path="external/sony/boringssl-compat" remote="github" />
</manifest>

Did you "make clean" after previous attempts to build?

You'll normally want to do the following list of commands:

cd ~/android/system/
make clean
repo sync
. build/envsetup.sh
brunch victara

My box is an older dual core 2.66ghz, 8gb ram, and fast, single SSD drive. It takes a little over 4 hours to do a clean build the first time. If CCACHE is enabled, it will take around an hour and a half each time after the first one.
[X 2014 Original Android Development] testkeys:
Good info that will get handy ...one day...

Dang you for now putting "start shopping for a replacement SSD" in my head though

:p

My old Postville (Intel 80GB X25-2nd gen -lol) primary SSD drive is going to blow is 6th candle soon (which is probably twice the original manufacturer warranty time). It has survived through 2 "boxes", 3 MBs and have seen 3 old gen HDDs died has its secondary drive partners in the war... So all this to say that it is my excuse for not to start building...: that thing just won't die! (props to Intel on this). I have no space to set up my build environment and I won't build on my data drive...

OK, end to my nerd talk, but what's your guess on build time for my config (with the eventual [read mid/long term project] new SSD):

i4770 4 core hyper-threaded (so 8) @ 3.4GHz / 8Gb ?

Edit: re-read your post and no need to reply really: I should be under 4hours also I guess so no biggie there.
[X 2014 Original Android Development] mikeoswego:
The real bottleneck is disk access. The ultimate build box would have at least 2 SSD's; read the source from one, write output to the other. There are flags you can use to optimize the build on a multi-core box as well. But even without the fanciest box, you can just let it run overnight, while at work, etc. As a side note, if you want to experiment with the code, you can make a minor change and do a "dirty" build, only your changes have to be recompiled and, depending on what you modified, it might only take a few minutes to complete.
[X 2014 Original Android Development] Mennpiko:
I have corrected the xml and I used "make clean" does not work, no boot ROM, I do not know what can happen, thanks

Enviado desde mi XT1092 mediante Tapatalk
[X 2014 Original Android Development] nanca:
Network issues on 16/nightly. I'm still not able to change/switch from 2/3/4G.

Just to let you know... =/
[X 2014 Original Android Development] ticoticox3000:
OK, I will download OpenGApps, do a system wipe and then flash OGApss, right?

Thanks you
[X 2014 Original Android Development] Mennpiko:
Change LTE / 2G worknig in tomorrows nighlty,I've tried
[X 2014 Original Android Development] mikeoswego:
Yes, but either download a version of OpenGApps (or other GApps) that doesn't include the Google Camera or create a gapps-config.txt file to cause the Google Camera to be excluded. OpenGApps Super and Stock include Google Camera, the others do not. If you want the things that are in the Stock or Super package, make a gapps-config.txt file, put it in the same place as the OpenGApps zip file and put the following line in it to exclude the Google Camera:

CameraGoogle
[X 2014 Original Android Development] zax10:
OK guys. New to the Moto X but not Android. I have been around for a while on xda. Mostly Samsung and HTC.

My question is which gapps are we too use? I have looked at the slim and open but unsure of which one has a better track record.
[X 2014 Original Android Development] testkeys:
So, I got my SIM yesterday.

Good news: I got LTE.

Bad news: the reception is extremely poor and I probably average -100 dBm (or 0 - 2 bars) at my place.

But again I don't really care about 4G and I don't plan of getting a package after the initial first month's free 1GB. So I had great hopes of getting good 2G signal with the phone especially since GPS and Wi-Fi working so great. But I also couldn't switch from LTE in Networks Settings. So yesterday was a downer.

Little glimpse of hope today though: for some weird reason, after flashing 20160118, my phone was connected on Edge instead of LTE. And standing at the worst spot in my house, I still had 4 bars at -75dBm!

But the celebration didn't last long: 1 short 15sec test call and soon after (read 2 minutes maybe) the LTE was back on automatically and the bars were gone

[emoji22]

I saw that Chris seems to be still digging.. So please let me know if there's any way I can be of any help in troubleshooting.

Cheers

Oh! does the "my phone number" has to be inputed somewhere or do I have a glitch there also? thx

[XT1093 on China Mobile ].
[X 2014 Original Android Development] crpalmer:
The next build should allow you to change the preferred network mode (LTE, 3G, 2G).
[X 2014 Original Android Development] zax10:
[MENTION=3857343]crpalmer[/MENTION] which gapps do you recommend. I see you said slim mini but which build should i go for (newest build or most downloads)
[X 2014 Original Android Development] crpalmer:
I honestly don't know which gapps are best. I am using an older Slim gapps on this phone. Pick the source you want (e.g. Slim) and then use the newest version.
[X 2014 Original Android Development] Salo-S:
Im facing some weird problems with power button on last build. Sometimes when i try to put it on sleep, it just doenst respond, like the button was damaged... And sometimes i press it and it goes to camera. My button is OK, just seems little soft like all moto x i ever used. Can be a software problem? Thnx and sorry for my bad english, im trying to talk without google translate ?
[X 2014 Original Android Development] testkeys:
I have been experiencing similar issues with the power button and have reported here a couple pages ago, so you're not alone and yes, there must be something that need a fix somewhere.

Now two things:

Until this gets addressed/sorted out, you can: set your volume rocker to wake up the device (under settings/buttons) and also set the "double tap screen (statusbar really) to sleep" (under display and lights).

The other thing I've noticed is that when I want to turn off the screen and the power button seems dead, what I do is simply change the volume (like up a notch or two and back down). So I usually see the volume popup show up the right after, the power button starts working again.

I hope this helps..

Edit: I just received a SMS, and phone phone switched to Edge on its own and I went from barely no signal to excellent reception like described in my previous post. Let's see how long that last this time...

And thanks @ CRP btw; I'll anxiously wait the 0119 nightly.
[X 2014 Original Android Development] Salo-S:
This may seems to be a bug on CM13. Got a Moto G XT1078 from a friend and the same bug appears. Pressing the vol button solves, thnx!
[X 2014 Original Android Development] md07:
lastet nightly 19-1 fixed change prefer mode network. But can not pull quicksetting. Hope Maintainer fix this next build
[X 2014 Original Android Development] Salo-S:
Just pull statusbar and touch and hold config icon. This will be open to edit the tiles of of statusbar and you just need to add anything to it. Will fix the bug
[X 2014 Original Android Development] testkeys:
It first looked very small (all the icons) but after turning on Wi-Fi, it then resized properly.

And yes, Mr. Palmer is my hero again.

THANK YOU VERY MUCH
[X 2014 Original Android Development] ATaRiii:
20160119 - Netflix OK, 3G/4G OK

It seems to me this is the best CM13 nightly so far!

Very close to perfection, thanks a lot.
[X 2014 Original Android Development] gopik5:
yes mobile nw fixed in 1/19
[X 2014 Original Android Development] fajarlazuarding:
I also got this (well its a known issue), and when rebooting all the tiles are gone again. Do this also a known issue ?
[X 2014 Original Android Development] nandroidz:
Missing tiles is a known CM issue. It's happening on most devices running 01/19 update.
[X 2014 Original Android Development] fajarlazuarding:
Maybe "just dont reboot our phone for a while" is a good solution now ;) thanks for the heads up.
[X 2014 Original Android Development] ATaRiii:
Not here

I have not noticed this issue here.
[X 2014 Original Android Development] surrealjam:
Once the obvious quick settings issue is fixed, as far as I am aware, it's only the Screencast app which does not work. Battery life has also been consistently good :good:
[X 2014 Original Android Development] md07:
I can see many changelog about snapdragoncamera (snap), I think this a new camera app, but after flash nightly, it's still old CM camera.
[X 2014 Original Android Development] Aroch925:
The maintainer has to add it to our phone specifically. Some phones have it already and some don't. We just have to wait until he adds it to victara
[X 2014 Original Android Development] ATaRiii:
... and screen record app also doesn't work.

:(:rolleyes::crying:
[X 2014 Original Android Development] salaesp:
At least the description indicates that tiles should be working next build:

http://review.cyanogenmod.org/#/c/128894/
[X 2014 Original Android Development] lauren:
hey guys i'm interested to finally update from the last nightly of CM12.1 (21-11-2015 i believe) and i'm just wondering if it's just a case of factory reset, then flash rom, then flash apps, then reboot and wait? i have twrp 2.8.7.1 installed - is there anything else i need to do? i have searched the thread for the answer to this but couldn't find anything specific but apologies ahead of time if i missed it

ah yes ... also can i go back to CM12.1 if i need to?

thanks
[X 2014 Original Android Development] trimax84:
I was hoping this would be the fix, but Ambient Display doesn't seem to work for me at all. I've enabled/toggled it in settings ->Display as well as toggling the options in settings -> gestures.

I have even tried installing the Xposed module to force enable it to no avail.

Much searching has turned up empty... Seems like this should work. I miss the Moto active display, but would settle for ambient display working! Anyone have any tips or insight?

(edit, clean installed 1.19 last night and upgraded to the 1.20 nightly this morning. On xt1096.)
[X 2014 Original Android Development] nandroidz:
That should work perfectly

---------- Post added at 09:29 PM ---------- Previous post was at 09:27 PM ----------

Try a full wipe and then flash cm again.
[X 2014 Original Android Development] trimax84:
This was clean installed last night after a full wipe. Any options before going through all of that again?
[X 2014 Original Android Development] nandroidz:
Try grabbing a logcat and see if someone can help you identify the problem.
[X 2014 Original Android Development] fajarlazuarding:
Anyone updated to latest nightly ? How's the tiles issue ? Fixed ?
[X 2014 Original Android Development] nandroidz:
Yes and the quick tile bug is still present.
[X 2014 Original Android Development] fajarlazuarding:
I guess I'll just stick with 1/19 for now because everything that I'm using is working flawlessly and battery life is also good. Thanks for the heads up mate.
[X 2014 Original Android Development] surrealjam:
The tile bug is partially fixed. If you hold down the settings shortcut (i.e. the way you enable the UI tuner in stock) it will then go to the edit tiles option and from there you can successfully add the tiles back! Sure they will fix it properly soon but this is a workaround...
[X 2014 Original Android Development] vista178:
I do that and reboot my phone only to have all the tiles disappear again. I knew the risk of flashing nightlies - it'll get fixed. BTW I'm on the 01/20/16 build.
[X 2014 Original Android Development] lauren:
i went back to CM12.1 - Trebuchet is a bit weird on CM13 and the quick tiles issue, plus it seemed slower on my device even after changing the 3 visual delays to 0.5 sec ... not sure what the super duper must upgrade for features are for MM to be honest

great work by the devs though and i'm sure it will be as slick as 12.1 soon

:)
[X 2014 Original Android Development] nandroidz:
It's faster and has better battery backup than CM 12.1 to be honest. The quick tile bug is a recent bug and will get fixed soon. Till then read the posts above for a work around.
[X 2014 Original Android Development] testkeys:
I might be wrong, but I believe that for the ambient display to work, you do have to turn the Lockscreen on. It makes sense if you think about it because you need tge Lockscreen to display notifications and the clock/weather. Heads up notification disappear, so waving your hand with/without notifications would then just light up the desktop.

If that logic stands, then what could maybe be improved is to not allow the Ambient Display Quick Tile to be at the ON state without also having the Lockscreen also ON. That would avoid having an ON state that does nothing like we have now...

Re. the quick tiles, well I haven't changed theme yet on 20160120 and was on my personal custom one before and after install and no problem with them yet. I'd even say that this build definitely fixed them in regards to tile placement. I just couldn't find a way to place the tiles where I wanted them to be on the Jan19th nightly; it was like the CM11 Easter egg game where tiles fly away when you touch them. Well, that comparison is pushing it a bit, but it's day and night for me and I say go for this one no matter...

Edit (to an already long post... sorry):

I've rebooted changed theme twice, changed Tiles around: all good here on Jan20th.

And yes you need this for ambient Display to work (and potentially also a code - not just swipe up to unlock);

And one last thing on this: like I mentioned: Ambient ON / Lock screen OFF does nothing, but if like I've explained it is intended, the why are the IR sensors working? I've noticed that a few hours ago (I don't know about you, but I can see the sensors turn slightly red when they detect something) and I think that there might be battery saving to get by having them off in that case? Even if there is none, then this combination should not be possible so logically, if ambient is off, sensors off - no?
[X 2014 Original Android Development] trimax84:
I had tried enabling the lock screen before asking my question, as what you suggest has seemed to work for others.

However, I had enabled only the "Swipe" type of lock screen. So, after your prompting, I went back and enabled a pattern type of lock screen. And wouldn't you know - it actually worked! So now I had the Ambient Display, but had to put in a pattern, which would have been acceptable. But I took it a step further and went back to the Swipe type of lock screen, and now Ambient Display works with that one too (quirky android...). It seems this works a little differently (better) than the stock Moto active display when set to "Swipe" as the lock screen doesn't require a second swipe with this CM13 Ambient Display option (and who wants a second, wasted movement anyway?).

Thanks for the input! I'm glad this works now :)
[X 2014 Original Android Development] vista178:
Where is the configuration stored for tiles? Maybe clearing that will fix my issue. I've reverted to stock theme, yet every time I reboot the configuration reverts to brightness slider only. In fact, reset to defaults will sometimes actually revert the tiles as it should and others it will remove all tiles!

Edit: Looks like it isn't just me, more fixups in the next nightly.
[X 2014 Original Android Development] salaesp:
Quick tiles working now!!!
[X 2014 Original Android Development] fajarlazuarding:
A question, do we need to reflash gapps when updating to next nightly ? I am using open Gapss though.
[X 2014 Original Android Development] nandroidz:
No need to reflash GAPPS
[X 2014 Original Android Development] fajarlazuarding:
Updated and quick tiles issue is fixed

Thanks to the devs.
[X 2014 Original Android Development] salaesp:
I'm still having the incorrect time issue everytime I reboot. I'm also getting duplicated contacts when I install whatsapp. I have every contact twice.
[X 2014 Original Android Development] nandroidz:
Contacts that's not a bug.

Go to contacts--> 3-dot menu-->Contacts to display.
[X 2014 Original Android Development] salaesp:
Contacts on stock are merged automatically. This should be the default behavior. Otherwise I would lose the ability to send a whatsapp through the contact list

---------- Post added at 08:59 PM ---------- Previous post was at 08:58 PM ----------

What about the clock? Are you having this issue? Everyone is telling me that they are not experiencing anything like that and the bug is fixed in jira
[X 2014 Original Android Development] salaesp:
Looks like the issue with the time is CM13 + twrp. Using cyanogenmod recovery everthing seems to be working fine.
[X 2014 Original Android Development] fajarlazuarding:
Well I'm using twrp though and don't have any problems. But yeah at least the problems were already sorted out for you.
[X 2014 Original Android Development] salaesp:
It seems that the weather is not appearing on the notification drawer. I couldn't find anything in the thread about it.
[X 2014 Original Android Development] gkarthik16:
Try this:

Hold the settings 'wheel' till you get the quick tiles edit mode. Swipe left and you will see some settings like weather, large first row, etc. Try enabling weather there.
[X 2014 Original Android Development] meilbox:
ambient display ... suddenly stopped working... also no reaction when waving or picking up the device
[X 2014 Original Android Development] surrealjam:
I'm on the latest nightly and it seems to be working OK here. You might have to narrow down a specific setting that might be causing it.
[X 2014 Original Android Development] salaesp:
I had that option enabled, but still no luck. I just need to know if it's just me or if this is an issue with the ROM. Since I used aroma open gapps, maybe I deleted something I shouldn't.
[X 2014 Original Android Development] salaesp:
Is there any way to disable ambient display at night?
[X 2014 Original Android Development] psssss:
Also no weather here, nano gapps; It worked two days ago (cm-13.0-20160119-NIGHTLY-victara.zip I think),

since the tiles are fixed :good:, no weather ...

Not that important for me,

but I'm sometimes also experiencing wrong time issues, and disabling Google Search causes boot loop (is this okay? I could disable it on 12.1)

everything else is great so far,, thanks for all the work!
[X 2014 Original Android Development] JuggaloDroid:
Create a 'System Profile' for the night and turn off ambient display; or, add the ambient display quicktile and toggle it when you want.
[X 2014 Original Android Development] salaesp:
I was looking for something a little more automatic than that. Moto display had a "sleep" option, maybe something like that, but if it's not yet implemented or never will be, the profile will do the trick.
[X 2014 Original Android Development] bungphe:
It seems that "ok google" does not work in "any screen" setting.

Only work in home screen for me.
[X 2014 Original Android Development] salaesp:
This is a known issue for CyanogenMod. I have the same problem too
[X 2014 Original Android Development] matt99017d:
Is anyone having issues with hangouts not pushing notifications? Unless I open up the app itself I can't see what is being sent to me. The message shows up when I open it. I'm running slim G apps on 1/21 build for cm13.

Under the accounts sync, the last auto sync was at 2am. Not sure how (or if I can change ) how often it syncs.
[X 2014 Original Android Development] fourtwentybuddy:
Quote:

Originally Posted by bungphe

It seems that "ok google" does not work in "any screen" setting.

Only work in home screen for me.

this works for cm13 :)

http://xdaforums.com/xposed/modules/mod-ok-google-3rd-party-launchers-app-t2765635
[X 2014 Original Android Development] zax10:
Guys need some help. How exactly do you gain root access? I have enabled it in settings but still no access.
[X 2014 Original Android Development] nandroidz:
Just enable it under developer options, that's pretty much all you need to do.
[X 2014 Original Android Development] zax10:
That's what I did and nothing. Oh well I will figure it out.
[X 2014 Original Android Development] zax10:
Fixed my root access issue with newest nightie
[X 2014 Original Android Development] misterkickass:
Is there a relatively simple way to replace the default Camera and Gallery apps with their Motorola counterparts? I prefer to use those, and would not like to have multiple apps installed for the same purpose. I suspect it can be done rather easily when compiling CM13 from source, but I was wondering if there was a solution that has a less steep learning curve.
[X 2014 Original Android Development] nandroidz:
The OpenGapps aroma installer has a option to remove stock CM apps.

Once removed you can flash or install the moto apps from play store.

Edit: Or you can use a root explorer to remove the apps manually.
[X 2014 Original Android Development] misterkickass:
Thanks, I'll look into it.

I know that there are several app-based solutions to do that, but I'm looking for a more bare-bones approach, would prefer not to install an additional app just for this purpose.
[X 2014 Original Android Development] BootloopedMillennials:
crpalmer

I'm trying to tune interactive governor in CM13 following thread below. The problem I have is changing the CPU Governor tunable (with Kernel Auditor) go_highspeed_load always resets to 50. Other settings stick fine. Talking the members over in the Krait kernel for Moto X 2014 stock thread, I've deduced it seems to be the CM13 kernel.

http://xdaforums.com/nexus-5x/general/guide-advanced-interactive-governor-t3269557

Thank you.
[X 2014 Original Android Development] testkeys:
I don't use Moto Gallery but I sure do have Moto Camera as my main one (the one with a spot on my launcher's dock).

What I do is create myself a flashable zip that I routinely flash along (after obviously) each nightly. You can also add a line to delete whatever CM app you don't want.

For example here's currently have as my updater script:

ui_print("||");
ui_print("||");
ui_print("||");
ui_print("||");
ui_print("|- Olney font family (not light) -|");
ui_print("|- Black Calendar v5.3-108865406 -|");
ui_print("|- LockClock (Jan 18, 2016) modded -|");
ui_print("|- Hosts file[0.0.0.0](Dec 5, 2016) -|");
ui_print("|- Additional alarms and ringtones -|");
ui_print("|- Marshmallow android bootanimation-|");
ui_print("|- Clr Playstore v6.0.5 no update all|");
ui_print("||");
ui_print("||");
ui_print("||");
ui_print("");
ui_print("Mounting system...");
run_program("/sbin/busybox", "mount", "/system");
show_progress(1, 1);
ui_print("");
ui_print("Copying files...");
package_extract_dir("system", "/system");
ui_print("");
ui_print("Unmounting system...");
run_program("/sbin/busybox", "umount", "/system");
ui_print("");
ui_print("*** ALL DONE !! ***");

And I'm planning on adding to delete the CM sim toolkit next...

Like they say: hope this helps...

[emoji1]