yashsingh1/xdaforums huggingface dataset:
[X 2014 Android Development] contesauce:
Install went as expected. I was coming from another version of this img with adaway and xposed and bb, sqlite. I cleared cache before and after install, on boot everything went good, not too long. At first everything was smooth, I was letting it settle before playing with the new dialer, then I started getting mass unresponsive apps, mostly google. I did a reboot and haven't had a repeat of the issue yet. Adaway updates fine, xposed modules load fine, and busybox is good. Google dialer is operational if a little slow feeling to me, oh and the boot animation is gorgeous as well. Great work putting this one together, to all who input.
[X 2014 Android Development] Haxxa:
hmmm.. that sound a little scary might hold off until its confirmed that this was a one off issue. But thanks for the upload!
[X 2014 Android Development] contesauce:
To be fair it happened to someone else on one of the other threads with a dif image. Seems to be a one off after a reboot. Understand your trepidation though.
[X 2014 Android Development] ClydeDroid:
It actually just happened to me too. Rebooted and hasn't happened again. But yeah, it also happened to me with one of the previous builds as well, so I think it might just be a one-off problem. Will report if it happens again.
[X 2014 Android Development] Twistitup:
It does that with every new flash. Not sure why, but a reboot fixes that sucker.
[X 2014 Android Development] TokedUp:
Thanks for this! Any chance of getting this image without Xposed?
[X 2014 Android Development] ClydeDroid:
I can do that, do you want everything except Xposed?
[X 2014 Android Development] TokedUp:
YES! I had a very bad experience with Xposed once and i'll never use it again. Thanks. There's no rush though. Im on vacation so I wont be able to flash anything or donate to you until I get back home. I really appreciate it man and I promise I'll buy u some beer as soon as i get back.
[X 2014 Android Development] Mayze23:
Is this based off the image that has the HDR fix?
[X 2014 Android Development] Haxxa:
Alternatively you could flash this image and not use Xposed i.e. don't install the APK. Libs are't doing anything important.
[X 2014 Android Development] ClydeDroid:
Yep!
[X 2014 Android Development] Haxxa:
Installed! Thanks for the Birthday Present ;) -

As a suggestion you could modify the Build.prop to add a custom Rom Name under settings and custom details etc. That way you can really feel ownership of your changes.

Also if you really wanted you could delete Verizon Apps under the /system/app partition to remove bloatware but I understand that may be a bit tedious and undesirable. Otherwise really good build, worked well - no issues. :D
[X 2014 Android Development] JulesJam:
Or you could just freeze them with TiBU. If you are not going to be able to use the space for anything else, no sense in deleting them. Also some Verizon customers actually use NFL Mobile, Verizon Navigator, MyVerizon, etc.
[X 2014 Android Development] tjohnstone3:
I've had the gapps issue as well, basically neutered the phone until I forced a restart. A reboot had fixed it temporarily but it came back again a couple of times. I eventually uninstalled updates for both Play Store (gapps) and Google Play Services and re-downloaded the updates. Have been fine for a while now.

My bluetooth has also been wonky. Used to connect to my car without issue but now I seemingly have to manually connect, or even reboot the phone to get it to connect. Wasn't having these issues on previous images...

Now that I've bltched, I really appreciate the work...and the changes are worth the few headaches! Thanks!
[X 2014 Android Development] JulesJam:
Do you have any interest in adding CF Lumen to your image? When I download it, it has to install a driver and that must be something that is installed on /system b/c it never gets installed. However, I don't know if drivers are something that is too complicated to bake into an image.

http://xdaforums.com/showthread.php?t=2711912

There is an unrooted mode but it doesn't work near as well as the rooted mode. With the rooted mode you can get the whites to be a very nice cool-toned white w/o any yellow/pink tinge.
[X 2014 Android Development] ClydeDroid:
Sure, I'll give it a shot!
[X 2014 Android Development] ClydeDroid:
That's really strange. I've only experience the gapps freaking out once, but this is worrying. I might do some research to try to figure out what the problem could be.
[X 2014 Android Development] tjohnstone3:
It's been 5 hours since I did the uninstall updates and reinstall them and I haven't had any issues since. So hopefully it's a thing of the past.

