Database Develop

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

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!
​

Reserved

Also Reserved

Great work! Will try it out once finished modding it for XT905.
PS: Why not add it to DevDB?

levizx said:
Great work! Will try it out once finished modding it for XT905.
PS: Why not add it to DevDB?
Click to expand...
Click to collapse
I was told none of these moto's have DevDB. I've never used it myself, might be why haha.

arrrghhh said:
I was told none of these moto's have DevDB. I've never used it myself, might be why haha.
Click to expand...
Click to collapse
Yeah, maybe that
Quick question: I'm noticing quite apparent banding on my screen, especially on white background. And occational white noise splash while turning screen on, is it normal or just because I'm using it on XT905? Seems to be kernel related. I'm actually testing out both Gummy and Carbon, both have the same problem.

levizx said:
Yeah, maybe that
Quick question: I'm noticing quite apparent banding on my screen, especially on white background. And occational white noise splash while turning screen on, is it normal or just because I'm using it on XT905? Seems to be kernel related. I'm actually testing out both Gummy and Carbon, both have the same problem.
Click to expand...
Click to collapse
This is not made for xt905, so I'm not sure... Do you know how that device differs? I'm not aware of any forum for that device...
Edit - just checked, seems CM doesn't support it either? How does CM run?

arrrghhh said:
This is not made for xt905, so I'm not sure... Do you know how that device differs? I'm not aware of any forum for that device...
Edit - just checked, seems CM doesn't support it either? How does CM run?
Click to expand...
Click to collapse
Should be almost the same since this is just the GSM version of XT907. By apparent I actually mean noticable by human eyes (on while background). It's has to have something to do with the buffer or refresh rate.
Actually all ROMs with minor modification works fine. Not as smooth as I'd hope ie not smoother than debloated stock 4.1, but all things work, sans the occasional white-noise splash while turning screen on and the annoying band morie pattern.
Another question, do you have any plans ditching the emulated sdcard? It's quite pointless with just about 4GB after a full wipe and you have to share the space with apps.

I can't find out the download package of the xt907, is that true? I love carbon team, the black theme looks really nice

allen_ho said:
I can't find out the download package of the xt907, is that true? I love carbon team, the black theme looks really nice
Click to expand...
Click to collapse
We are working on migrating to a new download site + mirror... as our infrastructure was not up to the task (downloads were REALLY slow).
Hopefully the new setup can handle the load! I'll upload the last build to a mirror.

The banding issue affects all 4.4 roms. I don't know the technical details but it seems 3D acceleration is about 50% slower than 4.2 roms. Since nearly everything is composted in the GPU now, everything seems to suffer from poor frame rates and other graphical anomalies.

which is going to be better as a daily driver this one, or the JB?

allenrb2 said:
which is going to be better as a daily driver this one, or the JB?
Click to expand...
Click to collapse
Personally I would not recommend anything above 4.2.2/CM10.1 at this stage.
It's fine if you want a test drive, and it's stable enough to be a daily driver.
But it's not as fast and feature-complete. Unless you desperately want the new things (ART etc),
you might have to wait for a while (after official kk for RAZR M/HD) before KitKat roms really take off.

levizx said:
Personally I would not recommend anything above 4.2.2/CM10.1 at this stage.
It's fine if you want a test drive, and it's stable enough to be a daily driver.
But it's not as fast and feature-complete. Unless you desperately want the new things (ART etc),
you might have to wait for a while (after official kk for RAZR M/HD) before KitKat roms really take off.
Click to expand...
Click to collapse
I don't know, I prefer the 4.4 ROMs over 4.2. Personally faster for me. It's just right now if people want a lot of features there aren't going to be as many in 4.4 as there are for 4.2, though that will change. It's only because obviously JB has been out longer, but honestly feature-wise things are catching up.

flashing kitkat, because jb was force close city, hopefully its stable

motoroid7 said:
I don't know, I prefer the 4.4 ROMs over 4.2. Personally faster for me. It's just right now if people want a lot of features there aren't going to be as many in 4.4 as there are for 4.2, though that will change. It's only because obviously JB has been out longer, but honestly feature-wise things are catching up.
Click to expand...
Click to collapse
KitKat is buggier than JB4.2 with our dated kernel/driver, that's a fact. For me the banding issue is a showstopper, period. Feature-wise, I do agree it's getting better, but we live in the moment don't we? Like I said, it's cool if you use it just to test it out, you might even be of help to the devs in identifying bugs.
But if you are asking the question "should I use this as my daily driver", the answer is probably no, otherwise you wouldn't be asking the question in the first place.

the kitkat rom seems to be running ok so far

