yashsingh1/xdaforums huggingface dataset:
[Moto X Android Development] MikeyNick:
I personally didn't but you should be able to just fine. I have a few meetings this morning but after that I'll post the new build that reports the proper version

EDIT:

Here is the clean build, which will correctly show 5.3.6 in your "About phone". Other than that it's exactly the same. below the zip is a link to the md5

<Removed> Builds moved to AndroidFileHost. See post: http://xdaforums.com/showpost.php?p=59124466&postcount=527
[Moto X Android Development] mikel.canovas:
Could someone post or link a changelog?
[Moto X Android Development] MikeyNick:
https://github.com/ResurrectionRemix/android_vendor_resurrection/blob/lollipop/CHANGELOG.mkdn

EDIT: I'd say the most welcome change is fixed bluetooth audio :D no more rebooting the device every time i want to connect to my car bluetooth or bluetooth speaker.
[Moto X Android Development] jshinn1:
Yep its been great the last couple of days on all the ROMS Bluetooth was the last issue that kept it from being my DD
[Moto X Android Development] kerryh420:
First I want to once again say thank you to the Dev's providing the community with such a great ROM. I've been using your ROM as my DD (bugs and all) and have been quite pleased, minus the lack of a dark theme as that is my favorite part of ROMing . Well done you guys. Much oblige.

I have never had a problem flashing any of the RR ROMS until recently. The last successful flash was 5.3.3. No error during flash, no boot loops, not ever. So I am confident in my ability to remove the lines of updater script that need to be removed for a successful flash. However Moved onto 5.3.4 and have had nothing but issues. While I got through the flash ok I had many issues with play services, and with Drive not just FC but I cant do anything else as every second there is a pop up interrupting me.

With no clue as to why or what is causing this (even after updating play services to 6.7.xx) I thought maybe I'll just go straight to 5.3.6. Deleted the req'd lines form the updater script. Wiped cache, dalvik, factory reset and clean to install a new rom. using latest philz.

I get an immediate status 6 failure. I know about using the search before asking and I know of the steps to go through before asking such trivial info but guys, I'm still pretty much a noob despite the fact I have many dozens of successful flashes dating back to the X2. I just don't understand computer stuff like you guys do ...yet.

Can anyone please help? I like this ROM alot and really would like to keep using it but 5.3.4 has got major issues on my phone and I can't use it because of it.

My question is how do I go from 5.3.3 to 5.3.6 successfully? (and whatever happened 5.3.5? I see no mention of it in the thread) And yes, I am aware that #Watchout# is on break for exams so I expect no reply from him. Please keep studying ....Anyone else? Please?
[Moto X Android Development] MikeyNick:
If I recall correctly, it was recommended to do a clean install for 5.3.4 because of some rather major changes. For that reason, I would expect that you would run into similar issues trying to dirty flash from 5.3.3 to 5.3.6