Though I haven't retested the bluetooth since this morning.
[X 2014 Android Development] smelkus:
I read into that a little bit and I think you would need to ask Chainfire to get it going. His cf.Lumen XDA thread says it is not to be prepackaged. There are two driver install methods, but without his help I'm not sure it is doable. Would really like it though.
[X 2014 Android Development] mdmogren:
Thanks and a request with a reward.

Awesome work, thank you!

Downloading now. Do you think you can find a way to get the necessary changes required for AirAudio to work?

https://play.google.com/store/apps/details?id=eu.airaudio&hl=en

It apparently needs to write something to system and requires a reboot after first launch, but doesn't obviously doesn't succeed in our setup.

I just sent you $5 now for this version, if you can make in image that includes everything here, plus AirAudio working, you've got another $20 coming your way.

Thanks again!
[X 2014 Android Development] ClydeDroid:
Just sent him a message!

Thanks for the support! :) I'll take a look and see if I can get AirAudio to work.
[X 2014 Android Development] ClydeDroid:
Just rebuilt the image to fix an issue with Busybox and to include the necessary files for AirAudio. Will flash later today and upload if everything looks good. Still waiting to hear back from chainfire on CF.lumen.
[X 2014 Android Development] tjohnstone3:
I redid the bluetooth pairing process with my car/phone and it seems to actually connect properly now...so hopefully that will fix my issues there.

The gapps haven't given me any issues either since I uninstalled the updates and reinstalled them. Thanks again for the image!
[X 2014 Android Development] trimax84:
That crazy boot image was too much for me. Too busy, too bright, too intense!

So I modified Clyde's ROM with the following edits....

Changed boot animation to this:

Credit to [MENTION=4542140]raishiro[/MENTION] here for a ton of great bootanimations.

Few mods on the build.prop for some mild performance/battery enhancements:

windowsmgt.max_events_per_sec=150

ro.telephony.call_ring.delay=0

wifi.supplicant_scan_interval=200

ro.HOME_APP_ADJ=1

debugtool.anrhistory=0

profiler.debugmonitor=false

profile.launch=false

profiler.hung.dempdobugreport=false

ro.config.nocheckin=1

ring.delay=0

ro.ril.enable.amr.wideband=1

Because it is basically just a lightly moddified version of [MENTION=2821926]ClydeDroid[/MENTION] excellent image, it maintains root, Xposed, AdAway (/data/data symlink) adblocker, busybox, tether, Google Dialer, and SQLite3.

Download Link: Here
[X 2014 Android Development] ClydeDroid:
Sweet edits! I actually agree, that bootanimation is a little over the top haha. I might take another one of raishiro's for my next build. Quick question, those build.prop edits, do you just add them to the end of the file, or do you have to edit lines that are already there?
[X 2014 Android Development] trimax84:
Yes, I just added them to the very end. If a value is already included, then you just edit it (but none of those were)
[X 2014 Android Development] ClydeDroid:
Okay, so I'm still having issues getting AirAudio to work, but I got Busybox working again and made some build.prop edits. I'm going to make a few more changes and upload the new build as version 1.1.
[X 2014 Android Development] trimax84:
Cool, looking forward to it.

What did you do for AirAudio (AirPlay? -that's what it's named in the link)? By unzipping the .apk file, seems like there are 5 files in /lib/armeabi that should be placed in the /lib folder of the system image? I couldn't find a file similar to previous flashable zips (update-binary) that details where they go and permissions/context. Based on other files in the /llib directory, I would sudo chmod 0644 and sudo chown 0:0 the files. Not sure about the context though....should they all be u: object_r:system_file:s0 ?

Hope you get it to work! This actually looks like an app I might pay for if it works.
[X 2014 Android Development] Haxxa:
Just checking if anyone has any issues with Google Dialer, I have certainly had issues with it closing or hiding calls in background certainly could be more stable. Also overall home-screen performance does encounter a few slow downs but haven't tracked it down yet; Could be an Xposed issue (maybe one of the modules) or from an issue I have encountered. On another note, People are suggesting to wipe GAPPS Cache, does this literally involve going to Settings - Apps and wiping every google app or is there an easy method?
[X 2014 Android Development] gunit25:
Hi Clyde,

Loving everything you are doing and keeping a close eye on this thread as your image develops, but I do have a simple request. Do you think you can keep a changelog running of the changes you are making? All of the work you are doing is awesome and exciting but I am worried to jump in with so much undocumented change.

