yashsingh1/xdaforums huggingface dataset:
[Moto X Android Development] tirian_:
I'm having some trouble with this rom. It will work after the first boot, right up 'till I turn off the screen for the first time. After that, I will be in an infinite loop of System UI crashes. I'm also not able to change the lockscreen type, or to get to security settings.

A look at logcat shows issues with keymaster.mdt

E/QSEECOMAPI: (11814): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt
E/QSEECOMAPI: (11814): Error::Loading image failed with ret = -1
D/QSEECOMAPI: (11814): QSEECom_start_app sb_length = 0x2000
D/QSEECOMAPI: (11814): App is not loaded in QSEE
E/QSEECOMAPI: (11814): Error::Cannot open the file /firmware/image/keymaste.mdt
E/QSEECOMAPI: (11814): Error::Loading image failed with ret = -1
E/QCOMKeyMaster(11814): Loading keymaster app failed
E/keystore(11814): could not open keymaster device in keystore (Operation not permitted)
E/keystore(11814): keystore keymaster could not be initialized; exiting

I found posts about permission issues with the files, so I double checked that they were 0644:

root@ghost_verizon:/vendor/firmware/keymaster # ls -l
lrw-r--r-- root root 2015-03-15 01:46 keymaster.b00 -> /firmware/image/keymaster.b00
lrw-r--r-- root root 2015-03-15 01:46 keymaster.b01 -> /firmware/image/keymaster.b01
lrw-r--r-- root root 2015-03-15 01:46 keymaster.b02 -> /firmware/image/keymaster.b02
lrw-r--r-- root root 2015-03-15 01:46 keymaster.b03 -> /firmware/image/keymaster.b03
lrw-r--r-- root root 2015-03-15 01:46 keymaster.mdt -> /firmware/image/keymaster.mdt

They were, but I noticed they were all symlinks to /firmware/image. I wanted to make sure, so I checked there:

root@ghost_verizon:/vendor/firmware/keymaster # ls -l /firmware/image/keymaster*
/firmware/image/keymaster*: No such file or directory
1|root@ghost_verizon:/vendor/firmware/keymaster #

Turns out, I don't have those files.

So, what happened? Did I wipe everything too aggressively? I followed the steps outlined earlier in the thread, and yes, I did read the entire thread.
[Moto X Android Development] anilrawal:
Did not work

I tried flashing cm11 and cm12 and there also it has the same behaviour stuck on CM boot logo.
[Moto X Android Development] athulele:
1. Full wipe

2. flash Cm11

3. boot into cm11

3. reboot into recovery

4, full wipe

5. flash cm12

6. flash gapps

