yashsingh1/xdaforums huggingface dataset:
[X 2014 Android Development] slogar25:
I believe been explored, however not sure if there is such a thing as an xr1095 running on Verizon. Also not sure if it would work. Custom roms such as CM run on modified kernel built from their source and since we are unable to flash a custom kernel.... But I guess anyone can always download a copy of CM for the XT1095 and try to flash with mofo and see if it boots. That would be a starting place. At least if it boots could potentially make the necessary edits to that system img so that our device would actually function as a phone.(apns_config.xml?)
[X 2014 Android Development] drewski_1:
Just got a used XT1096 yesterday and immediately mofo'd it to 5.1 w/ Xposed :D

Looking pretty smooth so far! Thanks for putting this together! :good:
[X 2014 Android Development] mikeoswego:
Delete - bad info
[X 2014 Android Development] mikeoswego:
<deleted>

MMU on hold..
[X 2014 Android Development] firewater88:
Testing now. Was going to update the old way then saw this this morning. Will report back

Edit: Process went very smooth and easy. I worked off the new base and selected option 4 for patches. Had it reboot phone, it got to boot animation and then a black screen. Re-booted manually and now optimizing 221 apps, so all should be good!

Thanks for the easy way to keep up to date!
[X 2014 Android Development] amd_h4x0r:
wow, this util is awesome! thanks for including BetterBatteryStats in v3!

edit: maybe add the option to wipe cache after a successful flash?
[X 2014 Android Development] mikeoswego:
I used to recommend erasing the cache until reading about how mofo works and then observing the phone screen. Mofo is wiping the cache multiple times when it does its thing, so there is no need to wipe the cache manually. :)
[X 2014 Android Development] mikeoswego:
<deleted>

MMU on hold for a bit
[X 2014 Android Development] nola5712:
Hey thanks for the reply! It turns out that I didn't actually take the update, the phone just downloaded it automatically. So now I just get this silly reminder everyday until I install the update (which I of course keep pushing back every day). That being said, I'll try and mofo up to 5.1 later today, and I shouldn't have any problems correct? Also, in the future I will definitely try to freeze with TBU. So it will just show up in the list named exactly that, "OTA"? Thanks again in advance!
[X 2014 Android Development] redwings73:
Great utility...worked like a charm!
[X 2014 Android Development] mikeoswego:
You can freeze the ota app with Titanium or I'd suggest you use one of the debloat images that just don't have the functionality and also don't check in with Motorola.

I'm adding the process to update a phone from 5.0 to 5.1 to my Mofo Utility and may have that ready later tonight or tomorrow if you want to wait and try that out.
[X 2014 Android Development] drewski_1:
Is Smart Lock working for folks?

I'm getting everything greyed out saying "disabled by administrator"

I have Agent MDM for work, but on my other 5.1 devices only Face Unlock is greyed out b/c Admin

Sent from my Moto X
[X 2014 Android Development] amd_h4x0r:
for me it un-greys after you select a screen lock option besides none or swipe
[X 2014 Android Development] drewski_1:
hmm, so it looks like something funky with stock Exchange on the Moto-X applying policies

I uninstalled Agent MDM - no change. all Smart Lock greyed out

I removed my Exchange Account - all Smart Lock available

I re-installed Agent MDM - only Face Unlock greyed out (same as all my other 5.1 devices)

I re-added my Exchange Account - all Smart Lock greyed out

I removed my Exchange Account, installed Outlook, and added my Exchange account there - only Face Unlock greyed out (same as all my other 5.1 devices)

Feature request [MENTION=5849464]mikeoswego[/MENTION]

Would you consider installing Exchange3 to /system/app similar to what you did for BBB in /system/priv-app ? :o

This is the Exchange that works with GMail so you can add Exchange accounts to Gmail vs. the standalone Email app. Not sure if that will help this issue or not.

The latest Exchange3 from TK GApps is attached. This can co-exist with Exchange2 that works with the Stock Email so no other changes would be required other than putting into /system/app
[X 2014 Android Development] mikeoswego:
I'll check that out and get back to you. Shouldn't be a problem.
[X 2014 Android Development] mikeoswego:
MMU on hold for now...
[X 2014 Android Development] jrbmed08:
I was unable to get the batch to work but was able to patch your 3.0 image and am flashing it manually as we speak. I suspect it's a driver issue - MMU was able to see my phone and that it was fastboot capable but couldn't find ADB. ADB has always been very tricky on my computer - it only works on 1 of 3 USB ports and sometimes I have to unplug and replug the cable to make it recognize my phone as an ADB device. So probably not anything you can do about it, but just thought I'd share my experience.
[X 2014 Android Development] drewski_1:
Release 4 worked perfect for me to upgrade from Base 2 to Base 3!

