• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Boost Mobile] Official CyanogenMod 11 Nightlies!

sdcard1 invalid path on ES and other apps I use. In ES I can browse to extSdCard in order to access my files but some apps dont allow this. Could I mount extSdCard to sdcard1 somehow?
 
sdcard1 invalid path on ES and other apps I use. In ES I can browse to extSdCard in order to access my files but some apps dont allow this. Could I mount extSdCard to sdcard1 somehow?

I read somewhere that the SELinux status can affect the ability to fully use the SD card if the status is set to Enforcing instead of Permissive. Don't know if changing the status will allow sdcard1 to become a valid pathway, I have just been using extSDCard myself with no problems.
 
So 12/12/2013 nightly for CM 11 is already on Android build 4.4.2; for those who haven't been following that, the release of KitKat 4.4 was followed rather quickly by 4.4.1, and the first official Cyanogen build on 12/7/2013 was based on that code source. Four days later, Google updated Android again, to 4.4.2, these rapid upgrades have been primarily aimed at keeping the users of the Nexus line happy, as they have had camera issues, among other things, that probably shouldn't be happening on such a new device as the Nexus 5. First world problems I know, God forbid your phone not be able to take pictures using all the MP's available or rated for the device! Anyway, just downloaded the latest nightly, am going to dirty flash first to see if it is compatible or if GApps decides to act up. I know there are already GApps packages being put out that are supposed to be compatible with 4.4.1 and 4.4.2, so will let you all know what the final verdict is; Paranoid Android for sure did just update their GApps package, and that is the one I have been using. A word of warning about their version however, is that they include the Google browser, and it will replace the stock AOSP browser included in the ROM, so if you have a "stock" browser preference, Banks GApps (usually available on Goo.im) is probably going to work better in terms of leaving more items intact and just installing what you need from the Google side. Normally I recommend debloating GApps packages yourself, this is what I usually do, but I am pretty sure Google has linked several .apks including the browser in order to make the whole "Google experience" function properly, so probably not a good idea to just remove the launcher from the PA GApps as it will possibly make something else misbehave.

Anybody who needs links please let me know!
 
Awesome news!! looking forward to the verdict as I would like to try this new nightly. I would like a link please and thanks you :D
 
Awesome news!! looking forward to the verdict as I would like to try this new nightly. I would like a link please and thanks you :D

Not a problem, coming shortly after I make some coffee and get this bad boy modified and installed. New PA GApps were actually about 100 mB larger than the actual ROM file by the way, but I downloaded the full version and not the scaled down versions offered by PA. I can also upload my personal modified copy of the ROM itself like I did with the first official nightly if anyone wants it.
 
Sure I wouldn't mind trying it :D You just debloat your own right?