The other thing I noticed is that, if you wipe data on a cm12 rom (or maybe just this one? haven't tried with others, but would assume it would apply elsewhere), you end up with a bootloop. I haven't tried doing a factory reset from the phone's settings, and I can't speak to using philz, but using twrp, i always got a bootloop if i wiped data. the only way i ended up successfully achieving a clean install was to wipe, install cm11, boot, and then install this.

I had built version 5.3.5 but shortly after 5.3.6 was available so i didn't see a point in uploading 5.3.5. I've been running stable for the last couple days on my xt1053, but i don't need to remove any lines from the updater script either.
[Moto X Android Development] ##W4TCH0UT##:
For getting dark theme, [MENTION=4144763]westcrip[/MENTION] has made a theme called "pitchblack". Search on the play store for it " pitchblack". It's already included in 5.3.6, I guess. Just change the theme to pitchblack from theme manager. You can only use pitch black on versions 5.3.6 and above.

Screenies of pitch black:

Regards
[Moto X Android Development] MikeyNick:
Moving the builds over to AndroidFileHost. Just uploaded 5.3.6 from the other day there, and will be pulling it off my dropbox. Here is the new link:

https://www.androidfilehost.com/?w=files&flid=26955

I'm currently building 5.3.7. Once I get out of work I'll flash it just for sanity and then upload it.

EDIT: dirty flashed over 5.3.6 and all is good. 5.3.7 has been uploaded to the above link. Happy flashing!

Changelog: https://github.com/ResurrectionRemix/android_vendor_resurrection/blob/lollipop/CHANGELOG.mkdn
[Moto X Android Development] EvilDragonEX:
changelog please?
[Moto X Android Development] MikeyNick:
My bad, updated the post with the changelog. This link will continue to show the change log for future versions, but I'll try to remember to post it with new builds just for convenience.
[Moto X Android Development] makysssdroid:
I can update from 5.3.4 or clean flash ust better ?????
[Moto X Android Development] Yann68:
How can I remove the lines in updater-script? Can I make this on the phone or PC? Which program should I use?

Thanks
[Moto X Android Development] CsR0501:
RR 5.3.7 + xposed framework (greenify LL beta) + V4A 2.3.4 (LL) = the best mix of all the time! :')

Thanks to the devs!!! [emoji7]
[Moto X Android Development] ##W4TCH0UT##:
For changelogs, there is a link in op. Check that. Also do try pitchblack from play store.
[Moto X Android Development] Zaibu:
help please

I cant flash twrp in my moto x 1st gen please help how to flash it with fastboot :(
[Moto X Android Development] Cassini-Huygens:
the 5.3.7 build is not booting up for me
[Moto X Android Development] kerryh420:
---------- Post added at 07:01 PM ---------- Previous post was at 07:00 PM ----------

[/COLOR]

---------- Post added at 06:59 PM ---------- Previous post was at 06:43 PM ----------

[/COLOR]I assume you are rooted and bootloader is unlocked? Are you familiar enough with ADB to get into fastboot through ADB commands? Double check to see ,you need to have install from unknown sources, and USB debugging checked or on)? Also make sure all of your files are in the root directory and that you have the command window aimed at it.

If this is done then into the command prompt type:

adb devices (to check to see your device is found)

adb reboot bootloader fastboot (phone reboots to fast boot)

fastboot devices (again to make sure your phone is recognized)

Fastboot flash recovery [recovery file name]

DONE.

Reboot your phone to recovery and see if it worked. What is your recovery right now if I may ask?

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

I DL CM12 2/20 build (Couldn't find a CM11 build) Flashed ROM, Flashed gapps. rebooted to recovery and tried to immediately, without wiping cache or data, flash 5.3.4 (with updated script) over it. Immediate flash fail.

Also did the same as above but rebooted to system instead of straight to recovery, I did not go through the setting up process before rebooting to recovery and Flashing 5.3.4, again without wiping anything.

I am using latest philz recovery and have never had a problem flashing anything until now. looked for CM11 on cyanogenmod but all build are page not found errors. My errors are happening during the first few seconds of the falsh, I never even make it to bootlooping.

What exactly did you mean by clean install? sbf 4.4.4? and now that 5.3.6 and 5.3.7 are out can I skip straight to those?

Does anyone else notice what I am doing wrong?

Thanks guys

EDIT: Should I have NOT updated the script for my xt1060???
[Moto X Android Development] MikeyNick:
You should be able to dirty flash, but I haven't, and haven't seen anyone else say they have. But i think it should be fine. You could always be the trailblazer and let us know after a nandroid ;)

extract the zip and then go in the META-INF/com/google/android, and in there is an "updater-script", which you can open in notepad++ or sublime text to edit (or any text editor)

That link goes to an old gist showing the changelogs for 5.3.6, not the actual change log file on the repo.

And yes, definitely try pitch black. Better than the other dark theme, which themes too much and ends up with dark fonts on dark backgrounds and such.

Did you wipe data? if so, that is why. What were you coming from?

To my understanding, it was only XT1052 that needed to do that, but looking at the updater script, i don't see why they would need to do it either... I'd say try flashing it without removing the line. All the first line does is assert that your device is some variant of ghost, which xt1060 certainly is
[Moto X Android Development] ##W4TCH0UT##:
Changed link to future changelogs in op.
[Moto X Android Development] jco23:
Trying this out now. Was first in OSE, then BlissPop. Simply wiped dalvik/cache, installed ROM, then GApps.

First thing that I noticed was that the other two had adaway built in. No woodies, I just installed it manually.

Other than that, very smooth.

Thx!
[Moto X Android Development] JimJ2Mz:
How's battery life on this ROM? Currently on BlissPop and battery is eh.
[Moto X Android Development] jco23:
I can let you know in a few days. Bliss was great at first, but latest killed battery.
[Moto X Android Development] JimJ2Mz:
Oh crap. Latest BlissPop has bad battery life? I was gonna flash the latest tonight. :c

Thanks.
[Moto X Android Development] CsR0501:
I have very serious problems with the dialer (I think) because when I call somebody I can't hear nothing....

Clean install and wipe the dialer, cache/dalvik... But nothing :(
[Moto X Android Development] kerryh420:
Try to toggle the speaker on /off real quick once the call has been placed .
[Moto X Android Development] anadarco7:
Blissops ROM is good he is doing his best he may provide update for this battery issue later so can we just talk about only RR please NOM
[Moto X Android Development] CsR0501:
V4A problem... Forget it! [emoji16]
[Moto X Android Development] eeriikk:
I'm running the latest build (5.3.7) with tdh kernel, and have used V4A with it as well with hardly any issues at this point. I had switched to OSE ROM after initial 5.3.4 RR, and was anxious for an RR update as OSE's battery life left me disappointed and I would get FC's when trying to turn on my network traffic indicators. My battery life hasn't irritated me yet on this build...for example, I flashed it on my way to work at 7 am on Friday, and when I left at 5:40pm I still had 40%, and I screw around on my phone a LOT while at work. Also no longer have any in-call audio issues :)
[Moto X Android Development] kerryh420:
network issues

Is anyone else having issues with network connections since 5.3.7? When I try to open google, googles settings or google now it says network error and I can't use anything in those apps. I am connected to my router/modem both 5G and 2.3 so I have no idea what it's talking about.

Anyone know what is wrong and how to fix, please?!
[Moto X Android Development] jco23:
No issues for me. How about mobile data? If that works fine, then it could your WiFi settings.
[Moto X Android Development] kerryh420:
That's what I don't understand. I can see and connect to my 2.3ghz, 5ghz and _EXT Wi-Fi networks, surf the web, email and all that but it's those three google apps that won't launch. Keep getting "network error check your network connections".

It is talking about my home router/modem, right? I'm kinda bummed. This is a big deal. google settings controls almost every app I utilize. I may have to revert to an earlier build until I figure out what is causing it. I'm thinking it's something simple. The only thing I did today that was different is I plugged the ethernet cord from my computer into the router/modem physically rather than using the Wi-Fi. I don't think that would have caused it as all other devices work and most of the apps in my phone too.

Anyone else have any info or ideas to offer. This is driving me insane. Thx
[Moto X Android Development] imparables:
Have you tried any of these?

http://www.techkhoji.com/no-connection-retry-google-play-store/
[Moto X Android Development] jco23:
Reflash gapps
[Moto X Android Development] imparables:
Also try deleting your card preferences... Just saw it on Google+
[Moto X Android Development] bernardad99:
yes let me know which one you need

---------- Post added at 02:06 PM ---------- Previous post was at 02:01 PM ----------

why cant i do 60 fps recording
[Moto X Android Development] jshinn1:
Was having same issue this worked for me Google now is showing my cards again
[Moto X Android Development] jco23:
has anyone gotten "ok google" to work from a locked screen? I thought I read somewhere that some folks were able to this, but I cannot.

I made sure to enable voice recognition and I am using the google launcher app.

thanks!
[Moto X Android Development] jco23:
I would like to be able to upload my pictures from my gallery app to my picasa web album (and specify which album to place them). i believe this is standard on stock OS. however, I've noticed on this ROM (and other CM12 ROMs) that it will only allow you to upload to photo albums (essentially place them in a "backup" album, after then, I can move them to the appropriate album via computer).

am I missing a setting, or do I need to re-install the stock motorola gallery app?

thanks!
[Moto X Android Development] MikeyNick:
It's possible that this was a feature of the stock gallery app. Typically, the app which has the content broadcasts an intent to the rest of the system, and any apps registered to handle that intent are presented for the user the choose. It could be that the aosp gallery app is not firing the proper intent for what picasa is expecting, but that seems kind of unlikely. You could give the motorola version a go.

---------- Post added at 09:41 PM ---------- Previous post was at 09:33 PM ----------

Version 5.3.8 is up: https://www.androidfilehost.com/?w=files&flid=26955

Changelog: https://github.com/ResurrectionRemix/android_vendor_resurrection/blob/lollipop/CHANGELOG.mkdn

EDIT: Link fixed. sorry bout that!
[Moto X Android Development] stevenx37:
Please fix the link to the download. It requires us to login to access it.

Thanks in advance :)
[Moto X Android Development] flick36:
Dirty flash?

