yashsingh1/xdaforums huggingface dataset:
[X 2014 Android Development] mikeoswego:
At least this log doesn't have the corruption in it!

For the No SIM, turn the phone off, take out the SIM, make sure it is clean, reinstall and power back up. This is another thing that actually disconnecting power by unplugging the battery *might* help.

Back to the spontaneous reboot..

You might try disabling Xposed or all modules and see if that makes any difference.

I've realized that the "Report pwrkey press event" entries are probably you turning the screen on/off rather than some mechanical problem.

It looks like during this log the phone was connected to a computer via USB but I presume the reboots happen when the nothing is connected to the phones USB port.

I'm not sure why at 1128.731180 it mounted mmcblk0p38 (system) twice when it was already mounted at 5.612335.

Then right after that is the emergency remount of mmcblk0p37 (cache), that seems to be a common log entry for spontaneous reboots no matter what the cause. It can also mean a problem with the memory or file system. Wiping cache in TWRP won't hurt though I think you already did that.

So, it's still not conclusive as to whether the problem is config/setup, file system corruption, or hardware issue. You should try to capture the system log like was mentioned before to see if that log shows any app or xposed module acting up right before the reboot. You could just wipe Data in TWRP and set the phone up again and see if that fixes anything (might fix both the SIM problem and the reboot problem.) If it's only taking 20 minutes to fail, you don't have to set it all the way up and could restore a backup if nothing changes for that test.

BTW, if do decide to format Data, use the repair function in TWRP -> Advanced Wipe and make sure you format in f2fs. TWRP defaults to ext4 which won't hurt anything but f2fs is the factory default (for data only) and is much faster. I actually did that in 2 steps not knowing any better; did the format and then went back later and changed the file system to f2fs.
[X 2014 Android Development] redwings73:
Yes! No funny characters!

I did just grab the phonelog.txt (7zipped due to size), but I'm not certain it will be much help this long after reboot....but attached anyway!

EDIT: Disregard....I just read that the kmsg reset after reboot....I'll try the Catlog app like you said and try to force a reboot....they seem to happen when I have a lot going on withe the phone.

If the CatLog app does not capture what I need to tell the story, when do I need to try to capture another kmsg through ADB?

To be clear, if I TWRP Advance Wipe to format f2fs, I'll remain on your recent 5.1 image correct?
[X 2014 Android Development] redwings73:
Well, I couldn't even get the CatLog app on the phone before it rebooted, but I grabbed the kmsg AS the phone was rebooting....attached.
[X 2014 Android Development] RyanBRZ:
I just flashed the latest CM13 nightly and I absolutely love it. I'm using the Dark Material theme which is perfect IMO. Everything works perfectly so far. If you haven't tried it yet I highly recommend it.

https://download.cyanogenmod.org/?device=victara

[MENTION=5849464]mikeoswego[/MENTION] - Do you have a Marshmallow/CM13 rom brewing yet?
[X 2014 Android Development] rumi409:
I'm guessing you are on Verizon. How has the service been with CM13? Battery life?
[X 2014 Android Development] RyanBRZ:
Yes, no issues with service at all. Battery life seems a little better. Overall very happy with it.

Unrelated question, but are you aware of any glass screen protectors that fit without the sides not sticking? I heard a hair drier can help with this
[X 2014 Android Development] mikeoswego:
I've run CM13 off and on since it first started working with Verizon. I've been running it continuously for more than 2 weeks now. I don't have any plans to make a custom version of CM13 but I do participate in the CM13 thread here on xda (http://xdaforums.com/moto-x-2014/orig-development/rom-official-cm-13-0-nightly-releases-t3256580) and am registered to submit proposed changes to the code. I'll probably have minor stuff like zips to flash different boot animations or similar things in the future. I do build my own unoffical nightlies of the ROM and was going to post one last night but saw that the CM build box was working again. (My builds have no changes, they are identical to the CM official nightlies.)

I am on Verizon and the service works fine calls, data, etc. Battery life seems about the same but as mentioned in past conversations, battery life isn't a big concern for me and I don't pay close attention to it. The phone seems much faster as far as screen response with CM13 over the stock rom.