7. reboot
[Moto X Android Development] bvsbutthd101:
I don't think you're suppose to do a full wipe after flashing cm11. At least I don't remember doing so. Just wiping cache + dalvik cache is all you gotta do.
[Moto X Android Development] athulele:
Performing a full wipe works perfectly fine.
[Moto X Android Development] tomh12player:
Will this ROM be updated to 5.1 anytime soon? I can't wait :)
[Moto X Android Development] Quasar:
It's already been updated for other devices. I've been super busy with exams and family the last month or so. I'll try updating soon.
[Moto X Android Development] tatttoo46:
battery is not charging fast also standby is not good:(

---------- Post added at 05:11 PM ---------- Previous post was at 04:59 PM ----------

sorry wrong post...wrong section
[Moto X Android Development] bvsbutthd101:
No rush, life comes first. I'm still on the version before the last update and it's still running great. Haven't run into a single issue yet. Besides GPS not working initially but running those two command lines in fastboot fixed that right up.
[Moto X Android Development] dhasha1:
access to motorola apps after rooting

Will I still have access to all Motorola apps. I really like using those apps. With apps i mean the moto alert and moto assist kind of stuff.
[Moto X Android Development] cdiamond:
Nah man its not a stock base ROM unless you side loads these apps via apk

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

And once you leave stock ROM you leave all the features that are with it
[Moto X Android Development] Raldios:
Installed this a few days ago, flawless so far. Haven't had any problems as far as I can tell. Thank a lot for the good work!
[Moto X Android Development] bvsbutthd101:
Anyone else getting "Unfortunately, Google Play services has stopped" error? I just downloaded the new Google photos app today and when I go to sync a folder of pictures that has a lot in it it won't sync and just comes up this error.
[Moto X Android Development] jco23:
I got that too, but after I unblocked the wake via privacy settings, it stopped.

Battery life still seems solid.
[Moto X Android Development] bvsbutthd101:
Can you elaborate more on that? I can't seem to find anything saying "wake" via the privacy settings.
[Moto X Android Development] jco23:
Settings - security - privacy - privacy guard - (menu) advanced - google play services - keep awake.

I initially blocked that, but when I unblocked it (default), the force closes stopped.

But keep in mind that I'm the nexus experience ROM.
[Moto X Android Development] bvsbutthd101:
Mine was unblocked by default. Blocking it and unblocking I'm still getting the force closes.
[Moto X Android Development] jco23:
then perhaps your Google Play Services app is not the most recent version. I recall seeing here a link to each daily release.
[Moto X Android Development] bvsbutthd101:
I'm on 7.5.71. I know a new one is being released soon. Maybe that'll fix my issue.
[Moto X Android Development] ricardopablo1:
Can't unmount USB OTG

Hi!

I have installed CyanHacker-Lollipop and it works fine and well in all that I can test in 4 days, except that the system mounts any USB stick in OTG mode but isn't any way to unmount, in "Settings"-"Storage" (there may be a section named "External Storage"), by example. And when I remove the USB stick, I get a message "SD card removed - Please insert a new one". Is not necessary to manually unmount the USB?

I have read all the post and have make many searches but I can't find answers by myself.

Thanks for this great ROM!
[Moto X Android Development] kieranc88:
Clean or dirty flash?
[Moto X Android Development] Quasar:
Clean. The answer to all the secrets of the universe is clean flash.
[Moto X Android Development] kieranc88:
OK so come from cm12,full wipe and install your ROM +gapps.
[Moto X Android Development] fuzzylax:
Thanks for answering my question, I did see that but just wanted to be certain that I did everything to a T..I
[Moto X Android Development] yugonline:
CM 11 required?

I was wondering, how does it matter whether I am running a CM11 or stock if I am going to a clean flash anyway ?

I am using TWRP 2.6.3.0 I have clean flashed the unofficial CM12 ROM before, and that time the CM11 to CM12 thing was not there, what is this sudden change of events. :confused:
[Moto X Android Development] perfoliate:
Somewhere around December 17-18 CM12 based builds stopped booting when coming from non-CM based ROMs.

Nobody has figured out why you need to flash over a successfully booted CM ROM first even though you'll do a full wipe, but it is necessary at the time being.

You can actually flash over any of the successfully booted CM12 builds built prior to the December 17-18 change instead of CM11, but to ease the confusion its generally recommended to flash over CM11 because it works.

I'm guessing a CM commit around December 17-18 could be reverted to fix this.
[Moto X Android Development] Quasar:
It might be a firmware or driver upgrade. CM seems to be doing that on CM12.
[Moto X Android Development] perfoliate:
Unfortunate I'm not qualified to find and fix it but it would very beneficial if someone could track it down and solve it. Especially since most ROMs are based of CM.

Is there a "ghost" maintainer for CM these days? I'd like to reach out to them.
[Moto X Android Development] Quasar:
Haha it wouldn't be wise to revert the commit since it's only for the better (usually). The CM ghost maintainer is Ethan Chen.

P.S. I might be able to pick out the update (if there is any) from CM11 and add it to the CH zip.
[Moto X Android Development] sruel3216:
yea its a bit of a hassle but nothing major. i just keep a cm12 booted nandroid on my phone for now. everytime i wanna try a new rom, i just restore the nandroid real quick

---------- Post added at 09:16 AM ---------- Previous post was at 09:10 AM ----------

one day with the rom and its running well. only bug is google maps navigation. it doees not update turn by turn. i have seen this problem on a few cm12 roms however.

as far as batter...seems better than cm12 nightly but still not as good as 4.4.4 rom i was on. good work!

---------- Post added at 09:18 AM ---------- Previous post was at 09:16 AM ----------

fyi, cm12 2/18 build has fixed bluetooth.
[Moto X Android Development] icerebro:
Nice

I have tried this rom since last night, it seems really god, is smooth and still not crash. I like the thing that wakes up the phone when you pick it up, I thought it was never going to be implemented. I am going to try the "Ok Google" feature and with that it will be awesome!!

Thanks for this work!
[Moto X Android Development] matt1313:
Does this have navbar customization? I.e. remove recents and put search in its place?
[Moto X Android Development] sruel3216:
i just tried...you can add search, but i cant figure out how to delete the recents
[Moto X Android Development] SomeDooD123:
How long should the first boot be taking? Mine is still trying to boot (at boot animation), has been about 30 minutes so far.
[Moto X Android Development] JimJ2Mz:
It shouldn't take that long.

Refer to my post a page or two back and see if you missed anything.

It should be a long post of instructions.
[Moto X Android Development] matt1313:
Thanks hopefully it will be updated
[Moto X Android Development] jco23:
my theory is that it could be kernel related.

i also theorized that one needs be on ART prior to the flash given that lollipop is ART-based. but my attempt failed.
[Moto X Android Development] Quasar:
That's on the way. Probably, by the next few builds it will be implemented.

Definitely not related to ART. I constantly cross-flash between dalvik and ART on my other devices, and it never causes issues, and it never would.
[Moto X Android Development] matt1313:
Sounds good. Looking forward to it.
[Moto X Android Development] JimJ2Mz:
Anybody play around with the performance settings yet?

Governors, I/O schedulers, KSM, all that.
[Moto X Android Development] icerebro:
Anyone have tried the Ok Google feature in voice google settings? I trained the command but I doesnt wake up when I say it...
[Moto X Android Development] Quasar:
You're trying to use the Google Now Launcher integrated voice wakeup. That will only work on screen off when your phone is charging. CM hasn't implemented the stock "OK Google Now" feature yet.
[Moto X Android Development] icerebro:
No, I ment when I tried CM12 it worked with the screen on, I said Ok Google, and it listened all what I asked. But now I can not in this ROM. I can activate the feature, I can record the command (3 times as asked) but when I say it it doesn't do anything. I am not in Google Launcher.
[Moto X Android Development] JimJ2Mz:
New build today, maybe, [MENTION=5585603]Quasar[/MENTION]? ouo

Also, will wakelock blocker be added to this ROM or.
[Moto X Android Development] Quasar:
Ahh. We don't use the CM launcher. So you'll need Google Now Launcher for it to work. :)