Can i dirty flash 5.3.8 over 5.3.7?
[Moto X Android Development] MikeyNick:
Yes
[Moto X Android Development] St.Noigel:
Hmmm...

From changelog -

What it means? Does anybody already try 5.3.8?
[Moto X Android Development] CsR0501:
:good:Now ambient display works with the proximity sensor too!
[Moto X Android Development] MikeyNick:
Indeed, it appears you can now wave your hand just above the screen to activate the ambient display. Not quite the foot or so you get with the moto x 2014, but probably 1 or 2 inches.

On a side note, I'm actually getting system UI force closes when going into landscape mode... Not sure if i did something or it has to do with 5.3.8. I probably should have done a backup first :-p Anyone else experiencing this?

EDIT: Indeed, a change that was made late yesterday introduced the issue (a null ref in PhoneStatusBar). I know the fix, I just have to make it and I'm a little busy at work today so it'll probably be later today...
[Moto X Android Development] MikeyNick:
Alright, I made the fix and rebuilt. I removed the previous build from AFH and put the new one, but it's the same name so might not seem like it... but trust me it's thee new one.

Anyone that already installed it, just flash this over it and it'll fix landscape. For anyone that hasn't updated yet, just flash the one that's currently on AFH and you're good. Same links as before forr build/changelog
[Moto X Android Development] kerryh420:
FYI- Google play services keeps crashing upon boot for me. Unlike the last few updates the play services error was fixed by installing the most recent version of it. That did not work for me this time. Instead of FC I'm getting "play services is not compatible with this device".