CM13 is not perfect yet, for instance I use an alarm clock called Alarm Clock Xtreme and it won't wake the phone to sound the alarm, the alarm doesn't go off until you wave your hand over the phone, pic it up or otherwise wake it. (although Google Deskclock and probably the CM deskclock do work properly.) Until this morning I thought this was a problem with the app. This morning a text came in and the notification sound didn't go off using Google Messenger as the MMS app and the Repeating Notifications app didn't sound either until I woke the phone. I will have to try the stock MMS app and see if it works correctly. Every so often, like maybe once a week, the phone will reboot itself when it is just laying there doing nothing. The stock rom never does that for me. I'll start looking at this notification while dozing thing to see if I can figure something out.

I'm not abandoning the stock rom, maybe Verizon will surprise us and allow a 6.0 update to go out but I'm not holding my breath..
[X 2014 Android Development] rumi409:
Sounds like CM is coming along nicely. I've bought a Droid Turbo and have been using it for the last week, however, I have the Moto X unlocked and might go back if CM or Marshmallow becomes stable.

Is it possible to enable "Advanced Calling" in CM or Stock? When the Moto X was released, I know it was suppose to be compatible.

I haven't tried a glass protector on my phone yet.
[X 2014 Android Development] mikeoswego:
The Turbo or Turbo 2? I'd like the Turbo 2 with the shatterproof screen when the price comes down a bit, though either one is nice phone.

If you mean VoLTE, then no, neither stock nor CM has that for the Moto X Victara. CM does have that for other phones, so it must be a problem with proper firmware for the phone rather than CM.
[X 2014 Android Development] rumi409:
I got the original turbo. It had the "advance calling" feature, 64GB, and a larger battery.

That sucks that Verizon abandoned the VoLTE on the Moto X. I'm guessing there is no way to reverse engineer a firmware from the droid turbo or maxx.
[X 2014 Android Development] Legacystar:
does anyone know if it's going to be possible to port the XT1095 marshmallow to the XT1096? or is there a way to convert the verizon version to pure?
[X 2014 Android Development] mikeoswego:
I'm not aware of any way to do this but would be happy to learn otherwise. It is the requirement for CDMA for voice that is the problem.
[X 2014 Android Development] Legacystar:
Isn't that just based on the modem firmware? We wouldn't need to change that would we?
[X 2014 Android Development] drewski_1:
sounds like people have tried it (direct flash. no other porting) for 5.1, but CDMA didn't work "out of the box" so maybe some other drivers or software hooks needed.

where's that Advanced HD Calling feature when you need it?!?
[X 2014 Android Development] dudicle:
I second this request! Mike, your images have been very stable for me - I really appreciate your work on this. However, I am currently on "TotalX" simply because it has AdBlocking. Unfortunately, it also seems to have some bugs. Are you comfortable with the symlink method used to access the hosts file?

Thanks again, I really appreciate you.
[X 2014 Android Development] azndan2:
I have the same request. Currently running your awesome image!! Thank you!
[X 2014 Android Development] Mayze23:
Viper4Android if possible? Stock equalizer only works for external speaker or wired headsets. I'd love to be able to make my Jaybird bluebuds sound better. ?
[X 2014 Android Development] astaccz:
Your image is stable. Thank you. Can you make an image. The one with the google messenger and google dialer and add a line in build.prop that disables the navbar/softkeys. I love using LMT. However right now I am using an app thatbhides softkeys and it uses memory. Willing to donatev
[X 2014 Android Development] Mayze23:
Install the Xposed module gravitybox for lollipop. It has all those options and a lot more.
[X 2014 Android Development] astaccz:
Using Xposed makes my device a bit laggy. Well I used flat style color bars and it made my device laggy. I'm skeptical to try gravity box. Does gravity box make your device laggy? If not I'll give it a try.
[X 2014 Android Development] Mayze23:
There is no adverse effects on my phone using GB. If it lags your phone all you need to do is uninstall it.
[X 2014 Android Development] trimax84:
[MENTION=5849464]mikeoswego[/MENTION]

Getting AdAway to work should be as easy as:

-Move /system/etc/hosts to /data/data

-symlink /data/data/hosts to /system/etc/hosts (ln -s /data/data/hosts /system/etc/hosts)

-Make sure the permissions are properly set the files (0644 for /data/data/hosts), I think the symlink would just be 0777 and you wouldn't have to change permissions

I haven't tried this, so not sure if you'd have to "sudo chcon" the linked file to u: object_r:system_file:s0

Then those of us flashing your image file via MoFo would have to download the AdAway apk and install like a normal program from this link.