Thanks!
[X 2014 Android Development] ClydeDroid:
I've actually been in contact with the developer, he gave me an apk to stick into priv-app but that didn't do it. I've tried sticking those files into /system/lib and changing the permissions and owners like you suggested. Just flashed, I just wish my phone didn't have to optimize 240 apps every time I flash, it takes over 30 minutes every flash and my phone starts baking...

I haven't had any issues with Dialer yet, except once it popped up during a call and said "Mobile data not available." Let me know if you have any more serious issues. As far as the gapps wiping, I haven't tried it myself yet, but I assume the important one to get is Google Play services. If that doesn't work you can do the others like Maps, Gmail, etc.

I will certainly set up a changelog once I get a stable 1.1 uploaded. Thanks for the suggestion!
[X 2014 Android Development] mdmogren:
Thanks for working on the AirAudio stuff, anxious to hear if the latest files/permissions does the trick!
[X 2014 Android Development] ClydeDroid:
Okay, finally uploading v1.1. Changes include a new bootanimation, busybox fixed, the Google Messenger app, build.prop enhancements by [MENTION=2921457]trimax84[/MENTION]. Detailed changes will be in the changelog on the first post. Still working on getting AirAudio working with the developer, and still waiting to hear back from Chainfire about CF.lumen. I'll probably end up extracting the CF.lumen apk to see if I can implement any changes myself.
[X 2014 Android Development] gunit25:
Is there any impact loading one over the other? AKA:

Stock -> 1 -> 1.1

stock -> 1.1
[X 2014 Android Development] ClydeDroid:
As far as I know, there shouldn't be any issues moving between any mofo images in any order. I've been flashing image after image and things have been pretty stable. Just be sure to wipe cache before and after each flash!
[X 2014 Android Development] JulesJam:
Do you need to wipe both before and after? I usually only do after.
[X 2014 Android Development] ClydeDroid:
I've been doing both, just to be safe. It probably only needs it after, but it can't hurt to wipe too much!
[X 2014 Android Development] trimax84:
Not sure about the specifics, but I went from your original to my edit (different bootanimation and build.prop mods) without deleting the two cache folders, without an issue.... So not sure if you need to do that between flashes of the same base ROM (might save you sometime)

I still 'fastboot erase cache' though, just for fun.
[X 2014 Android Development] Pizzuto:
I have a message in my recent apps that says "Unable to load widget". Do we know what app to install to make this widget work, or perhaps how to remove the widget from the recent apps screen?
[X 2014 Android Development] contesauce:
Did you remove google search, or freeze it? Had this problem on my Nvidia Shield tablet and it was originally because the third party launcher I was using (nova beta) did something funky to the google search bar in recent apps. The fixes over there range from boot into safe mode, try google launcher see if that fixes it, or uninstall reinstall google search, the usual gamut.
[X 2014 Android Development] trimax84:
Thanks [MENTION=2821926]ClydeDroid[/MENTION]! Let us know how that's progressing :)

I did some small modifications on your base image....

-Switched the bootanimation to that color disco ball looking one

-Reclaimed about 300mb of space by deleting a few system apps (like VZW caller ID, vzw navigator, NFL, etc) and removing help video/image files.

If anyone is going to use it, make sure you do the usual erasing /data/dalvik-cache as well as clearing other cache (fastboot erase cache).

Download here: Link
[X 2014 Android Development] JulesJam:
What other system apps did you remove and what can you do with the freed up 300MB of space on the system partition?
[X 2014 Android Development] trimax84:
I realized after I uploaded the file that I should have kept track, but if I remember the apps were vzw navigator, caller ID (or was it City ID?), chrome (I wanted to use chrome beta instead), NFL, visual voicemail, vzw tones, Hindi IME, Latino IME, maybe others that I can't remember....

And from what I've read, since we can't write to the System partition, that space basically goes unused? I thought of throwing some of my usual /data apps in there to use that space and save some from the data partition, but haven't gotten time to grab the APKs and what not.

Have you gotten your USB yet Jules? Are you modifying or building your own ROMs? Do share :)
[X 2014 Android Development] JulesJam:
Yeah, the apps would have to be baked into the system partition pre-flashing.

