-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root [5.1.1][UNOFFICIAL] Paranoid Android 5.1 [12.30.2015]
- Thread starter Seraph08
- Start date
Seraph08
Android Expert
Seraph08
Android Expert
DaKillaWilla
Well-Known Member
Giving this a shot for the day, seems very smooth and stable. Off to work.
mvaness
Android Enthusiast
No matter what, I always seem to gravitate back to this rom. It's clean, elegant, and buttery smooth.
So after day one, seems great. Although I did have a missed call and when I got to the phone there was a popup that said com.android.something stopped working and shut down or something along those lines. I was in a hurry so I just clicked it away and went on with the day. Everything seemed to run just fine with it for the rest of the day so I don't know what the issue was with the popup. Very smooth, think I'll stick with it a while.
Seraph08
Android Expert
Thank you very much. This ROM is my baby. And I'm happy to hear it is being enjoyed.
Just wait for L's source code to drop, that when its going to get funky.
Seraph08
Android Expert
There was an issue with in the in call UI sources from cyanogen that trickled all the way down to all of us building on their sources. We're all aware of the issue and its being sorted out.
I'm running a new build as I type this, it will be posted in the morning.
Seraph08
Android Expert
Once again for anyone that did not see the intructions in the OP
Flash in this order
ROM
GAPPS
Boot screen fix
MMS Fix
SuperSU zip
You should have a AOSPA Rom with full support of everything. Any FCs coming up, we do apologize from AOSPA, currently working our balls off getting L ready so when the source code is released, porting it over to our device Moto G (falcon) goes as smooth as possible. There is nothing we want more then the day after L gets released, we can port it at that moment for all of our supported devices.
Once again WE DO APOLOGIZE integrating L is going to cause some issues, but these issues should be across the board ROM wise, all things built off of CM will have these issues for the time being, new sources to configure is NO EASY TASK. Especially when integrating the native features that will always be built into the ROM with no extra tools to provide them [ie Hover, Pie, Peek].
Me personally, once I started building this ROM I went out and bought a new machine. This computer is incredible (with the previous machine my builds were taking over 24 hours each, with the new one they take 4-5). And it was a necessary purchase, not only to continue this hobby, but my entire college schedule is 100% focused on Android. I am doing a special project (think research paper and a very long and hard final project)along with my roommate. He is an incredible programmer. While I am not that great at writing single programs, I have become a certified Linux Admin, and I can build like a mofo now. I plan to feed my future children with these skills, thats the level of my dedication to this. And in the progress its only going to get better.
Our final project will be a new custom ROM we have built with our own sources, my roommate Michael and I are right now brain storming the few apps we will be creating, and I can promise, the ideas we are running with will be like nothing you have ever seen before.
Flash in this order
ROM
GAPPS
Boot screen fix
MMS Fix
SuperSU zip
You should have a AOSPA Rom with full support of everything. Any FCs coming up, we do apologize from AOSPA, currently working our balls off getting L ready so when the source code is released, porting it over to our device Moto G (falcon) goes as smooth as possible. There is nothing we want more then the day after L gets released, we can port it at that moment for all of our supported devices.
Once again WE DO APOLOGIZE integrating L is going to cause some issues, but these issues should be across the board ROM wise, all things built off of CM will have these issues for the time being, new sources to configure is NO EASY TASK. Especially when integrating the native features that will always be built into the ROM with no extra tools to provide them [ie Hover, Pie, Peek].
Me personally, once I started building this ROM I went out and bought a new machine. This computer is incredible (with the previous machine my builds were taking over 24 hours each, with the new one they take 4-5). And it was a necessary purchase, not only to continue this hobby, but my entire college schedule is 100% focused on Android. I am doing a special project (think research paper and a very long and hard final project)along with my roommate. He is an incredible programmer. While I am not that great at writing single programs, I have become a certified Linux Admin, and I can build like a mofo now. I plan to feed my future children with these skills, thats the level of my dedication to this. And in the progress its only going to get better.
Our final project will be a new custom ROM we have built with our own sources, my roommate Michael and I are right now brain storming the few apps we will be creating, and I can promise, the ideas we are running with will be like nothing you have ever seen before.
Seraph08
Android Expert
And lastly, the lead designer for AOSPA has put out a "Calling all designers".
If you cannot translate that, it means the old AOSPA is more then likely, on its way home.
And I would also like to say I apologize deeply for the amount I check in personally to handle some of these issues. I have an insanely busy schedule. And I am supporting 3 different distributions alone (I also host everything myself). I have a team of a few guys from on here who test my builds immediately when they are released. I am typically aware of any issues the moment they arise. And attack them ASAP of me being aware of them. Luckily in here we have great guys, like SuperR who can help. If anyone here is to have a true issue, please PM me. They will get to me quicker then me checking in here.
If you cannot translate that, it means the old AOSPA is more then likely, on its way home.
And I would also like to say I apologize deeply for the amount I check in personally to handle some of these issues. I have an insanely busy schedule. And I am supporting 3 different distributions alone (I also host everything myself). I have a team of a few guys from on here who test my builds immediately when they are released. I am typically aware of any issues the moment they arise. And attack them ASAP of me being aware of them. Luckily in here we have great guys, like SuperR who can help. If anyone here is to have a true issue, please PM me. They will get to me quicker then me checking in here.
mvaness
Android Enthusiast
I get that too. From my understanding, it is common with CM based roms (anyone, please correct me if I am wrong).
But I can't seem to get hangouts to send mms. Followed directions to a tee, but fiance is not receiving sms or mms. I can send messages to myself (to test) and that works.
I use the stock gapps.
Is there some setting I am missing somewhere? I'm on Boost.
Seraph08
Android Expert
I am not sure about why that wouldnt be working. I haven't heard this problem before. The MMS fix is not my work, so I cannot be any help on that.
I just looked at what the MMS fix in your OP does, and it does not change the apns, just the build.prop. Give mine a go and see if it works. If it does you are welcome to link it
falcon_Boost_Service_2.zip