yashsingh1/xdaforums huggingface dataset:
[X 2014 Android Development] intx:
So I couldn't find anything new about including it in ROM except the possibility of Lollipop having a smaller reserved space for /system, maybe causing you to have to remove an app to make it fit.

However, everything I've read about it actually working on 5.1: We need to change the SELinux Mode to Permissive, apparently. I don't know if that's something that can be toggled on your side, but there are applications on Android that can do it for you.
[X 2014 Android Development] redwings73:
Deleted.... Solved.
[X 2014 Android Development] mikeoswego:
You won't see the emojis until you reboot your phone after first installing or after a factory reset. So try rebooting first. If they are still not there look in /data/data for the NotoColorEmoji.ttf file. If the file is there and you have rebooted, try the emojis in some other app like the stock mms or messenger app. If there is still a problem try deleting /data/data/NotoColorEmoji.ttf and reboot twice. Or follow these instructions from the changelog and then reboot:

If iOS Emojis are desired,
Copy /system/fonts/NotoColorEmoji.ttf.iOS to
/data/data/NotoColorEmoji.ttf

To restore the stock font,
Copy /system/fonts/NotoColorEmoji.ttf.stock to
/data/data/NotoColorEmoji.ttf

Remember, this is Linux so cAsE matters!

The next version, 3.1f will have the emojis available on the first boot instead of requiring the second reboot if the file doesn't already exist in /data/data
[X 2014 Android Development] mikeoswego:
You won't see any particular performance improvement by upgrading to v3.1e. v3.1f will have some performance improvements, though, if everything continues to work out!
[X 2014 Android Development] mikeoswego:
Viper4Android has annoyed me so far.. It actually has not been properly updated for Android 5.0, the latest driver in the zip is for Android 4.4. I was able to get it say that it was installed properly but didn't get it to process anything. It did make some clicks and pops as I tried various things. I might work with it some later.

How about the CM AudioFX as a substitute? It doesn't have all the features of Viper but does allow control of Bluetooth, speaker, headset all separately. I've replaced the stock Audio Effects with it for v3.1f, screenshot below.
[X 2014 Android Development] mikeoswego:
Looking for feedback

Ok, I have CF.lumen and Viper4Android working and want some feedback on what you guys want going forward.