I got it - a 128GB PNY 3.0 USB flash drive for $30 - and it was DOA!!! Grrrrr. Sending it back and waiting for another deal. There was a 256GB HP 3.0 for $50 but I missed the deal.
[X 2014 Android Development] Interflop:
MMS is no longer working correctly for me, probably because of AdAway. Is there a way I can revert the changes and start from scratch again?
[X 2014 Android Development] GatorsUF:
I'm on 1.1 and HDR is broken as well as the Google dialer. Not sure if it's just me...
[X 2014 Android Development] contesauce:
I can confirm HDR is broken for me as well, but google dialer operates just fine for me.
[X 2014 Android Development] JulesJam:
I downloaded it and HDR is broken for me too.
[X 2014 Android Development] GatorsUF:
Disregard, the Google dialer works. Just the HDR is broken.
[X 2014 Android Development] hotpass105:
I'm using this system image and I'm having problems with android system using most of the battery and HDR still causes a fc. This is with v1.1
[X 2014 Android Development] ClydeDroid:
Sorry guys, finals week has been brutal. I was aware of the HDR issue, I know how to fix that, so I'm gonna start working on 1.2 soon and upload it!
[X 2014 Android Development] contesauce:
No worries man, I know how that goes, just finished finals myself.
[X 2014 Android Development] JulesJam:
Whether or not android system uses the largest percentage of the battery is dependent on what you are doing with the phone. If you use a lot of data tethering but don't use a lot of apps, text or talk on the phone much like me, then the Android OS will use the most of your battery.

Now if you are getting decreased battery life using the phone the same as you use it on stock, that would be important to note.

I haven't seen any decrease in battery life with this image. But I just flashed it so I will have to see at the end of the day.
[X 2014 Android Development] Mayze23:
I've been using 1.1 since release and I haven't experienced any abnormal battery drain either.
[X 2014 Android Development] mdmogren:
VoLTE?

Will it be possible for us to beat Verizon to the punch and bake in some "Advanced Calling 1.0" aka Voice Over LTE or do we have to keep waiting? The Google Dialer Caller ID doesn't seem to work when not on Wi-Fi due to this issue.
[X 2014 Android Development] JulesJam:
I think this is a network thing not just a device thing. The feature not only needs to be added to your line, Verizon's network needs to recognize your device as one that is capable of making/receiving HD calling. We would have to understand exactly how Verizon's network does that and we don't.
[X 2014 Android Development] Legacystar:
Anyone else having issues with hrd?
[X 2014 Android Development] GatorsUF:
I too have had issues with battery on this image. Haven't used it any different. My battery is usually dead by early afternoon.

I turned off all my xpsed modules today and it seems better so far.
[X 2014 Android Development] contesauce:
Read a few posts back.
[X 2014 Android Development] drwhitney:
[MENTION=2921457]trimax84[/MENTION] Does this image have working HDR?
[X 2014 Android Development] trimax84:
No, this was based off of the OP's.
[X 2014 Android Development] drwhitney:
Does the link for TotalX1.0 still exist? It was removed from the OP. If I remember correctly, it had working HDR.
[X 2014 Android Development] JulesJam:
I have an earlier version of his ROM that has AdAway and working HDR. I will double check that I am right about that and post it if someone wants it. Just let me know.
[X 2014 Android Development] drwhitney:
I just flashed [MENTION=2921457]trimax84[/MENTION]'s latest image that he posted in [MENTION=5849464]mikeoswego[/MENTION]'s image thread. That post is here: http://xdaforums.com/showpost.php?p=60866087&postcount=106. It has working HDR and the right mix of apps that I was looking for. So I don't think I need the old TotalX anymore. Thanks.
[X 2014 Android Development] JulesJam:
Ok well if anyone wants an older version of [MENTION=2821926]ClydeDroid[/MENTION]'s image that has Busy Box, SQLite3, Xposed, AdAway and free WiFi tether, let me know and I will post it. It has the stock boot animation but no HDR camera bug.
[X 2014 Android Development] JulesJam:
It seems like modifying the build.prop may be the cause of the HDR bug. It doesn't really make sense to me, but trimax84 had success by not modifying the build.prop.

http://xdaforums.com/showpost.php?p=60846657&postcount=98

Also, I have one of your older images with the stock boot animation, bb, sql, xposed and adaway and it does not have the hdr camera bug.
[X 2014 Android Development] Pizzuto:
This worked like a charm for me! Not build prop at all, but the editor, switched editor and presto. Thanks Jules
[X 2014 Android Development] JulesJam:
What editor were you using and which one did you switch to?
[X 2014 Android Development] Pizzuto:
VIM ---> Geany

Debian / Ubuntu