Thanks for your work on maintaining & improving the Mofo-ing process! :good:
[X 2014 Android Development] mikeoswego:
The batch should work as long as you have mofo and xdelta3. Is checking for adb causing the batch to fail? Or the warnings about not having it were to annoying? It might be better to swap some of the checks around if people are going to have the batch fail if adb is installed but broken.
[X 2014 Android Development] jrbmed08:
I cancelled it because I was concerned it would screw something up on my phone because of not detecting adb. Good to know it would have worked anyway. I'm not sure what the best thing to do about that is. I wouldn't say the warnings were annoying but perhaps misleading? So I probably wouldn't change the batch at all but would say something about that in your instructions.
[X 2014 Android Development] RashaMatt:
Not entirely... It works for a while, then it stops auto-unlocking the device when I'm at home.

This issue might be triggered by having a trusted Bluetooth device connected, and then disconnecting it.

If I remove my trusted devices and re-add them, it works again, but only for a while.

I'm guessing it's an Android bug, not an issue with this ROM specifically.

EDIT:

I rebooted, then forced A GPS lock by opening a GPS test app. Smart Unlock has since been working - based on my being at Home, I assume, since no trusted Bluetooth device has been connected yet.
[X 2014 Android Development] RashaMatt:
Had anyone been able to use custom notification sounds (ogg files on your sdcard) ?