arrrghhh said:
We are working on migrating to a new download site + mirror... as our infrastructure was not up to the task (downloads were REALLY slow).
Hopefully the new setup can handle the load! I'll upload the last build to a mirror.
Click to expand...
Click to collapse
I found the KK nightly as the same path on GOO.im for JB, is it the same team working on?
http://goo.im/devs/carbon/xt907/nightly/

allen_ho said:
I found the KK nightly as the same path on GOO.im for JB, is it the same team working on?
http://goo.im/devs/carbon/xt907/nightly/
Click to expand...
Click to collapse
We are no longer using goo.im. I might've missed a nightly job, I'll doublecheck.
Edit - perhaps someone already fixed it... uploads are going to our new mirror.

Is there an error with the reported signal in the battery options? Cell standby shows very high percentage time without signal, upwards of %50. On stock based roms I have never seen more than %1 time without signal.

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

What ROM would you like to see/use on your L90?

Alright, I'll try to keep this short and simple. I have been developing for various devices over the last 2 years (Galaxy Captivate, Galaxy S2, Nexus 4, Kindle Fire Lineup, etc) The Nexus 4 was my main phone, up until recently. I dropped the phone getting out of the car one night, and now the touch screen is completely unresponsive. So I decided to grab a cheap replacement for the time being, while I order a new screen for the N4. I see some devs have gotten several custom ROMs running for this device, awesome job! When I got this phone, I had no idea it would be developer friendly, what a surprise. This lead me to the decision to start compiling something for the L90. What I want to know from everyone here, is what ROM would you like to see on your device? I've gathered up several choices, so I'd like to start a little poll.
My intentions are to either compile something from source, and frequently update it here for everyone. Or to fork over CM, and customize it myself (via cherry-picks, custom wallpapers, optimized toolchains, performance enhancements, etc) However these builds would be less frequent, unless some people were willing to contribute. If so, then feel free to let me know! Also, please ask as many questions, or make as many suggestions as you want. I'm trying to get my post count up lol. All the development I've done prior to this, has been mainly released on Google+. I figured I would target a larger audience here for now though, until I can create a community specifically for the L90 on G+. I'd greatly appreciate any and all feedback!

Great to see such motivated will. What I'd like to see on L90 is completely stable LP rom, doesn't really matter which one, but out of two I had chance to use - which is CM and Ressurection Remix - I'd choose RR. Dunno if devs of roms such as AOKP and billions of others are making/are planning to make LP versions though

agreed, it would be nice to see a fully functioning ROM whether it be kitkat or lollipop. When i say stable i mean video playback and recording working camera quality back to normal (on all roms their is a lack or clarity,crisp,and focus) and good memory management. If you can get those working i don't care what kind of rom is is

cataclysm rom

Longpinky said:
agreed, it would be nice to see a fully functioning ROM whether it be kitkat or lollipop. When i say stable i mean video playback and recording working camera quality back to normal (on all roms their is a lack or clarity,crisp,and focus) and good memory management. If you can get those working i don't care what kind of rom is is
Click to expand...
Click to collapse
What a nice feeling not having D415 thus those problems...
Also, I think it is impossible to get stock LG camera libs to get to work on custom roms, or - at best - it would have take a hell of time. So I guess quality will stay like this forever...

I appreciate all the feedback so far! I'm an android enthusiast for sure. Ever since I used my first custom ROM, which was CM 7 if I'm not mistaking, I fell in love. From there, I spoke with a few developers I had met, and started learning everything about compiling ROMs. They were a huge help, and they also pointed me to some great guides online. After lots of trial and error, I was able to get my first source built ROM booted up, and running. From there on out, I was hooked lol. With that being said, I'd love to build some new custom ROMs for all the L90 users here. Also I have a few questions before I start the process, so if any L90 dev's see this, send me a PM or something. Just curious about a few things, such as unified builds and what not. I'm going to go ahead and set my build machine up, and get it ready to start compilation. But in the meantime, keep the comments/ideas/suggestions coming in! Also, the poll will be up for 14 days, but I'm sure I'll start building something before then

omnirom

I want a custom kernel with OC and other features.

Just a quick update for everyone. I installed LXLE on a laptop to get my builds going. Unfortunately that distro brought in a lot of headaches. And on top of that, I couldn't get any source to finish a simple sync. (Tried mokee, and cm) I'm not sure why, but my best guess was it had something to do with that screwy LXLE distro. Now I just finished putting Mint on the laptop, so I'll post an update again once I see if the repo sync command will finish without hanging up at 99%

Could you start by a AOSP one? Then go for custom ROM.
Sent from my LG-D405n using XDA Free mobile app