First, Viper4Android does require sellinux enforcing to be turned off which is supposed to be a security risk and almost all current apps work with it enabled by now. Viper4Android is not being officially supported and the driver that works is for Jellybean so it's really old. For those 2 reasons I'm not completely happy with this being in the mainstream rom (and it's to messy to pull it in and out like I can with Xposed, CF.lumen, and the GApps.)

So having said all this, was the recent request (and past request) for Viper4Android really just for some adjustments in bluetooth output which might be satisfied with the CM AudioFX or is there a majority wanting all the other features like AGC, CureTech, etc.?

Also, will CF.lumen be considered bloat and not wanted in the debloat roms?

Attached is a screen shot with CF.lumen in "sleep" mode and showing the Viper4Android driver enabled.
[X 2014 Android Development] mikeoswego:
xt1096-5.1-v3.1f-viper.img

I suppose you guys can check this out before making your opinions known...

Here is the latest version for testing: xt1096-5.1-v3.1f-viper.img.7z

It includes CF.lumen and Viper4Android audio effects

I added CM's Trebuchet launcher as a secondary launcher option. The first time you boot this rom, you'll be asked which launcher you want to use. To keep everything the same select Google Now Launcher and then select Always. You can change this later in Settings->Home if you want to check it out. Trebuchet is not in the debloat rom.

Updated apps in /system are Chrome, Docs, and Drive.

I've completely redone how the system updates things if you've got updated apps from the playstore that are equal or older in version number to those installed in system. Your settings will no longer be lost during this update/clean up process. However, in order to do things properly, the system will reboot 30-90 seconds after the lock screen comes up. There will be occasional toasts telling you this is happening. There is no need to wipe dalvik-cache with this new method of updating. (Although other types of updates may still require clearing the dalvik-cache.) This cleanp routine will only run the first time a new rom version is installed.

The Xposed framework is updated to v69 but there are no changes affecting our phones and no need to wipe dalvik-cache for this change either.

Selinux enforcing has been disabled to allow Viper4Android to work. This is actually the main concern I might have about leaving Viper4Android in the rom.

There is a debloat patch attached below.
[X 2014 Android Development] JulesJam:
Could you summarize how you got CF Lumen working? I will add it to the MoFo image modification thread so others can modify the XT1097 image to include CF Lumen too.
[X 2014 Android Development] tbacba:
Great, thanks. I'm looking forward to it!

Tbacba
[X 2014 Android Development] intx:
Mike,

I'll be checking out the patch either later tonight or tomorrow. I did see about two posts above it that you were having trouble getting it to work and were looking into another program. Does this patch being released mean you've got it sorted out?

Thanks so much for spending the time to mess with it!!
[X 2014 Android Development] RashaMatt:
Personally I do not want Viper nor CF Lumen in my deboated ROM.

@Mike - How simple would it be for us to mount your image on a PC (or Linux) and tweak it ourselves before flashing? I know there are PC tools for mounting ext4 partitions (not sure about image files).

For example I'd like to add a few notification sounds. Getting apps to use sounds that aren't in /system/media is sometimes problematic.

One possible bug (probably not your doing): When I plug in a USB storage device it gets auto-mounted, but the first write attempt always fails and then it's RO. I have to manually unmount and remount the device (from Settings/Storage) to get it to work properly. Minor PITA.
[X 2014 Android Development] mikeoswego:
I've just posted v3.1f and it has the CM AudioFX replacing the stock Moto Audio Settings. Then there is a patch to replace AudioFX with Viper4Android and it works fine. Everything seems to work fine in this image so maybe that's what the f in v3.1f should stand for!
[X 2014 Android Development] mikeoswego:
I've already posted the new update with CF.lumen in the image. I'll remove it in the next debloat unless there is debate about it.

I modify these images while mounted to an Ubuntu 14.04 system. I dual boot Win7. You could do simple adds and deletes with the Android/Linux ext4 file system image mounted to your Windows box but with a Linux box, you can test run scripts with only minor changes instead of doing everything on the phone.

In regard to the sounds, I have sounds in /sdcard/Alarms, /sdcard/Notifications and /sdcard/Ringtones and all are seen by any app that I've tried. I could add the CM sound pack from CM11 to the image if there's interest.

I regularly use a USB-OTG drive with my phone via ES File Explorer. It does not have any write/mounting problems.
[X 2014 Android Development] mikeoswego:
Attached is a new debloat patch that also removes CF.lumen from the image. Cf.lumen is now added to the debloat list.
[X 2014 Android Development] tbacba:
Re the changelog "Major improvement to updated /system app cleanup of apps in /data. Now takes 2 seconds instead of 90. Cleanup happens seamlessly, no reboot required". Is this cleanup process related to the image being flashed, or is it some sort of manually initiated system cleanup that the user can initiate? Thanks!

Tbacba
[X 2014 Android Development] intx:
Excellent! I'll be giving it a shot later tonight with the F version.

I think having it as a separate patch is smart and seems like it will work well!

Thanks again, you rock!
[X 2014 Android Development] AlienZombieEater:
I'll try to flash the various debloated v3.1f images and get some numbers on system performance over the next couple days using the different launchers.
[X 2014 Android Development] redwings73:
Deleted... Again.
[X 2014 Android Development] mikeoswego:
When I add a new version of an app like Chrome to the image after you have already downloaded the new version from the Play Store (or APK Mirror) you end up with 2 copies of the app; 1 in the system image and the other in the /data partition. Before Lollipop, Android would automatically detect this and remove the duplicate app in /data freeing up space that is available under /sdcard. My cleanup routine replicates this function but only for apps that do not rely on the new Lollipop behavior.

In v3.1f, this runs every time you reboot your phone. In the next version, I'll detect if it has already been run for the current rom and exit if it doesn't need to be run; I may be the only one that will notice that change.
[X 2014 Android Development] mikeoswego:
And I was just getting ready to answer you! :)
[X 2014 Android Development] redwings73:
Thanks.... For some reason I couldn't find the app in the drawer, so I was thinking there was a trick I missed somewhere. Then I find it. All good.
[X 2014 Android Development] tbacba:
Nice explanation, thanks!
[X 2014 Android Development] RashaMatt:
Any reason to flash the new 3.1f if I'm already on xt1096-5.1-v3.1f-viper.img ?
[X 2014 Android Development] AlienZombieEater:
Ok, did some more tests.