I can choose them (only by using a file manager app - the default media chooser doesn't see them), and then they do work fine...

But after a reboot they no longer work, and the app where they are specified shows the selected filename as some number.

(This might not be related specifically to this ROM - sorry if that's the case.)

EDIT:

Hm, seems to be working for me now. Thanks for the feedback.
[X 2014 Android Development] mikeoswego:
Looks like they are working for me. Looked in several apps with there own choosers and this system chooser. The Calendar Notification sound is in sdcard/Notifications.
[X 2014 Android Development] pyro6128:
I followed the instructions in post 2 after having successfully mofo'ed while on 5.0, and everything seemed to go well. Except once the 5.1 image in post two was done flashing, I tried to go into recovery to wipe cache (like in Jules noob thread) and not my phone isnt working. I keep getting the dead android with the triangle, but it only flashes on screen for a sec and then the screen goes black. Can anyone help me out here?

Edit: Tried flashing the return to stock image and it did not work. But I can now reliably get back into the bootloader. I'm thinking something must have gotten messed up when flashing the different bin files in the first part of the second post.

I'm getting error E: can't mount /cache/recovery/last_log

E: can't open /cache/recovery/last_log
[X 2014 Android Development] mikeoswego:
Ok, make sure you have the correct files. You can get them here if want to make sure: XT1096_5.1-Base.7z Extract the files from the archive, put them in the same folder as your mofo program

Put the phone into fastboot mode, connect it to your computer and then run the following commands:

fastboot flash logo logo.bin

fastboot flash boot boot.img

fastboot flash modem NON-HLOS.bin

fastboot erase modemst1

fastboot erase modemst2

fastboot flash fsg fsg.mbn

fastboot flash recovery recovery.img

Then, immediately mofo flash the 5.1 image that you want to install. Do not go into recovery to erase the cache, mofo has already done that if you look at the last line on your phone screen. Just push volume up on your phone when mofo is done (not the power button.) You should be good to go!
[X 2014 Android Development] pyro6128:
Well I have the files in the same folder adb is in, and then mofo is saved in a subfile there, maybe thats the issue. My file structure looks like this

/motox2014/(adb files, mofo folder, and 5.1 base files are here)/mofo/(mofo files and 5.1 mofo image are here). I'll try moving the 5.1 base files into the mofo folder along with the 5.1 mofo image and see if that fixes the issue. Thanks for the reply.

Edit: So I was in the middle of trying again after redownloading the files when you replied. Everything seems to have worked now. I think I must have gotten some corrupted files, but I just made some test calls, tried tethering, and verified android version is 5.1. Thanks for the assistance and all the work you've done!
[X 2014 Android Development] Jilaman:
Where is the Messages app (green icon)?

Where is the Messages app (green icon)?
[X 2014 Android Development] RashaMatt:
Thanks Mike! If flashing this over v2, I assume it's a dirty flash (i.e, data will not be wiped)?
[X 2014 Android Development] gunit25:
Same question here. Flashed xt1096-5.1-mofo-base (7/9/15). Can I just dirty flash over? Assuming I should clear cache first, but any other precautions?
[X 2014 Android Development] mikeoswego:
Deleted
[X 2014 Android Development] mikeoswego:
It's replaced by Messenger which is identical but a few more features. If people are going to miss the old one, I can put it back in.
[X 2014 Android Development] mikeoswego:
Yes, dirty flash. Probably best to clear out dalvik cache. Data won't be lost

(I'd definitely say so if that was going to happen!)
[X 2014 Android Development] gunit25:
Sorry to bother but not sure what "version" I downloaded... It was

Flashed xt1096-5.1-mofo-base (7/9/15).

Can this be dirty flashed to the newest version? Do I need delta files or can I just flash the new image.
[X 2014 Android Development] mikeoswego:
Download the latest image from the post before or from post 2 and flash that. No patches needed unless you don't want xposed and/or all of the apps.
[X 2014 Android Development] joshnat:
Just FYI, I wasn't able to find the iOS emoji font in /system/etc/, but I did find it in /system/fonts.
[X 2014 Android Development] mikeoswego:
Thanks for pointing that out. I've corrected the posted info!
[X 2014 Android Development] tacosrdelicioso:
I can't get any speed from android file host on LTE. Seems Verizon throttles it. So I'm having trouble downloading
[X 2014 Android Development] mikeoswego:
Wonder if it's a regional thing. The files were put there with LTE in like 6 minutes..
[X 2014 Android Development] tacosrdelicioso:
Idk. It's also likely that Verizon was throttling me because it was peak usage time. I have unlimited data so they definitely don't mind making my life hard. Anyways it did finally download.

Install went as planned haven't had any issues dirty flashing from the initial 5.1 build whatsoever
[X 2014 Android Development] JulesJam:
Verizon can't throttle you while you are on Band 13. I use LTE Discovery app to determine what band I am on.
[X 2014 Android Development] tacosrdelicioso:
I'm sure they do anyway haha
[X 2014 Android Development] JulesJam:
No they don't. They aren't going to jeaopardize their block C licenses. There is a lot of congestion on Band 13 due to VoLTE as well as just plain old data use.
[X 2014 Android Development] azlodaniel:
ADaway and BetterBattery

Is there anyway to get a Img that does not have AdAway and BetterBattery in it? Upgrading from V2img to V3.1 has decresed my battery life, and I am wondering if those might be the cause.

Thanks,
[X 2014 Android Development] mikeoswego:
Neither AdAway or BetterBatteryStats run in the background or do anything unless you have them open and should not affect battery life.

If you want to verify they aren't the problem, go into Settings->Apps->All, find those apps, click on them and select Disable; that will be the same as if they weren't installed.

It may also be some other app which you could find in Settings->Battery (or use BetterBatteryStats, its purpose is to help find these problems.) If you do find something like Connect or Hangouts, etc. that you aren't using but is using battery, disable it.
[X 2014 Android Development] tbacba:
App updates disappear

I updated to 5.1 using the instructions and all seemed to be fine, except: when I update any of the system installed apps (like Google Maps) via the Play store, they revert to their previous versions after a reboot. Any ideas? Thanks.
[X 2014 Android Development] mikeoswego:
This problem is fixed in the update I'm posting now. Thanks for pointing it out!
[X 2014 Android Development] tbacba:
Patch problem

I attempted to use xdelta3 to do the base image patch and received the error shown below. The 3.1a. image is the same one I flashed a couple days ago, so I would think that file is ok. Did I screw something up?

Thanks.

C:\Users\Desktop\Moto X 2nd Gen\mofo\windows>xdelta3 -d -s xt1096-5.1-v3.1

a.img 3.1a--3.1b.patch

xdelta3: using default output filename: xt1096-5.1-v3.1b.img

xdelta3: target window checksum mismatch: XD3_INVALID_INPUT

xdelta3: normally this indicates that the source file is incorrect

xdelta3: please verify the source file with sha1sum or equivalent
[X 2014 Android Development] mikeoswego:
You did it right, I screwed up the patch file.

I'll have it fixed soon.
[X 2014 Android Development] mikeoswego:
Here's the corrected v3.1a to v3.1b patch: 3.1a--3.1b.patch.7z The original message has been updated.
[X 2014 Android Development] tbacba:
Thanks. This was my first attempt doing a patch so I thought I wasn't sure. Thanks for all your help!
[X 2014 Android Development] tjohnstone3:
First off I'd like to say thanks for creating these images/patches. Good to have root and be on 5.1

Having said that, my battery life has been insanely bad since updating (full disclosure, I just received this replacement phone on Friday and updated yesterday, so I can't compare battery life prior to going to 5.1) but I unplugged this morning at around 9am and as I type this (11:25am) I'm sitting at 56% battery and spent over an hour in church/driving where I didn't touch my phone.

I don't see anything really crazy in the battery stats, but the phone has been awake 54% of the time since I unplugged. Is anyone else seeing this?
[X 2014 Android Development] AlienZombieEater:
With some of the other images I flashed I was noticing significant battery drainage but not since I went to 5.1 yesterday morning.
[X 2014 Android Development] drewski_1:
phone unplugged for about an hour. Battery says 99% with 91% Deep Sleep / 9% Awake.

have you looked at wakelocks with something like Better Battery Stats?
[X 2014 Android Development] tjohnstone3:
I didn't notice anything weird with wakelock detector but am charging to try again.

Another thing is my phone is reading about 112 degrees while charging. That can't be good either. It was also running really hot earlier when in my pocket.
[X 2014 Android Development] jrbmed08:
I was fine before the latest image but flashed v3.1b and am having the same experience. Very slow and hot charging, horrible battery life. I'm glad it's not just me! Might just go back to the previous version which was nice and stable for me. I'm also not seeing a lot in terms of wakelocks, just extreme heat and battery drain.
[X 2014 Android Development] tjohnstone3:
Did you use any of the patches or just the full image? With or without xposed?

I used the debloat patch with xposed.
[X 2014 Android Development] jrbmed08:
For 3.0 (the last build I was on, which was stable for me) I only used the Xposed patch. For 3.1b, Xposed was baked into the image, so I used the image with no patches.

Edit: I never did a factory reset after updating from rooted 5.0 to rooted 5.1. I keep hearing factory resets after OTA updates are advised, but wasn't sure if it was important after this kind of update. The first thing I'll do is roll back to v3.0 since that worked well, but I'm wondering if it might be helpful to factory reset too.
[X 2014 Android Development] drewski_1:
Full image with Xposed. No debloat.

Running Amplify & Greenify in Xposed.

Sent from my Moto X
[X 2014 Android Development] tacosrdelicioso:
Huh. I'll just deal with the system apps reverting then
[X 2014 Android Development] Legacystar:
dealing with the same battery drain and phone is always hot and won't charge all the way. i don't see anything unusual in battery stats but who cpu is running at full speed all the time. anyone have a version i can flash back to till this gets fixed?
[X 2014 Android Development] jrbmed08:
To expand on what I posted above, I also had the same experience with failing to charge fully. I flashed the image for 3.1b right before I went to bed, then fell asleep as it was optimizing apps while on the charger. I woke up about 8 hours later to a blazing hot phone, GSAM showing 118 degrees, and it was stuck at 66% charge. Later after lots of plugging and unplugging different chargers and cables, I got it to charge to 80% but never past that. And hot enough to fry an egg within minutes each time I put it on the charger.

I have 3.0 patched with xposed, so I rolled back to that and it's back to normal. For some reason Google Play Services disappeared from my system, so I sideloaded the latest 438 build from APK Mirror and it works great now. Oddly enough, I searched through this thread and couldn't find the post with the 3.0 image, but I found at least the base image that Mike posted on Android File Host: https://www.androidfilehost.com/?fid=24052804347773711

For what it's worth, I never tried 3.1a so I can't tell you if that has the same issues as 3.1b.
[X 2014 Android Development] AlienZombieEater:
I don't have any heat or battery issues. I didn't use any patches, just flashed the full image for v3.1b.
[X 2014 Android Development] tjohnstone3:
I'm wondering if it is the patches.

I was able to get past my extreme battery issues and the phone seems to sleep most of the time when not in use. I re-deleted the dalvik-cache/data folders and rebooted.

However, things still seem to run really hot (especially when charging, along with charging really slowly...I haven't had issues with getting a full charge other than it took over 3 hours to charge fully).

I went to sleep last night with the phone at around 92-93%. Woke up this morning and it was at 65% which was about 7 hours after I last touched it. Still not ideal. According to wakelock detector the phone was only awake 3% of the time but still drained about 4% an hour.

I'll probably reflash without the patch over lunch and see if that helps.
[X 2014 Android Development] tacosrdelicioso:
Hmm. I need that debloat patch!
[X 2014 Android Development] mikeoswego:
We have the base rom here created by Motorola for Verizon that I've added root and Xposed to. Then the patches simply delete things from that image. The noxp patches delete the Xposed libraries and restore the backups of the original libraries. The debloat patches just delete the folders containing the apps listed.

Recently, I've started putting in newer versions of the Google apps into the ROM. My additions to mange old versions of the apps when a newer version is in the image is a script that runs about the time the red Verizon logo goes away or right before the lock screen is displayed. That script does not stay in memory, it exits when done.

The ROM itself has not changed since the day Motorola released it. You guys with battery/heat problems have something else installed causing this. Of course your phone is going to get hot every time it does the optimizing apps process after deleting the dalvik-cache and it is going to charge more slowly while still hot after that process. Whenever you install a new ROM, there are processes that run indexing things, and other clean ups for a few hours afterward. You need to let things settle down for a several hours before assessing battery life, etc.

The worst of these images for battery life should be the full rom without debloat which is what I'm currently running. Last night, after being on the charger, my phone sat for 8+ hours untouched and went down to 90% battery leaving 4 days of standby time. I think the battery life is fantastic considering that the battery isn't very big.
[X 2014 Android Development] drewski_1:
Phantom Nav Keys (Recents / Home / Back)?

Anyone else seeing Nav Key actions on dialog boxes where the keys are not displayed?

For example on the pop-up for different applications where the bottom says "Just Once" & "Always" touching that area brings up Recents / Home instead of selecting the App. I need to double tap on the App to select.

In Connect App when trying to activate the service pressing "OK" (on the right) brings the Recents & "Cancel" (in the middle) goes to Home.

Anyone else seeing something like this?
[X 2014 Android Development] mikeoswego:
Are you saying the nav keys disappear at times? Mine don't unless I use one of the Immersive modes in Gravity Box.

I went into Connect and after answering the "Yes, I'm In" question, if I hit cancel on the next dialog, it took me back to the previous dialog which wasn't very helpful.. Pressing ok took me on to the My devices screen as expected.

I've also not seen what you're describing in the just once/always dialog box, do you mean when you press on an area in the dialog box that isn't one of the choices you get the recents screen or pressing one of the choices does this. I'm sure that a setting or combo of settings in Xposed app(s) could cause this behavior.
[X 2014 Android Development] mikeoswego:
And just to clarify, you are touching the area in the dialog box with the word ok or Always and your phone behaves as if you actually pressed the recents button?
[X 2014 Android Development] drewski_1:
yes, that's right.

my Nav buttons have disappeared in this case (see screenshot) and i do ahve Gravity Box, so maybe something I accidently selected there
[X 2014 Android Development] drewski_1:
i turned off Gravity Box (i didn't have Extended Desktop on) and it's still doing the same thing in the Connect app (OK brings up Recent Apps instead of processing OK)

will try re-flash 3.1.b this evening
[X 2014 Android Development] joshnat:
Mine feels a little warm since updating to 3.1b debloated today. I looked in Better Battery Stats and under CPU States it shows that the phone is either running at 2.46GHz or is in Deep Sleep all the time. Nothing in between. On 3.1a, it was running cool, and those stats showed a majority of time at much slower processor speeds, as one would expect unless you're running something resource intensive. Not sure what to make of it.
[X 2014 Android Development] jrbmed08:
Yeah I really don't think it's an app because it's not like that on the 3.0 image. Both before and after 3.1b. I'm happy to stay on 3.0, no big deal! Just shared my experience since we're essentially beta testers.