Umm... I don't think wakelock blocker is high on the priority list since we have a lot of other things to add before it. Also, new build will most likely be tomorrow because I'll be looking to add a few features and optimizations to CH today. ;)
[Moto X Android Development] enmriley:
I have the same issue, however it did respond once but not again.

---------- Post added at 06:42 AM ---------- Previous post was at 06:41 AM ----------

Does anyone know how to disabled SU or where it is burried?
[Moto X Android Development] icerebro:
Anyway, I had to uninstall it, cuz after 2 days of use, I lost Internet Connection. Lost my 3G and couldn't get it back...!!
[Moto X Android Development] JimJ2Mz:
Just a heads up for those in the US, Motorola's having a sale for the Sol Republic Tracks Air until March 3rd.

Originally $200, now only $75. > http://www.motorola.com/us/accessor...la/TRACKS-AIR-by-SOL-REPUBLIC-x-Motorola.html

I'm getting them today, and I just realized that the current build of CH is one day before the bluetooth fix CM pushed out. These headphones use bluetooth. q-q

On the other hand though, I really like this ROM. Wally, one of the CH apps, specifically. All these wallpapers are just so gorgeous.
[Moto X Android Development] Quasar:
New build in 8 hours. (Overnight for me)
[Moto X Android Development] JimJ2Mz:
I sort of forgot we live in different timezones. XDA, why u do dis
[Moto X Android Development] sruel3216:
sweet i cannot wait!!! last build has finally become my daily driver over all other lollipop roms. new build will be even better im sure!
[Moto X Android Development] JimJ2Mz:
There's been things like Quick Capture (twist for camera) and proximity sensor detection for Ambient Display (which makes activation closer to that of Moto Display) that have been merged with the latest CM builds.

Interesting indeed. Side note, I've encountered a single random reboot during usage today. No biggie though.

Quick Capture - http://review.cyanogenmod.org/#/c/89406/

Ambient Display via proximity sensor - http://review.cyanogenmod.org/#/c/89407/
[Moto X Android Development] Quasar:
All that will come in a few hours. ;)

EDIT: Drat! The build errored again. A little longer now. :D
[Moto X Android Development] JimJ2Mz:
Thanks again for the effort, really.

I'm all for waiting for as long as it takes, so there's no need for ETAs. But yeah, thanks, Quasar.
[Moto X Android Development] matt1313:
How about remove recent Navy button ?
[Moto X Android Development] Quasar:
Didn't quite understand that....
[Moto X Android Development] matt1313:
Remove recent button in navbar and replace with search button
[Moto X Android Development] Quasar:
That's already there. Look in button settings. Navbar customizations are there.
[Moto X Android Development] matt1313:
Can you try it as it didn't work for me. I couldn't remove the recents button
[Moto X Android Development] Quasar:
Okay... looks like CM hasn't implemented removing buttons yet. I'll cherry pick some other navbar customizations soon.
[Moto X Android Development] matt1313:
Cool thanks
[Moto X Android Development] JimJ2Mz:
Yeah, bluetooth is dead on the current build. Definitely fixed after 2/18.
[Moto X Android Development] tomh12player:
Really like the ROM's under the hood tweaks - it would be awesome if you could add a sound mod like this (http://xdaforums.com/android/software/audio-engine-absolute-sound-project-t3015180), or Viper4Android itself. I personally think it's miles better then the stock audio.
[Moto X Android Development] JimJ2Mz:
[MENTION=5585603]Quasar[/MENTION]