Here are the previous results:

v3.1c debloated - ran once, 46262

v3.1e full image - fastest was 46651

v3.1e debloated - ran 4 times, average 46630, about 200 points higher than full image, fastest was 46968

For the new tests I ran AnTuTu Benchmark v5.7.1 7 times.

v3.1f debloated (image with CFLumen) and default Google Launcher - average 47098, fastest 47766! Damn, Mikeoswego stepping up his game!

v3.1f debloated (image with CFLumen) and CM 12.1 Trebuchet Launcher - average 47125, fastest 47953. A bit better performance over default launcher; one run was significantly lower than the rest which brought the average way down.

I'm waiting for the IT department to install Python on my work PC so I can flash other images and test them :D
[X 2014 Android Development] Pizzuto:
Can I get a link to the "f" debloat patch that leaves CF-lumen in?
[X 2014 Android Development] AlienZombieEater:
Post 556
[X 2014 Android Development] betarepeating:
Not sure what I did, but I seem to have bricked my phone... Deleted Dvalik Cache and then mofo flashed xt1096-5.1-v3.1f-de.img over my current xt1096-5.1-v3.1d-de.img. Everything seemed fine so I tried to navigate into recovery in order to wipe the cache... and that's when things started acting weird. The dead android icon would flash for a split second and then disappear. Now I can't get back into the bootloader. Holding down Power + Vol Up will cause the yellow text to flash as if it's about to enter recovery

"E:Can't mount /cache/recovery/last_log

E:Can't open /cache/recovery/last_log

qe 1/1"

Then it just goes black and the dead android starts blinking again. The pattern is about 10 seconds of black screen followed by half a second of the dead android blinking on. If I hold down power button long enough I can get it to reboot (it shows the Moto X Blue circle briefly) and then goes right back to the same pattern.