Yes to both the ROM and the GApps packages, as well as obviously modifying the updater-script in the ROM so that it will flash properly. Even though I gave the warning about modifying the GApps package in terms of not removing the launcher, I still plan to go in and remove GMail (don't use it on my phone because it is a resource hog/battery killer), Currents, Magazines, essentially all the Google apps which should just be Play Store items for those who want them. Paranoid Android says all that stuff is in their full packages because it puts the apps into /system and not /user, so it is just a matter of which partitions you have room in ultimately (they are saving /user file space by putting apps which would download from Play Store to that partition into /system instead). See my OP for the things I always remove from the ROM file, same info is also listed in my stickied tutorial on the VM side of the forums.
 
As a quick side note, I think TRIM must be working better in 4.4.x, and here's why I think that: I use a program called SD Maid to clean up a lot of the "garbage" that accumulates in the system due to everyday app usage, basically it's a way to do intentionally the things TRIM is designed to do in the background. I am finding that the amount of space SD Maid finds that needs clean up is much less on 4.4.x than it has been on any build previous. This could just be a placebo or in my mind only, but that is my suspicion. For those that don't know what TRIM is, in a nutshell, when apps interact with the system, there are all these little memory pathways that are created, which remain in place even if the app is eventually deleted. Think of it kind of like a spider web that is constantly being built. Over time, this slows down the system and causes noticeable lag. TRIM is supposed to clean up unnecessary file directories and pathways in the background to prevent this lag, it is an "official" Google feature introduced in 4.3. Granted, this is definitely not the "technical" explanation, not by a long shot, but it should sum things up for everyday users (this includes me, I usually need things laid out in plain English, I definitely am no developer nor do I play one on TV). I will also say that my 3G connections even seem quicker or more responsive on 4.4 than they did on 4.3.x; again, probably just a placebo, since I "know" in my mind that I am running the "latest and greatest" but still I like it!
 
That may very well be the case lol. I suffer from the same Placebo effect from time to time lol. I use Clean Master is SD Maid a similar program?
 
That may very well be the case lol. I suffer from the same Placebo effect from time to time lol. I use Clean Master is SD Maid a similar program?

Pretty sure they perform the same function. I think a lot of people, myself included, have app preferences based on what they first stumbled across. For example, I swear by ES File Explorer, but Astro, Root Explorer and several others all do the same thing, I just have been using ES since I first rooted several devices ago and realized I needed a valid file explorer option. I think a lot of it is just the need for a familiar user interface, at least in my case! Don't get me wrong though, I am always open to app suggestions, that is one of the awesome things about a community like this is that so many users have tried so many different things and are willing to share their experiences.
 
Oh I agree absolutely!! Our app combination preferences are as unique as we are. I love doing all this and learning from others as well as lending my advice or experiences in hopes of helping others as others have helped me.
 
As I am in the process of debloating the latest PA GApps packages, I wanted to reiterate why I would not recommend messing with the browser, at least on the front end. I use Nova anyways, so will make that my default once installed. Anyway, since PA has set up their GApps to force the Google launcher and Google Chrome as the new defaults, overwriting the AOSP versions (they were doing this with Google Keyboard as well but I don't know if they still are) probably involves some part of the overall program which might go sideways during the flash if it can't find those files. Plus, as stated before, I am pretty sure Google launcher is tied into at least a couple of other .apks in order to complete the "Google experience" (like being able to launch Google Now with a voice command from the home screen). It would certainly suck to flash this and the new ROM from scratch (I'm going to dirty flash first) and have the flash "succeed" but with no launcher in place, or with multiple other things going south once the ROM boots. As always, better safe than sorry!
 
Have both my fingers and toes crossed lol. In the event that Others want to try this using the default PA apps, Are you using pa_gapps-stock-4.4.2-20131212-signed as the base for your debloating of the gapps?

Yes. I also went into the build.prop and set SELinux to "Permissive" instead of "Enforcing" on the CM 11 ROM, I am tired of resetting that every time I reboot. Didn't debloat the GApps as much as I normally do, but definitely got rid of the apps I never use. Usually I get rid of stuff I might use but seldom, but this time I left those in just for grins.
 
Good deal. I posted that in the event that anyone else reading this post would have the option to use the full gapps if they so desired. Really excited about trying your version of this rom though :P
 
All right, all is well with a dirty flash and installation of newest PA GApps! Don't worry if initial boot hangs after a few seconds, it will restart itself and boot just fine. This has actually happened to me about half the time on CM 11 anyways when rebooting back from recovery. Standard disclaimer from OP applies about bricked phones, personal responsibility, etc., etc. Also, I in no way claim to be directly responsible for the original ROM or GApps, these are just the versions I modified for personal use after downloading. All credit goes to CyanogenMod Team and Paranoid Android. Modification of build.prop to set SELinux to permissive did not stick or else I need to modify another line I don't know about, so for now changing from enforcing to permissive requires manual intervention. Good luck, happy flashing!

Modified CM 11 Nightly from 12/12/2013:

https://www.dropbox.com/s/lsqyunric96bqo7/Official%20CM%2011%20Nightly%2020131212%20Android%204.4.2%20Modified.zip

Modified PA GApps (Full package) from 12/12/2013:

https://www.dropbox.com/s/29430annphsl50p/PA%20GApps%20Full%2020131212%204.4.2%20Modified.zip

Don't forget, appropriate APN fixes (specific to Boost or VM, depending) are still necessary.
 
I was curious as to what the change from enforcing to permissive actually does and how do we exactly go about doing it?
 
I was curious as to what the change from enforcing to permissive actually does and how do we exactly go about doing it?

"Enforcing" causes havoc with some root apps, and is the standard setting on 4.4.x; before, on 4.3.x, it was set to "Permissive" and didn't cause any issues. I can't really explain it more than that, except that it is like a mini-me version of Knox on the Google side (without the serious side effects). To disable, I like to use Terminal Emulator, when possible I am a "hands-on" type of guy, but there is also an app available which will do it called SELinux Mode. Haven't tried it yet but heard it works well and is user friendly. Anyway, in Terminal Emulator, type "su" (no quotes) in order to gain Superuser/root access, the $ will be replaced by a # sign to start the next line, then type (again without quotes) "setenforce 0" (that is a zero not the letter O), and then be sure to close Terminal Emulator entirely or else it will run in the background and eat battery. To check your status, go to Settings/About Phone and scroll to the bottom, there is a line which will show your current SELinux status. Every time you boot, this will be reset to "Enforcing" because it is part of the build.prop, this is what I am trying to figure out how to modify. I found the line I was sure I needed, but there might be another line or two that goes with it as well. Any input is welcome on that front.
 
Cool thanks for the brief explanation. I Am wondering where he messaging app is? It isnt in the original file from Cyanogen either :/ I see it in priv-app but it doesn't show up in the phone
 
Cool thanks for the brief explanation. I Am wondering where he messaging app is? It isnt in the original file from Cyanogen either :/ I see it in priv-app but it doesn't show up in the phone

Looks like Hangouts replaced it as well by default. Been giving it a try just for grins, will use it for the next day or two just to give it a fair shake. By the way, dirty flash, for the first time ever, left my apn settings intact, so didn't need to flash the fix we use on VM.

Huge thanks to wetbiker7 for letting me test MMS on Hangouts!
 
Back
Top Bottom