Anything new on the build update front?

Sorry for bothering you, but I've been a bit anxious, waiting for the update.

I'll admit I've refreshed this thread a lot, haha.
[Moto X Android Development] Quasar:
Haha I know that feel. The source is a little messed up right now, so builds are erroring. Once everything is cleaned up, new build will be out. ;)
[Moto X Android Development] EiOL147:
How long does it take? 5 minutes? 10 Minutes?

I'm five minutes waiting stopped in the logo screen.
[Moto X Android Development] enmriley:
Every 5.0 build I use, both on my Moto X and Nexus 5 does this. I usually give in and reboot, things then boot just fine.
[Moto X Android Development] Quasar:
Alrighty. Issues sorted, and new build uploaded. For the changelog, checkout our GitHub.
[Moto X Android Development] JimJ2Mz:
yeeeeeah

been waiting for this to drop- thanks so much!
[Moto X Android Development] sruel3216:
I am patiently impatiently-waiting haha
[Moto X Android Development] mikey0000:
Bugs

Awesome rom guys, loving it so far.

Just two things I've noticed, smart lock fails to read NFC tags and completely locks up settings, I have to reboot to be able to access settings again

and encrypt device doesn't seem to work, just ends up in a boot loop.

again thank you for your hard work.
[Moto X Android Development] SomeDooD123:
Do I need to do a clean install going from 20150217 to 20150223 or can I just flash without wiping? Also is BT fixed in 20150223? Thanks!
[Moto X Android Development] jesan9:
the 02/23 build is working good so far (everything that i use)... very fast, smooth and not even a freeze or reboot... i think im not going back to stock in a while :D Good job! :good:
[Moto X Android Development] sruel3216:
i did not know it was out already!!
[Moto X Android Development] guimeleiro:
My moto x has a bug on GPS. How to fix it?
[Moto X Android Development] sruel3216:
i dirty flashed over the previous nightly and started to have a ton of bugs. did a clean flash and everything is working well now. great job

---------- Post added at 10:57 AM ---------- Previous post was at 10:06 AM ----------

can i give a recommendation?

under settings menu, i think it look more organized if each section was listed alphabetical

just a thought lol
[Moto X Android Development] sasokutenshin:
I'm pretty sure CM hasn't merged it in CM12 (no idea if they plan to), but if you're feeling froggy, it'd be pimp if you re-added Voice+ and the necessary supporting framework tweaks. Hopefully someone here is OG enough to know what I'm talking about lol.
[Moto X Android Development] dakshkhorana:
http://xdaforums.com/devdb/project/?id=8280#bugReporter

Please follow the above link for my problem.
[Moto X Android Development] Quasar:
That would be hard because it includes a lot of proprietary code, but if you could link me to it, i could try. :)

Did you flash the CM11 M12 prior to flashing this ROM? If not, this ROM will bootloop. Otherwise try reflashing.
[Moto X Android Development] orky87:
See here!
[Moto X Android Development] dakshkhorana:
You mean to install cyanogen mod first by factory wipe and then apply update and then apply update from sd card and choose cyanhacker(without wipe?)?

Thanks
[Moto X Android Development] Quasar:
Oh no. Do a full wipe, then flash CM11. Then wipe again, and flash CyanHacker and gapps. :)
[Moto X Android Development] dakshkhorana:
Full wipe?

You mean clearing everything susch as dalvik and all that?

Also then whats is the meaning of flashing CM11 and then wipe again.

Would please ilustrate how to do a full wipe...

Googling it I got that wipe everything 2 times!

Is it correct or some other method should I follow.

Thanks for your help
[Moto X Android Development] Quasar:
There is a sort of a firmware update in CM11 which will prevent a bootloop on CM12. A full wipe is basically wiping system, data, cache and dalvik cache.
[Moto X Android Development] luiscedillo80:
OMG

Wooow iam impressed the best and better ROM ever, the most complete of all ROMs thank s a lot developers I love so much this work :D
[Moto X Android Development] Quasar:
New build up. For changelog, check out the CH GitHub.
[Moto X Android Development] sruel3216:
what a nice treat. thanks!

---------- Post added at 12:48 PM ---------- Previous post was at 11:52 AM ----------

