[ROM][AOSP][Nightly/Release] CarbonRom KitKat [moto_msm8960] - Droid RAZR M Android Development

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.

Related

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

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!

[ANNOUNCEMENT] New developing team for P8 Lite

Since people say on every rom released with OpenKirin source codes that there are same bugs on every rom, I joined forces with some of my friends and in result=> KirinMixTeam Development, name's not fully decided, so it may change, but that's not important.
The important thing is that we already started working on a new P8 Lite source code: https://github.com/KirinMixTeam/device_huawei_hi6210sft/tree/AOKP-7.1.2 ,there are much more bugs to fix, I'm sure ril will not work on first hand, at least hopefully wifi works.
Our team goal is to develop for as much as we can, and now that I've finnaly repaired my computer I have 2TB of free space to develop on.
Reminder: Do not take our team as a rival to OpenKirin or haky86, or any other developers, we do not want to do that, take this as some good news that P8 Lite will get even more developers to work on its platform and others!
Also, since for now we're just 3 members in the team, maybe one of you want to get in. PM me or @AymenDe7 for further information, but if you think you are not ready for this please do not fill our inbox worthless.
P.S. Do not overhype already, wait until at least a bootable rom to be sure that our source code works. Tommorow I'm already testing first build of AOKP 7.1.2, so we'll keep you updated!
Thank you.:good:
Wow so P8Lite isn't dead
Nice news !!
I just want to get a stable rom that consists no bugs, and as stable as huawei's stock firmware. I've tried all of the custom roms and there are lots of annoying bugs such as,
slow and laggy interface,
poor app performance
720p 60fps playback issue
headset issue,
low download speeds on my mobile network etc. etc.
I've now converted back to stock and unrooted firmware, I will be waiting and checking for a %100 stable custom rom. good to see you're determined to make a good rom, good luck and thank you.
tayfuntb1393 said:
I just want to get a stable rom that consists no bugs, and as stable as huawei's stock firmware. I've tried all of the custom roms and there are lots of annoying bugs such as,
slow and laggy interface,
poor app performance
720p 60fps playback issue
headset issue,
low download speeds on my mobile network etc. etc.
I've now converted back to stock and unrooted firmware, I will be waiting and checking for a %100 stable custom rom. good to see you're determined to make a good rom, good luck and thank you.
Click to expand...
Click to collapse
Nor OpenKirin roms nor haky86's are slow, they get almost all of them 30K in antutu. Problem with 720p 60fps is related to codecs, but I don't know what causes the headset issue.
XTutorials said:
Since people say on every rom released with OpenKirin source codes that there are same bugs on every rom, I joined forces with some of my friends and in result=> KirinMixTeam Development, name's not fully decided, so it may change, but that's not important.
The important thing is that we already started working on a new P8 Lite source code: https://github.com/KirinMixTeam/device_huawei_hi6210sft/tree/AOKP-7.1.2 ,there are much more bugs to fix, I'm sure ril will not work on first hand, at least hopefully wifi works.
Our team goal is to develop for as much as we can, and now that I've finnaly repaired my computer I have 2TB of free space to develop on.
Reminder: Do not take our team as a rival to OpenKirin or haky86, or any other developers, we do not want to do that, take this as some good news that P8 Lite will get even more developers to work on its platform and others!
Also, since for now we're just 3 members in the team, maybe one of you want to get in. PM me or @AymenDe7 for further information, but if you think you are not ready for this please do not fill our inbox worthless.
P.S. Do not overhype already, wait until at least a bootable rom to be sure that our source code works. Tommorow I'm already testing first build of AOKP 7.1.2, so we'll keep you updated!
Thank you.:good:
Click to expand...
Click to collapse
Super!
If i can help in something, just ask!
PS: Maybe i can learn something from you guys!
:good:
.
persona78 said:
Super!
If i can help in something, just ask!
PS: Maybe i can learn something from you guys!
:good:
.
Click to expand...
Click to collapse
How you can help if you only work on stock rom Don't take it bad! or maybe I missing something
persona78 said:
Super!
If i can help in something, just ask!
PS: Maybe i can learn something from you guys!
:good:
.
Click to expand...
Click to collapse
Thank you! We'll count on you!
I, actually... want you in the team, please send me a PM, so we can talk more.
Thank you.
I would be interested to learn more about android. I'm not excepting you to hold my hand through android basics. But if there is anything i can do. Feel free to pm me. I have some kinda google skills
Good news, best wishes!! ✌
I learn how to upstream kernels, not helpful for you, but eh maybe i will question some things in the future.
Thank you so much for your support!
For your interest, but not interesting, I'm already compiling AOKP 7.1.2 for Nexus 6P. After that will get back to P8 Lite.
wait wait best ROMs kkk
Guys dont take me wrong if any of you are willing to try ROM building but cant do it due to various reasons like Computing power or HDD space or slow Internet speeds etc.., . Here is the best alternative even a small mobile is enough to build the ROM.
https://forum.xda-developers.com/chef-central/android/guide-how-to-build-rom-google-cloud-t3360430
I have compiled aokp 7.1.2 yesterday but it's stuck on boot logo and i don't know why
redknight65 said:
I have compiled aokp 7.1.2 yesterday but it's stuck on boot logo and i don't know why
Click to expand...
Click to collapse
For P8 Lite?
@XTutorials
I wish you luck but in my opinion you (and we as community) should focus on fixing bugs in OpenKrirn's source rather than making a new ROM from scratch
Actually on their nougat we just need video recording, 60fps videos (here emui 4.1 kernel and blobs can fix this I think), GPS and deepsleep to have a fully functional ROM (I don't count dual SIM).
HWC is unfortunately a different story...
That's the best option, we don't want other roms, we want fixes for current ones, like thst cpu fix... Maybe GPS, deepsleep, wifi fix etc
dominj97 said:
@XTutorials
I wish you luck but in my opinion you (and we as community) should focus on fixing bugs in OpenKrirn's source rather than making a new ROM from scratch
Actually on their nougat we just need video recording, 60fps videos (here emui 4.1 kernel and blobs can fix this I think), GPS and deepsleep to have a fully functional ROM (I don't count dual SIM).
HWC is unfortunately a different story...
Click to expand...
Click to collapse
Unfortunately, in my opinion I don't think is right to just continue OK source code and post it as yours.
How it is said, better do it slowly than doing it fast and bad.
I know you really want asap a fully-stable ROM, and we put a lot of effort in doing that. Expect a booting ROM in 1-2 weeks from now.
Thank you for understanding!
XTutorials said:
Unfortunately, in my opinion I don't think is right to just continue OK source code and post it as yours.
How it is said, better do it slowly than doing it fast and bad.
I know you really want asap a fully-stable ROM, and we put a lot of effort in doing that. Expect a booting ROM in 1-2 weeks from now.
Thank you for understanding!
Click to expand...
Click to collapse
I'm not talking about posting it as yours I'm talking about contributing to their project.
Pls don't get me wrong I know it's hard to develop on this phone (and we don't pay you for it) but you will probably also have problems with your project (maybe even the same as OpenKirin and XePeleato when there was no OpenKirin yet). What's the reason of doing the same job again?
dominj97 said:
I'm not talking about posting it as yours I'm talking about contributing to their project.
Pls don't get me wrong I know it's hard to develop on this phone (and we don't pay you for it) but you will probably also have problems with your project (maybe even the same as OpenKirin and XePeleato when there was no OpenKirin yet). What's the reason of doing the same job again?
Click to expand...
Click to collapse
Well, I'm working for the first time source codes ( working seriously, not just edit BoardConfig and other .mk's) and I need some practicing and learning, so first ROM will come out harder, if you let me practice and learn then I will fix bugs and build roms faster.
Thank you.

Categories

Resources