yashsingh1/xdaforums huggingface dataset:
[X 2014 Android Development] redwings73:
OH! Thank the Lord it's not just me...I've been pounding my head against the wall trying to fix this! I've tried Textra, XHangouts module, APN edits (for whatever reason all the edit options are grayed out on my VZW Moto X '14), Hangouts, Google Messenger, Root Explorer edits to the build prop (http://forums.androidcentral.com/ve...41691-mod-add-apn-editor-system-settings.html) ....build prop edits won't stick because we can't write to /system.

Is there a chance that it's fouled becasue we no longer have the stock messenger as it was replaced with Google Messenger?

EDIT:

Using your MaxHDR

Same APN settings for me, too.

Name: Verizon Internet

APN: VZWINTERNET

MMSC: http://mms.vtext.com/servlets/mms

MMS port: not set

MCC: 311

MNC: 480

APN type: default,dun,supl
[X 2014 Android Development] JulesJam:
MMS is working fine for me. I am running one of ClydeDroid's older images.

Name: Verizon Internet

APN: VZWINTERNET

MMSC: http://mms.vtext.com/servlets/mms

MMS port: Not set

MCC: 311

MNC: 480

APN type: default,dun,supl

Everything is greyed out and uneditable except APN.

---------- Post added at 07:39 PM ---------- Previous post was at 07:32 PM ----------

I have one of ClydeDroid's older images that was made from mike's which was made from btdownloads7's. It has root, modified build.prop for free WiFi tether, busy box, sqlite3, Xposed and AdAway. Works great, no HDR camera bug. Do you want me to post a link to it?
[X 2014 Android Development] redwings73:
That would be great if the MMS is working! Thank you, ma'am.
[X 2014 Android Development] JulesJam:
OK I will zip it, upload and then post a link when it is uploaded.

---------- Post added at 08:15 PM ---------- Previous post was at 07:59 PM ----------

Try flashing back to stock system, clearing cache, booting, then doing a factory reset. Then reflash your image using mofo.exe and see if that makes a difference.

I had to do that to fix issues with my phone after flashing an AT&T image. I guess there were changes made to the data partition that needed to be cleared, not sure.
[X 2014 Android Development] dudicle:
Thanks JulesJam - I appreciate your help. Does the image have any "debloating" or changes to the build.prop (aside from the free wifi teather)? I'm looking for a minimal amount of tinkering - and I use some of the "bloat" :)

Thanks,

Tom
[X 2014 Android Development] JulesJam:
All of the Verizon apps are in the image.

AFAIK it is simply btdownload7's image with modified build.prop for free WiFi tether, Busy Box and SQLite3. Then Mike added Xposed to it then Clyde added AdAway. It was Clyde's first image I think. I don't see where anything else was done. Stock boot animation too.

I simply freeze the Verizon apps I don't want with TiB/U Pro. No HDR camera bug and everything is working fine for me - calls, texts, MMS, MHS.

It is about 1/3 uploaded now.

---------- Post added at 09:31 PM ---------- Previous post was at 08:42 PM ----------

Link to one of [MENTION=2821926]ClydeDroid[/MENTION]'s earlier images that has been working problem free for me (no HDR camera bug, MMS working). It has root, free tether, BB, SQL, Xposed, AdAway. Please follow the instructions in the beginning of his thread about deleting /data/dalvik-cache/arm and /data/dalvik-cache/profiles folders and downloading the Xposed Installer and AdAway apks.

https://mega.co.nz/#!tpFi3ZYD!aCYxIUZo4bGrknGLWFAeatG22obWyH4vG0ZnC21n7Cc

MD5 of the unzipped file is 56FDFC8667B8F098901504C5EB3F8D35
[X 2014 Android Development] trimax84:
Thanks [MENTION=5983610]JulesJam[/MENTION]

Built off of this one to add my usual boot animation, bootanimation memory leak fix, deleted system apps/media files. HDR and mms seem intact.

Link for anyone who wants it.
[X 2014 Android Development] JulesJam:
Did you see this post?

http://xdaforums.com/showpost.php?p=60905451&postcount=73
[X 2014 Android Development] trimax84:
Ooh, good to know. Any idea what type of "issues" he was having?
[X 2014 Android Development] JulesJam:
No but if you post to him and ask he may respond. What editor were you using when you were having issues in your image?
[X 2014 Android Development] mikeoswego:
I'm sorry that I've been gone unexpectedly and unable to answer questions. Hopefully you got this fixed but what you need to do is erase your cache and delete all the things in /data/dalvik-cache to get the original dialer to work again after having had the Google dialer installed. I'm going to do some further tests; if you are still having trouble. please try deleting /data/dalvik-cache/arm/system@priv-app@Dialer@Dialer.apk@classes.dex only and erasing cache to see if that fixes the problem, if so let me know. Otherwise the first solution of wiping everything in /data/dalvik-cache and erasing cache will fix it.
[X 2014 Android Development] mikeoswego:
Is this on your debloated rom that you're having trouble? Did you delete MmsService, VZWAPNService, VZWAPNLib, or vzwapnpermission apps?
[X 2014 Android Development] mikeoswego:
Just for the record, I've used Gedit on these images with no problem. I also use editor, never did grow to like VIM over the years but would be very surprised if it caused problems since it is the "father" of all unix editors!

I think these random failures of HDR and other random problems on these images may be due to improper unmounting of the image from the filesystem before flashing or compressing it for distribuition but have no evidence for that.
[X 2014 Android Development] JulesJam:
In general, if people find themselves with problems with their phones after flashing a MoFo image, they can flash back to stock, wipe cache, boot and then do a factory reset. At that point they can start from scratch with another MoFo image.
[X 2014 Android Development] trimax84:
I do not remove any of those folders/apps. I only delete ones I know are safe to remove, any question and I don't touch it.

And [MENTION=5983610]JulesJam[/MENTION], I used the standard Gedit in the Ubuntu virtualbox (Oracle VM) when I edited the build.prop. After your comment, and then not opening build.prop, the HDR issue went away (same base ROM, same typical changes I do....everything but changing build.prop). So, could it be related to unmounting the phone improperly? Sure - that would make more sense to me actually. But seems like, for whatever reason, it was from editing build.prop :confused:
[X 2014 Android Development] mikeoswego:
Yes a factory reset would do it as well but there is no need to wipe everything just to fix the dialer issue.
[X 2014 Android Development] JulesJam:
I said in general, I wasn't addressing the dialer issue. The point I was making is that not all of us know how these images were made or what to do to fix problems we encounter and if someone can't find an answer to fix their issue, then my instructions will work for them if they need to get their phone issue fixed and don't know how else to do it.

The other point I was making is that I would not do a factory reset with a MoFo image on my system partition - I would flash back to stock first. It may be fine to do a factory reset with a MoFo image on your system partition, idk, but I do know my instructions are safe. It is quick to flash back to stock and so that is what I do to prevent any potential problems that could arise.
[X 2014 Android Development] trimax84:
After my MMS issue, I factory reset on a MoFo image. Was working fine until suddenly the Back and Home buttons on the navigation bar stopped working (yet the Recent Apps button was fine...probably some conflicting apps). So I factory reset again (still on my build of the MoFo image) and I've been running fine since.

This is just to say it is possible and has worked for me.......your instructions remain safest though.
[X 2014 Android Development] JulesJam:
Gtk. I flashed the ATT and PE ext4 system.imgs to my phone and the home button wouldn't work, wouldn't make phone calls either. Then after that when I flashed an XT1096 Mofo image, Moto Assist and Touchless Controls didn't work. But going back to stock and doing the factory reset cured the problems.
[X 2014 Android Development] trimax84:
[MENTION=4307096]redwings73[/MENTION] - I figured it out this morning...

After it happened to me again, I thought that it must be related to an app or combination of apps conflicting. At first I thought Xposed, but disabling/uninstalling didn't work. Then it hit me.....what other program can block outgoing or incoming data?! ADAWAY! I was using some aggressive ad blocking files (specifically, the ones from the links posted here). Reverted back to stock hosts file and it started working again!

Went to go post my findings in that ad block thread, and turns out someone else also had the same issue. Wish I saw his post earlier.

Either way, hope you figured it out too!
[X 2014 Android Development] JulesJam:
wow that is unbelievable that that ad blocker is blocking mms.vtext.com. Why on earth would it block the Verizon picture messaging server?
[X 2014 Android Development] redwings73:
Glad sometime figured it out.

I had a feeing it might be Xposed or AdAway, but couldn't figure it out.

I unchecked that host in AdB reapplied, reboot, etc... Still not able to use MMS. What exactly did you do?
[X 2014 Android Development] lovetohustle:
Will this also work on XT 1097 Variant?

Will installing busybox and alpha Xposed apk also work on the Moto X XT 1097 variant?
[X 2014 Android Development] JulesJam:
This image won't work on the XT1097. But someone who knows linux could make an ext4 image just like this for the XT1097 starting out with the pre-rooted XT1097 image I made.

btdownloads7 was the one who put BB and SQLite3 in this image, then mikeoswego put Xposed in this image then ClydeDroid put AdAway in this image.
[X 2014 Android Development] lovetohustle:
nevermind gots it.
[X 2014 Android Development] trimax84:
I unchecked the two links that I had added (so just the ones that come with AdAway by default were checked) which it seems you have done. Then I clicked "Disable Ad Blocking" to revert back to the stock hosts file. I actually did this for both the target /data/data/hosts as well as /system/etc/hosts (although I probably only needed to do /data/data/hosts). Then I rebooted. When I checked to make sure ad blocking was off by navigating to this forum since xda has a bunch of ads - they showed up so I knew I successfully reverted to the stock hosts file. Then I sent a test MMS which worked. Afterwards, I ran AdAway again to reapply the stock hosts file.
[X 2014 Android Development] redwings73:
Worked perfectly! I forgot there were TWO links that I added and only unchecked one.... Thanks for the instruction!
[X 2014 Android Development] trimax84:
That's great! Such a relief it's something simple. Too bad I wasted a lot of time troubleshooting (including factory reset, twice. And installing apps individually without restoring data from titanium in case that was the issue. Not to mention a ton of reboots)
[X 2014 Android Development] skytbest:
Has anyone been able to get stock signal icons working reliably? I was trying the SignalIconsAOSP xposed module but it was giving me a lot of issue. This was a couple weeks ago so I'm just wondering if anyone has found anything else that will work.

Thanks!
[X 2014 Android Development] narknon:
Fixed my MMS!!!!! Thanks!
[X 2014 Android Development] tacosrdelicioso:
No, nobody seemed to care
[X 2014 Android Development] fakieskr8333:
I haven't had any luck either. Every now and then i'll reenable the module just to try it bc i still get random crashes.
[X 2014 Android Development] tacosrdelicioso:
Yeah. I'd pay for it lol...$10..$15...for aosp signal icons with the LTE indicator
[X 2014 Android Development] JulesJam:
Ask ClydeDroid if he can do it - he is a recent college grad so I am sure he could use the money and he seems open to requests.
[X 2014 Android Development] fakieskr8333:
Is anyone having any google search app crashes? I have wiped the app's data and am still getting crashes, it wont even open. I am running the latest version and i cant uninstall updates bc the button is greyed out.
[X 2014 Android Development] redwings73:
See post #93 and #94 here: http://xdaforums.com/moto-x-2014/development/img-totalx-root-tether-busybox-sqlite-t3101853/page10

Hope that helps!
[X 2014 Android Development] fakieskr8333:
Oh thanks so much! I thought I had tweaked something in appsettings that caused an issue (i have a bad habit of tweaking things in the middle of the night when i can't sleep and then forgetting what I did), i would have never guessed that lolistat would have been the culprit!
[X 2014 Android Development] redwings73:
Glad it worked for you. Nothing has worked for me. I can't get anything above Google App 4.5 to not FC.... I've done all the wiping and blacklisting, etc.

Anyone have a clue what the issue could be?

I'm on TotalX 1.3.

UPDATE: I can only get 4.6.10.19 to work with the swipe right function of the Google Launcher....

SOLVED: I disabled all of my xposed modules and then, one by one, narrowed it down to the "force immersive mode" module....
[X 2014 Android Development] trimax84:
Note sure if this is exactly what you're looking for, but check this out..... http://xdaforums.com/moto-g/themes-apps/app-moto-checkbox-1-0-t2859003
[X 2014 Android Development] tacosrdelicioso:
Checked it out. It doesn't work :(

Edit: I installed an older kk version of it and so far it hasn't given me issues
[X 2014 Android Development] tacosrdelicioso:
Spoke too soon. Sysui fcs everywhere
[X 2014 Android Development] stay-down:
just flashed, dialer crashes and messaging crashes once clicked on. So far no IMG is working quite right for me. been a long crappy night so far.

Guess im flashing back to stock and trying again tomorrow
[X 2014 Android Development] mikeoswego:
You could try going into Settings -> Apps -> All and then click into each dialer and messaging app listed and clear cache then clear data for each one, reboot and try the dialer and messaging again.
[X 2014 Android Development] contesauce:
[MENTION=4135340]stay-down[/MENTION] like Mike said you can try clearing cache for each app but what worked for me was erase your cache and delete all the things in /data/dalvik-cache then reboot to get the original dialer to work again after having had the Google dialer installed. if you are still having trouble. try deleting /data/dalvik-cache/arm/system@priv-app@Dialer@Dialer.apk@classes.dex only and erasing cache to see if that fixes the problem

The first one should work for you, when you boot up again its going to optimiZe all your apps again so be patient.

(instructions given by [MENTION=5849464]mikeoswego[/MENTION] in an earlier post)
[X 2014 Android Development] stay-down:
Thanks guys!. i ended up flashing just a rooted image with tether enabled by [MENTION=2278321]btdownloads7[/MENTION], seems to work so far. I really only need tether but would love to have xpposed working to. Ill run this a bit and maybe flash the others to see if i can get then img to work correctly. Thanks for the help!!
[X 2014 Android Development] mikeoswego:
It didn't occur to me that you might have installed an image with the Google dialer and then tried to flash one without. Like [MENTION=5122731]contesauce[/MENTION] said, you would then need to clear out the dalvik-cache stuff to clean things up. Sounds like you've got things working. You should be able to flash the xposed image from the first post by following the instructions there. I removed the image I'd posted in the past with the Google dialer because it turns out that among other problems, you can't dial 911 with it; so there is now just the one image to choose from in the first post.
[X 2014 Android Development] stay-down:
Yeah I think I tried TotalX first and it wouldn't run basically at all. I deleted the necessary folders for xposed, but I obviously did something screwy because I had memory full notifications and nothing would open. It was weird but I just went back to stock and tried another, then dialer and messaging wouldn't work, I'm barely getting started messing with the 2014 moto X so I'm still noob at this IMG flashing, I have always had devices with unlocked bootloader so it was a bit easier to flash roms and what not. I recently got the X and the Turbo and have successfully flashed rooted images to both so I do really appreciate all the work and help with everything, and all my questions.
[X 2014 Android Development] contesauce:
No worries that's why the community is here.
[X 2014 Android Development] jlwtformer:
If and when Verizon releases the 5.1 update, if I'm on this image will the update brick my phone? I'm assuming I'm going to have to disable all Xposed modules to make the update go smoothly.
[X 2014 Android Development] contesauce:
[MENTION=5519696]jlwtformer[/MENTION] you won't be able to update unless you flash back to stock then update.

The update will simply fail if you are on a modified image. I'd wait until a modified 5.1 image is available.
[X 2014 Android Development] jlwtformer:
Well where do I get the stock 5.0 image then? Is it on Moto's website?
[X 2014 Android Development] contesauce:
It may be on their site I'm not 100%. If no one posts a link to it (I'm sure it's on XDA someplace) I'll upload it to Google drive tomorrow and put a link with instructions on how to flash here.

---------- Post added at 11:28 PM ---------- Previous post was at 11:08 PM ----------

[MENTION=2747697]astaccz[/MENTION] made a one click tool specifically for this task. Comes with the image and works specifically for mofo images. Be sure to give him a thanks.

http://xdaforums.com/moto-x-2014/general/tool-xt10965-0lxe22-46-11-auto-flasher-t3139190
[X 2014 Android Development] mikeoswego:
New image with Xposed v65 (and some 5.1 update info)

I've uploaded a new image with the latest Xposed v65. It's available here: XT1096_5.0-tether-root-bb-sqlite3-XposedV65.img.7z

You'll also need the latest Xposed installer available from here: http://xdaforums.com/attachment.php?attachmentid=3383776&d=1435601440

Install the new Installer first.

Then, use your root file explorer to delete both directories within /data/dalvik-cache and everything in /cache.

Enter bootloader mode and flash the new image with Xposed v65.

(If you're not running an image with Xposed already, follow the instructions in the first post!)

Also, I've looked at the 5.1 soak test files. The update patches many of the files in /system but also patches boot.img (the kernel) and other files that are outside of /system. The update is almost all patch files, no complete images. I'm relatively certain that I could use the file to patch one of our rooted images but to use it would require that all the other files on the phone are updated. To do that would require restoring to stock, running the update and then flashing the modified system image. It's my understanding that mofo isn't going to work on the 5.1 system so until that changes, it won't be worth the time investment to make a 5.1 image.
[X 2014 Android Development] Haxxa:
If we upgrade to 5.1 can we revert back to 5.0? Also does the 5.1 update patch the MOFO exploit in the Bootloader if not why would it prevent flashing of modified images on 5.1? On a totally different note I will be moving to your Rom as a previous Rom I was using was dropping emergency calls, so thanks for your support :)
[X 2014 Android Development] mikeoswego:
I don't know if it will be possible to revert from 5.1 to 5.0 or if the 5.1 update (which includes a new GPT.BIN/bootloader file) will prevent mofo from working. It might be possible to keep the old bootloader while updating the rest of the files. 5.1 is supposed to be somewhat faster but Xposed is less developed for it at the current time. I'm not feeling left behind running 5.0 especially with GravityBox and am not brave enough right now to risk bricking my phone with so many unknowns involved..
[X 2014 Android Development] Haxxa:
Yes, at the moment with all the unknowns involved probably best to wait and see :)
[X 2014 Android Development] redwings73:
I use Muzei and it requires Live Wallpaper Picker... Could I reinstall that somehow if I use this image (thanks for this, btw).
[X 2014 Android Development] mikeoswego:
I don't know of a way to manually install the live picker, sorry. I'll put it back in the next time I work with the image.
[X 2014 Android Development] mikeoswego:
Just so we are on the same page.. Live Wallpaper Picker is still in the rom. The stock live wallpapers are removed.
[X 2014 Android Development] redwings73:
Thanks. I just figured that out... I forgot there were system apk's called LiveWallpapers and LiveWallpapersPicker".

Sorry about that confusion on my part.
[X 2014 Android Development] redwings73:
This is great!

Is there any way to get AdAway to work? I get the "symlink creation failed" error.
[X 2014 Android Development] RyanBRZ:
Can I just flash the image in the first post, or do I first need to install xposed first? The post is a little confusing.

A step by step from a bone stock moto x would be great.
[X 2014 Android Development] mikeoswego:
From bone stock, you need to first flash either image created by btdownloads7 posted in this thread: http://xdaforums.com/moto-x-2014/development/img-xt1096-victara-lollipop-images-mofo-t3100601. Follow the tutorial posted here to do that: http://xdaforums.com/general/paid-software/mofo-root-turbo-t3064404

Then you will have root and be able to follow the instructions in the first post of this thread. You should go ahead and install the Xposed installer apk first before flashing the image that contains the Xposed framework. When you reboot after flashing, Xposed will be ready to go and you can start adding modules like Gravity Box for LP.
[X 2014 Android Development] mikeoswego:
I'll consider making an image with the AdAway symlink but I thought that it caused random DNS problems for people who were using the TotalX image that [MENTION=2821926]ClydeDroid[/MENTION] made..
[X 2014 Android Development] contesauce:
Unless there were other issues the adaway worked great, the problem that he had a while back was adding a more strict host list to the ones in default, it was blocking Verizon's mms port. He removed that host and everything was golden for me until the 911 bug.
[X 2014 Android Development] JulesJam:
What is this?
[X 2014 Android Development] mikeoswego:
Calls to 911 fail with the TotalX image, according to posters in that thread. I tested my image the other day and 911 does work (much to my embarrassment..)
[G2 Q&A, Help & Troubleshooting] Edwardian 00:
Hey guys ..

I have lg g2 n i recently bought a new charger for it(1.8 amp) but the charging is slow takes about 2.30 or 3 hours to charge ..i used an app called Ampere n the charger gave a max current of 1.4 Amps ..i wanna know is it normal or should i get a new charger?

Thanks :)
[G2 Q&A, Help & Troubleshooting] siggey:
Original cable?

_____________________________________Read more write less and be smart
[G2 Q&A, Help & Troubleshooting] Edwardian 00:
I dont know ..how to find out?
[G2 Q&A, Help & Troubleshooting] siggey:
Is the cable coming from your original charger?

But

Your charger is 1.8A nominal

That means usable at 80% so 1.44A

And 3000mAh/1440mA=2,083h

Not so different from the values you show

_____________________________________Read more write less and be smart
[Verizon HTC One (M9)] bytethegroove:
BuuF HD ported to HTC m9....

From the same guy who's brought u buuf universal vrtheme, miui theme,and many many phones before, I bring u BuuF HD for our awesome HTC one m9.

Once we unlock look forward to a full BuuF experience....screenshots will be posted soon.

Get the HTC theme here: https://themes.htc.com/actions/theme/share/com.htc.theme.t9f3acbdf-0352-4592-b853-ad51743abf1d

peace

bytethegroove
[Verizon HTC One (M9)] Archangel:
Looks great! Finally someone who did a theme where the lockscreen weather doesnt look like a 7 year old drew it with a crayon LOL. Now if we can get that in my favy color blue LOL.