Any ideas what could be wrong?
[Moto X Android Development] bloodletting284:
Can I flash this over 5.3.4? Or should I flash something in-between? Thanks!
[Moto X Android Development] flick36:
You have to make a full wipe (dalvik and cache) and make a clean install cause don't remember what was add on 5.3.5 and later that was fixes on 5.3.4.
[Moto X Android Development] kerryh420:
Does anyone else have the problem or does anyone know why the pitchblack RR theme from play store (paid version) is only making dark some of the apps that t says it inverts? For example, contacts and the dialer become inverted yet the stock messenger app does not.

Any ideas why or how to fix?
[Moto X Android Development] jco23:
Perhaps wipe cache/dalvik before flashing and install gapps after each update.
[Moto X Android Development] MikeyNick:
Awhile back, messenger was listed under "coming soon". I thought he hadn't gotten to it yet but it lists it there now... I guess just wait for a future update and hope it comes!

For what it's worth, I always wipe cache/dalvik and flash gapps after rom, and i haven't run into this issue.
[Moto X Android Development] nathanharmonn:
So how's the battery if on this ROM like? Cm always likes to drain my battery with new wakelocks... Opinions please!
[Moto X Android Development] MikeyNick:
Not as good as Kitkat for sure, but no lollipop roms have been (even stock, for people with devices that got the official). There are things you can do to make it better, like using greenify, which is now supported on lollipop. I usually was able to get 40-48 hours moderate usage on Kitkat, that's probably somewhere in the range of 24-36 on lollipop, typically closer to 24.
[Moto X Android Development] jco23:
I'm actually getting better battery life compared to stock.

Daily driver for me. Kudos to Dev!
[Moto X Android Development] caviera:
bootloop

Always bootloop in 5.3.8... how to solve: flash gapps and wipe dalvik+cache :)
[Moto X Android Development] Megatron007:
U need to flash this rom over cm11
[Moto X Android Development] caviera:
Yes I did, as described in instructions, but despite that it always do bootloop, until flash gapps...
[Moto X Android Development] devarajan_p:
No audio in calls

There's no in-call audio in 5.3.8... speaker phone and Bluetooth works good though
[Moto X Android Development] caviera:
Did you flash over 5.3.7 or CM11?
[Moto X Android Development] zapinho:
Where can I find the new Nightly? The website link just brings me to 5.3.4. Where is the link 5.3.8?
[Moto X Android Development] Kir6y:
I removed these lines from the updater-script file. As told in your recent post.