After installing, open the app, go to Preferences, scroll down and click "Target Hosts File" and select the "/data/data/hosts" option

I had not heard of this strong additional host file to add to AdAway until [MENTION=2821926]ClydeDroid[/MENTION] mentioned it, but you can include "http://adblock.mahakala.is/" to the host source.

And you can also add "http://moaab.tk/hosts.txt" as a host source (both of these are discussed in this thread)

Edit: Easiest way I found to add the hosts file was to copy from a different ROM image (already symlinked to /data/data) and turns out you have to use sudo chcon -h to change the symlink context. Shouldn't have to chmod.
[X 2014 Android Development] trimax84:
I modified [MENTION=5849464]mikeoswego[/MENTION] ROM (the one with Google Dialer and Messenger) with the following edits:

-Added AdAway host symlinks. Seems to be working for me, interested to know if others have success

-Removed approx 250mb of /system space via various apps and help files/media

-Added a few build.prop tweaks. Pretty minor stuff to try to help with performance and battery

-Changed bootanimation since that other one is too crazy for me

Unfortunately my camera still crashes with HDR enabled....anyone have tips for how to fix this?

In case anyone wants to try it out: Link
[X 2014 Android Development] JulesJam:
Idk but isn't it strange how this bug keeps appearing and then disappearing?

[MENTION=2278321]btdownloads7[/MENTION] was the one who was able to get the HDR bug out of the image so maybe he can chime in and let you know how to fix it.
[X 2014 Android Development] neh4pres:
Don't you technically need a tripod to use hdr properly? Wouldn't seem like a widely used feature.
[X 2014 Android Development] trimax84:
No, the phone just shoots two photos at different exposures and merges them. Takes a few seconds. I think it usually enhances the photo.
[X 2014 Android Development] dudicle:
Thanks, [MENTION=2921457]trimax84[/MENTION]. You willing to try another version based off of Mike's image that only includes the hosts symlinks? I'm not too knowledgeable about this stuff, but I wonder if removing apps and tweaking the build.prop could be causing the HDR bug. Maybe we can narrow it down if you make the changes one at a time. Thanks again for your efforts!

Tom
[X 2014 Android Development] trimax84:
No, the root of the issue is deeper. It was traced back to the original fxz file and present before I removed any apps or changed the build.prop.
[X 2014 Android Development] neh4pres:
I have been having a issue with getting phone calls. I get a odd issue where for a brief second I get the answer/ignore circle, then it goes away and just goes to lock screen.. So then when I unlock the phone and it takes me to the phone app and pops a notification up telling me I won't have data during a call. I'm not sure if it's a exposed module doing it, or a part of the new dialer app.. Has anyone else seen this? It's getting very annoying.
[X 2014 Android Development] tacosrdelicioso:
Awesome. Next time you make one can you do aosp status bars with the LTE indicator?
[X 2014 Android Development] JulesJam:
No, I went back and tested them all. It was not in the original stock fxz - it was in the unrooted 5.0 w/modified build.prop ext4 file. Also, I am running the original stock fxz right now and it doesn't have the HDR camera bug in it. So I have tested it multiple times.

But btdownloads7 started from scratch and his pre-rooted image with BB and SQL in it were the starting point for mikeoswego's and ClydeDroid's images and btdownloads7's images do not have the HDR camera bug in them.

http://xdaforums.com/showpost.php?p=60514114&postcount=420

http://xdaforums.com/showpost.php?p=60516126&postcount=434

I wonder if the problem has to do with the editors people are using to modify the build.prop?
[X 2014 Android Development] trimax84:
That may very well have been it!

I took Mikeoswego's base image from the first post in this thread (with dialer/sms) and make some edits without touching the build.prop, and it seems to have worked. My changes took, and HDR seems to be working fine now after multiple tries. Thanks [MENTION=5983610]JulesJam[/MENTION]. What text editor is recommended? I thought I was using the special one that XDA forums talk about, but I guess not.

I'm uploading the file now in case anyone else wants to use it and will post the link when done.

Edits I made (see my post a few back for links and details regarding the following):

-Symlink hosts file to allow AdAway to work

-Different boot animation

-Bootanimation memory leak fix (details) - not sure how important this is, but [MENTION=2821926]ClydeDroid[/MENTION] used it in his ROM and I figured it couldn't hurt)

-removed multiple apps/media files/bloatware to save about 300mb

