yashsingh1/xdaforums huggingface dataset:
[X 2014 Original Android Development] lizaSB:
I'm sure you've noticed how fine tuned the vibrations on stock are. The double twist for camera is amazing... CM on the other hand just throws it on at full strength and calls it a day.

Moto probably realized how strong the motor was and tuned it down... Devs here have had to tune it specifically in the same way moto did
[X 2014 Original Android Development] crpalmer:
Reminder: review.CyanogenMod.org

If you have better vibration patterns, make the change and submit and I'll try them out.
[X 2014 Original Android Development] lizaSB:
I'm not upset, just trying to help explain to others. Personally I think these values have come a long way from what they used to. There is some funkiness with long presses, like on the home screen of nova launcher or collapsing a comment thread in reddit sync -- it's still a bit strong.

[MENTION=2281583]0.0[/MENTION] has adjusted things in the temasek port and I found them more to my liking. I've never messed with commits before, so my apologies, but his post from the last page might offer insight

Edit: I'm headed to bed now, but if no one has submitted a code review when I wake up, I'll look into it
[X 2014 Original Android Development] nerotix:
[MENTION=3857343]crpalmer[/MENTION]

Not sure if this is ROM related but for some reason I can't write to my sdcard, when using for example Airdroid to put some files in a folder. However, when I write something to the root of the sdcard (so not inside a folder) it works fine.

Any idea?

Edit: Also there's 1 folder that I cant delete or anything.. doesnt seem related to the ROM tbh. I cant write anything to the folder nor delete the folder, seems bugged. However when I view the properties of the folder, it does says its readable and writable.
[X 2014 Original Android Development] crpalmer:
Any simple app that shows a problem? I tried a couple of random file explorer apps and I seemed to be able to access the sd card fine. Airdroid sounded like more than I wanted to install to test...
[X 2014 Original Android Development] tanishque italia:
[MENTION=3857343]crpalmer[/MENTION] do you have your unofficial builds of cm12.1 ?
[X 2014 Original Android Development] nerotix:
Yeah thing is tho, even the same stuff happens on ES File Explorer with root and r/w root permissions, seems to be online that folder as well.. really weird.

Thanks tho!
[X 2014 Original Android Development] crpalmer:
Weird. ES File Explorer was one of the ones I tried last night. I didn't do anything crazy hard with it but I created some files in random directories and deleted both those files and existing files without any problems.
[X 2014 Original Android Development] 0.0:
[MENTION=3857343]crpalmer[/MENTION] would you be willing to add in other CPU governors to the kernel? Like the smartmax governor?
[X 2014 Original Android Development] crpalmer:
Nope.

You really want to be using interactive anyway.

Ignore any comparisons you find online about governors. The interactive governor that we are using is WAY better than the stock one and it is tuned with other options and modules such as the CPU boosting.
[X 2014 Original Android Development] Flamehell:
Guys,someone knows if cm 12.1 has already merge to the new aosp build?LMY47O.....tnx :)
[X 2014 Original Android Development] nerotix:
Just check gerrit and saw A LOT of commits merged to CM12.1 from Crpalmer, good stuff, will be building tonight again.
[X 2014 Original Android Development] Flamehell:
Are you building for yourself?:)
[X 2014 Original Android Development] nerotix:
Yep, if interested, just pm me. Don't pollute this thread ;)
[X 2014 Original Android Development] Flamehell:
Pm on the way,tnx!!:)
[X 2014 Original Android Development] 0.0:
[MENTION=3857343]crpalmer[/MENTION] when I use the double twist gesture or chop-chop for open the camera when phone is unlocked, it will open Snapchat instead. I would have to uninstall Snapchat and reinstall so that the camera will open. Is there some way to make it so that it won't happen?
[X 2014 Original Android Development] crpalmer:
At some point you must have made snapchat the default camera action?

Try clearing default actions from snapchat (in Settings >> Apps) and see if you can then pick the camera to launch when you launch it with the screen enabled.
[X 2014 Original Android Development] crpalmer:
FYI, I've kicked off unofficial nightlies and created a new thread for it. Let's keep the 12.1 discussion in the new thread and let me know there if you have any problems.
[X 2014 Original Android Development] 0.0:
I did not notice that I had no camera as default. I made the Google camera the default from the lock screen. Thanks!