assert(getprop("ro.product.device") == "xt1052" || getprop("ro.build.product") == "xt1052" || getprop("ro.product.device") == "ghost" || getprop("ro.build.product") == "ghost" || getprop("ro.product.device") == "xt1053" || getprop("ro.build.product") == "xt1053" || getprop("ro.product.device") == "ghost_retail" || getprop("ro.build.product") == "ghost_retail" || getprop("ro.product.device") == "xt1055" || getprop("ro.build.product") == "xt1055" || getprop("ro.product.device") == "ghost_usc" || getprop("ro.build.product") == "ghost_usc" || getprop("ro.product.device") == "xt1056" || getprop("ro.build.product") == "xt1056" || getprop("ro.product.device") == "ghost_sprint" || getprop("ro.build.product") == "ghost_sprint" || getprop("ro.product.device") == "xt1058" || getprop("ro.build.product") == "xt1058" || getprop("ro.product.device") == "ghost_att" || getprop("ro.build.product") == "ghost_att" || getprop("ro.product.device") == "ghost_rcica" || getprop("ro.build.product") == "ghost_rcica" || getprop("ro.product.device") == "xt1060" || getprop("ro.build.product") == "xt1060" || getprop("ro.product.device") == "ghost_verizon" || getprop("ro.build.product") == "ghost_verizon" || abort("This package is for device: xt1052,ghost,xt1053,ghost_retail,xt1055,ghost_usc,xt1056,ghost_sprint,xt1058,ghost_att,ghost_rcica,xt1060,ghost_verizon; this device is " + getprop("ro.product.device") + "."););

Before removing anything I had still received the message and also i'm on TWRP v2.8.1.0.
[Moto X Android Development] ##W4TCH0UT##:
I get that. But before the error did any message come up on the screen. That actually defines your error.
[Moto X Android Development] Kir6y:
Updating partition details...

Full SELinux support is present.

MTP Enabled

Installing '/sdcard/Resurrection_Remix_LP_v5.2.4-20141221-ghost.zip'...

Checking for MD5 check: no MD5 file found

Can't install this package on top of incompatible data. Please try another package or run a factory reset.

E:Error executing updater binary in zip '/sdcard/Resurrection_Remix_LP_v5.2.4-20141221-ghost.zip'

Error flashing zip '/sdcard/Resurrection_Remix_LP_v5.2.4-20141221-ghost.zip'

Updating partition details...

---------- Post added at 02:16 AM ---------- Previous post was at 02:00 AM ----------

Apparently after my 3rd time Wiping and Factory Resetting it install. Working great now :). Thanks for your help and I'll keep posted if I find not mentioned bugs .
[Moto X Android Development] jashan7492:
I flashed the rom without changing the update script but the rom booted up fine after 5 minutes thank you dev :D :good: :cool:

---------- Post added at 04:02 PM ---------- Previous post was at 03:49 PM ----------

I still cannot set my photo in the account:confused ::confused:
[Moto X Android Development] 690sid:
hey guys.... does ambient display work properly in this rom? does it respond to picking up?
[Moto X Android Development] Kir6y:
It doesn't for me :(. But he did say its in. Still a great rom :)
[Moto X Android Development] txt11:
I remowed it,I saved it Notepad and twrp 2.8.0.1 I am useful.:(
[Moto X Android Development] piskr:
Followed instructions 100% and failed to flash the rom on xt1052.
[Moto X Android Development] vasili_defy:
To all facing the flashing problem ,try changing TWRP to 2.6 version ! 2.8 version gives errors
[Moto X Android Development] Kir6y:
Also aside of what vasili_defy said, Don't forget to Wipe and Factory Reset. I had to do it a couple of times. :)
[Moto X Android Development] mulle1:
Is not working for me,only bootloop.

I have 3x wiped and Factory Reset,the problem is the same.

My phone was EU XT 1052.
[Moto X Android Development] ##W4TCH0UT##:
What was the error that was occuring while flashing the ROM? And did you wait for 5-10 minutes...It's actually the bootanimation that's looping.
[Moto X Android Development] ##W4TCH0UT##:
This ROM is now official!!!!

Thanks to [MENTION=4144763]westcrip[/MENTION] and his wonderful ROM.

Enjoy guys!!
[Moto X Android Development] mulle1:
Under TWRP 2.6. bootloop, I wait over 15 Minutes.

TWRP 2.8. is not working on my Phone, Error Message before flashing.
[Moto X Android Development] ##W4TCH0UT##:
What is the message? Post the full log.
[Moto X Android Development] mulle1:
Look like the Pin, TWRP installed over toolkit 1.44