Now if only I could find a way to prevent the keyboard from popping up nearly every time I open Chrome/Chrome Beta! Anyone?!?

Edit: Link
[X 2014 Android Development] JulesJam:
The only thing I ever used was NotePad++ but idk if that is the one or not. But whatever one Slack3r used may have caused the problem initially and then whatever btdownloads7 used didn't cause the problem. If they used the same one, then that theory goes out the window.

---------- Post added at 05:21 AM ---------- Previous post was at 04:59 AM ----------

I saw that on one of the images but I have flashed so many I can't remember which. It doesn't really bother me and hopefully when 5.1 is released we will have VoLTE so it wil be a non-issue.
[X 2014 Android Development] neh4pres:
VoLTE won't fix it omho. It's the fact it's hard to answer the phone, between the answer circle disappearing on the lock screen, then needing to unlock, then getting a pop-up I have to clear out of, before finally seeing why my phone is ringing and who it is. It's very annoying, if anyone knows why it's happening, or if you also have this issue please let is know.
[X 2014 Android Development] mikeoswego:
It is but like drewski said, the rom software has to interact with that firmware for everything to work right.
[X 2014 Android Development] JulesJam:
Keep your eye on swappa - there was a promo through last weekend with the DT2 if you opened a new line and a bunch of people got DT2's just for the promotional credits and will be selling their devices on swappa I am sure in January. So I suspect you will see the price of the DT2 on swappa drop when that happens. The only issue is that the promo was for the device payment plan so make sure you buy from a reputable seller if you get one.

I got one and it is a nice phone, I really like it but you can't root it so I don't use it as my daily driver. Too much Verizon bloat and no free WiFi tether.
[X 2014 Android Development] mikeoswego:
Good info, thanks!
[X 2014 Android Development] JulesJam:
Woot!!!! Happy Day!!!! Motorola unlocking the XT1096 bootloaders!!! Now I can get my refurb replacement for my shattered screen XT1096!!!

http://www.androidcentral.com/motorola-enables-bootloader-unlocks-verizon-moto-x-2014

:victory::victory::victory::victory::victory:

Now if we could only get VoLTE enabled.
[X 2014 Android Development] mikeoswego:
I saw that and was totally caught off guard. I guess if Verizon won't allow an official upgrade to Marshmallow they should allow the unlock. Have to give them credit for that.

CM has some bright devs maintaining the Victara models, at least one uses an XT1096 on Verizon so maybe VoLTE will arrive sometime.
[X 2014 Android Development] JulesJam:
That would be great but I think it would mean modding the modems, not just the ROM and kernel.
[X 2014 Android Development] mikeoswego:
You're probably right. The Qualcomm site says the Snapdragon 801 in our phone is VoLTE ready and other phones using the same chipset are listed on Verizon's site like the Galaxy S5, LG G3 (that page only lists what they are currently selling.) The Moto phones listed use newer chipsets.