sent from my Moto X Pure Edition
[X 2014 Original Android Development] 0.0:
removed. wrong section
[X 2014 Original Android Development] utk_spartan:
Deleted
[X 2014 Original Android Development] alvareo:
okay this was fixed. Thanks, I guess.
[X 2014 Original Android Development] andersonaragao:
Friends, I get WiFi Hotspot fixed here. Sending the patch to CM gerrit.

EDIT: Sent. http://review.cyanogenmod.org/#/c/96623/
[X 2014 Original Android Development] Shemploo:
Can you elaborate? - Cause it sounds like you made a new thread for personal CM 12.1 builds?
[X 2014 Original Android Development] alvareo:
Response for your question will be answered on the 12.1 thread
[X 2014 Original Android Development] Gafanhotz:
Happens on 2013 Moto X too, but in every single call. On CM11 David 'DHacker' managed to fix it somehow.
[X 2014 Original Android Development] antnyhills:
Service

I'm on T-Mobile pure edition and not able to get any service, I've tried resetting and removing/inserting sim-card. Any ideas?
[X 2014 Original Android Development] fastercon:
Same here..I've had tonstay on the 1/16 build...both builds after seem to leave no APN settings and it won't stick if you do add the correct apn
[X 2014 Original Android Development] crpalmer:
Some changes got merged that broke a lot of devices. Try the 1/19 build (tomorrow) or later and hopefully it should all be fixed.
[X 2014 Original Android Development] fastercon:
Thanks crpalmer
[X 2014 Original Android Development] da900:
[MENTION=3857343]crpalmer[/MENTION] Could this (http://review.cyanogenmod.org/#/c/85575/ ) be the fix for missing mobilr service in the latest 2 or more nighlies?
[X 2014 Original Android Development] crpalmer:
What I am thinking of would be fixed by

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

(or alternatively another commit by cyanogen to add backward compatibility if we hadn't made the fix).
[X 2014 Original Android Development] da900:
Thanx a lot. Just flashed 19/01/2014 nightly and mobile service is working finne. Great ROM. Everything is smooth. The only thing that is not woring is built-in root. I flashed latest official nightly to my OnePlus One ant root via Privacy Guard is working, but on Victara it is not. I thought that it could be because of enforcing SELinux, but setting-up it to permissive via adb does not help. What could be the reson for that?
[X 2014 Original Android Development] crpalmer:
What are you doing that isn't working. Aka, specific steps that I can follow to see what you are seeing.

Did you remember to enable root in developer options?
[X 2014 Original Android Development] da900:
Activate Developer Options -> Sett Root access to "Apps and Adb" -> install any root app (for example, Root Explorer) -> open it and navigate to data -> it says that my device isn't rooted. The same happens with all the root apps I use (AdAway, Titanium Backup, flashify etc). No any root permissions listed in App Ops.
[X 2014 Original Android Development] crpalmer:
Did you deny them at some point?

I just installed flashify and it correctly prompted me for root (which I accepted and clicked remember) and then I successfully used it to backup my recovery (which should require root access to work).

If nothing else, try a factory reset and verify that it works for you too.
[X 2014 Original Android Development] da900:
Found a reason for not working built-in root. There are 2 SU files in /system: 1. /system/bin/su and 2. /system/xbin/su. I compared permissions for these 2 files on Moto X and OnePlus One (on wich root is working fine). So, permissions on Moto X was different. I've created a zip for recovery to fix permissions for these 2 files. And everything werre fixed. :p
[X 2014 Original Android Development] crpalmer:
Did you install busybox or supersu? Something is jacking with the su files.

On my phone, I have /system/bin/su which is a symbolic link to /system/xbin/su which is what I would expect it to be. If you have something different then some package you've installed probably did that to your phone..
[X 2014 Original Android Development] crpalmer:
Tomorrow's build contains a massive set of changes to the kernel, new adreno firmware and a bunch of other changes.

Please let me know if something starts acting wonky with the new build.
[X 2014 Original Android Development] da900:
Only ROM and Paranoid GApps... Don't know, but on my phone at first /system/bin/su was also a symbolic link. But on OnePlus One all su files have 0755 permissions. And I have changed theme this way.
[X 2014 Original Android Development] VoluntaryMan:
Is everyone else experiencing broken gesture typing on 1/19?

Can't wait to try out tomorrow's nightly!
[X 2014 Original Android Development] da900:
Works for me. Google keyboard.
[X 2014 Original Android Development] da900:
Flashed this build. do not see any bugs so far.
[X 2014 Original Android Development] Jmaniac55:
is this a universal build? or only for a certain version of Moto x 2014.... I have the Pure Edition XT1095

why is this officially on CyanogenMod's site?

is that root fix implemented in new builds or do we still need to flash it?
[X 2014 Original Android Development] crpalmer:
All I can test on XT1095. Other people claim it to be working on other variants.

By "on CyanogenMod's site", do you mean their github? If so, that's because I asked nicely and wanted to be able to make use of their gerrit to collaborate with others doing work on it. That work-flow is MUCH better than trying to use pull requests on github.

AFAIK, there is no "root fix" but rather one user that had a messed up install in some way. As I said, I had no problems installing a program that needed root, and using it.
[X 2014 Original Android Development] Jmaniac55:
Are the Moto apps going to be fixed eventually?

I am experiencing some lag btw. not sure if it is because it is a fresh install or not

---------- Post added at 10:02 PM ---------- Previous post was at 09:54 PM ----------

and no I mean like in there official list of devices
[X 2014 Original Android Development] crpalmer:
No, there will never be moto apps because those depend on custom changes Motorola made through the system.

However, I am currently working on my own implementation of some of the sensors which you will get in a nightly soon.

The moto x in the list of supported devices is the 2013 model ("ghost").
[X 2014 Original Android Development] TheMorpheus:
Hi, thanks for your work [MENTION=3857343]crpalmer[/MENTION]

I've been following your work on github and gerrit and I'm beating myself to not unlock the bootloader and try CM12, but the only thing that I'll be missing (I'm missing already, I'm not a huge fan of Moto Display) is doble tap to wake.

It will be possible to have this feature?
[X 2014 Original Android Development] crpalmer:
I have no idea. I have't looked into and therefore I don't know if our hardware can support and if it can support it if there is enough code/documentation available to figure out how to enable the hardware support.

Without proper hardware support there is no chance as it is very battery inefficient to fake it.
[X 2014 Original Android Development] crpalmer:
Today's build should contain a new package that enables the stow sensor and the camera activation sensor. The stow sensor IMO makes Ambient Display into a useful feature.

To use the stow sensor you must enable "Ambient DIsplay" in Settings >> Display. Once enabled, the stow sensor will light up the ambient display whenever your phone is unstowed. Unstowed means take it out of your pocket, turn it face up after it was laying face down, etc.

You can also trigger the stow sensor by covering the top right corner of the phone (where the proximity sensor is).

The camera activation sensor is always enabled when the display is turned off (it does not depend on the ambient display feature). It's the same gesture as stock and launches the camera securely without unlocking your phone.

Note: There is still no support for the IR Gesture sensor (aka wave you hand in front of the phone to view notifications or act on notifications).
[X 2014 Original Android Development] pbg_87:
Confirmed working. Nice thing to have on CM12.

Installed it this moring. Many German translations are missing in settings menu. But i know its related to CM sources ;)
[X 2014 Original Android Development] VoluntaryMan:
Do you have any plans for a method of accessing Google Now without the phone being plugged in or having its screen on? Might be impossible without a proxy app like Motorola uses, I wouldn't know.

The ROM is coming along great, thanks for all the work you're doing.
[X 2014 Original Android Development] aamzalag:
twist gesture for camera

Do you think it will be possible to have the gesture work while the screen is on in the future? Like stock Moto software?

BTW its awesome how much you were able to do to make old moto things work.

Thanks!
[X 2014 Original Android Development] crpalmer:
I honestly have no idea how hard it would be to do that. The always listening is different hardware from the normal voice recognition microphone and it will most likely require some changes to the infrastructure and therefore is a big project. Because it's a big project, I haven't looked at all at how well documented any of the hardware is in the kernel, etc so I just don't know if it's possible.
[X 2014 Original Android Development] crpalmer:
Oh, does the gesture really work all the time on stock? I thought it was only when the phone was off so that's what I implemented. Can you tell I never really used the moto software? :)

I just changed it to always be enabled. Try tomorrow's build and let me know.
[X 2014 Original Android Development] aamzalag:
Sweet! Im excited!!! - What do you think the prospects of getting the IR sensors to work to make ambient display turn on from the wave? Is it likely?
[X 2014 Original Android Development] nerotix:
What's wrong with the UI? everytime u click something to turn something on or off in the settings, u see like a weird grey 'box' around the click animation or something.. looks really weird. Can it be solved or should I wait for a new release?

Thanks for all the hard work btw :)<3
[X 2014 Original Android Development] rayb1966:
Ambient display is great
[X 2014 Original Android Development] crpalmer:
I would like to. The hardware that handles all of this is completely undocumented on the internet and therefore it's an experimental process to figure out what you can do with it. The IR Gestures currently work great if you don't let the phone deep sleep and fail entirely while it is in deep sleep. I couldn't figure out how to change that even though it appears that the hardware supports it. I'll have to look again later and see if I can figure out something new with fresh eyes.
[X 2014 Original Android Development] tiaoalvino:
Is there any way to implement this as a mod to stock versions? Because this truly has made Ambient Display useful and more interesting than Moto Display. Congratulations!
[X 2014 Original Android Development] lizaSB:
Thanks for all your hard work in getting our device up to speed. Who knows if we'll ever get IR support, but the simple fact that you've got ambient display working and the twist gesture as well, is amazing!
[X 2014 Original Android Development] dobbs3x:
Yeah, the twist gesture and ambient display are working great for me. No problems with the January 24 build for me yet. And the stow sensor works pretty good too.

