yashsingh1/xdaforums huggingface dataset:
[X 2014 Android Development] tjohnstone3:
I'm not trying to sound ungrateful, I really appreciate the work [MENTION=5849464]mikeoswego[/MENTION]. I'm just trying to figure out what's happening with my phone. I don't have anything crazy installed that I can think of (have less apps installed than on my previous phone that was running one of your 5.0 images and didn't see any issues).

Quick question, how do I go back to 3.1 if I wanted to see if that works better for my phone?

I re-flashed the 3.1b de-bloated over my lunch today. Came back to work around 1pm with 19% battery. It's been 2.5 hours and I'm still not fully charged (81%).

So something still seems amiss. I understand it's only been a few hours/settling or whatever. But the phone is still incredibly hot to touch and charging very slowly. I don't know why a 'rogue app' would cause the battery to charge slowly?
[X 2014 Android Development] mikeoswego:
That's interesting. It looks like the nav buttons are still there just covered up by the overly large dialog box. I don't even get that dialog box when I activate Connect. After I sign in, I have the screen attached. My status bar is also green when running Connect. Did you install Connect from the playstore and using the debloat image? Or installed from the playstore and using the full image? If using the full one, look and see if you actually have 2 copies, if so delete the play store version.
[X 2014 Android Development] mikeoswego:
All the previous 5.1 images are here: https://www.androidfilehost.com/user/?w=settings-dev-files&flid=34964

Let us know if reverting does fix things up for you.
[X 2014 Android Development] mikeoswego:
I'm seeing a variety of speeds in CPU States as expected. If you're running any Xposed modules would you mind disabling them, rebooting and see if the problem continues?
[X 2014 Android Development] briosita:
I had a similar problem a few images back, but it seemed to go away when I disabled air-audio. I am running debloated 3.1(b) (I downloaded the full image and applied the debloat patch then installed with mofo). Battery is great, and no heat issues (though it gets a bit warm when quick-charging, but that is normal in my experience). my guess is it something to do with your setup/apps.
[X 2014 Android Development] Legacystar:
I went from the 65xposed rom to the 3.1b and phone nearly melted down, went back to 65xposed and everything is good. No new apps where installed expect what you put I to the 3.1b. On that rom I couldn't even charge the phone while off.
[X 2014 Android Development] mikeoswego:
I'm glad the older version works well for you. There are a lot of changes in the 4 versions between the one you say works well and 3.1b so I couldn't begin to try and track down the problem.

One thing I know, everyone running these images has the exact same phone and the only difference between my experience (and others who are not having problems) is whatever apps you have installed. You will have to figure out which of those apps is causing (or revealing) a problem and if you do and I can duplicate the problem, I can make an attempt to fix it. Otherwise you'll just have to stay on the version that works for you.
[X 2014 Android Development] tjohnstone3:
Tried something last night. Left phone off and unplugged over night. So phone was room temperature (72 Fahrenheit). When I woke up, I plugged it in and left it off for about 20 minutes while I showered/got ready. When I went to unplug it, again it was blazing hot. Turned it on and as soon as it powered up it was at 104 Fahrenheit.

Again, I'm not trying to sound ungrateful. I am so glad to have an option (I can revert to a previous version) with root/tether. But an app didn't cause my phone to rise to over 104 degrees while charging and off.

---------- Post added at 07:59 AM ---------- Previous post was at 07:55 AM ----------

I don't seem to have access to any of these files.

Access denied

looks like you don't have permission to access this folder. Make sure you are signed in to an account that has permission, or check with the developer to request access.

EDIT: Can I go back to the V65 img without having to reflash anything in fastboot?

EDIT 2: The links to the debloated and debloated with adaway images seems to be broken.
[X 2014 Android Development] mikeoswego:
Would anyone who is having heat issues please send me a copy of your /data/system/packages.xml file? You'd do that by using your root file manager to copy it to your downloads folder, from there you can attach it to a message or pm.

Try this link if you want older images: https://androidfilehost.com/?w=files&flid=34964
[X 2014 Android Development] tjohnstone3:
Sent in a PM
[X 2014 Android Development] mikeoswego:
Thanks for sending that. I'm uploading a new version now that may fix the problem.
[X 2014 Android Development] jrbmed08:
Is it still useful for you to have mine even though I'm back on 3.0 with Xposed 65? I'm happy to do that if you will find it helpful.
[X 2014 Android Development] tjohnstone3:
I snuck in and downloaded the 5.1c files you had uploaded at 11:44 (I see you've since updated them). My phone has definitely run cooler since I flashed the 5.1c image. I'm charging it now to see if it gets really hot again and/or charges more quickly.

Tho I'm assuming something still wasn't quite right since you didn't say it was ready and have uploaded a newer version.

Thanks again for taking the time to look into it, appreciate it.

EDIT: Yup, probably jumped the gun. Still smoking hot when charging. That's what I get for jumping the gun, but hey it was worth a shot!
[X 2014 Android Development] joshnat:
Sorry, I didn't get to do this before reverting back to 3.1a. Running cool again and looking forward to figuring out if there's a problem. Let me know if I can provide any other info.
[X 2014 Android Development] mikeoswego:
I realized just as those files finished uploading that there was another potential situation I hadn't accounted for. I'm compressing and getting ready to upload now.

There were 2 issues. First, my script to remove updated apps could go into an infinite loop in 3.1b. If that happened, then the system might not load the proper proceessor governer data info for the chipset in our phones. The loading part of that data should have been fixed in the version you downloaded. (And I'll point out that if you fast charge your phone, it's going to get hot and you can probably live with that.)

I think that with the version I'm uploading now corrects the infinite loop potential which you would have experienced in the 3.1b version due to differences in your packages.xml file that are not defects, just something that didn't occur in my copy. That infinite loop definately could have caused some heat and could keep the processor running full speed.
[X 2014 Android Development] tjohnstone3:
Awesome. :good: I'll check it out tonight when I get home and report back. I'd flash here at work (I'm a java dev, so can get away with running terminals and what not at work) but I forgot to save my mofo link so I could download at work too. Ugh.

Just FYI, not using a fast charger (haven't sprung for one yet...as an aside, they worth it?) just a regular old charger. Can definitely live with the hot if my phone is charging quickly! Less so when it's in my pocket. :)
[X 2014 Android Development] jrbmed08:
Not to threadjack, but I really like fast charging especially since the Moto X battery doesn't often make it through a full day for me. The claim of 60% charge in 15 minutes is true, and while it does get a bit hot while charging, the heat dissipates as soon as you take it off the charger. You can get relatively cheap ones (at least cheaper than the OEM Motorola one) from Amazon.
[X 2014 Android Development] drewski_1:
+1

fan of the turbo charging

Sent from my Moto X
[X 2014 Android Development] Legacystar:
Dude make the investment, you don't need the over priced Motorola model, I have 4 of these and they are awesome

Tenergy 18W Turbo USB Universal AC Wall Adaptive Fast Charger with ... http://www.amazon.com/dp/B00OVD3FEU/ref=cm_sw_r_udp_awd_049TvbK2V5AK5
[X 2014 Android Development] mikeoswego:
I've found that even generic but high output car adapters charge very rapidly with this phone. I suspect that there is no special circuitry for fast charging in the power supply, that the phone takes whatever it can from the adapter and just has higher limits on what it will take than past phones.
[X 2014 Android Development] mikeoswego:
At the risk of being repetitive.. I'm really interested as to what is going on here because your screen shot doesn't look anything like what I have. The attached screen shots show what the initial Connect screen looks like, then the login screen. I also attached a shot of a just once/always dialog box for comparison.
[X 2014 Android Development] tjohnstone3:
Thanks for the link, will try these out (they're Amazon Prime and everything).

---------- Post added at 03:24 PM ---------- Previous post was at 03:22 PM ----------

Awesome, thanks [MENTION=5849464]mikeoswego[/MENTION]!
[X 2014 Android Development] drewski_1:
Flashed 3.1c and Just once/Always is back to normal.

I got past the Connect thing in 3.1b by pressing slightly high above that OK button and eventually got it instead of Recents. Haven't gotten that screen again even after clearing Data for Connect.

Of course, now it's FC'ing when I try and activate the Connect Chrome Extension . . . [emoji20]

Sent from my Moto X
[X 2014 Android Development] tjohnstone3:
I wonder if what drewski was seeing is at all related to something I was running into on 3.1b. Whenever I tried to give an app root permissions, I couldn't get the dumb thing to grant. It would time out and deny the permission. I finally had to just set it to default mode of grant instead of prompt to get any root apps working consistently.
[X 2014 Android Development] mikeoswego:
This is fixed in v3.1d that I'm posting now.
[X 2014 Android Development] drewski_1:
You should try a Qualcomm Quickcharge 2.0 charger. I have both high output 5v chargers and QC 2.0 chargers and the difference is dramatic!

The QC 2.0 chargers output @ 12v to start and then 9v and finally 5v to top off the battery.
[X 2014 Android Development] mikeoswego:
I didn't realize they actually use stepped voltage in addition to high output. I'll have to get one to try!
[X 2014 Android Development] tacosrdelicioso:
currently flashing 3.1d-de now! at the risk of being off topic I also use a QC2.0 charger in my '15JKUR, it works very well!

progress:85%

progress:93%

progress:100% rebooting now.

verizon logo for DAYS

optimizing app 19 of 174(cleared dalvik as instructed)

(opens beer)

optimizing app 138 of 174

(chinese invasion to collect begins)

optimizing app 147 of 174 has taken quite a long time now

(i hate clearing dalvik cache!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!)

optimizing app 162 of 174(phew)

starting apps

SUCCESS

gmail and wallet fc on startup. (when I installed 3.1a i had to uninstall gmail because the app icon had ended its life. ive always used debloat images maybe that has something to do with it. but i had to use tibu to do this as it was a system)

rebooting now to see if it happens again

no issues! Thanks mike
[X 2014 Android Development] tjohnstone3:
Hmm, I just remembered I didn't clear dalvik-cache when I flashed to 3.1d over lunch today...haven't seemed to run into any weird issues...

Will probably do it when i get a spare minute...
[X 2014 Android Development] joshnat:
3.1d running nice and cool. Thanks Mike!
[X 2014 Android Development] betarepeating:
Just flashed to the latest debloated image and... Why is Google Earth on there? I've never ever in 5 years of android had Google Earth installed, and now all of the sudden it's in system apps and can't be removed, only disabled. I'm curious why it didn't make the cut for debloating.

Scrolling through, the installed apps, I see a few more things that are stuck in that seem to be out of place:

Motorola's Camera app

Emergency Alerts

Inbox

Messaging (the green one

Messenger (the blue one)

News & Weather

Setup Wizard

Did I screw up my debloat patch somehow? I started with xt1096-5.1-v3.1d.img and patched using xdelta3 and the 3.1d--3.1d-de.patch.
[X 2014 Android Development] mikeoswego:
Yeah, depending on what has changed, that Verizon logo can stay there for a scary long time! These fc's on updated apps will open but you'll notice they go away by themselves. The reason is that the clean up for apps that are newer in the ROM than on your system can take place after you've already logged into your phone. The fc is because the old version has "disappeared" and then the new version is found and takes over. You'll only see those if you log into your phone as soon as the lock screen comes up after an update.
[X 2014 Android Development] mikeoswego:
In order to get Connect to work, I had to put back in all of the 3c apps which are odexed. There is no way for me to get your phone to see that those apps are now in the system which would force Xposed to de-odex them so that they will be compatible. If you never use Connect or any part of that suite, you won't see any problems. If you do, all of those apps will fc over and over until you force Xposed to redo the dalvik entries by clearing it out.
[X 2014 Android Development] mikeoswego:
Thanks for the update! The clean up of updated apps is probably the last change I'll make to this ROM aside from updating the system apps as time goes by. Things should remain stable now!
[X 2014 Android Development] mikeoswego:
You did not screw up the debloat patch. Google Earth was put into the image with the update to TK Gapps as was listed in that post and I said at the time that the list of debloat apps was up for discussion; why didn't you mention it back at the time?

Emergency Alerts and any setup wizards will not be removed, disable if you don't like them. Earth, Inbox, Messenger, News & Weather would definitely be candidates for removal in the debloated image and I'll do that for the next release. While the Moto camera may not be the best, it actually works well and is the only one that works with the "wrist twist" so I'd be surprised if a majority would want it removed.

It is trivial for me to change what is (or isn't) deleted to create the debloated image but you are the first to make any input about the topic.
[X 2014 Android Development] betarepeating:
Sorry, I want to first apologize if I came off as upset or demanding. I was asking about bloat because I had previously installed the original 5.1 debloat image and some of the current apps weren't in it (particularly the Google Earth app prompted me to scratch my head and come make a post). I don't want to sound like i'm ungrateful for your hard work. I only asked because I wanted to know what justification (if any) there was for inclusion, and I hadn't seen anything in the last few pages explaining some of the additions. I did surmise from the patch notes that you added Earth due to the updated Gapps but was curious if it had some feature that merited inclusion, or if you just hadn't had time to trim it.

I haven't been on the forums recently or I would have been happy to weigh in on the list of debloat apps. I'm sorry I missed the window! I will try to follow this thread more closely.

Fair :]

I have no problem disabling things that you don't wish to "debloat", as that's what i was doing before.

+1 to this! I might even use Inbox, but I think it certainly qualifies as "bloat" regardless and should be left optional for the user to install

Honestly, I didn't know Motorola made the "wrist twist" context only open their Motorola camera. I seem to remember on my old Moto X (2013) I could choose the camera app the first time I used it. It looks like with the new "Moto" app this is no longer the case. So I would agree it makes sense to include. I don't really have any preference between the Google and Motorola camera, in my eyes they performed almost identically. I will probably drop the Google camera in favor of the Motorola one now that I realize this is the case.

Thanks again for all your hard work.
[X 2014 Android Development] mikeoswego:
I think there is a big misconception about debloating that I have contributed do. I actually wish at this point that I had never suggested and created the debloat version. My only reason in creating the debloat version was to reduce the space used in /data (and thereby sdcard) by dalvik-cache entries that will exist even if an app is disabled or frozen. There is absolutely no difference in system performance, ram usage, etc between the debloated rom and the full one where apps have been disabled (aside from the potential space savings mentioned above.) I've tested this multiple times with AnTuTu and actually find about a 200 point increase in the performance score with the full rom over the debloated one; that is counter intuitive and I don't have an explanation for it. This topic probably falls into the area of religion and my process for creating the debloat image is pretty much automated so I'll continue to create it.

The thing is, all it takes is for one or two of the debloated apps to be reinstalled by the user to permanently negate that space savings especially now that I'm rolling the update system apps into the images.

You're right that with the 1st gen Moto X, the camera twist was not part of the camera app and you could choose which one you wanted.

I added Google Camera into the image because there is about 600mb free and it has a different panorama method and photo sphere. I still use the Moto Camera as my daily driver.
[X 2014 Android Development] redwings73:
I tried this as I didn't have the u0_a40 option either. I left the default (root) option....now the phone loops and restarts after the new boot animation begins for a second. Not sure what to do now? Any ideas?
[X 2014 Android Development] mikeoswego:
Try booting in safe mode. With the phone turned off, turn it on and as soon as it vibrates, hold the volume down button until it is completely booted up. If that works, you will see the words safe mode in the lower left corner of the screen. You could then use adb to delete the bad animation. with a command window open on your computer enter:

adb shell

when adb is running and in shell enter:

su

then:

rm /data/local/moodle/bootanimation.zip

If you can't do any of this, you'll probably have to factory reset from recovery..

With power off hold volume down & power for 5-6 seconds and release to enter fastboot mode

Volume down once to scroll menu to Recovery

Volume up to select

When you see the dead android:

Hold down the power button and then tap the volume up button

Use volume down to scroll to Wipe data/factory reset

Hit power button to select that option

Sorry that this has happened! It's too bad we can't put TWRP on these phones, then we would have better options for this type of situation!
[X 2014 Android Development] redwings73:
No worries!... It's the risk I take, right?

I didn't get a reply before I got into recovery and did a factory reset. I remained on 5.1 with root, etc. and the new boot animation file was gone from data/local/moodle. All good now, it seems.

Thanks for the reply. That is helpful info to know for future reference!
[X 2014 Android Development] drewski_1:
just want to make sure i did the right process for this step

does the "wipe cache partition" option in recovery clear the Dalvik? i did this after flashing 3.1.d, but didn't see the whole "Optimizing Apps" thing

is there an option i'm not seeing in recovery that is Dalvik specific?
[X 2014 Android Development] mikeoswego:
Wiping cache in recovery does not wipe the dalvik-cache. The problem with adding/deleting apps in the ROM is that Moto didn't program it to detect that kind of change and refresh the dalvik-cache. The only way for us to force the update is to delete everything in dalvik-cache. Very painful with the Xposed versions for 5.x to wait for all those apps to be optimized!

The only option in recovery that would wipe the dalvik-cache is the wipe data / factory reset option.
[X 2014 Android Development] drewski_1:
got it. thanks!

i saw in Post #1 that i need to delete contents of /data/dalvik-cache . . . RIF (reading is fundamental) :eek:
[X 2014 Android Development] drewski_1:
3.1d fixed the Moto Connect FC'ing, but Connect Extension wouldn't connect to phone until the Dalvik Cache rebuild :D

finally working again and i can delete Verizon Message+ from my computer to get SMS across devices :good:
[X 2014 Android Development] tjohnstone3:
The Anker chargers [MENTION=2250617]Legacystar[/MENTION] mentioned in his post are QC 2.0 chargers. Picked up a couple (1 for work, 1 for home) and they are as advertised. Went from 30% to 50% in less than 10 minutes. Phone did get super hot a little later when I was playing clash of clans and boom beach while still charging, think it was up to 112 tho, so will probably try to avoid using it too much while on those chargers.

But man, that was definitely worth the investment.

Last post by me on that topic and want to say thanks again to [MENTION=5849464]mikeoswego[/MENTION] for making those changes in 3.1c and 3.1d. Phone temp and battery life are soooo much better!
[X 2014 Android Development] AlienZombieEater:
In my debloated v3.1c I got a score of 46262. Flashed v3.1e full image this morning and ran it and got a score of 46651 as the fastest. I did run it several times after cleaning up apps on v3.1e and it did better with each run. I'm going to flash the debloated image and post the results.

Update: I flashed the debloated v3.1e and ran it 4 times: 46968, 46182, 46453, and 46917. Averaging 46630, about 200 points higher than the full image.
[X 2014 Android Development] sonic1675:
Guys, I switched from v65 to this one and now whenever I try to turn on tether, I get an error and it turns off... If this was already referenced could someone link me to the corresponding post.
[X 2014 Android Development] mikeoswego:
Interesting. Thanks for sharing your results!
[X 2014 Android Development] mikeoswego:
That's a new one. Did you delete /data/dalvik-cache/arm and /data/dalvik-cache/profiles?
[X 2014 Android Development] sonic1675:
Yea I forgot to do that. Smh my bad... But yea that fixed it.
[X 2014 Android Development] intx:
[MENTION=5849464]mikeoswego[/MENTION],

Firstly just want to say thank you for working on these images. I was able to pick up a XT1096 on the cheap and I'm using it on T-Mobile in combination with your ROM and it's been fantastic.

Have you ever looked into adding Viper4Android? You've probably heard of it, but it's a *vastly* improved audio driver that also adds a bunch of new features as well. It works for any rooted device, but it does need to install a driver(which gets erased on reboot obviously).

I've considered adding it myself, but I haven't had time to look into how to do it yet. Figured it may be something you would like to add.

The thread on XDA for it:

http://xdaforums.com/showthread.php?t=2191223
[X 2014 Android Development] mikeoswego:
I'm not opposed to this and have had Viper installed on previous phones. I took a quick look at the first couple posts in the thread and it is only stated to work up to Android 5.0 and we are on 5.1. Do you know for sure that it does work with 5.1 (I doubt that any differences between 5.0 and 5.1 would affect Viper but you never know!)

The instructions there for including the driver in the ROM stop with v4.0. I can probably wing it but it would be helpful if you could find specific references or posts about installing the driver into 5.1 roms.
[X 2014 Android Development] infernohit:
Is there a way to get cf. lumen working with this image?
[X 2014 Android Development] mikeoswego:
That's probably doable as well.
[X 2014 Android Development] tbacba:
Mike, I flashed the v3.1b image about 10 days ago and have been happy with the results. I just checked this thread again and see you are now up to v3.1e! I've not experienced any of the overheating battery or force close issues that others have mentioned. So, perhaps a dumb question, but is there any advantage to flashing the 'latest and greatest' (and ongoing) from a system performance perspective?

Thanks again for all your continuing work!

Tbacba