That would lead me to think that Moto never wrote the code for the modems to work with VoLTE (or it wouldn't work properly on their implementation of the chipset.)

Modding the modems is a lot more advanced than making a custom ROM that just interfaces with the modems so that does reduce the odds of our seeing VoLTE with the XT1096.
[X 2014 Android Development] JulesJam:
I think I read somewhere that Motorola did write the code but the issue was the money to do the testing on Verizon's network - Lenovo didn't want to pay for it. Who knows. It's a shame b/c I like the form factor of the MX14 more than the MX15PE.

Yeah, I don't think it will happen. I suspect that you would need to know proprietary information about how Verizon decides to route calls over LTE vs. CDMA so I don't think it is something someone could do without some inside information.
[X 2014 Android Development] neh4pres:
Mike. Is there any way you could mod a stock MM Rom from another carrier to flash on xt1096 now that we have fully unlocked phones?
[X 2014 Android Development] mikeoswego:
Like JulesJam and I were discussing about VoLTE, the modem firmware files have to interact with the ROM for everything to work. The kernel (boot.img) also comes into play. Not only do I not have the skills for that sort of thing, it would probably take inside info from Motorola and Verizon to pull it all together (without countless hours of just trying things.) This is all because Verizon still uses CDMA for voice (except for VoLTE devices in a VoLTE service area) and the rom has to be designed to work with that.
[X 2014 Android Development] neh4pres:
Damn. That sucks. I swear there was a dev for the galaxy s3 that transferred a Rom from another carrier to work with Verizon. It was so long ago,I wish I could remember who it was. But I think the source was from att who got a specific update before Verizon did. It may have been adrenalin who did it, but not sure.. I'll look through my past subscribed threads this weekend to see if I can find it. It is possible the op changed at some point afterward, but maybe if I'm lucky I'll find a comment about it, or a quote.
[X 2014 Android Development] mikeoswego:
AGISCI, the OP of this thread has a great deal of knowledge about the Moto X models, he says this can't be done: http://xdaforums.com/moto-x-2014/development/rom-xt1095-flashable-stock-rom-t3277874

He specifically talks about this here: http://xdaforums.com/showpost.php?p=64787634&postcount=74

Wish I had something better to say about all of this!
[X 2014 Android Development] neh4pres:
Thanks.. Is there any aosp Rom that includes the specifics we all enjoy from our specialized hardware? for example, using our specialized language processor, or infra red detectors for waking the phone?
[X 2014 Android Development] Haxxa:
I live in Australia and CDMA has no purpose here, would a normal stock (marshmallow xt1095) Rom work without CDMA - would it even boot?
[X 2014 Android Development] OrenGazala:
Yes, I've flashed stock 6.0 xt1095 and this is awesome. System recognizes my phone as xt1095 right now lol
[X 2014 Android Development] mikeoswego:
There is not AOSP ROM that makes use of the language or low power processors in the Moto X. There are a lot of things that come close. For instance in CM13 you do have the wave to wake, twist for camera, chop for torch, wave to silence, etc. It also has a feature where the screen never times out as long as your looking at it.

I was never a big fan of the Moto voice thing. Even though I speak clearly, Moto Voice kept trying to call my elderly neighbor and I always kept it turned off. Most things that I want voice to do are redirected to Google Now anyway, so disabling Voice and going directly to Google Now saves a a second or so for each request.

Make a backup, give it a try. You can always restore your backup if you don't like it. I've been running CM13 for a couple months now but a couple issues have cropped up in the latest nightlies that are annoying me and I'm returning to the stock ROM after making this post.
[X 2014 Android Development] donslade:
I am not knowledgeable enough to answer this question:

The Victara designation is applied to all the Moto x 2014 variants (XT1095/96/97). Each variant has a unique OEM ROM which accounts for its market and modem set among other things like carrier customizations. I expect some of this customization is in the kernel. The OEM ROM for the XT1095 will install and work on an unlocked XT1096 but the CDMA communications will not work.

How is it that CM13 and derivatives work on ALL variants while keeping each variants communication capabilties? Those ROMs do not contain new modem files. Do those ROMs retain the OEM kernel so the communications remain functional? That is what I think happens but I'm not knowledgeable enough to be sure. Can someone elaborate?

Thanks in advance.
[X 2014 Android Development] dunderball:
I would love to know this too. It seems odd that we have a working XT1095 Moto X Pure Rom that can be flashed on the XT1096, but CDMA isn't working. As far as I've heard, popping a Verizon Sim card into the XT1095 works fine.
[X 2014 Android Development] AGISCI:
It's a combination of the rom and kernel. The cm13 kernel and rom have support for cdma in it, because the cm13 kernel and rom are NOT stock. The stock kernel and rom for the xt1095 for example does not have cdma, and it would serve no purpose because the xt1095 does not physically have cdma parts in it. So naturally when the made the stock firmware they excluded the cdma parts.
[X 2014 Android Development] donslade:
You've heard that putting a Verizon sim in a XT105 activates the CDMA modem? I had not heard that. How can we verify this?

I would expect that putting a Verizon sim in a XT1095 would allow usage of Verizon LTE 4G data no CDMA for voice or 3G data. For voice it would use GSM.

---------- Post added at 07:11 PM ---------- Previous post was at 07:04 PM ----------

That is what I thought as far as the kernel and ROM working together.

I tried to check the FCC certification records and it looked to me like all the variants are the same hardware wise but are differentiated by the modem firmware. Maybe I'm wrong, maybe I did not search correctly, but that is what it looked like to me when comparing the XT105 against the XT1096 information.

I wonder if anyone has tried putting a Verizon sim in a XT105 running CM13 to see if it works on Verizon in CDMA mode. Might be an interesting experiment. I can provide a VZW sim if needed!
[X 2014 Android Development] AGISCI:
Sorry, but that is incorrect. The hardware in the xt1096 is different. It has the physical cdma parts which the other models do not have.