Any help? :[

---------- Post added at 03:00 PM ---------- Previous post was at 02:42 PM ----------

Well I can't edit my posts for some reason, so sorry for the double post. After 10 minutes of panic and mashing all the buttons it suddenly worked, I held down all three buttons out of desperation and counted to 30 and... lo and behold the bootloader window popped up and i was able to choose "start normally" from there. My custom boot animation played and everything seems to be behaving normally. I'm not sure what went different this time but I guess chalk it up to random weirdness? This is my third or fourth time doing this process and I'm familiar with the correct key sequences so I'm not really sure why it decided to freak out this time.

I rebooted after everything came up and it weirdly shoved me into the recovery menu instead of booting normally. I wiped the cache and rebooted and it booted right back up. Once booted I rebooted again and was greeted with my custom bootloader followed by a normal boot. So, everything is fine?

To be clear, did I do everything right in the update process? Everything seemed standard up until I tried to enter recovery after the flash to clear out my cache, and then things started acting all screwy.

I guess I'm not sure what this post accomplishes anymore except to report that everything works fine now. The update itself feels great and I have had no issues so far.
[X 2014 Android Development] JulesJam:
Since we have copies of both stock 5.0 and 5.1 for our device, as long as you can get into bootloader mode and use fastboot, you are not bricked.

---------- Post added at 08:54 PM ---------- Previous post was at 08:52 PM ----------

It seems that people get that issue after flashing to a modified 5.1 system image using MoFo when they try to boot into recovery without first booting into system. When you encounter that issue, get back into bootloader mode, boot into system through BP Tools and then use adb to boot into recovery to wipe cache.
[X 2014 Android Development] gunit25:
I apologize in advance for re asking, but if you are coming from an older version you just flash over the existing image correct? The patches are to alter the current image if you want to remove or add certain features
[X 2014 Android Development] mikeoswego:
It's the second in the list. When it is installed it shows the name I posted before. It isn't fully functional, it says 4g, the toggle to LTE doesn't work. It's one icon wide, smooth signal ramp instead of bars.
[X 2014 Android Development] tacosrdelicioso:
I assumed that since it hasn't been updated since 2014 it wouldn't be compatible with lollipop

---------- Post added at 12:35 AM ---------- Previous post was at 12:23 AM ----------

Anyways the memory leak fix module is called "Fix Lollipop Memory Leak" it seems to help my device
[X 2014 Android Development] mdmogren:
I have it installed as I mentioned, but don't know if it actually works without being able to write to system, and is definitely an ultimate fix, time will tell. Navigation closing while in use and podcasts and music stopping mid playback is just completely unacceptable. I can't believe more people haven't had this issue or thought it was a major deal, but I guess I'm a much "heavier" user than most.
[X 2014 Android Development] tacosrdelicioso:
I don't have these issues and have used both music over Bluetooth in my car and navigation for over an hour straight multiple times
[X 2014 Android Development] fakieskr8333:
I installed it and started getting systemui crashes left and right. Settled down after a few minutes then came back. Uninstalled and it went away. Not sure if it is conflicting with something else or what.
[X 2014 Android Development] tacosrdelicioso:
These are all my modules that I use. All of them work perfectly. Surprising a module for June of 2014 works for a completely new os but hey idc.
[X 2014 Android Development] mdmogren:
I'm happy for you, and jealous, but this issue is incredibly well documented and confirmed by many many users. For me, last time I had Lollipop it was a daily issue (on my previous '14 X before I RMA'd it.) I listen to easily 4+ hours of audio every day and use navigation to multiple locations, maybe that's the difference, maybe it's specific to an app I use. For most people, this bug comes up once every 72 hours or so and they have to reboot, for me, it was more frequent, like every 12 hours, sometimes even less. See here for extensive discussion of this issue: https://code.google.com/p/android/issues/detail?id=79729
[X 2014 Android Development] tacosrdelicioso:
Oh I totally had that issue in lollipop music would often kill itself if I opened snapchat while driving and launcher redraws and all that. But I haven't seen it yet. Obviously I haven't had all this stuff for very long and hopefully the system leak fix from xposed extends the time needed before reboots.
[X 2014 Android Development] mdmogren:
Airplay

One thing I was really looking forward to with root was Airplay via AirAudio or Allstream, but neither work. they ask you to reboot, but that doesn't work, just keep asking after reboots, I guess they have to write to system. Any chance of baking this in to an image?

---------- Post added at 09:46 PM ---------- Previous post was at 09:38 PM ----------

SNAPPREFS doesn't seem to work for me, I can set everything up, but don't see the new options like select all and it doesn't save the images. Is it working for you?
[X 2014 Android Development] tacosrdelicioso:
What you have to do is have the latest Snapchat all up and running and then use tibu to back it up. Then source the last supported version of Snapchat. Uninstall Snapchat then install that older version supported by snapprefs which is 9.3.1.0. Don't touch it yet. Then go into tibu and restore data only from that Snapchat backup and voilà you've won the internet. Tibu=titanium backup. I've owned the pro version for years and I'm not sure if you need it for data only app restores. You might. But yeah that's it
[X 2014 Android Development] mdmogren:
Cool, thanks, I'll give it a shot.

---------- Post added at 10:39 PM ---------- Previous post was at 10:29 PM ----------

It works, just for the record, the sender won't get a screenshot notification, right?
[X 2014 Android Development] tacosrdelicioso:
Haha no
[X 2014 Android Development] fakieskr8333:
I couldn't live with the Verizon icons again so I gave this module another chance and it appears to be worming with no crashes. I think using the LTE icon is what caused issues even though I had turned it back off. Either way it is working now and I am happy!
[X 2014 Android Development] tacosrdelicioso:
Thanks again for this. Ugh I can't believe I was dealing with stock just a short while ago.
[X 2014 Android Development] mikeoswego:
I added another image, it is identical to the previous one but replaces the stock dialer and mms apps with Google's dialer and Messenger app.

If you are already running the Xposed image, you can just flash this one without any special steps. The original dialer and mms app icons will disappear from the home screen(s), the Google app icons will be in the app drawer for you to drag out to the locations you want.

Here's the link: XT1096_5.0-tether-root-bb-sqlite3-Xposed-G_Dialer-G_Mms.img.rar
[X 2014 Android Development] JulesJam:
why are these better? just curious.
[X 2014 Android Development] mikeoswego:
The Google dialer is the same as stock but adds Google caller ID for incoming calls and if you use search within the dialer and, for instance, type in pizza, it will show the nearby pizza joints in addition to whatever you have in your contacts. Messenger is just a little more colorful than the stock MMS, you can set colors for conversations. Messenger can be gotten from the play store if you want to check it out.
[X 2014 Android Development] skytbest:
I tried the AOSPSignalIcons Xposed module and now I am getting SystemUI crashes to the point where my phone is unusable. I installed this module yesterday and it was working fine all day, however I was on wifi (but I did switch wifi off for a couple minutes to test, and it was working fine with the LTE icon). Today I headed out the door for work and the next time I picked up my phone I noticed the message "SystemUI has stopped working". I click OK and it crashes again and shows the same message. Over and over. I can't do anything at all on the phone, I've been trying to open the app drawer between crashes but it is impossible.

Is there anything I can do right now? I'm at work so I don't have access to Mofo for the rest of the day.
[X 2014 Android Development] mikeoswego:
Try putting your phone in safe mode: http://www.phonearena.com/news/How-to-enable-Safe-Mode-in-Android_id63639

Once there you can disable the Signal Icons module (or try changing it to 4g, it might not work on LTE.)
[X 2014 Android Development] skytbest:
I was able to get to the xposed app and disable it when I was rebooting the phone (right after it booted, before it picked up a cell signal). I tried chanigng it to 4G and that was giving me the same problem. So I did the same thing, immediately after reboot I just disabled the module alltogether.

Is anyone else having the same problem? A bit dissapointing, especially since it works for a little while and I can see the LTE or 4G icon there fine, but then I start getting the SystemUI crashes.

Thanks for your help.
[X 2014 Android Development] mikeoswego:
No, only minor differences.
[X 2014 Android Development] mikeoswego:
If you have time,vwhat I'd really like to know is if there is any difference between the debloat rom and the full image with the same apps disabled. There is a way that I think can be setup where you guys could disable apps in a way where they wouldn't even show in the disabled list. You'd also be able to enable just one app or whatever each person wanted.
[X 2014 Android Development] mikeoswego:
I didn't make one pending a request. I'm in the middle of two disastrous Win 10 upgrades at the moment.:p
[X 2014 Android Development] mikeoswego:
Guys, just don't go into recovery. Don't worry about the cache it will take care of itself. The dalvik cache needs attention at times but you can't fix that in recovery anyway.
[X 2014 Android Development] mikeoswego:
That's correct!
[X 2014 Android Development] AlienZombieEater:
Should I freeze just the apps in your debloat list or do I need to freeze some processes, too?
[X 2014 Android Development] mikeoswego:
Just freezing the apps would be great!
[X 2014 Android Development] jrbmed08:
Hi Mike, quick question. I'm still running smoothly on 3.0 ever since I rolled back from 3.1b, and I don't feel the need for any of the new additions (cf.lumen, viper, emoji). Will I still benefit from upgrading to 3.1f? E.g. battery life or performance improvements? Thanks!
[X 2014 Android Development] JulesJam:
I think the issue is that you have to boot into system before ever booting into recovery. Not sure why but the issue seems to arise when you flash a modified 5.1 image using MoFo then boot into recovery. But if you boot into system instead, you are fine. At least that is how it works for me.
[X 2014 Android Development] mikeoswego:
No, there is nothing improved as far as battery life or performance improvements, just the new additions.
[X 2014 Android Development] mikeoswego:
The issue is that mofo wipes the cache (multiple times even) and recovery is not expecting that to happen. Recovery looks for files in /cache/recovery and barfs if they aren't there. On first boot, Android creates those files and directories in /cache and then recovery can work properly.

However, and again, there is no reason whatsoever to manually wipe the cache after running mofo. The last line on your screen after flashing with mofo is "erase cache". The only reason anyone should ever go into recovery is to do a factory reset as a last resort if something in /data is corrupted.

Custom recoveries like TWRP handle the case of an empty /cache partition properly, obviously the stock Motorola one does not and it is has no use for us.
[X 2014 Android Development] mikeoswego:
Here it is!