cr do you know if victara will ever make it to official support under cm?
[X 2014 Original Android Development] 0.0:
[MENTION=3857343]crpalmer[/MENTION] I've been trying to look around on how to get the "ok google" phrase to activate with screen off. I found this http://xdaforums.com/nexus-6/general/ok-google-everywhere-aosp-rom-t2963716. It's for the n6, but I found that there are lib, xml, and apk files that are used to supposedly make it work

I have no clue if the above will work. I did read about something else that it may be a flag that needs to be toggled, possibly in the Google Now app and/or the device itself

sent from my Moto X Pure Edition
[X 2014 Original Android Development] crpalmer:
You can probably just add the CMActions app to stock and it would work. I don't plan in supporting that though.
[X 2014 Original Android Development] crpalmer:
It will be made official when all the problems are solved and I can claim 100% base hardware support. Adding a device requires passing a high standard...
[X 2014 Original Android Development] tiaoalvino:
Dude, it worked!!!

Thank you so much!

EDIT:

Not for long. :(

After some time, the screen doens't on anymore, even after a restart.

Unfortunately. :crying:
[X 2014 Original Android Development] aamzalag:
Is there anything we can do to help get a2dp working? Do you know what the issue is?
[X 2014 Original Android Development] nerotix:
Had a chance to check this out perhaps?
[X 2014 Original Android Development] ticoticox3000:
Today's (January 25) nightly working perfectly.

New boot animation, Cyanogenmod account, News toggles for the notification drawer and Twist gesture with screen on, were added. :D

Btw a question, do I need to wipe Dalvik and Cache every time that I flash a new nightly?

It would be possible that in some nightly will be added the action from the soft-buttons? (swiping action from soft-buttons)
[X 2014 Original Android Development] 0.0:
[MENTION=3857343]crpalmer[/MENTION] With the a2dp bug, could it be an audio_policy.conf file issue? Maybe the sampling rate needs to be lowered? I'm only throwing out ideas. I'm sure you looked at that

btw, were you (or anyone) able to try the n6 screen off google now fix? did it work?

sent from my Moto X Pure Edition
[X 2014 Original Android Development] nerotix:
Could you test something for me please?

If you turn something on in settings, the small turn on/off switches.. is it bugged on how the animation looks? Like a grey box around it when pressed.. for example go into Display settings and press the switch for "Adaptive brightness" a few times and see if a weird box appears during the switch of it turning on.
[X 2014 Original Android Development] VoluntaryMan:
It appears to be the two parts of the button getting out of sync with their touch reactions.

I have it too.

Additionally Bluetooth audio stopped working yesterday for me.

I feel like it's just cm bugs at this point, not device issues (other than possibly Bluetooth)

I also checked my old nexus 5 running 5.0.0 and it didn't have the bug.
[X 2014 Original Android Development] dobbs3x:
I get the graphic glitch on mine doing this on Jan 25 nightly. Never noticed it before you mentioned this.
[X 2014 Original Android Development] nerotix:
[MENTION=3857343]crpalmer[/MENTION] Maybe he can took a look at what it is.
[X 2014 Original Android Development] ticoticox3000:
Yes, the bug still there.
[X 2014 Original Android Development] dobbs3x:
Looks like a lot of commits in tonight CM nightly build with a lot of Bluetooth related commits.
[X 2014 Original Android Development] beelzebu:
Just found a bug, tried dirty flashing from 25 to 26 builds and and none and ambient display seams broken trying right now a clean install. Will let yo know what happens.

Edit: Tried the clean install and everything is working again.
[X 2014 Original Android Development] crpalmer:
The n6 screen off google now isn't likely to magically just work. The N6 (on cyanogenmod) is using stock blobs for a lot of audio that we aren't using. That gives them access to the additional adc that can work in a low power mode. We don't have support for that adc in our builds so it really can't work.

In terms of the a2dp, I run using either 48000 or 44100|48000 and someone else was running with 44100 only and none of that makes a difference.
[X 2014 Original Android Development] aamzalag:
Is the A2DP issue a cm12 issue or a hardware specific Victara issue?
[X 2014 Original Android Development] beelzebu:
Ok, overall i think this is the less bug rom I have tested on my moto x 2014, so very pleased with it. Anyway I have found some kindda bugs i want to share so everyone else know's what may have issues, for me those issues are not important so I'm happy with this rom.

When you themes, and select lock screen wallpaper, you will have 2 wallpapers but you can only change the system wallpaper and only use the theme lock wallpaper. To get this around unselect the lock screen wallpaper and delete the file under /data/system/user/0/keyguard_wallpaper doing so the lock screen wallpaper will act as usual, using the same wallpaper for lock screen and home.

When charging ambient display will not work. sometime it does, sometime it does't.

When using custom themes the square glitch in setting does not appear.

Sometimes when you upgrade the rom ambient display is not working, you need to disable and reenable ambient display.

Hope this helps anyone :)
[X 2014 Original Android Development] EvoYas:
Will OTG work with this rom?
[X 2014 Original Android Development] pbg_87:
Yes it's working.
[X 2014 Original Android Development] VoluntaryMan:
I feel like most of this belongs in the general cm12 thread. This is for device issues, really
[X 2014 Original Android Development] beelzebu:
It may be but, I own this device and ambient display is something that was made for this device also. As [MENTION=3857343]crpalmer[/MENTION] is working on this device, I think it is a good place to point this things and how there is a workaround for them. I know that the wallpaper issue is cm bug and it is nothing to do with the moto x 2014.
[X 2014 Original Android Development] dobbs3x:
I'm going back to Jan 23rd nightly, I've been having network radio issues on Jan 25th and later builds. I just flashed back completely to stock and flashed recovery and rooted and now going to flash the Jan 23rd nightly and see how it goes. I'll update here in a min after I flash how it is working.

