Database Develop

[DEV][WIP] CM9/Ice Cream Sandwich

I have been working on porting CM9 to the VS910. So far I have gotten it to boot to the lock screen.
What Works
Boot animation
Lock screen
SurfaceFlinger
logcat/adb shell
3d accel is half working. I have gotten SurfaceFlinger to load up and interface the proprietary drivers (from GB) correctly, but HardwareRenderer (java framework) fails because the drivers don't give up a valid config.
What Doesn't Work
Touch screen
HardwareRenderer (fails because HardwareRenderer.chooseEglConfig() returns null value)
Everything else
Currently this ROM is totally unusuable for anything except for development. At this point, I do believe it is possible to get CM9 running, but it will take a good bit of developer effort. It would be helpful for any other developers around here to give some insight on the errors that come up in the adb logs.
How To Build
Follow Google's instructions for setting up a Linux system or VM for Android AOSP building
Follow CM9 build instructions up to brunch command
git clone git://github.com/andyichr/makerom.git to a location, such as ~/android/makerom
Overlay the files in ~/android/makerom/cm9-system/overlay onto the cm9/system directory (this adds vs910 brunch)
Adjust values in makerom.sh to match your own paths (MAKE SURE TO POINT IT AT A VALID KERNEL --I didn't include instructions for building a kernel)
Adjust values in makecm9.sh to match your own paths
Run ~/android/makerom/makecm9.sh to build cm9 (this takes a long time, depending on your system)
If build is successful, run ~/makerom/makerom.sh which will output a ROM which may be flashed to the device for testing
This is very rough work, but it proves that the basic parts of CM9/ICS do function on the Revolution. The cyanogenmod developers have already added some patches to the android source which allow ICS to run using video drivers from Gingerbread. This means it should be possible to get things working.
The current major problem with this ROM is that the HardwareRenderer does not initialize. Immediately after this, the main trebuchet process is killed and the system reboots itself after a while.
I will be happy to do what I can to support the process of porting CM9 to our phones. I read that a couple of other devs may be looking into porting CM7, but I think focusing on 9 might be more worth the effort, since we already have Gingerbread.
I have also attached a logcat to this post which should give developers some idea about what exactly is broken, which will lead to the first steps of debugging and porting.
Any interested developers should fork my repo on github (git://github.com/andyichr/makerom.git) which has the build scripts and patches.
That's about it for now. I very well may have left out some steps along the way. If you try to follow this process and it doesn't work out, let me know and I'll help you out.
ROM Download (very broken --only use for testing and development)
http://www.multiupload.com/GI0MLQYTE0 - Flash this if you want to see ICS boot to the lock screen or help test/debug. It's not useful for much else at this point.
We're getting there! I've already patched the android egl framework code slightly and built a kernel. CM team already patched frameworks/base for 2.3 video drivers. We'll patch what we have to to get this thing running! I am pretty busy but I will follow this thread and I hope for this to be a collaborative, transparent porting process! Good luck!

Nice, get with Mtmichaelson and Cubed, they are working on Cm9 also!
Sent from my VS910 4G using Tapatalk

Great! I saw in the CM7 thread that thecubed put up a git repo. I'm not sure exactly what his development plan is, but I'd be happy to fork his repo and trade patches, logs, etc. The more devs we have on this, the better... it's not a trivial task and I'm sure my wife hates me by now for spending so many hrs on it so far.

If I read correctly, thecubed just got a master repository set up for the revolution, so maybe the files that are needed could be lurking in there? I'll see if I can find the link and post it here.
Here's the link: https://github.com/thecubed
BLITZ ledded adshot nitro supercharged Gingerlution

I know in irc tonight cubed was talking about it. Guess they have to work on a few things but it's coming along. Wish I knew more so I could help out in this to. Guess I could be the Guinea pig.
Sent from my VS910 4G using Tapatalk

aichrist said:
Great! I saw in the CM7 thread that thecubed put up a git repo. I'm not sure exactly what his development plan is, but I'd be happy to fork his repo and trade patches, logs, etc. The more devs we have on this, the better... it's not a trivial task and I'm sure my wife hates me by now for spending so many hrs on it so far.
Click to expand...
Click to collapse
Awesome job so far! For a lot of things to work correctly, it's my understanding that you'll need a new kernel. For at least the touchscreen issues, you need the "idc" file in the "/system/usr/idc" directory (not sure if you have that or not, I didn't get a chance to check yet)
Either way, if you'd like to get in contact with me, hop on IRC and I'd be happy to answer any questions you may have.
Excellent work!

indyred99 said:
I know in irc tonight cubed was talking about it. Guess they have to work on a few things but it's coming along. Wish I knew more so I could help out in this to. Guess I could be the Guinea pig.
Sent from my VS910 4G using Tapatalk
Click to expand...
Click to collapse
Yeah I see thecube's repo at https://github.com/thecubed/android_device_lge_revolution. His CM files are a lot cleaner than mine... I just copied the crespo config and haven't had time to clean it up yet. I'll do some diffs of his vs mine and see about getting things merged. My github repo has some additional files so what I could do is replace my vs910 device folder with a fork of thecube's repo.
I'm not sure whether his files are for CM7 or CM9 (or if it doesn't matter). I'm new to CM porting, but I'm not new to linux or android app development.

thecubed said:
Awesome job so far! For a lot of things to work correctly, it's my understanding that you'll need a new kernel. For at least the touchscreen issues, you need the "idc" file in the "/system/usr/idc" directory (not sure if you have that or not, I didn't get a chance to check yet)
Either way, if you'd like to get in contact with me, hop on IRC and I'd be happy to answer any questions you may have.
Excellent work!
Click to expand...
Click to collapse
Thanks for the tip. I'll check that out. So far I've mainly been banging my head on getting the adreno205 drivers working, but it sure would be nice to have touch working. That'd be the next priority.
I'm tempted to switch of 3d acceleration but I am focusing on one thing at a time.
I'll hop on IRC. Which channel are you on specifically?

As always guys, I'm happy to assist in testing. Nor very knowledgeable on coding or porting, but I can definitely put my phone at risk
BLITZ ledded adshot nitro supercharged Gingerlution

wish I knew more about this stuff so I could help
keep up the great work!
crossing fingers, hoping I'll get the chance to start making themes for CM9!

aichrist said:
Thanks for the tip. I'll check that out. So far I've mainly been banging my head on getting the adreno205 drivers working, but it sure would be nice to have touch working. That'd be the next priority.
I'm tempted to switch of 3d acceleration but I am focusing on one thing at a time.
I'll hop on IRC. Which channel are you on specifically?
Click to expand...
Click to collapse
Head over to #lgrevolution and I'll be there as IOMonster.
Yep, for ICS we need a lot of work in the KGSL department in kernel for getting proper Adreno support working... Tiamat is working on adding the new KGSL/USB/Genlock support to his MSM7X30 repo here ( http://git.tiamat-dev.com/7x30/htc-kernel-msm7x30/ ) and after that we need to merge our kernel sources with his (boardfiles, includes, configs, etc)
Booting to lockscreen is great, but there's a LOT of work to be done before we can have a "working" ICS by any stretch of the imagination... ICS is a whole new beast, unfortunately...

Cubed beat me to it.
Sent from my VS910 4G using xda premium

thecubed said:
Head over to #lgrevolution and I'll be there as IOMonster.
Yep, for ICS we need a lot of work in the KGSL department in kernel for getting proper Adreno support working... Tiamat is working on adding the new KGSL/USB/Genlock support to his MSM7X30 repo here ( http://git.tiamat-dev.com/7x30/htc-kernel-msm7x30/ ) and after that we need to merge our kernel sources with his (boardfiles, includes, configs, etc)
Booting to lockscreen is great, but there's a LOT of work to be done before we can have a "working" ICS by any stretch of the imagination... ICS is a whole new beast, unfortunately...
Click to expand...
Click to collapse
Great --I'll be on the channel as achristianson or achristi.
Thanks so much for all that info.
I'm sure it is a long road to a fully working ICS. I see it as a challenge and will just keep fixing the next broken thing...

I'd be happy to test this. I got a spare revo cuz I had a warranty and this dent on the outer corner was driving me nuts.
Gingerfused Gingervolt 1.3 + Blitz

It's really awesome to see everyone working on this. I really wish I knew more about this stuff to be able to help. All this is really making me wanna read up on this stuff and learn how to do some of it. Until that happens, I'll be more than happy to help out with any testing or in any other way within my capabilities. I got a Revo just sitting there deactived waiting for that ICS goodness.
Thanks a lot for everyone working on this. Those of us that aren't as gifted really aprreciate the work you guys are putting in.

Grizzy3 said:
It's really awesome to see everyone working on this. I really wish I knew more about this stuff to be able to help. All this is really making me wanna read up on this stuff and learn how to do some of it. Until that happens, I'll be more than happy to help out with any testing or in any other way within my capabilities. I got a Revo just sitting there deactived waiting for that ICS goodness.
Thanks a lot for everyone working on this. Those of us that aren't as gifted really aprreciate the work you guys are putting in.
Click to expand...
Click to collapse
If you've noticed my post in the CM7 Thread, which somehow 'feels' like it's sparked something off here (maybe just timing, lol), I am beginning to work on this stuff.
Anyone can do it, but the problem is motivation and the willingness to learn something new. You will never learn this stuff unless you're willing to fail and fail again. You learn by mistakes and mistakes sometimes turn into innovation for new things and ideas.
There is a lot of Dev's all of a sudden and I do agree, it's great to see. I was almost about to start looking at the Nexus. When I realized I would lose out on the $130 of extra accessories for my Revo (Car Dock, home dock, extra battery, car charge, etc.), And the fact the the Nexus had no External SD Card, I was like... Nah.. Time to step up and see what I can do to make the Revo a well-supported, up to date, kick-ass device. If LG and Verizon wanna sit on their asses, let'em. We make the phone better anyhow, right? MT, Cubed, and anyone else who has already contributed so much, has made this phone 10X's what it ever was out of the box. And, unlike LG and Verizon, Dev's like MT (and others) don't give us the run around on the next release, but a timeline.
-Cybie

Cybie257 said:
If you've noticed my post in the CM7 Thread, which somehow 'feels' like it's sparked something off here (maybe just timing, lol), I am beginning to work on this stuff.
Anyone can do it, but the problem is motivation and the willingness to learn something new. You will never learn this stuff unless you're willing to fail and fail again. You learn by mistakes and mistakes sometimes turn into innovation for new things and ideas.
There is a lot of Dev's all of a sudden and I do agree, it's great to see. I was almost about to start looking at the Nexus. When I realized I would lose out on the $130 of extra accessories for my Revo (Car Dock, home dock, extra battery, car charge, etc.), And the fact the the Nexus had no External SD Card, I was like... Nah.. Time to step up and see what I can do to make the Revo a well-supported, up to date, kick-ass device. If LG and Verizon wanna sit on their asses, let'em. We make the phone better anyhow, right? MT, Cubed, and anyone else who has already contributed so much, has made this phone 10X's what it ever was out of the box. And, unlike LG and Verizon, Dev's like MT (and others) don't give us the run around on the next release, but a timeline.
-Cybie
Click to expand...
Click to collapse
Exactly how i feel. Forget LG and Verizon. You guys are the ones taking these average phones into something great. I definitely gave up on getting any real support from either of them.
I really want to start getting into this. I have a little bit of time on my hands and will definitely be reading up on all this. I think you sparked something with your post lol. I know other people like MT and theCubed were already working on some things but I think you definitely added a little spark lol. Very happy to see other people jumping on board to help out. Hopefully I can too

Grizzy3 said:
Exactly how i feel. Forget LG and Verizon. You guys are the ones taking these average phones into something great. I definitely gave up on getting any real support from either of them.
I really want to start getting into this. I have a little bit of time on my hands and will definitely be reading up on all this. I think you sparked something with your post lol. I know other people like MT and theCubed were already working on some things but I think you definitely added a little spark lol. Very happy to see other people jumping on board to help out. Hopefully I can too
Click to expand...
Click to collapse
Yup! The motivation for me has been that support by LG and VZ is diminishing. This is the beauty of open source, though. Now the community can support it.
I believe the Revolution really is a good phone. It's got a good GPU and CPU. It's not dual-core, no, but with a good ROM on there, it can be much more efficient than a dual-core phone that is loaded with crapware.
Cybie did inspire me to put my work up sooner so that we can all focus on it and not duplicate our efforts as much.

thecubed said:
Head over to #lgrevolution and I'll be there as IOMonster.
Yep, for ICS we need a lot of work in the KGSL department in kernel for getting proper Adreno support working... Tiamat is working on adding the new KGSL/USB/Genlock support to his MSM7X30 repo here ( http://git.tiamat-dev.com/7x30/htc-kernel-msm7x30/ ) and after that we need to merge our kernel sources with his (boardfiles, includes, configs, etc)
Booting to lockscreen is great, but there's a LOT of work to be done before we can have a "working" ICS by any stretch of the imagination... ICS is a whole new beast, unfortunately...
Click to expand...
Click to collapse
OK so I was doing more debugging last night in the EGL/SurfaceFlinger/HardwareRenderer code. I also looked at some of Tiamat's work on the MSM7X30 kernel.
I can see now what you mean with regard to merging parts of that kernel into our own. I am assuming that kernel is being crafted to work with ICS-friendly EGL blobs for the adreno205. Is that correct? If so, then that kernel would have code that would be required to talk to the binary blob EGL drivers for Adreno205 that we would pull from some device that has the same chip and has official proprietary drivers for ICS available. I believe the HTC Droid Incredible 2 is one such device. Is this roughly what you were thinking?
I initially had thought of going down a different path: Instead of using newer ICS proprietary drivers and updating our kernel to support it, I was planning on keeping the kernel we have and the binary drivers we have, which are already made to work with each other. The work then required to get ICS working would be to change parts of the ICS userspace code such that they'd work with our older drivers. I don't have the links on hand, but I believe this is possible because I read about others taking this strategy on other devices that do not have ICS support officially but do have proper GB support. It also makes sense to me logically that the userspace code could be changed to our heart's content to work with older drivers, since we have full access to that source code. One option that I read about that we could potentially do is write a wrapper for the *adreno200*so librares that would implement the newer API that ICS is expecting and would translate the calls into the older API that is supported in our GB proprietary drivers.
It looks to me like we have two possible ways forward with regard to getting hardware acceleration working: upgrading the kernel and drivers to have "proper" ICS support, or patching ICS userspace code to work with GB drivers and kernel. I believe that patching the ICS userspace code would get us up and running faster while upgrading the kernel and adding newer drivers would be the better long-term solution.
Here are a couple of patches that people have already implemented to support older EGL blobs/kernels:
https://github.com/VorkTeam/android_frameworks_base/commit/429e922fb6f2660fc40472e939175688af52b1d2
https://gist.github.com/CyanogenMod...mmit/5d689bd02531f8ff256b3b1eddcaa8040c9f3559
https://gist.github.com/CyanogenMod...mmit/f8e2430be2d6b3e88afd7190f6712f3bc1df0cbf
Let me know what you think.
Also, what do you think about using the BOARD_USES_QCOM_HARDWARE := true directive to our CM board configuration? I noticed references to the QCOM_HARDWARE flags all over the video code. It seems we would want this since we are using a QCOM video chip. The only problem is the build failed for me when I added this flag. There's an issue about it on github: https://github.com/CyanogenMod/android_hardware_qcom_display/issues/3#issuecomment-3457179.

aichrist said:
OK so I was doing more debugging last night in the EGL/SurfaceFlinger/HardwareRenderer code. I also looked at some of Tiamat's work on the MSM7X30 kernel.
I can see now what you mean with regard to merging parts of that kernel into our own. I am assuming that kernel is being crafted to work with ICS-friendly EGL blobs for the adreno205. Is that correct? If so, then that kernel would have code that would be required to talk to the binary blob EGL drivers for Adreno205 that we would pull from some device that has the same chip and has official proprietary drivers for ICS available. I believe the HTC Droid Incredible 2 is one such device. Is this roughly what you were thinking?
I initially had thought of going down a different path: Instead of using newer ICS proprietary drivers and updating our kernel to support it, I was planning on keeping the kernel we have and the binary drivers we have, which are already made to work with each other. The work then required to get ICS working would be to change parts of the ICS userspace code such that they'd work with our older drivers. I don't have the links on hand, but I believe this is possible because I read about others taking this strategy on other devices that do not have ICS support officially but do have proper GB support. It also makes sense to me logically that the userspace code could be changed to our heart's content to work with older drivers, since we have full access to that source code. One option that I read about that we could potentially do is write a wrapper for the *adreno200*so librares that would implement the newer API that ICS is expecting and would translate the calls into the older API that is supported in our GB proprietary drivers.
It looks to me like we have two possible ways forward with regard to getting hardware acceleration working: upgrading the kernel and drivers to have "proper" ICS support, or patching ICS userspace code to work with GB drivers and kernel. I believe that patching the ICS userspace code would get us up and running faster while upgrading the kernel and adding newer drivers would be the better long-term solution.
Here are a couple of patches that people have already implemented to support older EGL blobs/kernels:
https://github.com/VorkTeam/android_frameworks_base/commit/429e922fb6f2660fc40472e939175688af52b1d2
https://gist.github.com/CyanogenMod...mmit/5d689bd02531f8ff256b3b1eddcaa8040c9f3559
https://gist.github.com/CyanogenMod...mmit/f8e2430be2d6b3e88afd7190f6712f3bc1df0cbf
Let me know what you think.
Also, what do you think about using the BOARD_USES_QCOM_HARDWARE := true directive to our CM board configuration? I noticed references to the QCOM_HARDWARE flags all over the video code. It seems we would want this since we are using a QCOM video chip. The only problem is the build failed for me when I added this flag. There's an issue about it on github: https://github.com/CyanogenMod/android_hardware_qcom_display/issues/3#issuecomment-3457179.
Click to expand...
Click to collapse
You guys are great! I hope this is doable, keep up the hard work..
Sent from my Nexus S 4G using XDA App

Post your first impressions

So I've just flashed OmniROM on my LG Optimus 4X HD (p880). Probably this is the first unofficial build, built from Gerrit repos, I'm really proud of myself.
I'm pretty impressed that there were only a few changes needed and almost everything works, only BT doesn't work (easy to fix). I really like the quick settings flipping and how it shows Wi-Fi IP address when flipped. :good: I attach some screenshots.

Adam77Root said:
So I've just flashed OmniROM on my LG Optimus 4X HD (p880). Probably this is the first unofficial build, built from Gerrit repos, I'm really proud of myself.
I'm pretty impressed that there were only a few changes needed and almost everything works, only BT doesn't work (easy to fix). I really like the quick settings flipping and how it shows Wi-Fi IP address when flipped. :good: I attach some screenshots.
Click to expand...
Click to collapse
Is this build available for download? Really eager to try it out
And will you be maintaining for the P880 on a Nightly/Weekly/whenever flexibly based? Sorry for asking that, just curious

penguin449 said:
Is this build available for download? Really eager to try it out
And will you be maintaining for the P880 on a Nightly/Weekly/whenever flexibly based? Sorry for asking that, just curious
Click to expand...
Click to collapse
Not yet. It's not even built from published sources, though there isn't much change in published ones yet.
Yes, probably I will.

Nice to see
In terms of going forward in terms of builds, we will be addressing these issues when we can. For now though, Omni isn't "officially" released in any kind of binary packages.
When the time comes, we will invoke the release processes, which will give nightly builds, with a weekly "tagged build". On Omni, nightly builds are expected to be stable, and encourage bug reports on them. A "weekly" is just a nightly that is tagged as "working fine", for those who don't want to update every day.

pulser_g2 said:
For now though, Omni isn't "officially" released in any kind of binary packages.
Click to expand...
Click to collapse
Not anymore: http://forum.xda-developers.com/showthread.php?t=2481929

When OmniROM is going to be released on Nexus 4?

I hope they will have their own theme going on soon...was hoping it wouldn't look like cm/aokp out of the box lol

mgbotoe said:
I hope they will have their own theme going on soon...was hoping it wouldn't look like cm/aokp out of the box lol
Click to expand...
Click to collapse
I hope it looks like AOSP out of the box, who cares about CM/AOKP?

Testraindrop said:
I hope it looks like AOSP out of the box, who cares about CM/AOKP?
Click to expand...
Click to collapse
Considering cm/aokp look just like aosp...I care it dont look like that o.o

Can somebody who's already built and run the ROM do a hands-on impressions video of it?

mgbotoe said:
I hope they will have their own theme going on soon...was hoping it wouldn't look like cm/aokp out of the box lol
Click to expand...
Click to collapse
The current look is the "AOSP" look. I imagine that longer term, there will be reason to look into modular theming systems. A lot of people want a "pure android" look, and generally the best way to avoid breaking things is to make any themes optional extras.

pulser_g2 said:
The current look is the "AOSP" look. I imagine that longer term, there will be reason to look into modular theming systems. A lot of people want a "pure android" look, and generally the best way to avoid breaking things is to make any themes optional extras.
Click to expand...
Click to collapse
Thank you, you kind sir for the response

Sounds really nice guys!!! Happy to see entropy and xplod working on android roms again after the cm thingy! Also nice to see that maxwen is working on this!

Made a build for the Nexus 10. I installed it breefly and from what i could see is that it is indeed mostly AOSP. Nice touch is the rotating tiles. If you rotate the wifi tile, you will see the ip adres.
Anyway i am still too much used to some CM additions (like the ability to close all apps at once).
It is a good start and will keep an eye on the development.

scanno said:
Made a build for the Nexus 10. I installed it breefly and from what i could see is that it is indeed mostly AOSP. Nice touch is the rotating tiles. If you rotate the wifi tile, you will see the ip adres.
Anyway i am still too much used to some CM additions (like the ability to close all apps at once).
It is a good start and will keep an eye on the development.
Click to expand...
Click to collapse
More features on the way
It's mostly AOSP right now, we are currently in the process of adding a lot of the "useful" parts we know and love. If you want to get involved, feel free to do so on Gerrit.

pulser_g2 said:
More features on the way
It's mostly AOSP right now, we are currently in the process of adding a lot of the "useful" parts we know and love. If you want to get involved, feel free to do so on Gerrit.
Click to expand...
Click to collapse
Already created an account
Sent from my TF300T using Tapatalk 4

So another build for i9500
Everything is working except Bluetooth
Love it ^^

I've installed tilal6991's build on my Xperia T and it works like a charm. No superuser for some reason but otherwise it's perfect! Can't wait for this project to mature
Sent from my Xperia T using Tapatalk now Free

Made a build for HTC Explorer,and it's running great,albeit with a few bugs(most are easy to fix)
The major thing i noticed was that all 4.3 roms for this device have a "lockscreen lag bug",but this doesn't!

sakindia123 said:
Made a build for HTC Explorer,and it's running great,albeit with a few bugs(most are easy to fix)
The major thing i noticed was that all 4.3 roms for this device have a "lockscreen lag bug",but this doesn't!
Click to expand...
Click to collapse
Woah dude, you got this running on an Explorer? That thing is like...ancient. I didn't even think it would be capable of Android 4.1+ Props!

[ROM][AOSP][Nightly/Release]CarbonRom KitKat[N5110]

About Carbon
CarbonRom is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look at, build, and use our code on CarbonDev GitHub. and on our Gerrit CarbonDev Gerrit.
We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository.
Special thanks also go to Slim Rom for some of their features, PA, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
Features
All of our features can be found on our site here:
Carbon Features
Here are some screenshots:
Carbon Screenshots
Carbon Updates
Join us on these Social Media Channels to keep yourself up-to-date on all the latest Carbon news, updates, contests, and more! Join our completely open Google+ community for insider conversation with devs and other users.
Download Carbon
All Carbon downloads and further information such as features, changelog, and FAQ can be found on our website.
Carbon Downloads
Changelog
For a detailed changelog, check out the changes made each night here:
Carbon Changelog
Support
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Ask a question on our IRC channel. Connect to #teamcarbon on irc.freenode.net or click here. You'll find several other Carbon fans and usually one or more devs as well. Please be polite.
Who is Team Carbon?
Find out here:
Carbon Team
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
****************** All links below this are UNOFFICIAL builds ******************
GAPPS
CWM 6.0.4.4 w/ swipe - Heimdall
TWRP 2.6.3.0 touch recovery w/ working AROMA touch (N5110)
ROM Downloads:
Initial Release
Changes:
-Initial Release
Jan 26th
Changes:
-Fix interface crashing
-Fix back camera freezing
Feb 2nd
Changes:
-Fixed electron beam screen off animation
-Upstream Sync
Feb 7th
Changes:
-Upstream Sync
-Fully working camera
​
​Sources:
Rom Sources
My GitHub
Kernel Sources
Device Tree
XDA:DevDB Information
[ROM][AOSP][Nightly/Release] CarbonRom KitKat [N5110], a ROM for the Samsung Galaxy Note 8.0
Contributors
ryukiri
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Version Information
Status: Beta
Created 2014-01-24
Last Updated 2014-02-23

Reserved
How to Build this ROM
1) Setup Your Computer
Stop at
Code:
$ mkdir ~/android
$ cd ~/android
2) Download Source and Compile!
Code:
$ mkdir Carbon4.4
$ cd Carbon4.4
$ repo init -u https://github.com/CarbonDev/android.git -b kk
$ repo sync
$ . build/envsetup.sh
$ lunch (then select device from the list)
$ make carbon
3) Wait till it finishes and grab the zip from the out directory.
*Note: Syncing the repo will take a long time (downloads about 15 gbs of source), depending on your internet speed.

Reserved

Yes! Will flash and report right away!
Update: Took my time to test it, restore my apps, test them and mess a little with the options.
Update 2: After spending even more time with the newest release, this is practically a 0 issues ROM. I'll update my review along with new releases.
My micro SD 32gb works perfectly, if you have a 64gb card I would recommend to be formatted as "exFAT".
Smooth ROM and good RAM usage.
Packed with awesome features and I know there's more to come, CarbonRoms has A LOT of features. From changing status bar colors(and it's icons) to edit the menu and back buttons lights duration and remap the buttons(love it), see screenshots in the OP to have an idea.
No issues at all restoring my apps with Titanium Backup.
Stylus is working perfectly and this ROM has the Buttons settings for our device.
Camera is now working perfectly and more features are being added!
*Remember to do a full wipe clean install.*
Two things I want to mention, they're not annoying and they do not break the ROM at all.
*Interface option under Carbon Fibers crash, however given the fact that you guys are still merging those nice features I think it's kinda obvious. That's why I don't consider this annoying, nor ROM breaking, is just a work in progress. I thought I could mention this so no one get scare about it.
*This one is not even an issue is just a question, I use this device in landscape mode all the time, and every time I turn off the screen it rapidly rotates the screen before shutting down. There's no option for the effect to select or to turn it off, my question is: Is that one of the features to be added later within carbon fibers interface? I apologize, I used Carbon a lot with my N7 flo but I can't remember where that option was located.
*Both fixed on newest release*

NekroWolfen said:
Yes! Will flash and report right away!
Update: Took my time to test it, restore my apps, test them and mess a little with the options:
1.My micro SD 32gb works perfectly.
2.Smooth ROM and good RAM usage.
3.Packed with awesome features and I know there's more to come, CarbonRoms has A LOT of features.
4.No issues at all restoring my apps with Titanium Backup.
5.Stylus is working perfectly and this ROM has the Buttons settings for our device.
Two things I want to mention, they're not annoying and they do not break the ROM at all.
*Interface option under Carbon Fibers crash, however given the fact that you guys are still merging those nice features I think it's kinda obvious. That's why I don't consider this annoying, nor ROM breaking, is just a work in progress. I thought I could mention this so no one get scare about it.
*This one is not even an issue is just a question, I use this device in landscape mode all the time, and every time I turn off the screen it rapidly rotates the screen before shutting down. There's no option for the effect to select or to turn it off, my question is: Is that one of the features to be added later within carbon fibers interface? I apologize, I used Carbon a lot with my N7 flo but I can't remember where that option was located.
Click to expand...
Click to collapse
I found out about that crash during my 2 minutes with this rom..I'm assuming its because of them not finished merging stuff yet. I also see multiwindow and halo both on their gerrit so I'm guessing they'll merge those when its stable
I'm not sure since I've never used Carbon before, but I think what you are talking about is describing the bug thats in all of our roms. Its just the animation right? if you turn the screen back on, it stays in landscape mode? Can't test it because I'm not using this rom right now
And also, not sure if you noticed yet, but the back camera doesn't take photos..I'm almost 100% sure CM broke something in the common device tree because the back camera works in omni, so right now I'm figuring that out and transferring all the files to our own common device tree instead of using the one shared by all the smdk devices.
Edit: Confirmed interface crash is due to a recent commit. Should be fixed soon.

ryukiri said:
I found out about that crash during my 2 minutes with this rom..I'm assuming its because of them not finished merging stuff yet. I also see multiwindow and halo both on their gerrit so I'm guessing they'll merge those when its stable
I'm not sure since I've never used Carbon before, but I think what you are talking about is describing the bug thats in all of our roms. Its just the animation right? if you turn the screen back on, it stays in landscape mode? Can't test it because I'm not using this rom right now
And also, not sure if you noticed yet, but the back camera doesn't take photos..I'm almost 100% sure CM broke something in the common device tree because the back camera works in omni, so right now I'm figuring that out and transferring all the files to our own common device tree instead of using the one shared by all the smdk devices.
Click to expand...
Click to collapse
Yeah is the animation, I was just curious about it, it doesn't bother. The camera thing actually it doesn't bother me either because I can take pictures with any camera app from the app store.
It may be a work in progress, but for a initial release of this beta is pretty darn good. I'm still using it and I think I'm gonna keep it, I've been a huge fan of Carbon for awhile.

NekroWolfen said:
Yeah is the animation, I was just curious about it, it doesn't bother. The camera thing actually it doesn't bother me either because I can take pictures with any camera app from the app store.
It may be a work in progress, but for a initial release of this beta is pretty darn good. I'm still using it and I think I'm gonna keep it, I've been a huge fan of Carbon for awhile.
Click to expand...
Click to collapse
Oh okay btw, can you provide some (maybe 4 or so) good screenshots that I can put in the OP that show some of the carbon options / settings and stuff?
EDIT: Screenshots added.
Sent from my GT-N5110 using Tapatalk

A N5100 version would be very nice

redukt said:
A N5100 version would be very nice
Click to expand...
Click to collapse
I believe @tejkkarani will be taking care of that...if any unexpected things occur then he'll contact me and i will release it.

ryukiri said:
I believe @tejkkarani will be taking care of that...if any unexpected things occur then he'll contact me and i will release it.
Click to expand...
Click to collapse
Great! Great! Grat! :laugh:

New build is up with some relatively big fixes.

ROM is running great and yes it fixed the Carbon fibers, the camera still freezing thou(the ones on the playstore works btw).

NekroWolfen said:
ROM is running great and yes it fixed the Carbon fibers, the camera still freezing thou(the ones on the playstore works btw).
Click to expand...
Click to collapse
Really? For me the back camera doesn't freeze anymore..only the front.
Sent from my GT-N5110 using Tapatalk

ryukiri said:
Really? For me the back camera doesn't freeze anymore..only the front.
Click to expand...
Click to collapse
Rear camera & interface settings are working fine for me on the second release.

Nackler said:
Rear camera & interface settings are working fine for me on the second release.
Click to expand...
Click to collapse
ryukiri said:
Really? For me the back camera doesn't freeze anymore..only the front.
Sent from my GT-N5110 using Tapatalk
Click to expand...
Click to collapse
Sorry for the late reply, yes I too can confirm the camera works, I dirty flashed(just cache and dalvik)the update. Later on I did a full wipe clean install to make sure and voila. So now we can surely say there's no issues on this ROM.

NekroWolfen said:
Sorry for the late reply, yes I too can confirm the camera works, I dirty flashed(just cache and dalvik)the update. Later on I did a full wipe clean install to make sure and voila. So now we can surely say there's no issues on this ROM.
Click to expand...
Click to collapse
Both rear and front cameras working?

hermeticist said:
Both rear and front cameras working?
Click to expand...
Click to collapse
For me, only both cameras work in snapchat, hangouts video, oovoo, and skype...so far (same as the apps that worked in omni)

hermeticist said:
Both rear and front cameras working?
Click to expand...
Click to collapse
Yes sir, all working good, I really recommend this ROM, is the one I'm using.

NekroWolfen said:
Yes sir, all working good, I really recommend this ROM, is the one I'm using.
Click to expand...
Click to collapse
I can also confirm that we'll get official support since one of the devs have a note 8. I think he'll make a new thread when its ready..

ryukiri said:
I can also confirm that we'll get official support since one of the devs have a note 8. I think he'll make a new thread when its ready..
Click to expand...
Click to collapse
Nice! I'm noticing a lot of movement in the gerrit, those are good news. Carbon was my one of my favorite with the Nexus 7 flo, and I'm still surprised by how well and smooth it is on the Note 8, to be honest I wasn't expecting this ROM here, hence why I'm so excited.

Rom Port Team Effort - Let's bring a diversity of roms to our P880.

Rom Port Team Effort
Hello P880 community.
This post has the purpose to put together a group of users / developers, who are willing to participate into bringing a different set of roms into our community.
These set of roms that I'm thinking, can range from complete Sense ports to more customized and maybe less popular roms (like ColorOS, LiGux, FlymeOS, FluidUI, etc..).
What's valid on this thread:
- CM / AOSP (any base we already have) themed (like Samsung TouchUI, Optimus, Blur, etc..). So you can grab any rom (with author authorization), theme it (i mean, not just shove an apk as default theme, I mean neat theming ).
- Ports from other devices (evert port needs to have clear authors permission to port it).
- All users are very welcome, everyone can participate, users with porting / developing skills are needed as well.
The idea is simple, we're not going to use this thread to post the work, this is just a thread to talk about possible projects.
We can start by listing which devices are hardware compatible and the port is "easily" possible.
Roms that can be used as a base for eventual future ports.
CM10.2 - thanks to laufersteppenwolf for compiling this build promptly for this purpose
http://goo.im/devs/laufersteppenwolf/CM10.2//cm-10.2-20140305-UNOFFICIAL-p880.zip
- - - - -
I strongly recommend the use of MultiRom for testing ports and other roms. That way you can maintain your working rom and whenver feeling adventurous you can without going through the hassle of backup / restore / yada yada yada that we are all too familiar with.
http://forum.xda-developers.com/showthread.php?t=2655988
- - List of Devices with hardware similar / close / identical to the 4X - -
- HTC One X
- HTC One X +
- More ??
- Possible roms to port:
Right now would be nice to see a OEM rom, such a touchwiz or Sense
Work in Progress
N/A available
(awaiting sugestions
So, what do you guys think? ? Any users with good porting skills ? I know we have good developers! Ideas? Sugestions?
Write away
A few guides from XDA - They may not be all you need to get the job done, but a LOT of important information is written here. Don't forget to thanks their authors
Guides / Tutorials
How to Port Roms by @saywhatt
How to Port Manufacturer Rom. by @GalaxyUser
How to port Stock/GB/CM7/CM9/ICS/CM10/JB Based ROMs by @Peteragent5
PS - Every work that is possible to port and if someone decides to invest time in it, it needs explicit authors permission.

Sure if a few people want a particular rom i can bring it to our device, but i would much prefer helping first time rom builders do this own their own then they can maintain it also

JoinTheRealms said:
Sure if a few people want a particular rom i can bring it to our device, but i would much prefer helping first time rom builders do this own their own then they can maintain it also
Click to expand...
Click to collapse
Well, I though about some sort of "voting" to bring a "specific" rom.
Personally, I'd love to have Sense on our device. I had two HTC's before and I miss that Sense interface :b
But far as I'm aware, isn't an easy thing to port.
About your offer, this thread stands mostly with learning. The idea is everyone being able to contribute and more users start bringing roms as their first times. So, thank you so much for lending your help and know how, I'm sure we'll have a fine list of possible ports and then we can talk about how to port them over
Everyone can ask for help and the idea is to everyone who is able to - help.

I like the idea of this thread, but what would also be quite usefull is a list of available ROMs and their maintainer(s).
Also the list should include ROMs someone is working on ATM, so it cannot happpen that 2 devs are working on the same ROM
However, your idea is good, but porting a ROM not from sorce is quite hard, and might need some smali "hacking" in order to resolve bugs.
But well, we're a community, and I guess we can help each other if needed, right

laufersteppenwolf said:
I like the idea of this thread, but what would also be quite usefull is a list of available ROMs and their maintainer(s).
Also the list should include ROMs someone is working on ATM, so it cannot happpen that 2 devs are working on the same ROM
However, your idea is good, but porting a ROM not from sorce is quite hard, and might need some smali "hacking" in order to resolve bugs.
But well, we're a community, and I guess we can help each other if needed, right
Click to expand...
Click to collapse
That's correct! :good:
The main point is to learn helping each other who knows in a month or so, today's whiners are tomorrow's contributors
Jokes aside, the first post will be edited in order to structure and add information.
I'm gonna start with compatible devices (the ones that allow porting in a easy way). Ideas? Besides the HTC One X ? I'm guessing the grouper (N7 2012) besides having the same soc, doesn't have the same screen...
PS - (this would be better with an experienced porter) - Maybe we could start with a easy one, and go on from there
I know we have "how to port" threads all around xda ,but each port is different so we can't use "one hat to fit them all" ... or a ring to rule them all, so we should treat each port differently.
However.. I'm gonna put some xda links about porting to bring some light into the matter for who is "new" on this subject... or for whom's feeling adventurous and can't wait to have "their" rom on "our" device

Oh yes finally, have been waiting for a thread like this for a long time me as well would love to see a sense rom on this phone
cm/aosp roms are not that hard to port most of the time u only need the same screen resolution for it to work. (ported a nexus s touchwiz rom over to my old lg optimus 2x) but would have loved to see some oem roms ported over as well, even though it would be a lot harder to port over. but as a wonderful community as this is we might be able to pull it off

MidnightDevil said:
That's correct! :good:
The main point is to learn helping each other who knows in a month or so, today's whiners are tomorrow's contributors
Jokes aside, the first post will be edited in order to structure and add information.
I'm gonna start with compatible devices (the ones that allow porting in a easy way). Ideas? Besides the HTC One X ? I'm guessing the grouper (N7 2012) besides having the same soc, doesn't have the same screen...
PS - (this would be better with an experienced porter) - Maybe we could start with a easy one, and go on from there
I know we have "how to port" threads all around xda ,but each port is different so we can't use "one hat to fit them all" ... or a ring to rule them all, so we should treat each port differently.
However.. I'm gonna put some xda links about porting to bring some light into the matter for who is "new" on this subject... or for whom's feeling adventurous and can't wait to have "their" rom on "our" device
Click to expand...
Click to collapse
You can add the HOX+ to the list as well
About porting, you need to seperate it in two halfs, porting from source, and "winzipping". TBH, I'm no fas of winzipping at all, but some stuff (like sense or TW) can only be winzipped...
BTW, if you need a 2nd/3rd post, just let me know

Personally, I'd like to see a GFlex or even better, a G2 (/mini) ROM for our phone (KitKat, of course )

This thread has potential
I'm new to this forum,so i dont know whats going on about roms,i see there are few devs working full time.
I think this is the best way to go: Port ALL open source roms,such as we have already,but we need them all.
Second,make a badass kernel,with all features and customizations,possibly 3.4.
Third,and just a suggestion,Make a community ROM?
I really like this thread,and i even more like this OX4 community,you all get along,and i've missed that,i was on a forum that has no frendly people whatsoever.
And,about the roms,the idea is awesome,but i always think of the clash of clans rule,max everything out before going on a higher level.
Sent from my LG-P880 using XDA Premium 4 mobile app

Regarding stock roms, it's an interesting thing, but I'm guessing stock roms are more trouble to port comparing to AOSP or CM.
I remember on the HTC Sensation forums the headaches sense brought to many developers and porters, the bunch of files that needed to be edited, kernel changes (aosp kernel is different from stock / sense kernel in that case).. so Stock roms are maybe harder to port fully.
Right now we have some apks from the G2 (lock screen, messaging, etc..), maybe someone will port some things from the Flex, but the whole base.. hum
@DeHuMaNiZeD , thanks for your reply
The other roms based of AOSP and CM, in my opinion, unless they're different (modded, themed, customized - etc..) but if not, if they are "clean" roms with no changes, then - we have them already I believe you'll agree. (Unless the idea is to test something).
A 3.4 kernel would be something, but perhaps a developer can shed some light here - what benefits would we have from a 3.4 kernel ?
A community rom is indeed long due. This thread is a different subject because it's about *several* roms, ports and tutorials, maybe you would like to create a thread here on General about that? You can start with votes (i believe it's a proper way to do it) with which base should we use (Cm, AOSP, Stock, etc..), included apps (or not), possibly aroma maybe and so on

DeHuMaNiZeD said:
This thread has potential
I'm new to this forum,so i dont know whats going on about roms,i see there are few devs working full time.
I think this is the best way to go: Port ALL open source roms,such as we have already,but we need them all.
Second,make a badass kernel,with all features and customizations,possibly 3.4.
Third,and just a suggestion,Make a community ROM?
I really like this thread,and i even more like this OX4 community,you all get along,and i've missed that,i was on a forum that has no frendly people whatsoever.
And,about the roms,the idea is awesome,but i always think of the clash of clans rule,max everything out before going on a higher level.
Sent from my LG-P880 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well, this sounds quite good, but the real problem is: this is a hell lot of work. Also, it needs resources. The sourcecode of a ROM is ~25-30GB. When it's compiled it's about double the size, and takes my PC (8 cores @ 4GHz) about 75Min to compile. Not to mention the time 'til the sources are Downloaded. My 500GB HDD is near to its limit very soon, so sooner or later I will need a new HDD, then I might be able to get another ROM ported, but right now, hard...
Also, why do you need a 3.4 kernel?
MidnightDevil said:
Regarding stock roms, it's an interesting thing, but I'm guessing stock roms are more trouble to port comparing to AOSP or CM.
I remember on the HTC Sensation forums the headaches sense brought to many developers and porters, the bunch of files that needed to be edited, kernel changes (aosp kernel is different from stock / sense kernel in that case).. so Stock roms are maybe harder to port fully.
Right now we have some apks from the G2 (lock screen, messaging, etc..), maybe someone will port some things from the Flex, but the whole base.. hum
@DeHuMaNiZeD , thanks for your reply
The other roms based of AOSP and CM, in my opinion, unless they're different (modded, themed, customized - etc..) but if not, if they are "clean" roms with no changes, then - we have them already I believe you'll agree. (Unless the idea is to test something).
A 3.4 kernel would be something, but perhaps a developer can shed some light here - what benefits would we have from a 3.4 kernel ?
A community rom is indeed long due. This thread is a different subject because it's about *several* roms, ports and tutorials, maybe you would like to create a thread here on General about that? You can start with votes (i believe it's a proper way to do it) with which base should we use (Cm, AOSP, Stock, etc..), included apps (or not), possibly aroma maybe and so on
Click to expand...
Click to collapse
For stock ROMs to work, it's your best bet to use AOSP as your base, and then look for what's missing/broken. This, however, means you need an AOSP base first to work with. And AOSP is not always the easiest thing to get properly running.
About the benefits of an 3.4 kernel: None IMO. All you get is a higher version-number, and that's it. We actually already have some 3.4 features backported, and also tweaked the 3.1 kernel quite a lot. So the actual benefits are all in your head (well, except you count bugs as benefits )
Community ROM? Meh, what for? We have so many ROMs already, so everyone should find the one that suits him/her best
BTW: Thread stuck

laufersteppenwolf said:
Well, this sounds quite good, but the real problem is: this is a hell lot of work. Also, it needs resources. The sourcecode of a ROM is ~25-30GB. When it's compiled it's about double the size, and takes my PC (8 cores @ 4GHz) about 75Min to compile. Not to mention the time 'til the sources are Downloaded. My 500GB HDD is near to its limit very soon, so sooner or later I will need a new HDD, then I might be able to get another ROM ported, but right now, hard...
Also, why do you need a 3.4 kernel?
For stock ROMs to work, it's your best bet to use AOSP as your base, and then look for what's missing/broken. This, however, means you need an AOSP base first to work with. And AOSP is not always the easiest thing to get properly running.
About the benefits of an 3.4 kernel: None IMO. All you get is a higher version-number, and that's it. We actually already have some 3.4 features backported, and also tweaked the 3.1 kernel quite a lot. So the actual benefits are all in your head (well, except you count bugs as benefits )
Community ROM? Meh, what for? We have so many ROMs already, so everyone should find the one that suits him/her best
BTW: Thread stuck
Click to expand...
Click to collapse
Why dont you set up that build server,i think they're cheap atm,or someone could borrow you? It would take a lot less time and effort. that's why i think offical rom support is important,once it's merged to the build bot,its their responsibility.
Sent from my LG-P880 using XDA Premium 4 mobile app

DeHuMaNiZeD said:
Why dont you set up that build server,i think they're cheap atm,or someone could borrow you? It would take a lot less time and effort. that's why i think offical rom support is important,once it's merged to the build bot,its their responsibility.
Sent from my LG-P880 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's not as easy as you might think
I do have access to a buildserver, however I only have 100GB as it's a shared one, so this is genious for official builds, or quick tests/ports. But it isn't ideal for the long terms.
Also, having it official doesn't mean you're done you need to update it, and also fix it when it's broken. 'cause when it's broken, it can mess up the whole build process of the buildbot
But in general, you're right, having it official does help a lot

{fd}ware said:
Does anyone of you have a link to the latest CM10.2 (Android 4.3) for our device?
It seems like it's not anymore on get.cm and I wanted to start porting a TouchWiz (Note 3) ROM to our phone when I have free time
Click to expand...
Click to collapse
I can't find them either, but I'm on a tablet so I can't look properly. 
 @laufersteppenwolf, do you have any *spare* 4.3 build?

MidnightDevil said:
I can't find them either, but I'm on a tablet so I can't look properly.
@laufersteppenwolf, do you have any *spare* 4.3 build?
Click to expand...
Click to collapse
LOL, no, I do not, but gimme a few hours and I'll have one
Syncing right now

laufersteppenwolf said:
LOL, no, I do not, but gimme a few hours and I'll have one
Syncing right now
Click to expand...
Click to collapse
Thank you

{fd}ware said:
BTW, did anyone tried to port a ROM this way? http://forum.xda-developers.com/showthread.php?t=2245786
Click to expand...
Click to collapse
Nope, I actually never "winzipped" a ROM

Lot of things to comment on here. Very good initiative I have to admit. I'm sure I'll have more ideas as the discussion evolves.
Similar hardware: You can add HOX+ as laufer said. Very minor differences are there only.
What I would personally prefer is TouchWiz, at least Nature UX 2.0, but new S5 UI is also really awesome. I liked Sense till 4.5, but 5.0+ versions are now out of my 'inner circles'. Especially what I don't like is the UI.
Few suggestions:
FlymeOS (from Meizu MX) - I got 2.0 booting last summer, but had touchkey issues (they were freezing the device lol) and never released it. Nobody ever booted 2.0+ on other Android devices yet.
Porting LG roms might be the best start, I think porting full Optimus G system wouldn't be that hard. Just a pain in the *ss merging process.
What we mainly need is same screen size (unless you wanna resizing 100+ apps ). Similar SoC is a good extra, but that's very limited. Also, it's better to avoid Qualcomm SoCs to port from, it's extremely hard, there are a lot of code changes in low-level code which just make the device get into deep segfault cycles. :cyclops: Even Exynos is easier to port from, trust me. I got SGS3 leaked 4.2 booting on the O4X last autumn.
Big issue we have to note: In 4.2, Google radically changed graphics libraries code. We have old, 4.1.2 blobs and those need hacks in libgui.so and libsurfaceflinger.so to function properly (in 4.4+ libEGL.so, libGLES_v1_CM.so and libGLES_v2.so also need a change). Here comes the problem: Manufacturers do change these libraries, mainly adding Wi-Fi display and HDMI support code which other blobs rely on. Of course we can't just replace these libs, graphics wouldn't function that way. Either we have to guess those function signatures and reimplement some stub in the code, or use new blobs, i.e. what I did in Omni. But y'all now those are not perfect _yet_.
Regarding newer kernels: If, I emphasize, IF it's properly ported, it would cause a noticeable effect on overall performance, battery life, etc. What do I mean by proper porting: All machine-specific code must be updated to Nvidia/Google upstream, no excuses! I don't say anything for sure, I didn't check it much, but kholk didn't do this merge. His kernel still uses 3.1 files with slight modifications to be 3.4-compatible. What I mean would be a very long and painful process, but would surely benefit after all. 3.4 has no Android branch, mainline Nvidia Tegra kernel does only have Linux support, it might be even harder. 3.10 is maintained by Google for Android, issues I have found so far: No graphics driver support for T2 and T3, have to forward-port it and I didn't find core Android components like wakelocks, earlysuspend, etc. Weird.
A little related story: I initially started working on MultiROM so I can test and port different roms while I can keep a stable rom for myself and there'd be no need for reflash then. That's what I can suggest. Use MultiROM, it has so many capabilities! Maybe it's better with kernel sharing so you don't have to wait for hardboot on every reboot (which one needs a lot if porting). @MidnightDevil you could add this to the OP maybe.
MidnightDevil said:
I can't find them either, but I'm on a tablet so I can't look properly.
@laufersteppenwolf, do you have any *spare* 4.3 build?
Click to expand...
Click to collapse
Here you are! Compiled this because wanted to start porting from Note 2, but finally worked on Omni more and abandoned it.
{fd}ware said:
BTW, did anyone tried to port a ROM this way? http://forum.xda-developers.com/showthread.php?t=2245786
Click to expand...
Click to collapse
That's way too generic unfortunately.
Quick suggestion for you port: Use Note 2 base with Note 3 features. Note 2 has the same resolution and you won't need to resize.

Adam77Root said:
Lot of things to comment on here. Very good initiative I have to admit. I'm sure I'll have more ideas as the discussion evolves.
Similar hardware: You can add HOX+ as laufer said. Very minor differences are there only.
What I would personally prefer is TouchWiz, at least Nature UX 2.0, but new S5 UI is also really awesome. I liked Sense till 4.5, but 5.0+ versions are now out of my 'inner circles'. Especially what I don't like is the UI.
Few suggestions:
FlymeOS (from Meizu MX) - I got 2.0 booting last summer, but had touchkey issues (they were freezing the device lol) and never released it. Nobody ever booted 2.0+ on other Android devices yet.
Porting LG roms might be the best start, I think porting full Optimus G system wouldn't be that hard. Just a pain in the *ss merging process.
What we mainly need is same screen size (unless you wanna resizing 100+ apps ). Similar SoC is a good extra, but that's very limited. Also, it's better to avoid Qualcomm SoCs to port from, it's extremely hard, there are a lot of code changes in low-level code which just make the device get into deep segfault cycles. :cyclops: Even Exynos is easier to port from, trust me. I got SGS3 leaked 4.2 booting on the O4X last autumn.
Big issue we have to note: In 4.2, Google radically changed graphics libraries code. We have old, 4.1.2 blobs and those need hacks in libgui.so and libsurfaceflinger.so to function properly (in 4.4+ libEGL.so, libGLES_v1_CM.so and libGLES_v2.so also need a change). Here comes the problem: Manufacturers do change these libraries, mainly adding Wi-Fi display and HDMI support code which other blobs rely on. Of course we can't just replace these libs, graphics wouldn't function that way. Either we have to guess those function signatures and reimplement some stub in the code, or use new blobs, i.e. what I did in Omni. But y'all now those are not perfect _yet_.
Regarding newer kernels: If, I emphasize, IF it's properly ported, it would cause a noticeable effect on overall performance, battery life, etc. What do I mean by proper porting: All machine-specific code must be updated to Nvidia/Google upstream, no excuses! I don't say anything for sure, I didn't check it much, but kholk didn't do this merge. His kernel still uses 3.1 files with slight modifications to be 3.4-compatible. What I mean would be a very long and painful process, but would surely benefit after all. 3.4 has no Android branch, mainline Nvidia Tegra kernel does only have Linux support, it might be even harder. 3.10 is maintained by Google for Android, issues I have found so far: No graphics driver support for T2 and T3, have to forward-port it and I didn't find core Android components like wakelocks, earlysuspend, etc. Weird.
A little related story: I initially started working on MultiROM so I can test and port different roms while I can keep a stable rom for myself and there'd be no need for reflash then. That's what I can suggest. Use MultiROM, it has so many capabilities! Maybe it's better with kernel sharing so you don't have to wait for hardboot on every reboot (which one needs a lot if porting). @MidnightDevil you could add this to the OP maybe.
Here you are! Compiled this because wanted to start porting from Note 2, but finally worked on Omni more and abandoned it.
That's way too generic unfortunately.
Quick suggestion for you port: Use Note 2 base with Note 3 features. Note 2 has the same resolution and you won't need to resize.
Click to expand...
Click to collapse
Dang, you've beaten me but mine's as fresh as it could be
HERE you guys go, for all who need the newest CM10.2

laufersteppenwolf said:
Dang, you've beaten me but mine's as fresh as it could be
HERE you guys go, for all who need the newest CM10.2
Click to expand...
Click to collapse
Just don't delete the sources, you might need them in the close future.
I think we should create a schedule about what to do. As you all know, good buildings all have good grounding. So let's get started from the very beginning I say. First fix remaining bugs in MultiROM, then create a unified kernel so users don't have to choose. Very likely this is not possible as people think different so just make all kernels hardboot compatible. After these we have a solid base for starting all the work. Of course this cannot be done if not everybody is involved. Both devs and users should share a part in this magnificent journey.
(High expectations, I know. )
Sent from my OmniROM-powered LG Optimus 4X HD

Why the KK baseband for LP ROMs?

I'm not sure if it's just a D415/410/405 thing or if it's a KitKat to Lollipop thing. I'm not new to rooting, flashing, and customizing, but I'm in no way a dev either, so I was wondering why so many ROMs for our phone need a KK baseband? Alternatively, if I'm already on a debloated but otherwise stock LP ROM do I need to downgrade to the KK baseband first or can I flash over?
Note: the last time I was playing around with flashing ROMs was on a Galaxy Exhibit II 4G and I bumped it up from 2.3.6 to 4.4.2 without having to play with basebands. This is why the confusion.
Thanks in advance for any advice and answers.

I guess because no one really is maintaining LG L90 device sources.
For a log time there was Quarx but his device got broken so he's not really developing it anymore. He's only compiling CM12.1 from sources but I'm pretty sure it's all done by computer, fully automatically. After Quarx there was BigMajster who if I'm not wrong was the first one to introduced L90 owners to Lollipop. He was a great bug-hunter and he published a lot of great fixes for different L90 variants. If I'm not mistaken he was the one who fixed Double-tap-to-wake feature and storage 190MB bug for D415. He was a great developer until he disappeared somewhere in January I think. One day he was gone without saying anything. For some time I thought that something happened to him but after a little research I found out his real name and that he's pretty much alive and well. I didn't contact him though. I thought that if he left the way he did there was no point.
Other developers (I will not mention any names) are no really maintaining device sources. Most of them are just busy with their ROMs they are developing. The same bugs are present in all customROMs and no one is working to fix them. After months there is still no stable kernel for custom Lollipop, even though almost all of the current developing projects are based on Lollipop. Getting developers to work together, also didn't worked out. I probably forgot about some others important developers that are not with us anymore so sorry if I skipped anyone.
To be exactly clear. I don't make any accusations nor complaining. I just share my opinion with you, saying how I see things around here. I tried to state only facts, without my personal opinions but you should consider this whole statement as one.

A well thought out and thorough answer. Thank you for that. Any input on if I can flash from a stock LP base band or would I have to downgrade? That's about the only thing that makes me nervous and preventing me from trying 5.1.1 despite the random FCs

If you're on stock Lollipop and want to try CustomROM. Then you will have to downgrade to KitKat using KDZ or install bootstack.
Sent from my LG-D405 using XDA Free mobile app

@Xemidra
Keep in mind that NOONE of you pays us. You have no idea what we're doing on the source.
Quarx started with the device tree, kernel and vendor, so we don't know all what he did and how he did. We are working all or going to school(?), so we don't have so much time to rebase everything.
Also porting a Lollipop kernel from LGE source needs plenty much time.
In addition there is no "General source" to work on and maintain. All in all it's pretty cheeky to say something like we're doing nothing.

GrinningFerret said:
@Xemidra
Keep in mind that NOONE of you pays us. You have no idea what we're doing on the source.
Quarx started with the device tree, kernel and vendor, so we don't know all what he did and how he did. We are working all or going to school(?), so we don't have so much time to rebase everything.
Also porting a Lollipop kernel from LGE source needs plenty much time.
In addition there is no "General source" to work on and maintain. All in all it's pretty cheeky to say something like we're doing nothing.
Click to expand...
Click to collapse
Well, like I said it's was my opinion. That's how I see things around here.
I didn't mean any disrespect. I know that you don't get paid for your work so I don't have any right demanding anything from you and I don't but you also can't say that the current situation is a result of devs not getting paid.
I also put some work time into L90. I did made available all KDZ for Lollipop and some for KitKat. I made different versions of BOOTSTACKs and I made FlashableSTOCK. All that take a lot of my time, energy and also my internet connection, power supply etc. No one paid me for it. I basically paid for it from my own pocket. I'm not complaining. It's just how it is.
You can't get mad because someone did something not the way you wanted him to do while he did it for free.
At the same time you can't be mad at the current situation and say it's because someone didn't pay you to make it better.
That's my opinion.

@Xemidra
The problem isn't that we don't get paid for it - its' our hobby. But the point is that you're telling around that we do nothing on the device source, which is just wrong.

GrinningFerret said:
@Xemidra
The problem isn't that we don't get paid for it - its' our hobby. But the point is that you're telling around that we do nothing on the device source, which is just wrong.
Click to expand...
Click to collapse
I might have been wrong about the input in device sources.
Good you've stepped up and corrected me.
Sorry for the misunderstanding.

@Xemidra
Nevermind.

Sorry if this ruffled any feathers, guys. This was meant more to be an end user wanting to understand the dev and background process to be able to contribute and help more than a spirited discussion about who does what.
In any case, I thank you both for the information and the input. In the end I do understand a bit more.