running smooth. that new viper audio app is a lil weird. not really sure if it even works lol
[Moto X Android Development] Vinnie8018:
Any way to retain all of Motorola's features such as Active Notifications, Touchless Controls, etc..
[Moto X Android Development] Quasar:
Active notifications are included. Touch less controls are not.
[Moto X Android Development] Vinnie8018:
Thanks for the speedy reply! Oh, I cant find it on the settings menu - is there something else I have to do to enable / configure? I tried pulling the old APK from another moto x to no avail...
[Moto X Android Development] Quasar:
Enable ambient display from display settings
[Moto X Android Development] Vinnie8018:
Its on, no joy. The fact that I do not use a screen lock stop it working?
[Moto X Android Development] Quasar:
You don't use swipe to unlock? Then I don't think it will work
[Moto X Android Development] Vinnie8018:
Just toggled it, with swipe it works without it doesn't. :(

I have no need for the exercise of swiping the screen - shame active display worked without a lock screen

Thanks again
[Moto X Android Development] matt1313:
Any luck on cherry picking?
[Moto X Android Development] stealtheye:
Any Screenshots for this rom??
[Moto X Android Development] H4x0:
I was really impressed with this ROM, however i'm having some serious issues now (not sure if they are due to the ROM or not). I was running the latest build on my phone and it was working fairly well then i decided to try a new Kernel (specifically zwliew r11) so i backed everything up in TWRP and flashed the new Kernel. My first boot didn't work at all i never got to the boot logo it just kept kicking me back to TWRP so i restored the backup i had just taken before flashing the kernel. The backup managed to boot to the lockscreen but it had a ton of Google Play related errors so i waited a couple minutes then tried to reboot. After the reboot it would not make it past the boot animation (15-20min wait) so i went back into TWRP, wiped everything and reinstalled the ROM from scratch and still it won't make it past the boot animation. I've tried a fresh wipe and install 3 times now each time waiting 15-20min at least on the boot animation. I've also tried waiting a while on the boot animation and force restarting the device to no avail. Does anyone know what could be causing this and how i can fix it?
[Moto X Android Development] JimJ2Mz:
Wipe everything. And I mean EVERYTHING. Format Data as well.

Then flash the latest CM11 snapshot- https://download.cyanogenmod.org/get/jenkins/90775/cm-11-20141115-SNAPSHOT-M12-ghost.zip

If that doesn't boot, then you'll have to go back and try to boot with stock, and/or ask zwliew for help.

His kernel was STRICTLY MEANT FOR STOCK-BASED ROMS.

Every Lollipop ROM is AOSP/CM based and he has long since discontinued support for these ROMs.
[Moto X Android Development] H4x0:
Thanks, that worked. I flashed back to CM11 then upgraded to stock CM12 for now, everything seems to be working as usual now. I was a bit confused about compatibility with CM12 based ROM's because it seemed like other people on Lollipop were using it, turns out i was wrong :(
[Moto X Android Development] JimJ2Mz:
No problem. It happens.

You can wipe and flash CyanHacker again if you want.
[Moto X Android Development] moregt1:
I used this rom for 2 days last week. Really enjoyed it. But i never could get the stock messager to work. It wouldnt let me send any messages. And it would drop signal. I have the 1056 on sprint. Any ideas??
[Moto X Android Development] Quasar:
Logs or it didn't happen. ;)
[Moto X Android Development] cl06:
Thank you

:confused:
[Moto X Android Development] A2Trip:
I actually experienced same issue on my XT1055 (US cellular)
[Moto X Android Development] bvsbutthd101:
I just got this phone last night and installed this ROM and finished setting up this morning. So I never got to use the phone in its stock form. Does the notification light work on this ROM. I've seen it turn on but not exactly work with say for example my texting apps. I have it enabled in the settings so i don't know why it isn't working.

EDIT: Never mind
[Moto X Android Development] monster30:
got the same issue, i'm still running the rom so here's my log

https://drive.google.com/file/d/0B-ezF6AlYiwLTXM3U2V6UklNYTg/view?usp=sharing

don't know if i got it right, i follow instructions from another post :o
[Moto X Android Development] towir022:
hash tag pounds symbol in status bar

How do I get rid of the pound symbol in my status bar
[Moto X Android Development] bvsbutthd101:
Not sure how to get rid of it but from what I understand the pound symbol indicates a app that is running is using root.
[Moto X Android Development] towir022:
OK thanks I understand that it signifies root however I do not really like it there on my status bar all the time. Does anyone know of a way to get rid of it?

Also with the launcher is there a way to select which screen is your main home screen? I want my main home screen to be in the center not all the way to the left