Related
Got bored again, this time I merged my device tree and fixes into CM7 Gingerbread ROM is built from the newest CM7 source code, and has been merged with the majority of my device specific fixes from previous ROMs. I love open source, so of course source code is available for everything, here (ROM), here (kernel), and here (initramfs). If you would like to follow the changes I make, check my github rss feed here.
*** WORKING ***
RIL (calls/sms/3g data)
WiFi
GPS
sdcard and USB mass storage
rotation and proximity sensors
screen on/off animation
haptic feedback
*** NOT WORKING ***
Camera/Camcorder
MMS
BT
most video codecs - Youtube playback (LQ & HQ) is broken for example - youtube does work from a browser if you use a desktop user-agent
Voodoo lagfix conversions
There are still plenty of bugs! and there likely will be until we have a true GB leak or official release to work off of.
PLEASE READ
It is considerably difficult for me to stumble upon every issue out there, and even more difficult to narrow these issues down, let alone fix them. That said, PLEASE do not clutter this thread with "thank you" or "X/Y/Z doesn't work" or "I'd love to flash this if..." type posts. I APPRECIATE THE THANKS AND THE FEEDBACK!!! Don't get me wrong. But these posts are not at all helpful in moving this ROM forward, and simply add more clutter to the forum. If you make such a post, don't expect a response.
If you experience a bug, PLEASE GET LOGS! I can't fix something simply by knowing that it does not work. A bug report without significant details is a useless post, it just is what it is. Logs help identify the code affected, and thereby help facilitate the fixes that we all love. PLEASE share your issues if you can provide helpful data in fixing them
THANKS FOR READING
The ROM package currently includes the base CM7 ROM, and a compatible kernel. Flash gapps from the package linked below. DO NOT FLASH ANY OTHER GAPPS OR KERNEL PACKAGES! The ROM package uses edify scripting, so it is flashable with any iteration of ClockworkMod recovery.
ALSO: devs and noobs alike please take notice : this ROM uses ClockworkMod recovery 3.x. I will no longer be supporting older recoveries!
Much thanks to the EpicCM and teamhacksung folks for code and ideas, and of course props to the CM team for all they do, it's their ROM after all.
If you appreciate the time and effort I have put into this ROM please click the "Thanks" or "Donate" buttons. Either one is fine by me
***** Update 4/26 - ALPHA2 *****
fixed USB mass storage
fixed haptic feedback
fixed TiBu 'whoami' bug
update to 3.x ClockworkMod recovery
sync'd with latest CM code
updated to latest Market
stubbed the camera (yes, I know it takes pictures of nothing but a green android )
** package still includes gapps and kernel **
** changed to new kernel that can be used with BOTH rfs AND ext4 - but it does not include the Voodoo lagfix code, so no conversions! **
** Make sure to wipe data even if coming from the previous alpha! **
***** Update 5/11 - ALPHA3 *****
updated to latest CM7 code (7.0.3)
enabled recent CM code to prevent "ring only once" bug (lightly tested)
made one of my sms hacks "optional" for easy editing by the mesmerize/showcase users (simply remove "ro.sms.padding=1" from build.prop to fix sms on these devices)
fixed some memory settings in kernel - should fix the lag experienced when using previous versions
added other tweaks to kernel for speed improvement (increased sdcard readahead cache/lowmemkiller/etc)
included punk-kaos' recent camera changes into kernel (cam not working, but getting there)
unstubbed camera (no more pics of a green android )
cleaned up my build tree a bit for a smaller download for people building themselves
removed gapps from ROM package, download from link below (kernel still included in ROM package)
ROM package will no longer flash a recovery
switched to bmlwrite for flashing kernel (screen will no longer wig out during kernel flashes)
Instructions:
flash with Clockwordmod recovery
flash ROM first then flash gapps package
WIPE DATA! if coming from ANY other ROM
Don't worry about disabling lagfix or any of that nonsense, ROM will work whether you are using ext4 or rfs
ALPHA3
http://www.mediafire.com/?ziawa7ot8dhdq4k
GAPPS
http://www.mediafire.com/?ogylu5w024148lt
Enjoy and remember: If your phone breaks after flashing, YOU broke it! Not ME!
You work pretty quickly for someone who gets bored.
This may peg my level of knowledge but here goes. . .What logs would be most beneficial? Assuming alogcat is the standard method, there are a lot of different options of logs in there. Any specific ones that would be the most helpful in tracking down a bug?
Not trying to clutter, hopefully avoiding more in the future
dw77x said:
This may peg my level of knowledge but here goes. . .What logs would be most beneficial? Assuming alogcat is the standard method, there are a lot of different options of logs in there. Any specific ones that would be the most helpful in tracking down a bug?
Not trying to clutter, hopefully avoiding more in the future
Click to expand...
Click to collapse
any random bugs can usually be picked up from the main log. anything having to do with the radio (call issues/sms issues/etc) need the radio specific log
I'm not familiar with alogcat (market app right?), but the logs can be dumped using adb from a pc. ex:
adb logcat > logcat.txt
will dump the main log
adb logcat -b radio > radio.txt
will dump the radio log
thank you for your concern
Hey JT, I was talking to you on twitter today (@ScottColeBCS). I sent my email addy, I don't know if you got it. Let me know if you figure out a way for me to do that for you. Thanks Bro.
EDIT: Nevermind bro. I'm stupid. I just checked my email and saw that you sent the info I needed. Be expecting it.
I need to clean my keyboard...great job jt!!
Sent from my SCH-I500 using XDA Premium App
Thank you JT. You are a boon to this community. Have a beer on me.
Thanks Jt....good stuff
Sent from my SCH-I500 using Tapatalk
Sweet. So what are the chances this will bebe compatible with the Mesmerize eventually? I assume it is not currently.
Sent from my MIUI SCH-i500
What's the difference between this and the one you released on Twitter last night?
Hey JT, I know there are many thread junkies (like myself) who are constantly checking for bug fixes and updates. I also read in the OP that you said there will plenty of bugs still until we get an official leak. Does this mean that with what you have available to you at the moment the functionality will remain as is, or are you still plugging away at some of these issues? I ask this simply to see if we should be checking for updates. Not complaining one bit! I love this rom so far. Thanks a ton!!
running great
Sent from my SCH-I500 using XDA App
kidserious said:
Hey JT, I know there are many thread junkies (like myself) who are constantly checking for bug fixes and updates. I also read in the OP that you said there will plenty of bugs still until we get an official leak. Does this mean that with what you have available to you at the moment the functionality will remain as is, or are you still plugging away at some of these issues? I ask this simply to see if we should be checking for updates. Not complaining one bit! I love this rom so far. Thanks a ton!!
Click to expand...
Click to collapse
I will still make do with what we have. As far as what that entails, who knows. One thing I'm relatively sure of is the fate of the camera. It's likely to remain non-functional until we have a GB base to work with.
You are the man, man! Thank you so much that you do for us. You guys are awesome! Thank you again!
Sent from my SCH-I500 using XDA Premium App
jt1134 said:
I will still make do with what we have. As far as what that entails, who knows. One thing I'm relatively sure of is the fate of the camera. It's likely to remain non-functional until we have a GB base to work with.
Click to expand...
Click to collapse
Ok, Well I will take that as there is a definite possibility you will be able to fix some of the non-camera bugs. It lets me know that fixes for these issues are not out of the realm of possibility with current sources. JT, your new name is Mr. Fascinate (with a thunderbolt) Lol. Keep doing what you do brother, you're making a lot of people happy.
Did Punk.kaos stop working on CM7 too? If not, why don't you guy help each other?
What will be different between This rom and the Kaoscinate?
Sent from my SCH-I500 using XDA App
deaffob said:
Did Punk.kaos stop working on CM7 too? If not, why don't you guy help each other?
Click to expand...
Click to collapse
Apparently kaos has been MIA for quite a while now.
kallell said:
Apparently kaos has been MIA for quite a while now.
Click to expand...
Click to collapse
maybe he just likes the thunderbolt people better
Works damn good for an alpha.
I decided to make my first custom rom. The main difference over klin1344's klassic is the fact that we can customize what we want with the aroma installer. As of now, there's no customised interface (and there will not be. Consider this like WT Ho's rom for the 5.0).
I stop working on it because I want to try something other than stock. Also thanks for your consideration for this rom. (I will continue the maintenance of it though)
Features:
- Stock 2.3.6 XXKPQ
- Rooted
- Busybox
- Deodexed
- Zipaligned
- Aroma installer: An interactive installer
- Multiple bootanimations.
- Choice between TW 3.0, TW 4.5, Go launcher EX, Xperia S launcher
- Possibility to install DSP manager and voodoo app (for sound enchance)
- Features the CWM 5.0.2.7 (Intl Only. Kernel based from steve's 3.0) (V.1.0)
- US users will recieve the latest klin's R2 custom kernel* (V.1.0).
- Intl and US compatibility in a single zip. (v.2.0)
- SuperSU (v.3.0)
Changelog:
Code:
[B]V.3.0 (Vita) FINAL [/B]
- Deodexed and Zipaligned
- SuperSU is used instead of SuperUser
- Updated Google Play Store, Maps and Youtube app (Can play 720p) (It's real this time)
- Possibility to add Antutu Cpu Master Free (For Overclock)
[B]V.2.0 (Radiance)[/B]
- Name changed only to Renaissance
- Possibility to chose the device type (Thanks to dark_valor's Terra Silent)
- New Honeycomb bootanimation
- Possibility to add terminal to the rom
[B]v.1.0 (Etincelle)[/B]:
- Initial Release.
Download:
1.0
Intl: Intl Renaissance 1.0 Download
US: US Renaissance 1.0 Download
2.0: Renaissance 2.0 Download
3.0: Renaissance 3.0 Download
If you want there's the Xperia S Wallpapers: Xperia S Wallpapers Download
If there's a problem with antutu, install the apk here: Cpu Master Apk Download
If there's a problem with terminal reinstall it.
Instructions:
1. Boot into Cwm
2. Backup
3. Wipe data (BEFORE IT IS MANDATORY)
4. Run renaissance-device.zip
5. Follow the instructions.
6. Reboot
7. Enjoy!
If you do like please hit thanks button. If you have problem with installation, Send me .log file in aroma. If it's problem with the rom please let me know.
Thanks to:
amarullz: for Aroma installer
Klin1344, SteveS and stratosk for the kernel related things.
WT Ho for his base for aroma installer. (and help too )
GO Dev Team , Fr4gg0r and ra3al for their launcher
Dark_balor for his kernel (terra silent)
Jackpal for the terminal emulator
Antutu for the CPU Master
As this is the last version, If you want to use something in the rom (porting) ask me first.(Mostly for Aroma)
These are the possible implementations (suggestions)
- Deodex
- Performance tweaks
- More customisation options
- Better compatibility with apps (Like deviceID hack)
reserved again
screenshots please?
EcHoFiiVe said:
screenshots please?
Click to expand...
Click to collapse
Oh sorry about that. I will put them tomowrrow. (that depends which screenshots you want?)
Is ext4 enabled for data and dbdata? From stock its stuck at rfs.
Wheatly said:
Is ext4 enabled for data and dbdata? From stock its stuck at rfs.
Click to expand...
Click to collapse
Well I didin't enable ext4 so data and dbdata will be stuck at rfs. Sorry about that.
Does the CWM 5 in the kernel I gave you work well? Because when I gave it to you there seemed to be a lot of errors... But if it does, I'll probably apply those changes back to my kernel again and update to cwm 5 because it allows easier converting to ext4. Also, did stratosk give you permission because I used his cwm recovery files from his sources. (just making sure, so he doesn't come and flame me for porting cwm5 from his sources without permission)
Sent using Tapatalk
When you sent it to me back then it wasn't working well. So I fixed the errors on it (I did send a PM for you for testing). I do got permission from stratosk (that's why I put him in the thanks section.) I think I have the US kernel in my mediafire account. I'll upload it so both devices will have justice.
zaclimon said:
When you sent it to me back then it wasn't working well. So I fixed the errors on it (I did send a PM for you for testing). I do got permission from stratosk (that's why I put him in the thanks section.) I think I have the US kernel in my mediafire account. I'll upload it so everyone will have justice.
Click to expand...
Click to collapse
Ok thanks. But how exactly did you fix it? I didn't flash the kernel you gave me but where are your sources? (the Linux kernel is GPL licensed, so it's mandatory to have a source )
Sent using Tapatalk
Never mind for now I will just extract the initrd from your kernel and use git to track the changes from the one I sent to you.
But really, you need to provide a source if you release a kernel, as per the GPL license.
Sent using Tapatalk
From which release of the Klin rom you based yours ?
If it's from the R5, did you had the font that were missing ?
Is it supercharged ?
For the kernel I'm also curious to know what are the change you have done
Dark_Balor said:
From which release of the Klin rom you based yours ?
If it's from the R5, did you had the font that were missing ?
Is it supercharged ?
For the kernel I'm also curious to know what are the change you have done
Click to expand...
Click to collapse
He based it off stock rom. Tomorrow I'll figure out how he fixed cwm 5.0.2.7 from his initramfs.
Sent using Tapatalk
klin1344 said:
Never mind for now I will just extract the initrd from your kernel and use git to track the changes from the one I sent to you.
But really, you need to provide a source if you release a kernel, as per the GPL license.
Sent using Tapatalk
Click to expand...
Click to collapse
I had the source before but my ubuntu 12.04 bugged with my old computer (nvidia problem) so I downloaded 11.04 but I forgot to do a backup.
zaclimon said:
I had the source before but my ubuntu 12.04 bugged with my old computer (nvidia problem) so I downloaded 11.04 but I forgot to do a backup.
Click to expand...
Click to collapse
If you can extract the initramfs then that's basically your source because cwm is only an initramfs change.
But again, how did you do it? Surely you remember what changes you did? It sounds like a minor tweak because you sent me your kernel a matter of hours after I sent you mine.
Btw, you know that you can downgrade ubuntu without losing data right? Ndiswrapper wasn't working on 12.04 so I put my 11.04 disc in and was able to install without losing all my personal files.
Sent using Tapatalk
klin1344 said:
If you can extract the initramfs then that's basically your source because cwm is only an initramfs change.
But again, how did you do it? Surely you remember what changes you did? It sounds like a minor tweak because you sent me your kernel a matter of hours after I sent you mine.
Btw, you know that you can downgrade ubuntu without losing data right? Ndiswrapper wasn't working on 12.04 so I put my 11.04 disc in and was able to install without losing all my personal files.
Sent using Tapatalk
Click to expand...
Click to collapse
I made some changes to the init.rc and lpm.rc I think.
Screenshots like Homescreen, App drawer, Notification place thingy, and settings.
EcHoFiiVe said:
Screenshots like Homescreen, App drawer, Notification place thingy, and settings.
Click to expand...
Click to collapse
Because it is a stock rom (with multiple apps) I won't put screenshots. Once 2.0 will be released (UI modifications) I will put them. You can backup and try it?
zaclimon said:
When you sent it to me back then it wasn't working well. So I fixed the errors on it (I did send a PM for you for testing). I do got permission from stratosk (that's why I put him in the thanks section.) I think I have the US kernel in my mediafire account. I'll upload it so both devices will have justice.
Click to expand...
Click to collapse
zaclimon said:
I made some changes to the init.rc and lpm.rc I think.
Click to expand...
Click to collapse
Ok, I just used git to check your initramfs for your INTL kernel, and lpm.rc is exactly the same as my source, and in init.rc it's also the exact same thing as my source for the CWM 5.0.2.7 beta (not on github anymore), except that you forgot a '/' in enabling bootanimation support.
So I'm confused. When I gave you my kernel, there seemed to be many errors because I was screwing with my partition filesystems, and also got a lot of "md5 mismatches" when trying to convert, so I decided to stop and work on other things. You got it working, and you claimed that you "fixed the errors in init.rc and lpm.rc" without proof with a proper source when you CHANGED NOTHING AT ALL. You probably just got lucky with CWM restoring and no md5 mismatches like I had. So you're releasing a kernel with a CWM 5 port that I completely did, and claiming that YOU fixed most of the errors and got it working when proof shows that all you did was download my source before I deleted it and simply compiled them with SteveS's one click compiling script.
And since you don't have a Github account or a source of any sort, you thought you could get away with tricking everybody that you "fixed the CWM errors", when the work was originally done by me. You changed nothing at all. It was not my intention to flame you, but seriously, I am disapointed . I'm really discouraged and very tempted to just take down all my work for the Galaxy Player and just keep all the development to myself. Maybe that's why precious devs keep leaving XDA because people just use someone else's work and package it as their own. Learn to give proper credit to other people, and if you really didn't make something, don't act or say that you did.
Ok, I'm done. Really needed to vent.
klin1344 said:
Ok, I just used git to check your initramfs for your INTL kernel, and lpm.rc is exactly the same as my source, and in init.rc it's also the exact same thing as my source for the CWM 5.0.2.7 beta (not on github anymore), except that you forgot a '/' in enabling bootanimation support.
So I'm confused. When I gave you my kernel, there seemed to be many errors because I was screwing with my partition filesystems, and also got a lot of "md5 mismatches" when trying to convert, so I decided to stop and work on other things. You got it working, and you claimed that you "fixed the errors in init.rc and lpm.rc" without proof with a proper source when you CHANGED NOTHING AT ALL. You probably just got lucky with CWM restoring and no md5 mismatches like I had. So you're releasing a kernel with a CWM 5 port that I completely did, and claiming that YOU fixed most of the errors and got it working when proof shows that all you did was download my source before I deleted it and simply compiled them with SteveS's one click compiling script.
And since you don't have a Github account or a source of any sort, you thought you could get away with tricking everybody that you "fixed the CWM errors", when the work was originally done by me. You changed nothing at all. It was not my intention to flame you, but seriously, I am disapointed . Maybe that's why precious devs keep leaving XDA because people just use someone else's work and package it as their own. Learn to give proper credit to other people, and if you really didn't make something, don't act or say that you did.
Ok, I'm done. Really needed to vent.
Click to expand...
Click to collapse
ok don't go blaming me BECAUSE IT GOT ERRORS when YOU sent it to me. I corrected some errors but I can't remember which ones is it. I can't get lucky if EVERY of my backups works(Because I got errors for md5 mismatch as well too). It is sure that your init files are the same because I used some of the text you used when you were building YOUR R1 kernel. (so basically I used some of your sources) but you were always complaining about ext4 not working so you gave up on CWMR5.0. and when I said I've fixed them you didin't tested it. DON'T GO COMPLAINING IF YOU DIDIN'T EVEN TESTED IT. (also check all the init files to be sure and also check the thanks it is `kernel related things`.) -___-
EDIT: If you want all the credits. You can have them. I should have said that you made all the changes but the problem was that you gave up on CWMR5.0 so I was like (The kernel works now but I won't release it because you already have your custom kernel with CWMR3.)
It is my pleasure to introduce to you all my first ever ROM made from source. I am just beginning and learning to be a developer. Still need to learn how to use git so I can add features to this ROM. For now it is pure stock aosp. I am not sure if it boots as I am at work now and did not have time to test.
Gapps are not included and you must flash SuperSU to get root. I will do my best to add root soon.
Please let me know how it runs if you are brave enough to test this.
Thanks!
Features:
Pure AOSP...for now
Stock kernel...also for now
Install Instructions:
I recommend TWRP and a clean install. No dirty.
1. Wipe System, Data, Cache, and Dalvick Cache
1.5. If needed, unmount System
2. Flash ROM
3. Flash GAPPS
4. Flash SuperSU for root
Enjoy!
Links:
ROM: KAOS ROM v1.1
GAPPS: BaNkS GAPPS
SuperSU: SuperSU v2.00
Recommended Kernels:
(018) Nexus 5 (3.4+ Hybrid/UV/OC/FauxSound/Intelliplug/active) [06-04-2014]]
[GPL] [SM 4.10] TheArkenstone [3.4.x][N5]]
Credits:
Google
Rascarlo (for inspiration)
BaNkS
Chainfire
Changelog:
v1.0
Initial Release
v1.1
Build.prop tweaks
Added SuperSU apk (user must still install binaries)
AOSP Stock
To do list:
Built in root
Cherry Picks
Custom kernel
Click to expand...
Click to collapse
Donations:
Donations can be made to me via the "Donate to Me" button under my avatar. Donations are greatly appreciated, but by no means required. Thank you.
First. Awesome!!!!
Sent from my Nexus 5 using Tapatalk
KerryWood34 said:
It is my pleasure to introduce to you all my first ever ROM made from source. I am just beginning and learning to be a developer. Still need to learn how to use fit so I can add features to this ROM. For now it is pure stock aosp. I am not sure if it boots as I am at work now and did not have time to test.
Gapps are not included and you must flash SuperSU to get root. I will do my best to add root soon.
Please let me know how it runs if you are brave enough to test this.
Thanks!
http://www.androidfilehost.com/?w=files&flid=15919
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/google-nexus-5/development/rom-posting-t2548136
Good initiative, but I think rom missing detail, despite being a pure AOSP
Put some detail on the oo man
Although is aosp, its always good to see new development enthusiasts.
Keep up man! Hope you enjoy the experience.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Will update the OP with more details when I get home from work or during my lunch break. Might be a bit busy. I knew I was forgetting something.
Sent from my Nexus 5 using Tapatalk
Can anyone tell me if it flashes and boots OK?
Sent from my Nexus 5 using Tapatalk
I can't seem to get this ROM to boot. I did not have any build errors. I used the make otapackage -j4 command and everything went smoothly. I go into TWRP and try to flash it and it says Failed. Then I unmount System and try again and it is Successful, but when it restarts it hangs on the Google screen. Anybody got any ideas?
Sounds like you are missing the binaries for the device. They are not in aosp source and need to be added separately during build time.
Sent from my Nexus 5 using Tapatalk
I think you are right @kufikugel I am now following a different guide that shows me how to add the binaries. So I'm going to have everything ready to go by the weekend.
Just wanted to update everybody. I have been working on this ROM still and have been running into never ending fetch error while running repo sync. I am now trying the
Code:
repo sync -f -j4
command in the hopes that it will complete successfully. Once that is done all I have left to do is put in binaries and then build it. Today is my only day off until Tuesday, but I am hoping I can leave stuff running while I go to work and hopefully have a ROM to upload within the next couple of days. It would still be stock AOSP, but like I said before, I am still learning and will continue to do so and improve my ROM along the way. Wish me luck with this repo sync
Good to know!
Sent from my Nexus 5 using XDA Premium 4 mobile app
did you add the vendor files?
flex360 said:
did you add the vendor files?
Click to expand...
Click to collapse
If by vendor files you mean binaries then not yet. I am still waiting for the repo sync to finish.
Are these the files you mean? https://developers.google.com/android/nexus/drivers#hammerheadktu84p
I have downloaded and extracted them. Just waiting for sync to finish to move them into my working directory and start the build.
AHHHHHHH I keep having fetch errors!!!! This is getting really annoying. I am not sure what to do. I am going to try it one more time and then I am going to have to try doing this on a different computer in the house.
IT'S ALIVE!!!!!!!!!! Finally got everything to work. Installed it on my own phone (after making a nandroid of course) and everything seems to work perfectly. I am uploading it now and will post the link in the OP when it has finished.
ROM is up! Finally.
V1.1 is up! Just added some build.prop tweaks and added my ROMs name to it in the About phone page. Link is in OP. Enjoy!
@KerryWood34 its awesome to see you undertake this project and bring us along for the ride. Wish I had the know how..im jealous. I wont be flashing anytime soon..seems I have to have every feature possible in a ROM for me to be happy. But I will definitely keep tabs on your ROM. May want to put up a donate button. Heck I'd donate even tho Im not using your ROM. Kudos and keep it going!!
zulu888 said:
@KerryWood34 its awesome to see you undertake this project and bring us along for the ride. Wish I had the know how..im jealous. I wont be flashing anytime soon..seems I have to have every feature possible in a ROM for me to be happy. But I will definitely keep tabs on your ROM. May want to put up a donate button. Heck I'd donate even tho Im not using your ROM. Kudos and keep it going!!
Click to expand...
Click to collapse
Thank you @zulu888. I really appreciate that. I've always wanted to make my own ROM and finally just said "Let's do this!" lol.
I will be adding features I find creative/useful/necessary to me to this ROM. I was trying to cherry-pick Hover from PA but that wasn't happening just yet so I decided to go with something a bit small for my first cherry-pick and did native battery percentage. It's building now and I will test it when I get home from work.
As far as a donate button, I thought XDA had a built in Donate button, no? I'll have to look into it.
Thank you again. I hope to learn everything I can from the XDA community, especially developers that have been doing this much longer than I. Any help or advice is greatly appreciated.
Thank you for the donation @zulu888. I'm not sure if you want it or not, but here's the confirmation number: 4YX957512U063384U.
Thank you again!
The idea behind this project is to compile a Pure AOSP ROM. The difference is I have been little by little including and testing new changes and fixes added to the AOSP code from Google that has not yet been tagged or added to the release branch and will most likely be added into a future Lollipop update., hence the reason for 5.0.2_Plus. The only change added that was not committed by Google is that the ZIP can be flashed in TWRP without replacing TWRP with the Stock Recovery and that is it.
There is more coming but would like to first verify my testing on what has been done so far. The idea is to stay ahead of the curve with fixes and updates coming down from Google before they are released. As offered in the development Q&A Thread I started with this idea is that anyone who is able is welcome to jump on and help. All and all is just sifting over the AOSP Master branch adding new commits that have not yet been tagged as part of a release branch. Thought of the idea after reading a statement from Google true or not that allot of bug fixes have already or are in the process of being added into ASOP. These commits all come from the master branch developers do not build from and is more of a staging ground for future releases. A few of these commits are less than a week old. Anyhow so Instead of this being my Rom I would like us to just all have the most updated code base to work with so let me know and will give full permission to the Github organization. We wiil just need to set up separate branches for testing to insure our Master branch is stable at all times so it can be used and trusted by all our devs to use in their Roms. I am sure we can gather a team of testing volunteers. Otherwise this is again 100% AOSP code without any modifications outside what has been committed by Google and planned on keeping it this way. Although I am posting like stated above would not like to think this is my Rom but more for the community in general so our Developers have the latest stable code to work with when creating Roms and am not just posting because as Google has proven with Lollipop the more testers the better as we all have different set-ups and use are devices differently but I also wanted to give the project/idea a bit of attention.
A Few Added Update Examples.
https://github.com/Android-AOSP/And...mmit/a05556633ae5a6d1db164597b93f8b6cbbdf2608
https://github.com/Android-AOSP/And...mmit/e6beb1369165f97a4df24a1d1966c41e392c44e7
https://github.com/Android-AOSP/And...mitM/be42994b5a42914071adddfd5d989950e8e47bd9
https://github.com/Android-AOSP/And...mmit/0c89e1b9395093f71cf73508553d5e4058093ec0
https://github.com/Android-AOSP/And...mmit/4c53a7872b1f37ec184801f16d39584ca3b9bcce
https://github.com/Android-AOSP/And...mmit/9d2f14442f2e1d1507dbdc6cc7b9348513a907f9
https://github.com/Android-AOSP/And...mmit/905c6e72ecdc6e170744649b78e8fbb919f71efd
https://github.com/Android-AOSP/And...mmit/1a96e2b079e8007fe965bd30cd02cb191a613510
https://github.com/Android-AOSP/And...mmit/4fcbf285db7f9e20795783b676963d42499dbd64
https://github.com/Android-AOSP/Android-AOSP_bionic/commit/eaf5aa7d22bd2f6b2eae4c81a60950f89e2d7df4
https://github.com/Android-AOSP/And...mmit/74574e8aa5a2de32e10364fd2f495023fff2a267
https://github.com/Android-AOSP/Android-AOSP_build/commit/49657b7a459ee90b3635bef989f8f9728d564068
https://github.com/Android-AOSP/Android-AOSP_build/commit/1df3707a04651966ca17796f321d23ab3ed6ed2e
https://github.com/Android-AOSP/And...mmit/6fe9c73738e9da0192971576d120802d4c094556
https://github.com/Android-AOSP/And...mmit/44c1c3235d29095c4d987d19155c7260d1a33e0f
https://github.com/Android-AOSP/And...mmit/33baf53861712c3f84606a017943e36bdc680b50
https://github.com/Android-AOSP/And...mmit/a975a08cfb30ad6b2994647c0c6f09e2abd20e28
https://github.com/Android-AOSP/external_protobuf/commit/1a96e2b079e8007fe965bd30cd02cb191a613510
https://github.com/Android-AOSP/external_protobuf/commit/4fcbf285db7f9e20795783b676963d42499dbd64
https://github.com/Android-AOSP/frameworks_base/commit/cc50afe3bdcc3adfa0f4121bf461996996e69a3e
https://github.com/Android-AOSP/frameworks_base/commit/1be740dd60f4d95e1f9ac4aac7e4d6148e3b2dd1
https://github.com/Android-AOSP/frameworks_base/commit/1cca2282dc9a3b7ecc08729af201923842ddfc86
https://github.com/Android-AOSP/frameworks_base/commit/7db1192e72b45111556631dba125a635edff3235
https://github.com/Android-AOSP/frameworks_base/commit/b29136581cc3181e59193e0b6448f0c3f5990081
https://github.com/Android-AOSP/build/commit/de655233a4308340fc71490e86fd0f218cc7fec4
https://github.com/Android-AOSP/build/commit/ab6f841841a0930c7e178a949ada39152e24540f
https://github.com/Android-AOSP/hardware_libhardware/commit/9ede7f730bca338cd3ccad8962e253f28ae17976
https://github.com/Android-AOSP/hardware_libhardware/commit/d4f431fec4136f6eeee919ac3190762fba832942
https://github.com/Android-AOSP/hardware_libhardware/commit/898bcd96e3d80e99d9200cceb4af754bae6d5f4a
https://github.com/Android-AOSP/bionic/commit/d90f39af35c1f2a9972198f92e803e3ca73ac910
Downloads
Download Rom
aosp_hammerhead-ota-5.0.2_plus_r4.zip - 191.35 MB
aosp_hammerhead-ota-5.0.2_plus_r3.zip - 191.35 MB
aosp_hammerhead-ota-5.0.2_plus_r2.zip - 191.34 MB
aosp_hammerhead-ota-5.0.2_plus.zip - 191.34 MB
PA-Gapps
http://forum.xda-developers.com/par...apps-official-to-date-pa-google-apps-t2943900
So far I have been using the "Mini Modular package" for testing without any issues.
Root
Root is optional but recommend SuperSU
http://forum.xda-developers.com/showthread.php?t=1538053
Have had version 2.37 in storage and had been using without issue but updated to 2,40 with last test without any issues. What can I say Im lazy that way so unless having an issue just used what works but figured most would grab the latest so thought it best to give it a test before posting.
Kernel is also %100 stock but including a shameless plug for my Starship Kernel as in testing have worked well together and is the only other Kernel verified though am sure you should not have any problem with other AOSP/Stock Kernels.
Starship Kernel
Starship-lollipop_Kernel-3.4.36_r1.zip - 7.65 MB
Starship Kernel Source
https://github.com/Starship-Android/android_kernel_lge_hammerhead-starship/tree/lollipop
As usual I am not responsible for your device and you are using anything posted in this thread at your own Risk.
Is %100 pure AOSP so no screen shots as am sure you are aware what it looks like at this point.
Change Log 5.0.2_plus_r4
Removed the below commit "Add ip6-localhost to /system/etc/hosts."
https://github.com/android/platform_system_core/commit/25147416bb105914c3cdf8fd65ca7cc20dae0f3e
Looks like a few apps are not fans of having an ip6 entry for localhost. Transparent Weather Widget for example can not find the device location with the enty included.
In looking for the cause of the above issue also reverted.
https://github.com/android/platform_frameworks_base/commit/e4ec09da0b4a31e23f1a19bdd1ea99e0f87cadac
Honestly reverted looking for the cause and did not remember to restore once identifying the cause. Overall is an old commit and dont think will make any difference whatsoever or would have been tagged for use in a past release so not going to bother.
Before the ip6-localhost commit issue had been identified by a user from the Nexus 4 version of this project was testing newer commits. The following few had been in testing at the time and included with the N4 Mako build. They are just a few of what was intended but because updating to r4 for the bug fix these are included in the r4 release.
Add missing <string.h> includes.
https://github.com/Android-AOSP/and...mmit/718568d982f92a93da19bfb8d4ea6dd996913e25
Add missing <string.h> includes.
https://github.com/Android-AOSP/and...mmit/8cb6a047d89479e4f65e0bcfa1642b4891463c04
Fix missing parenthesis.
https://github.com/Android-AOSP/android_aosp_build/commit/49657b7a459ee90b3635bef989f8f9728d564068
Remove superfluous OpenSSL include paths.
https://github.com/Android-AOSP/and...mmit/b9e7a844fc751b9fdda7d452dee361f15815199b
Besides this am about %80 done Starship L Rom and have offered to join a development team so lots going on but plan to keep this up and finish my new Starship L rom. Otherwise looking very much foreword to once again working as part of a team as since I started developing 3 years ago these last few month of Nexus ownership has been the first time I have worked alone and so much more prefer having a team to work with and discuss things with. Love my cat but pretty sure he doesn’t understand what I am talking about and my friends although interested are intimidated believing developing is so over their heads they could never do it .
woot woot
Vero good
Why 2014
Good ROM, but since I am a Sprint user, the update-device.zip fix doesn't seem to work on this ROM, nor does the update profile/prl zip fix, which is important for calls.
Like the idea! Only complaint us that you could hide some text like the github picks and downloads under a spoiler
Edit. Oh and first page woot woot!
Sent from my Nexus 5 using XDA Premium 4 mobile app
The only thing bothers me is the aosp dialer icon, so anti-material, can someone solve that out?
Any bugs?
iamterence said:
Good ROM, but since I am a Sprint user, the update-device.zip fix doesn't seem to work on this ROM, nor does the update profile/prl zip fix, which is important for calls.
Click to expand...
Click to collapse
I am on T-Mobile and looks like neither Google or myself had been thinking about Sprint users. Needs to take a look
chairshot215 said:
I am on T-Mobile and looks like neither Google or myself had been thinking about Sprint users. Needs to take a look
Click to expand...
Click to collapse
Much appreciated, good sir. If nothing can be done, all will still be well. Still appreciate your efforts.
iamterence said:
Much appreciated, good sir. If nothing can be done, all will still be well. Still appreciate your efforts.
Click to expand...
Click to collapse
Think if rooted with bussybox installed fix may then work. Otherwise think would need to either build the fix in before compiling or build non block based and add files into the zip. Took a quick look and the fix I downloaded called on bussybox in the update-script when flashing so installing bussybox may fix the sprint fix, lol. Otherwise does not look like a hard fix taking a quick look at cm12. Have a meeting at 1:00 and look into some time after.
Any other download mirror ?
It is hardly possible for me to download the rom from dev-host
hunzhang said:
It is hardly possible for me to download the rom from dev-host
Click to expand...
Click to collapse
?????????
chairshot215 said:
Think if rooted with bussybox installed fix may then work. Otherwise think would need to either build the fix in before compiling or build non block based and add files into the zip. Took a quick look and the fix I downloaded called on bussybox in the update-script when flashing so installing bussybox may fix the sprint fix, lol. Otherwise does not look like a hard fix taking a quick look at cm12. Have a meeting at 1:00 and look into some time after.
Click to expand...
Click to collapse
Forgive my noobness, as I'm usually on point with this stuff, but how can I root WITH busybox? Would I need to boot up and then download the app from the store? Because if so, I can't get past the setup screen without constant update device FC's.
Now, what IS interesting is that if I just flash the ROM and update-device.zip, o don't get the FCs. But as soon as I flash gapps, that's when things start to head south.
iamterence said:
Forgive my noobness, as I'm usually on point with this stuff, but how can I root WITH busybox? Would I need to boot up and then download the app from the store? Because if so, I can't get past the setup screen without constant update device FC's.
Now, what IS interesting is that if I just flash the ROM and update-device.zip, o don't get the FCs. But as soon as I flash gapps, that's when things start to head south.
Click to expand...
Click to collapse
Sorry maybe bad word placement on my part but had meant root the Rom and then install busybox which requires root. You should be able to download SuperSU and then flash it in recovery. Once SuperSU is installed can download busybox installer from playstore.
This is the version of SuperSU I have used the last few builds.
https://www.dropbox.com/s/1y5m5vvtp55o4f0/BETA-SuperSU-v2.44.zip?dl=0
Still may be hard if you are having FC issues on setup. I am honestly not an expert but would not think being on Sprint would cause FC issues but again I don’t really know. If you are experiencing FC issues would try a full wipe including data if not done so previously and install again. Not sure its the case but I first tried a dirty flash from 5.0 stock to an AOSP build and all my Google Apps which I believe set-up wizard is included but was OK for me would not work, Not the best solution but ended up un-installing and reinstalling all my Google Apps. After that everything was OK. Think the issue was caused by having flashed different versions of the Google Apps that did not vibe with the updates from the play store. After I dirty flashed again from 5.01 to 5.02 using same version of Gapps and did not have any issues. Not saying is the case but not doing a data wipe can cause some strange bugs not always seeming to be related to the bugs experienced. I once had an issue back in the days og GB that my wifi had stopped working. Had been on forums and bugging out for a few days and then for some unrelated reason wiped the MMS app data in application settings and performed a reboot. First thing I noticed was wifi was working. How bad data from the MMS app could have broke wifi is still an unsolved mystery but just to be sure restored a Nandroid with the bad wifi twice and was able to reproduce the fix both times by wiping MMS data.
Otherwise let me know if anyone else has experienced a FC during set-up but only if you have wiped the data partition. I have otherwise flashed about 15 times so far and have yet seen an app FC on me.
kowalsfee said:
The only thing bothers me is the aosp dialer icon, so anti-material, can someone solve that out?
Click to expand...
Click to collapse
Yeah not all of AOSP is Material. I myself after flashing download a root file explorer and remove the calendar, voice dialler, music and MSS apk's and then download Google Calender and the new Google Messenger apps from the play store. I also install the Google Calender and have been using Google Inbox in place of Gmail. Otherwise not much else from Google as I also have an N7 and N9 so in general keep the phone slim and load up the now N9. Was not a fan at first but now a days can no longer use the N7. Only thing about the N9 that still bugs me is they copied Apple with the 4:3 aspect ratio. Is awesome for old TV shows on Netflix but all others pretty much take the same space they would have on the N7 making the larger screen pretty much null and void. Otherwise had been pretty disappointed at first but has grown on me big time.
Added a bunch more updates. Still working on a fix for sprint users but have a good idea what needs to be done.
Also had added from Google a record bug report option with power off seems I forgot to remove before building but all it does is dump a bug-report in storage. Has no other effect. Otherwise smooth a butter and bug free.
Any chance for a Mako port? I have a Nexus 5 myself, but someone I know has a nexus 4 that's acting up (SoD) and so i thought that this might help them out.
I just flashed over to this ROM from stock 5.0.1 I am hoping that this build will fix the memory leak I've had on the official build. So far everything seems to work well except for the security settings. Anytime I try to open it settings simply force closes. Does anyone else have this issue? I usually use smart lock so I am sad to see this broken. I have a unlocked nexus 5 running on AT&T and I did a full wipe before flashing. I also flashed the recommended GApps package. Thanks in advance
Yeah thats my bad uploaded the wrong .zip including a stock file experementing for Sprint Users. Will recompile and post correct build. Everything else should be the same so once fix is posted should be ok to just wipe system & cache before install. Just need to also reflash same gapps package as before.
Also going to post manifest so can build for all Nexus devices. Can also build it special if needed. If you guys are seeing improvments with the Updates let me know and can start posting builds for all Nexus devices. I only have the 7 (2013), 9 and 5 for testing. I see a few big improvmets but curious what others think before starting to build for every Nexus. Know a few apps like messaging are still not material and was surprised to see old school Music first time building pure AOSP but wanted purity so have laft those things be.
Is r2 the release build with the Sprint fixes?
This rom is built directly from the stock MRA58R Google image.
PSA
For pin to work you will need a permissive kernel, Rom is currently running enforcing so flash a permissive kernel if you want pin. No issues if your using cataclysm. I'm working on figuring out the fix thanks.
It is basically just the system folder extracted from the MRA58R Google update and repackaged as a flashable zip with a stock kernel with added features by @gerar_f.
I packaged this together for people that want a Stock Bloated Google experience. Or a fully stock rom to customize to the users liking.
Any mod made for the stock google rom should work 100% here.
Cataclysm mod is recommended if your looking for a more custom rom experience and I fully support flashing it over this rom.
http://forum.xda-developers.com/nexus-6/orig-development/rom-cataclysm-nexus-6-t3219121
Cataclysm flashes a kernel so if you like the added features of gerar_f's kernel then you will want to flash it after cataclysm. Link below
Rom Features
Odexed
None really. This is as stock Google as it gets, you will find all the gapps that will possibly fit in the system partition just like a stock google image.
Root is not included. Flash SuperSu 2.5.2 if you want. You can run this rom un-rooted with cataclysm mod flashed over top and have a custom unrooted rom with working android pay.
(Theoretically) I haven't been able to test pay around me
Busybox is also not installed so grab that from the playstore if you want/need it.
Included Kernel by @gerar_f
Included kernel is Custom "Stock" v4 created by @gerar_f big thanks to him and go over to his thread and drop a like.
http://forum.xda-developers.com/nexus-6/development/kernel-stock-kernel-root-color-control-t3218958
Kernel is stock in behavior with a few features. First it is without forced encryption, It is Seandroid Enforcing and includes several features, Root with rw if rooted, Disabled boot verification warning, Color control, Headphone and mic gain control, Vibration control, Wake gestures, Multirom support.
TIPS
There is only 33mb free in the system partition due to google including so many gapps. In my testing ive found that this is enough for installing 1 layers theme and Cataclysm Mod.
Some gapps may need removed to install things like Xposed modules, and other apps to the system(TBO apps, better battery stats etc) or anything that takes up more than a few megs going into the system.
I personally remove Fit, Sheets, and Slides which gives you around 100mb free in system which is enough for my use. I recommend this app for removing system apps you dont want. Root Required.
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp&hl=en
Thanks
@gerar_f for great custom stock kernel. (I couldn't even begin to figure out how to customize a kernel)
@tupac4u for the updater-binary and update-script to flash the zip properly. (my attempts at making the script were futile)
@atl4ntis for making Cataclysm and inspiring me to create a stock rom for said mod to be flashed over.
Google
@magnamentis @dhruvmalik for testing. @Chainfire for ROOTS!
Download
Rom
https://www.androidfilehost.com/?fid=24269982087001131
MD5
52526f45a3ffafd6d9b6bdd0b7f8836c
Install instructions
In TWRP, factory rest, wipe cache, dalvik, data, and system.
Flash Rom
If wanted flash additional stuff (supersu, cataclysm, and/or kernel)
Profit
Reserved for possibly more
Hi,
Thank you for this as this is very useful!
Droidphilev said:
Hi,
Thank you for this as this is very useful!
Click to expand...
Click to collapse
Thanks!
I was surprised that there was not a unmodified flashable Google rom out so I put one together.
Sent from my Nexus 6 using Tapatalk
GavinMazey said:
Thanks!
I was surprised that there was not a unmodified flashable Google rom out so I put one together.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I tried myself too but gave up
I wonder: this is a one time project? I mean if there's a new factory image can i just extract the system.img and put it into your zip and never ever bother you again?
(I'm not able to download today hence the question)
EDIT: please don't mind the kernel in this question
Droidphilev said:
I tried myself too but gave up
I wonder: this is a one time project? I mean if there's a new factory image can i just extract the system.img and put it into your zip and never ever bother you again?
(I'm not able to download today hence the question)
EDIT: please don't mind the kernel in this question
Click to expand...
Click to collapse
I'm planning on releasing more versions as Google releases it's monthly updates.
To answer your other question it's not as simple as just extracting the system.img but isnt too hard. Basically you extract the actual system.img from the Google update. Then use ext4 unpacker to unpack it into an ext4 file. Then you use ext2 explore to unpack the ext4 file which gives you the system folder with all the files within. Then just take the system folder a compatible boot.img and a working meta-inf folder and zip them up. Then you have your Rom.
Sent from my Nexus 6 using Tapatalk
GavinMazey said:
I'm planning on releasing more versions as Google releases it's monthly updates.
To answer your other question it's not as simple as just extracting the system.img but isnt too hard. Basically you extract the actual system.img from the Google update. Then use ext4 unpacker to unpack it into an ext4 file. Then you use ext2 explore to unpack the ext4 file which gives you the system folder with all the files within. Then just take the system folder a compatible boot.img and a working meta-inf folder and zip them up. Then you have your Rom.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Thank you for this info and explanation but after reading this i think i will just download your releases if you don't mind
Droidphilev said:
Thank you for this info and explanation but after reading this i think i will just download your releases if you don't mind
Click to expand...
Click to collapse
Lol that's fine with me.
Sent from my Nexus 6 using Tapatalk
GavinMazey said:
Lol that's fine with me.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yeah, thanks for the explanation, its nice to learn about stuff that has bewildered you for ages.
arifqur said:
Yeah, thanks for the explanation, its nice to learn about stuff that has bewildered you for ages.
Click to expand...
Click to collapse
Feel free to ask any other questions.
Yea that's very simple way to make a Rom. I wouldn't call myself a dev or anything. The other custom roms require a lot more work like modifying system apks to add the extra features. This is just full unmodified stock with a kernel. I figured it would be a great base to flash cataclysm over. Seeing how it's recommended to flash cataclysm over a full stock Rom this is as close as it gets right now. People have had luck flashing cataclysm over other stock modified roms but I worry that those modifications may cause issues with the modifications of cataclysm. With that said I'm personally running it without cataclysm. I just removed a few gapps I'll never use flashed and installed around 10 team blackout apps, and applied magpie midnight theme for a almost fully blacked out experience.
Sent from my Nexus 6 using Tapatalk
GavinMazey said:
Feel free to ask any other questions.
Yea that's very simple way to make a Rom. I wouldn't call myself a dev or anything. The other custom roms require a lot more work like modifying system apks to add the extra features. This is just full unmodified stock with a kernel. I figured it would be a great base to flash cataclysm over. Seeing how it's recommended to flash cataclysm over a full stock Rom this is as close as it gets right now. People have had luck flashing cataclysm over other stock modified roms but I worry that those modifications may cause issues with the modifications of cataclysm. With that said I'm personally running it without cataclysm. I just removed a few gapps I'll never use flashed and installed around 10 team blackout apps, and applied magpie midnight theme for a almost fully blacked out experience.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
As stated above by others, I was also surprised that there wasn't a flashable stock ROM available, primarily for those who wish to be stock, use xposed and or mods like Cataclysm.
This is working awesome; thanks @GavinMazey
Great idea, I'll probably be checking it out soon with CatMod. Any chance you could debloat it? It's not hard for me to just use Tibu to do it, but one less thing to do is always nice. No worries if you can't.
Thanks for the rom!
Thank you for this!
GeekMcLeod said:
Great idea, I'll probably be checking it out soon with CatMod. Any chance you could debloat it? It's not hard for me to just use Tibu to do it, but one less thing to do is always nice. No worries if you can't.
Thanks for the rom!
Click to expand...
Click to collapse
I'm not really planning on debloating, there is a plethora debloated roms for the n6. But if enough end up wanting it I might. But if I do it would be my personal debloat instead of removing as much as possible. Keeping it stock let's me update faster when google drops new images.
flashback7 said:
Thank you for this!
Click to expand...
Click to collapse
Thanks for checking it out.
Sent from my Nexus 6 using Tapatalk
+ 1 on NOT debloating. Every one could do it how they like it by themselves.
Thanks.. It's good to know I have an option to flash the zip. I might load up cataclysm tonight
This is great for those who want fresh out of box stock experience with working ANDROID PAY. Once you root it, trim it, customize it, then ANDROID PAY won't work.
cink40 said:
+ 1 on NOT debloating. Every one could do it how they like it by themselves.
Click to expand...
Click to collapse
Noted. That was my thought too stock bloated base for users to do what they want with it. I personally use most of the gapps included, I personally only delete sheets, slides, and fit (I may be a fatty lol). I've found most debloated roms remove too much so instead of having the gapps taking up system space I have to install them to internal storage taking up space where they don't need to be.
Too much free system space is wasted space imo.
Phrodini said:
Thanks.. It's good to know I have an option to flash the zip. I might load up cataclysm tonight
Click to expand...
Click to collapse
If your already on android m you should be good to flash this then cataclysm. Report back how it went if you do. Haven't had too much feedback on users actually flashing it. Hopefully because all works great [emoji12]
HueyT said:
This is great for those who want fresh out of box stock experience with working ANDROID PAY. Once you root it, trim it, customize it, then ANDROID PAY won't work.
Click to expand...
Click to collapse
That's exactly why I kept it unrooted. In theory someone could flash this Rom and then cataclysm without root and have a custom Rom with working Pay just no root. No where that I've been around me accepts pay so I am unable to test. But in theory it should work.
Sent from my Nexus 6 using Tapatalk
GavinMazey said:
Noted. That was my thought too stock bloated base for users to do what they want with it. I personally use most of the gapps included, I personally only delete sheets, slides, and fit (I may be a fatty lol). I've found most debloated roms remove too much so instead of having the gapps taking up system space I have to install them to internal storage taking up space where they don't need to be.
Too much free system space is wasted space imo.
If your already on android m you should be good to flash this then cataclysm. Report back how it went if you do. Haven't had too much feedback on users actually flashing it. Hopefully because all works great [emoji12]
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I am thinking about using multirom with this zip, cataclysm, and a lollipop rom.. Maybe kitkat too for one game that only works on kitkat lol
Phrodini said:
I am thinking about using multirom with this zip, cataclysm, and a lollipop rom.. Maybe kitkat too for one game that only works on kitkat lol
Click to expand...
Click to collapse
Flashing cataclysm will replace the included kernel with cataclysm kernel which you'll need to check supports multirom, I'm not sure off the top of my head. But if not re flashing the included kernel by gerar_f after cataclysm will give you multirom support. Also I'm not entirely sure you can run kitkat and marshmallow in multirom at the same time. I haven't used it myself but I think (I may be wrong) that multirom uses your main kernel for all other roms. So a different android version may not work properly. Again I might be wrong.
Sent from my Nexus 6 using Tapatalk