MOKEE

Modded stock kernel
A good OC-UC UV kernel would be good for the stock kitkat, i dont need a full rom, its very good with xposed framework! Thanks for your work!

Update
Alright everyone, I got all the issues I was having fixed. Just took some time. Right now, I have MoKee compiling(android version 5.1.0_r5) for the L90. Once it is complete, I'll flash it to make sure it boots up and everything. After that I'll leave a link here for anyone to flash if they want. This is strictly going to be straight MoKee from source, no changes on my end yet. Once I know everything compiles correctly, I'll start optimizing the build and trying to fix any bugs I can. As well as cherry pick features and what not. I'm also looking into the kernel config files so I can try to include a custom kernel(OC/UC and UV) I will start a new thread when all this begins though. Thanks for the support and suggestions so far!

Which L90 do you have? D415?
Sent from my LG-D415 using XDA Free mobile app

Longpinky said:
Which L90 do you have? D415?
Sent from my LG-D415 using XDA Free mobile app
Click to expand...
Click to collapse
Yea, I have the D415

Update
So the build almost finished yesterday, but I ran into an OOM error right at the end. I was using an old dual core laptop with 3gb of RAM, which worked fine with JB and KK etc. So I gave it another gig of RAM, and put a lighter desktop environment on it. Everything should go fine from here, see you all soon with another update!

CaptivateKing said:
So the build almost finished yesterday, but I ran into an OOM error right at the end. I was using an old dual core laptop with 3gb of RAM, which worked fine with JB and KK etc. So I gave it another gig of RAM, and put a lighter desktop environment on it. Everything should go fine from here, see you all soon with another update!
Click to expand...
Click to collapse
well done

Success!
The MoKee ROM compiled successfully! Now I will fork over repositories to my github, and start the customizations/bug fixes. It will take a little bit before builds start rolling out, but I will start a new thread for that. For those of you that would like to try out the MoKee build, I will upload it and leave a link here shortly. This is straight from source, no changes at all (except what was necessary to get it to compile correctly) It will have all the same issues the latest cm has (camera focus, etc.) I built it from quarx's unified device tree, so it should work on d405, d410, d415. Thanks for everyone's patience!

CaptivateKing said:
The MoKee ROM compiled successfully! Now I will fork over repositories to my github, and start the customizations/bug fixes. It will take a little bit before builds start rolling out, but I will start a new thread for that. For those of you that would like to try out the MoKee build, I will upload it and leave a link here shortly. This is straight from source, no changes at all (except what was necessary to get it to compile correctly) It will have all the same issues the latest cm has (camera focus, etc.) I built it from quarx's unified device tree, so it should work on d405, d410, d415. Thanks for everyone's patience!
Click to expand...
Click to collapse
That's great man thanks
Sent from my LG-D415 using XDA Free mobile app

Longpinky said:
That's great man thanks
Sent from my LG-D415 using XDA Free mobile app
Click to expand...
Click to collapse
No problem!

Willing to pitch in $10 for any developer(s) that can bring Pixel Experience ROM!!!

Who is with me? I am committing to donating as long as the ROM is a proper port/build and is stable and reliable enough to be a daily driver.
Let's see who else can commit to donate!
Can't stand MIUI!!!!

tdot.loco said:
Who is with me? I am committing to donating as long as the ROM is a proper port/build and is stable and reliable enough to be a daily driver.
Let's see who else can commit to donate!
Can't stand MIUI!!!!
Click to expand...
Click to collapse
this is not how it works... devs on xda are no professionnals, they build roms on their spare time, after school or work hours.
The main problem is not to build any rom, but is to make sure it is usable and stable.
Patience is a vertue

Forgive me, but I don't understand why people are waiting for custom ROMs to show up when a GSI is working perfectly fine (in a better state than the current build of LOS)
OP, what is stopping you from using a GSI. You can continue to use the vendor image from your stock MIUI build while swapping out top-level GSIs

hmm for me i cannot use GSI roms. it says 'wrong pin' whenever i set pin/pattern.

tdot.loco said:
Who is with me? I am committing to donating as long as the ROM is a proper port/build and is stable and reliable enough to be a daily driver.
Let's see who else can commit to donate!
Can't stand MIUI!!!!
Click to expand...
Click to collapse
xD i wont take 10$ but i can build PE

letsmakecakes said:
xD i wont take 10$ but i can build PE
Click to expand...
Click to collapse
$10 is actually nothing in comparison to the hard work that is required to build any ROM whatsoever, and that's why we must be grateful to have you building lOS for us for FREE!

i will pay $100