UPDATE: Still having radio issues after reverting back to the Jan 23rd nightly. Here's some screen shots.
[X 2014 Original Android Development] dobbs3x:
I've tried changing apns and making a new one with no luck. Tried factory resetting too and didn't help.
[X 2014 Original Android Development] david1985:
does it has the cm theme manager?
[X 2014 Original Android Development] beelzebu:
Yes it has
[X 2014 Original Android Development] Diesel779:
Anyone in the UK having any issues with data on this ROM? Oh, and thanks to the dev :)
[X 2014 Original Android Development] david1985:
I keep having encryption unsuccessful on every rom i'm trying to to install on the moto x any reason why?:rolleyes::rolleyes::rolleyes:
[X 2014 Original Android Development] ticoticox3000:
Try to wipe data and cache from fastboot or recovery, I had the same issue but I'm not very sure how I solve it.
[X 2014 Original Android Development] dobbs3x:
Data partition needs to be ext4 not f2fs
[X 2014 Original Android Development] david1985:
thanks will try now where do i go to make it ext4?

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

I got it but i lost everything when i formated it to ext4 but hey at least i could flash and thank god for dropbox

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

Having connection issues apn is all fine any workaround?
[X 2014 Original Android Development] Semicuda:
If the fact that formatting something makes your data go away is a surprise to you, you should maybe stay away from dev threads... no offense though.