*also had no luck with Gedit
[X 2014 Android Development] JulesJam:
Ok to translate, you were using Ubuntu and with the VIM and Gedit editors you had issues with your image but when you switched to Geany editor, the image did not have issues?
[X 2014 Android Development] Pizzuto:
Yes!
[X 2014 Android Development] JulesJam:
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] funtax:
Hi there,

I'm the dev of "AirAudio" and wonder if I can assist

Just to have it public.. everything which should be required to get AirAudio working on your ROM, should be:

1. extract the APK of AirAudio

2 take the file /res/raw/arsc.raw

3. rename the file to "AARSCService.apk" and place it under /system/priv-app/ .. so there finally exists a file named /system/priv-app/AARSCService.apk

4. chmod 644 /system/priv-app/AARSCService.apk

And that's all.. hopefully.

Do NOT copy any files of the /lib-directory - that's absolutely not required :)

Happy coding, contact me if you need help and I'll do my best.

Cheers & kind regards,

Martin
[X 2014 Android Development] ClydeDroid:
Hey guys, sorry I've been quiet, I just graduated college and my family was visiting. I've just gotten rid of the build.prop edits in a new image. Just flashed, no more HDR crash and busybox is working. Unfortunately, I am still unable to get AirAudio to work. I'll keep working at that, but for now I am uploading version 1.2. I'll update the first post when it's done. I'll also leave links to the old versions if people are interested in them.
[X 2014 Android Development] JulesJam:
Did you see these posts?

http://xdaforums.com/showpost.php?p=60942406&postcount=75

http://xdaforums.com/showpost.php?p=60942214&postcount=522

---------- Post added at 02:02 AM ---------- Previous post was at 02:00 AM ----------

Congratulations!!!!
[X 2014 Android Development] ClydeDroid:
Followed those instructions and no luck. Though I just tried changing the context of the file and I will report on whether that works soon.
[X 2014 Android Development] timofcourse:
Looking forward to this update! AirAudio and tethering are the two root features Ive missed most! Thanks for all the hard work (and thanks [MENTION=5262529]funtax[/MENTION] / Martin for helping integrate your excellent app)!
[X 2014 Android Development] ClydeDroid:
Good news, folks - AirAudio is working! :D Uploading version 1.3 now! I'm still also working on CF.lumen. I may also remove some bloatware apps in a future version.
[X 2014 Android Development] gunit25:
It's like devs know when I take the jump and release an update within a few hours ;).

Are there any issues if I go from an older version to a new? Do I need to delete ../arm and ../profiles folders?
[X 2014 Android Development] ClydeDroid:
I would do it, just to be safe. Otherwise, there shouldn't be any issues going from version to version.

EDIT: According to this post, adding the extra hosts source screws up MMS. So I would recommend reverting in AdAway, using only default sources, reboot, reapply, and reboot. That should fix any MMS issues!
[X 2014 Android Development] ClydeDroid:
Alright, I'm having some issues getting CF.lumen to work. After digging through the apk, I've figured out that there are four system files needed: libcflumen.so, surfaceflinger, surfaceflinger_cflumen, and surfaceflinger_shell. The first file is in the apk, however the other three are not. If anybody has a device that already has CF.lumen installed, perhaps you can pull these files from /system/lib and shoot them my way? [MENTION=5983610]JulesJam[/MENTION] mentioned having a Nexus 7 earlier on I think, maybe that could work? Hopefully there wouldn't be any cross-device compatibility issues.
[X 2014 Android Development] Haxxa:
Thanks for the Rom everything is working nicely :D Quick Question on the Air Audio addition if we don't use Air Audio, the added libs won't do anything right? It just means its an added feature nothing which could cause slow downs, etc. Right?
[X 2014 Android Development] ClydeDroid:
I'm pretty sure, yes. I only had to add one file for AirAudio, and it was a small one. Shouldn't affect normal use at all :)
[X 2014 Android Development] JulesJam:
I have a rooted XT1060 with CF Lumen on it. What files do you need?
[X 2014 Android Development] ClydeDroid:
I would need surfaceflinger, surfaceflinger_cflumen, and surfaceflinger_shell from /system/bin/. However, I'm wary of trying this because according to this guy it can cause a bootloop. Another idea I've had is to prevent CF.lumen from rebooting the device after normal installation in order to pull the files before they're erased, but I'm not sure how I would go about doing that.