Guys I have tremendous respect for all devs, of any device. I've owned myself from LG G2, G3, G4, Samsung S2, HTC M7 all the way to Samsung Note 8. I appreciate it all the hard work they put in. The reason why I took the initiative to incentive the very few ones that are following/owning our devices right now is because of that very same reason, there is little attention to this device.
I know most of them do this because it's a hobby or a side thing or to get some exposure/experience, but I know money is not the greatest motivator to them at all.

satadi said:
Forgive me, but I don't understand why people are waiting for custom ROMs to show up when a GSI is working perfectly fine (in a better state than the current build of LOS)
OP, what is stopping you from using a GSI. You can continue to use the vendor image from your stock MIUI build while swapping out top-level GSIs
Click to expand...
Click to collapse
I heard someone say there is still lots of bugs with LOS GSI on our device.
Can you confirm it is bug free on RN7 China version?

Still waiting for this

Pixie dust is out for treble.
Load it that way.
Edit:
https://forum.xda-developers.com/pr...evice-development/9-0-pixel-dust-pie-t3862484
Lots of other GSI images as well!
I am waiting three hundred hours to unlock bootloader, or I would give you more specific instructions.
Basically flash GSI image to your system partition, threads will include more information .

Hi OP, no offense, but offering $10 for personal rom request like this really cheapen out the dev's work. Porting a custom ROM isn't an easy work, and offering them this small amount of money is offensive.
Either wait until someone ported PE then donate to the dev, or join some lavender development group on telegram and throw some hundred bucks until someone's agreed to built you a rom.

why don't you want to use the pe already built for our device? this rom has been around for months yet you lot all appear to have never seen the thread.
https://forum.xda-developers.com/redmi-note-7/development/rom-pixel-experience-t3930709
official status means absolutely *nothing*. if it works, it works. official status doesn't automagically make it 100% stable either.

NightRaven49 said:
why don't you want to use the pe already built for our device?
https://forum.xda-developers.com/redmi-note-7/development/rom-pixel-experience-t3930709
Click to expand...
Click to collapse
Was about to make the same observation, I have just installed this Rom on my note 7 and seems to be bug free so far and even with small differences works just as well as the excellent Pixel expierence by jhenrique09 on my note 5. Give it a go!!

eh my bad, just realised this thread was started a couple of weeks before the initial pe rom thread was started. doesn't really seem to get much updates though.

Question Why is DT2W not yet implemented on any custom ROMs for juice devices?

Hi everyone. A lot of great custom ROMs have been developed for juice devices from the past few months (cheers to all the devs). However, the DT2W feature is still missing from the party, which I have always used way back on stock MIUI. Moreover, other devices seem to not have a problem with DT2W even when installing custom ROMs.
Can anyone explain what's the matter with this? Why is it difficult to implement? Are we still gonna have DT2W feature in the future updates?
I don't have a deep understanding of ROM development, so please enlighten me with the lore. Thanks!

dinsel said:
Hi everyone. A lot of great custom ROMs have been developed for juice devices from the past few months (cheers to all the devs). However, the DT2W feature is still missing from the party, which I have always used way back on stock MIUI. Moreover, other devices seem to not have a problem with DT2W even when installing custom ROMs.
Can anyone explain what's the matter with this? Why is it difficult to implement? Are we still gonna have DT2W feature in the future updates?
I don't have a deep understanding of ROM development, so please enlighten me with the lore. Thanks!
Click to expand...
Click to collapse
Things don't happen in a day or with snap of fingers, it takes time. And Gagan, Joboy, Anurag have been working on OSS Vendor which is about to get finished. Kindly wait or switch back to Meme UI also, don't compare development of different devices, every device is not the same and I mean what do you think, how old our custom development community is.
Kindly cooperate if you cannot contribute.

AvinashD1010 said:
Things don't happen in a day or with snap of fingers, it takes time. And Gagan, Joboy, Anurag have been working on OSS Vendor which is about to get finished. Kindly wait or switch back to Meme UI also, don't compare development of different devices, every device is not the same and I mean what do you think, how old our custom development community is.
Kindly cooperate if you cannot contribute.
Click to expand...
Click to collapse
Lol I'm just genuinely curious so i was actually hoping for a more technical explanation but i guess this kind of stuff would truly take a lot of time. Ok thanks

dinsel said:
Lol I'm just genuinely curious so i was actually hoping for a more technical explanation but i guess this kind of stuff would truly take a lot of time. Ok thanks
Click to expand...
Click to collapse
Lmao read logs for your technical explanation... And this needs to get fixed on the kernel side, Javashin has started working on it already.

any progress?