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 official Carbon downloads and further information such as features, changelog, and FAQ can be found on our website.
Carbon Downloads
For mondrianwifi downloads:
CARBON-KK-UNOFFICIAL-20140429-0035-mondrianwifi.zip
CARBON-KK-UNOFFICIAL-20140612-2345-mondrianwifi.zip
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
Hey folks.
None of this would have been possible without the hard work of @crpalmer - he got the device started on CM, and did 99.999% of the hard work for this device bringup!!
I have done some basic tests - it boots!
The stock keyboard seems to be missing a lot - I'm sure installing an alternative will solve that issue. I'm also getting a lot of FC's from Google Keyboard.
CarbonFibers is not happy, going to look into that.
Should be on par with CM. Let me know what you find!
Thanks for developing for this device, will flash when I get a chance.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Does this ROM remove multi-window?
KrazyAttack said:
Does this ROM remove multi-window?
Click to expand...
Click to collapse
Well I suppose if you are comparing to stock, yes, it does "remove" multi-window...
Just remember, this ROM is not based (loosely or otherwise) on any Samsung ROM. It's built from source AOSP base with patches from all over the place.
Makes me wonder where Omni left off with their multi-window. I haven't been following it lately.
Thanks so much for the time and work you put into this. I love seeing more roms for this great device!
Sent from my SM-T320 using Tapatalk
arrrghhh said:
Well I suppose if you are comparing to stock, yes, it does "remove" multi-window...
Just remember, this ROM is not based (loosely or otherwise) on any Samsung ROM. It's built from source AOSP base with patches from all over the place.
Makes me wonder where Omni left off with their multi-window. I haven't been following it lately.
Click to expand...
Click to collapse
Yeah I assumed it did, I wish I could run a nice feature rich rom but I use multi window probably 80% of my time on this tablet. I almost always have YouTube on one half and chrome the other like right now haha. Wish there was a way to keep it or an alternative but thanks anyways.
Luckily my nexus 5 feeds my rom itch nicely. For now I'll just stay with CleanROM.
arrrghhh said:
Hey folks.
None of this would have been possible without the hard work of @crpalmer - he got the device started on CM, and did 99.999% of the hard work for this device bringup!!
I have done some basic tests - it boots!
The stock keyboard seems to be missing a lot - I'm sure installing an alternative will solve that issue. I'm also getting a lot of FC's from Google Keyboard.
CarbonFibers is not happy, going to look into that.
Should be on par with CM. Let me know what you find!
Click to expand...
Click to collapse
Dear @arrrghhh I am not a developer, but I have a little guess as to what might be causing the FC's on the google keyboard. The keyboard learns the user style and way of writing (if you see the T it has many settings that are probably intefering with the absence on Knox.
I'm excited about Carbon for this device, but seeing that there's been no activity in the thread for over a week has me wondering if something is wrong with it. I'm using cm 11 right now and it's very stable if lacking in features.
From my Pro Tab 8.4
JaylanPHNX said:
I'm excited about Carbon for this device, but seeing that there's been no activity in the thread for over a week has me wondering if something is wrong with it. I'm using cm 11 right now and it's very stable if lacking in features.
From my Pro Tab 8.4
Click to expand...
Click to collapse
CarbonFibers has a FC issue which has been resolved... but some of the customizations are still lacking because the CF app isn't really setup for tablets at the moment... so the experience is a bit off. I didn't see the value in updating until the issue is completely fixed, as most of the reason to run the ROM is in that area .
That makes sense. I'll follow the thread for updates. This is the closest ROM to SlimKat, which is my favorite.
From my Pro Tab 8.4
JaylanPHNX said:
That makes sense. I'll follow the thread for updates. This is the closest ROM to SlimKat, which is my favorite.
From my Pro Tab 8.4
Click to expand...
Click to collapse
I saw a SlimKat tree from crpalmer, so I am assuming he is going to bring that out / is working on that... because I was going to attempt that as well until I saw that tree
Cool. Thanks for the heads up.
From my Pro Tab 8.4
arrrghhh said:
I saw a SlimKat tree from crpalmer, so I am assuming he is going to bring that out / is working on that... because I was going to attempt that as well until I saw that tree
Click to expand...
Click to collapse
Nope, I have no intentions of doing a slim build. I was trying that to sanity check that I had things configured well enough to make it easy for people to use the CM device tree to build other ROMs.
I had it booting and working reasonably well except that there were external sdcard problems (at the very least the lack of exfat support).
I do think I had to cherry pick missing commits into a few slim repos but I have forgotten what that was.
crpalmer said:
Nope, I have no intentions of doing a slim build. I was trying that to sanity check that I had things configured well enough to make it easy for people to use the CM device tree to build other ROMs.
I had it booting and working reasonably well except that there were external sdcard problems (at the very least the lack of exfat support).
I do think I had to cherry pick missing commits into a few slim repos but I have forgotten what that was.
Click to expand...
Click to collapse
Ah ok. I'll roll a SlimKat build too, see how that runs... I haven't really seen any of these on a tablet, so it's kind of interesting to see the difference. Carbon, at least CarbonFibers definitely has some work to be done for tablets.
arrrghhh said:
Ah ok. I'll roll a SlimKat build too, see how that runs... I haven't really seen any of these on a tablet, so it's kind of interesting to see the difference. Carbon, at least CarbonFibers definitely has some work to be done for tablets.
Click to expand...
Click to collapse
I wonder if SlimKat will have better luck, since it doesn't centralize all of its features into one thing like Carbon Fibers. I think they just added the 2014 Note 10.1 as officially supported. I have no idea if there's any similarities between that and our Tab Pro or if that would help even if there were.
From my Pro Tab 8.4
Who wants to try out multiwindow?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's definitely a bit quirky - and the issue with CarbonFibers is still present... but Bluetooth works great, so my builds of Slim must be missing something else outside of the device tree...
Great Rom
Just flashed new build. Works great so far. Thanks for the work.
So is this ROM finished now where there are no more updates going to be done?
Related
First of all I want to make some things clear:
This is my own custom build I made with the help of this great tutorial: http://forum.xda-developers.com/showthread.php?t=775505
This has nothing to do with the offical nightly build from Cyanogen and his team.
I won't provide any support for this. If you want to flash this you should know what you do. Don't ask me anything like "How do I flash this?".
This could be even more unstable then the official nightly build since I add commits that are not merged. It's a great feature preview, but I can't guarantee anything. I can't tell you if the features you see here will make it into any official build.
What is it?
Its a custom build of the latest Cyanogen sources spiced up with some not (yet?) merged patches.
What's inside?
A basic ROM with "a2sd light" and without g-apps. I removed ADW Launcher too since it's lags, included is the stock Android Launcher2.
I also removed CMStats since this one isn't anything official and could be more buggy then anything else.
Whats "a2sd light"?
Its like the original a2sd from here: http://forum.xda-developers.com/showthread.php?t=715940
but I removed all things that handle the dalvik-cache. I tried the original a2sd and didn't like it since it moved the /cache/dalvik-cache/ back to /data. Don't know if thats the way it should be.
I don't know how often I will make new builds, it depends if I find new things I want to try. If there are no new commits that interest me I won't make a new build.
I will only upload builds that work for me. So the basic stuff should work for everyone, if it doesn't try to wipe before flashing. If it still doesn't work use the official nightly/RC/stable/whatever... (Thats the point with "I won't provide any support").
So whats inside today/night?
All commits that were made until 28.Nov 2010 05:00pm (look here to get some details: http://review.cyanogenmod.com/#q,status:merged,n,z)
+ updateted gesture support on Lockscreen
+ custom app for lockscreen messaging slider
- User can now define unlock and sound toggle gestures.
- Lockscreen tabs can now be fully disabled, but ONLY if there is
some other method of unlocking the device enabled. This includes:
Trackball unlock, menu key unlock, and gesture unlock.
- Changed default gesture sensitivity to 3
Allow the user to specify which application to launch using
the lockscreen messaging slider.
Link:
http://www.multiupload.com/P00AYOA42T
Thanks to the devs of CyanogenMod and all other people contributing in this!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So the only difference between this and the official buildbot nightly is you added some a2sd that we can install via recovery anyway?
awesome idea for a thread!
daedelus82 said:
So the only difference between this and the official buildbot nightly is you added some a2sd that we can install via recovery anyway?
Click to expand...
Click to collapse
Tada, the first one that didnt get what this is about. Try to find the lockscreen in the official nightly. Guess what, its not there yet. Because the patch is not merged yet. And the buildbot uses only merged things.
Maybe you start reading and thinking before posting next time...
Sent from my Nexus One using XDA App
simms22 said:
awesome idea for a thread!
Click to expand...
Click to collapse
Thanks, great some people read the whole post and understand it
Sent from my Nexus One using XDA App
g4rb4g3 said:
Thanks, great some people read the whole post and understand it
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
ive been flashing quite a few custom cm builds lately and been finding it very refreshing
btw... it looks like you picked up that stupid lockscreen grass wallpaper bug
g4rb4g3 said:
Tada, the first one that didnt get what this is about. Try to find the lockscreen in the official nightly. Guess what, its not there yet. Because the patch is not merged yet. And the buildbot uses only merged things.
Maybe you start reading and thinking before posting next time...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I read the entire post but still fail to see it's worth.
I would rather wait a day for it to be merged and in the official nightly, than use a build which has no support and is stated will only be updated when you see fit.
It doesn't offer anything other than a couple commits which have not yet made it into the official nightly.
Also unless you plan on building it every day/night you should probably take [NIGHTLY] out of the title, I think it's a little misleading.
daedelus82 said:
I read the entire post but still fail to see it's worth.
I would rather wait a day for it to be merged and in the official nightly, than use a build which has no support and is stated will only be updated when you see fit.
It doesn't offer anything other than a couple commits which have not yet made it into the official nightly.
Also unless you plan on building it every day/night you should probably take [NIGHTLY] out of the title, I think it's a little misleading.
Click to expand...
Click to collapse
Well, if support is your sticking point, then even using the cyanogen nightly is something you should avoid. This is just a user posting his creation if someone wants to play with the ROM. Happens all the time here. That's why this is a great site. Pick your poison. All about choice. Ignore what you don't want to use. I don't think the OP tried to pass this off as better than anything else. Just offering something to play with. I thought it was communicated very clearly.
daedelus82 said:
I read the entire post but still fail to see it's worth.
I would rather wait a day for it to be merged and in the official nightly, than use a build which has no support and is stated will only be updated when you see fit.
It doesn't offer anything other than a couple commits which have not yet made it into the official nightly.
Also unless you plan on building it every day/night you should probably take [NIGHTLY] out of the title, I think it's a little misleading.
Click to expand...
Click to collapse
some people, obviously not you, experience the joy of flashing a rom for the sheer pleasure of flashing a rom. you dont have to flash it, or even read the thread(thats an absolute right that you have). but, i do see the worth in it. if not for anything else, the op is learning about building roms and has other people, like me, to test them out. i believe that it brings the op joy in building them and sharing. since its his own personal build, he can not post them in the official nightly thread. i was posting custom cm nightlies in the official thread and was asked to make a separate thread, and never did. btw, there are nights that there are no nightlies, so does the name of that thread have to change also? anyways, if you do have a good idea for the name of the thread, let the op know. maybe he will change it
daedelus82 said:
I read the entire post but still fail to see it's worth.
I would rather wait a day for it to be merged and in the official nightly, than use a build which has no support and is stated will only be updated when you see fit.
It doesn't offer anything other than a couple commits which have not yet made it into the official nightly.
Also unless you plan on building it every day/night you should probably take [NIGHTLY] out of the title, I think it's a little misleading.
Click to expand...
Click to collapse
A lot of people are asking about the lockscreen options in the Nightly thread. This should shut them up for now.
There's also no real need to support this at all. It's based on a nightly that is oudated in a few hours and it only has a couple patches. If anything is wrong he's not the developer of this ROM so there isn't anything for him to fix. It's just CM 6.1 built from source with new commits that aren't yet merged.
Just a taste of whats ahead.
P.S. <3g4rb4g3 <3simms22
Thanks to the OP for posting this. I like all the other flashing addicts find it refreshing trying out others peoples builds. Plus I have serious respect for the time, energy and hard drive space that goes into making these. Nice job.
Great job, I love the lock screen!, works perfect.
Last time I checked, Cyanogen nightlys were not supported either! just saying!
daedelus82 said:
I read the entire post but still fail to see it's worth.
I would rather wait a day for it to be merged and in the official nightly, than use a build which has no support and is stated will only be updated when you see fit.
It doesn't offer anything other than a couple commits which have not yet made it into the official nightly.
Also unless you plan on building it every day/night you should probably take [NIGHTLY] out of the title, I think it's a little misleading.
Click to expand...
Click to collapse
I don't care if you think it's worth flashing or not. I make my own "nightly" builds for several weeks already. Since some people asked I started this. Seems like there are people out there willing to try it. If you want to wait do so and keep it for yourself.
It seems you have a bad life, complaining about things that you don't like/think they are not worth trying... Try to read only topics that you are interested in. If you aren't interessted in this shut up, stop posting, go away and hate someone else.
I don't want to call it the best thing ever or anything else. This is just a feature preview. Maybe the features make it into a official build, maybe not. I don't decide that. But I decide which commits I want to use...
And about the "nightly" tag, I use it since I use the same sources for it. It should tell the people that this is nothing that got tested several days and it could contain bugs. (Like the stupid gras wallpaper on the lockscreen)
i think its a great idea, there is no need to bash someone for posting a modified nightly, this is a common thing in the open-source community
also there are many things you can merge and play with.
i for one merge some webkit stuff (from official webkit repo) when i get the chance , you should look into that.
- 2 pages of spam only
- great idea "g4rb4g3" keep it up!
New version, updated first post.
g4rb4g3 said:
+ White energy widget icons if you select the STOCK_Black theme in Settings>CyanogenMod settings>User interface>Tweaks extras>Select a theme.
This patch was made by me, I commited it and hope it will get merged.
Click to expand...
Click to collapse
That's awesome! If I hadn't gotten swept up in the whole MIUI craze, I would give it a go
updated first post
Great work, but i think that is better waiting for RC2 official release for mod it.
matiu said:
Great work, but i think that is better waiting for RC2 official release for mod it.
Click to expand...
Click to collapse
Of course you can wait, I couldn't
I want to begin this by saying I am in no way affiliated with Team Broccoli. Nor am I responsible for any damages or problems that may occur with your TF201 by using this rom.
I have been using this rom for a while now and i must say it is incredibly smooth, gaming works brilliantly and it has all the custom features I've come to love using AOKP on my other devices.
For the downloads head over to their Mini Site and download either R2 or their latest "nightly"
scar45 said:
updated on 05-30-2012 (mm/dd/yyyy)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This project is a representation of the benefits that open source brings. Using the Android ROM source of Team AOKP, we bring you a rock-solid, feature-rich base ROM, topped off with a serving of PCB goodness that gives your device a very unique look.
We plan on adding more features and modifications as the ROM progresses, so feel free to leave us suggestions and feedback via replying to this thread, or join us on IRC.
Keep an eye on our PCB Mini-Site for MUCH more information, as well as news updates and changelogs.
Acer Iconia A500 (picasso)
ASUS Transformer (tf101)
ASUS Transformer Prime (tf201)
HP Touchpad (tenderloin)
HTC EVO 4G (supersonic)
HTC One S (ville)
HTC Incredible (inc)
HTC Incredible 2 (vivow)
HTC Sensation (pyramid)
Kindle Fire (otter)
LG Optimus 2X (p990)
LG G2x (p999)
Motorola Xoom - Verizon (stingray)
Motorola Xoom - Wi-Fi (wingray)
Samsung Captivate (captivatemtd)
Samsung Fascinate (fascinatemtd)
Samsung Galaxy S (i9000) (galaxysmtd)
Samsung Galaxy Nexus GSM (maguro)
Samsung Galaxy Nexus LTE (toro)
Samsung Galaxy Nexus Sprint (toroplus)
Samsung Galaxy Tab 2 - 7" Wi-Fi (espressowifi)
Samsung Galaxy Tab 7" - Verizon (p1c)
Samsung Galaxy Tab 10.1" - 3G (P7500) (p4)
Samsung Galaxy Tab 10.1" - Verizon (p4vzw)
Samsung Galaxy Tab 10.1" - Wi-Fi (p4wifi)
Samsung Galaxy Tab 8.9" - Wi-Fi (p5wifi)
Samsung Nexus S (crespo)
Samsung Nexus S LTE (crespo4g)
Samsung Vibrant (vibrantmtd)
Unofficial Devices (Ports):
Motorola Atrix (olympus)
Motorola Photon (sunfire)
Samsung Infuse 4G (????)
--> Available on our PCB Mini-Site
Team Broccoli is a fresh collaboration of Android enthusiasts:
scar45
remicks
cr5315
sixstringsg
Contributors and thanks to:
Team Kang
Donators everywhere
ex0a
J2
+ more to be added, chat with us on IRC if you would like to help out
UOT Kitchen for their circle battery icons
Some other icons were obtained at IconFinder
hostedWithGeeks for the excellent hosting experience/service
if you like it... (I would greatly appreciate that!!) otherwise, a click of the THANKS button is awesome!
Disclaimer:
Flash this at your own risk! Team Broccoli is NOT responsible for any damage caused to your device, however we do use AOKPCB ourselves. Always perform a NANDROID backup + Cache / Dalvik Cache wipe (at the least) before installing. Also, PM me before you rip out any of my resources if you wanted to use them in your own theme/project. I can be accommodating so long as you get in touch first!
Click to expand...
Click to collapse
Looks great! Will be trying out.
Most recent nightly was released 6/10/12
Hi,
is that the same theme as PCB blue available on play store ?
Z0R said:
Hi,
is that the same theme as PCB blue available on play store ?
Click to expand...
Click to collapse
yes but this rom has more to it than just the theming on aokp. See their site for more details
thanks, i will be trying this on out for sure.
I hope this is not a noob question but I don't see if there are any problems with the rom enough to make it a daily (I use it for school/notes)
magicalan said:
I hope this is not a noob question but I don't see if there are any problems with the rom enough to make it a daily (I use it for school/notes)
Click to expand...
Click to collapse
It is completely stable if you ask me. I used it for about a week and had no problems. The battery life is great too. It's basically AOKP and Jermaine did a really thorough job of making it the first non-stock rom to be totally stable.
Sent from my Transformer Prime TF201 using xda premium
I think its outrageous that Jermaine hasn't been given credit in the original post. This seems like a slap in the face, in fact. Kudos for a new rom, but credit where credit is due.
adampdx said:
I think its outrageous that Jermaine hasn't been given credit in the original post. This seems like a slap in the face, in fact. Kudos for a new rom, but credit where credit is due.
Click to expand...
Click to collapse
I don't think this thread was started by Team Broccoli. It looks like the OP just cut and pasted from the ROM's website, which does credit Team AOKP as the source of this ROM. I don't believe any disrespect were meant towards any of the AOKP's devs.
~Azrael's Kiss~
adampdx said:
I think its outrageous that Jermaine hasn't been given credit in the original post. This seems like a slap in the face, in fact. Kudos for a new rom, but credit where credit is due.
Click to expand...
Click to collapse
Damn, no ****! I have followed Jermaine for months and have seen how much time and effort he has put into AOKP for the Prime. I am a little disappointed there is no mention of him anywhere!
I think it is outrageous, that people obsess about crediting a guy noone was willing to defend when he was being banned and kicked out for no apparent reason. I know that mods have their reasons, still this is ridiculous.
I for one, am really glad to see another aokp rom on xda. Have been using aokp since first release for tf201 and now this build seems even more stable and fluid to me. THANKS TEAM BROCCOLI, THANKS JERMAINE! <-------see this is how you give credit... the OP is not the only one who should.
Before aokp i was ready to give up on my tf201 as a device for work and i actually bought a notebook as i rely on a portable device professionally. Now I can take my tf201 with me again, instead of a clunky laptop without being embarrassed by it's lousy stock firmware. I am an assistant director at a performing arts theatre and i need to quickly change and edit texts, play samples (mikrosonic spc!!! Its great) in rehearsals and research on youtube/the web. So the tf201 is an ideal device, if stable.
Edit: oh yeah, jermaine also didn't create aokp nor is he involved in the creation of aokpcb. All he did was port and maintain another compile of aokp. Team broccoli build their aokp from source aswell,so why would they credit him? Please ppl, read up on what open source means, what licenses there are, the definition of kanging, maybe also about different rom cooking methods before bashing posts.
If you feel that I have not provided adequate credit please feel free to report this thread or contact Scar45 for me. I have neither the time nor the inclination to argue over who deserves credit and who does not. Jermaine works with Team Kang and Team Kang is credited in the OP, as far as I know he has not had any special role in producing AOKPCB that would merit special credit outside the umbrella of Team Kang.
I have no affiliation with Team broccoli or Team Kang. That said i merely copy and pasted Scar45's OP from another of his threads.
Please refrain from turning this into a flame thread and keep it on topic. Discuss any issues or problems with the rom. What you like dont like. If you must complain about giving credit then feel free to use the above channels or pm me direct.
- Cheers
This has to end. All has said their peace. Thanks OP for sharing this.
Sent from my PC36100 using xda premium
Sorry if that came across wrong, i was trying to defend OP
xnopasaranx said:
Sorry if that came across wrong, i was trying to defend OP
Click to expand...
Click to collapse
Was not directed at you, no worries
now let's move forward
New AOKPCB User
Hello AOKPCB Fans,
I finally got around to installing this ROM on my tf201. Overall great ROM. However there is 1 thing that is bothering me at the moment. I do not like to have sounds on key-press however I enjoy having the haptic feedback for that "I pressed a button" feeling. The problem is I can barley feel the haptic feedback, it too low. I also cannot find where the settings are to adjust it.
Another question, what launcher are most of you using with this ROM? AOSP launcher or Apex launcher?
Thanks,
nexwave-mat said:
Hello AOKPCB Fans,
I finally got around to installing this ROM on my tf201. Overall great ROM. However there is 1 thing that is bothering me at the moment. I do not like to have sounds on key-press however I enjoy having the haptic feedback for that "I pressed a button" feeling. The problem is I can barley feel the haptic feedback, it too low. I also cannot find where the settings are to adjust it.
Another question, what launcher are most of you using with this ROM? AOSP launcher or Apex launcher?
Thanks,
Click to expand...
Click to collapse
Ive never used haptic feedback personally but upon investigation it does seem to be broken, ill shoot Scar45 a pm about it, as to the launcher, i prefer APEX but im really just waiting for Chameleon to drop.
i have to say i am really digging this rom. been running it pretty hard since this morning and i have not found one isue.
i have been going back and fourth between apex and tsf shell launcher.
i am starting ti like tsf alot. it takes some time to get use to it.
lots of custom stuff.
i love that you can add more nav buttons and have them all do a second comand. one of my favorite things is you can choise to hide the nav bar automaticly in a full screen app.
i used the stock browser for bout 2 hours stait without any isues at all, big plus.
the only thing i havnt done is gaming on it. will do some gaming tomorrow and report back.
if you are thinking bout trying, please do.
I feel like a broken record asking this in every thread, but is there any chance a wireless gamepad (logitech f710) will work on this? I can only get it to work on stock based but I want aosp.
Hopefully Ill get some time to install and test, but I'm hoping someone will figure this out. Thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The Open ROM
Omni is a community-based project for the Android community which is Free^3:
Free to Use, Free to Modify, Free to Share. It's also about options, which is the beauty of Android
Introduction - What is OmniROM?
Omni is what custom ROMs used to be about – innovation, new features, transparency, community, and freedom. Our goal is to experiment with Android development because we enjoy it. Omni isn’t better, just different. It’s another option for the billion Android users out there. Android (vs. iOS and every other mobile OS) has thrived on options as well as the gigantic, talented development community that has emerged to build those options. That’s the beauty of Android – that you can pick and choose from a smorgasbord of devices with varying features and functionality.
Omni is a chance to get involved, no matter who you are. Developers, whether you’ve been developing apps for a week, or ROM features for 3 years, you’re welcome. Users, we know you want to help out, and now you can – Omni actively encourages bug reports and feature requests, which can be added to our publicly accessible roadmap.
Omni is about flexibility and giving users what they expect – and we are excited to see where the community goes with it.
What's Working
Support for old and new partition setups
Sound
Data / LTE
Voice
SMS
WiFi
Notification Lights
Sensors
GPS
other features TBD
What Needs Work
Under certain conditions (constant back and forth from 1x/evdo<->ehrpd/lte) the RIL will take it's ball and go home. This one I'm still working on getting sorted, but in the mean time toggling airplane mode will make it act right.
TBD - Let me know if you find more!
Downloads
See post #2
Code:
Disclaimer: Unless required by applicable law or agreed to in writing, this work is provided on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the software and assume any risks
associated with your use of any information or software provided to you.
In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate
and grossly negligent acts) or agreed to in writing, shall any contributor be liable to you for damages, including any direct, indirect, special, incidental,
or consequential damages of any character arising as a result of this or out of the use or inability to use the software (including but not limited to
damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such contributor has
been advised of the possibility of such damages.
If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and
the section as a whole is intended to apply in other circumstances.
XDA:DevDB Information
Omnirom-jewel-unofficial, a ROM for the Sprint HTC EVO 4G LTE
Contributors
xHausx
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: OmniROM
Version Information
Status: Beta
Created 2013-10-23
Last Updated 2013-12-27
Downloads
DevDB Download Page (Torrent)
Dev Host Unofficial Test Builds
omni-4.3.0-20131022-jewel-HOMEMADE.zip - 161.42 MB
omni-4.3.0-20131022-jewel-HOMEMADE-multiwindow.zip - 164.84 MB
omni-4.3.1-20131027-jewel-HOMEMADE-2.zip - 165.80 MB
omni-4.3.1-20131028-jewel-HOMEMADE.zip - 166.09 MB
omni-4.4-20131113-jewel-HOMEMADE.zip - 171.79 MB
omni-4.4-20131204-jewel-HOMEMADE.zip - 174.71 MB
omni-4.4.1-20131206-jewel-HOMEMADE.zip - 175.06 MB
omni-4.4.1-20131209-jewel-HOMEMADE.zip - 175.49 MB
omni-4.4.2-20131226-jewel-HOMEMADE.zip - 174.53 MB
omni-4.4.2-20131228-jewel-HOMEMADE-4.zip - 174.53 MB
omni-4.4.2-20131230-jewel-HOMEMADE.zip - 174.52 MB
omni-4.4.2-20140107-jewel-HOMEMADE.zip - 174.34 MB
omni-4.4.2-20140109-jewel-HOMEMADE.zip - 164.60 MB
omni-4.4.2-20140111-jewel-HOMEMADE.zip - 164.30 MB
omni-4.4.2-20140117-jewel-HOMEMADE.zip - 165.04 MB
omni-4.4.2-20140202-jewel-HOMEMADE.zip - 164.46 MB
omni-4.4.2-20140227-jewel-HOMEMADE.zip - 164.07 MB
omni-4.4.2-20140314-jewel-HOMEMADE.zip - 164.14 MB
omni-4.4.2-20140331-jewel-HOMEMADE.zip - 163.57 MB
Official Nightlies
Gapps
4.3 Gapps
OFFICIAL 0-Day PA-GOOGLE APPS (All ROM's) - PA gapps are recommended for OmniROM
Recovery
Patched TWRP for SE Linux Compatibility - courtesy of kushdeck
Native 4.4 TWRP with full SE-Linux support
Super SU
Sources
Device: https://github.com/omnirom/android_device_htc_jewel
S4 common: https://github.com/omnirom/android_device_htc_s4-common
Kernel: https://github.com/omnirom/android_kernel_htc_msm8960
Thanks
Thanks go out to everyone below and everyone who has contributed to AOSP, CM, Omni and the Evo in general. This wouldn't be possible without the prior work of many people to get our device running with AOSP.
kushdeck for kernel, device repos, and telling me what needed to be done to the kernel
Toastcfh, intervigilium & Flemmard for kernel and device repos
Everyone who has contributed to OmniROM
The entire Cyanogenmod team for all they've done for the community
Entropy512, xplodwild, CaptainThrowback, eagleeyetom, jmztaylor, Pulser, GoblinZ, shortyishere and everyone on XDA and in #htc-evo-4g-lte who has helped me along the way
Nice. I tried building Omni also, gonna use yours though. Wouldn't trust myself around a computer, let alone a rom
Sent from a non-i****
Awesome.. Something new to try..
-----Evo LTE..
Haus. To seeyou sharing is awesome. You've brought us a million so far (radios, downgrades, etc,...you've taken huge risks for the community. Anything yoibuild, I will try
Sent from my EVO 4G LTE using XDA Premium 4 mobile app
Awesome man I also got a build with this and got it booted but same issue I had with this ROM
Too much fun going on for our phone. Thanks Haus!!
Good stuff, bro. Now fix all teh borken stuffs .
Yeah I tried this one and had no radio on the current ota so it may only be good on 3.16 but I may try again later and give vanir as my daily but when I get home I will give this another shot
Sent from my EVO 4G LTE using XDA
zacnking said:
Yeah I tried this one and had no radio on the current ota so it may only be good on 3.16 but I may try again later and give vanir as my daily but when I get home I will give this another shot
Sent from my EVO 4G LTE using XDA
Click to expand...
Click to collapse
You DID read the OP, right?
Captain_Throwback said:
You DID read the OP, right?
Click to expand...
Click to collapse
THIS^^ and this..... (per OP)
*Cell service must be enabled by going to Settings -> More.. -> Mobile network settings -> CDMA subscription -> NV (Toggling airplane mode may be needed)
Ahh beat me to it good luck hope it works out great.
Sent from my EVO using XDA Premium 4 mobile app
Captain_Throwback said:
You DID read the OP, right?
Click to expand...
Click to collapse
I must have missed something in the fine print. . . that's probably why I'm still with sprint still as well :]
Sent from my EVO using XDA
numel007 said:
Nice. I tried building Omni also, gonna use yours though. Wouldn't trust myself around a computer, let alone a rom
Sent from a non-i****
Click to expand...
Click to collapse
If you still want to you should be able to build it by adding the three repos I linked to above to your .repo/local_manifests folder. For the proprietary drivers I used the ones from TheMuppets github, so I would recommend those as well.
To be honest I'm still fairly newbish when it comes to building from source as well, but now is as good a time as ever to learn.
untz1456 said:
Awesome man I also got a build with this and got it booted but same issue I had with this ROM
Click to expand...
Click to collapse
Were you able to get it with an up to date kernel? I ended up just rolling the entire kernel back to a few months ago where caf_2.6 was merged in, but unfortunately I removed a lot of important (security) patches in the process.
lreyes said:
Ahh beat me to it good luck hope it works out great.
Click to expand...
Click to collapse
The more the merrier, I think the GS3 (or one of the sammy devices, can't keep them all straight) already has four different builds. lol
One of the main reasons I posted this in it's current state was to hopefully help anyone else who was working on it. Plus, with the DevDB setup you can have multiple people as sort of co-owners for the project and let them edit the OP or accept ownership for the thread.
xHausx said:
If you still want to you should be able to build it by adding the three repos I linked to above to your .repo/local_manifests folder. For the proprietary drivers I used the ones from TheMuppets github, so I would recommend those as well.
To be honest I'm still fairly newbish when it comes to building from source as well, but now is as good a time as ever to learn.
Were you able to get it with an up to date kernel? I ended up just rolling the entire kernel back to a few months ago where caf_2.6 was merged in, but unfortunately I removed a lot of important (security) patches in the process.
The more the merrier, I think the GS3 (or one of the sammy devices, can't keep them all straight) already has four different builds. lol
One of the main reasons I posted this in it's current state was to hopefully help anyone else who was working on it. Plus, with the DevDB setup you can have multiple people as sort of co-owners for the project and let them edit the OP or accept ownership for the thread.
Click to expand...
Click to collapse
yeah i was able to for me all that it was missing was libs did u use evervolv source to build this ? or cm
Thanks for bringing this to the LTE xHausx. Of all the AOSP projects out there Omni ROM stands out. The concept and idea behind this project are what its supposed to be about. Definitely interested in where this goes.
Sent from my EVO using Tapatalk 2
untz1456 said:
yeah i was able to for me all that it was missing was libs did u use evervolv source to build this ? or cm
Click to expand...
Click to collapse
I forked from CM but so far everyone I found looks to have come from the htc-msm8960 group.
So looks like the only things broken are GPS and camera eh? I'm just going to assume that the GPS fix doesn't work here. Flashing soon!
Sent from my EVO using xda premium
numel007 said:
So looks like the only things broken are GPS and camera eh? I'm just going to assume that the GPS fix doesn't work here. Flashing soon!
Sent from my EVO using xda premium
Click to expand...
Click to collapse
It looks like GPS is due to the proprietary libs CM was using. I've got a new copy building that has updated props so hopefully that one will be good now.
edit: and the build failed, looks like it won't be quite that easy
xHausx said:
I forked from CM but so far everyone I found looks to have come from the htc-msm8960 group.
Click to expand...
Click to collapse
Hmm have u tried using evervolv kernel ? I think it might be the same as cm but it doesn't hurt to try since evervolv is aosp and they have their sources for 4.3
Edit: also try to get libs from other ROMs for camera and check if its the right size and what not
YOU HAVE NOW BEEN CARBONIZED
Built from the Carbon source, these unofficial builds will be updated weekly. Maybe more if time permits or there are any huge changes to be incorporated. Built specifically for our devices, no ports here anymore. This should allow it to run a bit better than a rom that was technically built for another device.
And now, on with the show!
About Carbon
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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.
Carbon Features
All of our features can be found on our site here:
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.
***NOW BUILT WITH ArchiDroid OPTIMIZATION STARTING 11/07***
Many thanks to @JustArchi for his commit regarding optimizations in Android builds. What are these optimizations? Check out THIS THREAD for more details on what this entails. In most basic terms, this optimizes code within the build a lot more than the traditional flags set by the code I build from. You may not see a doubled AnTuTu score, or doubled battery life. But this provides a lot more stability and smoothness than simply using the Sabermod toolchain that is also included in these builds. So props to him for this commit. Go give the man some thanks!
Special Thanks
Let me do this first and foremost before moving on with the downloads and installation instructions. This would not be possible without the help and guidance of a few other talented builders here in our community, and without the help of those who tested this before it was posted.
Thanks to @rogersb11 and @cyril279 for helping me out along the way. Their guidance and support have been most beneficial, and without that help, this thread wouldn't be here. So if you thank me, be sure to thank them too!
Thanks to the entire Carbon Team for the hard work they put into building such an amazing AOSP rom.
Thanks to my testers, @cyril279, @edwin270, @rogersb11 and @dsteele for being brave enough to be the first people outside of myself to take this new build for a spin.
To anyone else who has helped me along the way in my Android experience and journey from noob to only partially, just a bit of a noob. Your guidance and support has been appreciated more than you could know.
Download and Installation Instructions
As always, neither I, nor the people thanked in this thread, nor your neighbor are responsible for anything that may happen to your device including, but certainly not limited to: Soft Brick, Hard Brick, Exploding Batteries, One Fish, Two Fish, Red Fish, Blue Fish, raining porcupines, or male patterned baldness.
**IMPORTANT: If you are coming from ICS or JB, you MUST upgrade your recovery BEFORE flashing this rom. See below for compatible recoveries**
CWM - 6.0.4.4+
TWRP - 2.6.3.0+
For SGH-S959G
CWM - 6.0.4.5 from here
TWRP - 2.6.3.0 from here
1) Download the latest build from here (Current Build: 12/08 ). Older builds can be found here.
2) Download the Gapps pack of your choice. (I personally use Slim Minimal 4.4.4 which you can find here). But feel free to use whichever Gapps package you prefer.
3) FULL WIPE if coming from any other rom. If updating, wipe cache/dalvic before flashing, unless stated to do a full wipe.
4) Flash the ROM package
5) Flash Gapps package of your choice
6) (Optional) Reboot recovery, wipe dalvic/cache. (Recommended if you are coming from a custom kernel build.
7) Reboot device and enjoy the goodness.
SPECIAL NOTES
This will flash with the stock CM kernel with CWM Recovery, which many people find a little laggy. There are custom kernels in the forums that you can flash after the rom if you want more control, performance, stability, etc.
This is built straight from the source code found on the CarbonDev Github. The only things that have been changed are the removal of CarbonDelta and ROM Stats. Since these are unofficial builds, not supported by the Carbon team, these two apps really serve us no purpose. All updates will need to be flashed through recovery.
All bugs or questions should be reported to THIS THREAD ONLY. Do not send questions to the Carbon Team as this is not an officially supported device anymore. So don't bother them. Bother me instead.
For general CarbonRom questions, check out the FAQ.
That's all I have for now. If you enjoy this rom, please hit that thanks button and inflate my ego a little bit.
Happy flashing!
ROM: CarbonRom (Unofficial Builds)
Android Version: 4.4.4
Kernel: Stock CM Kernel Source
Built by: @TheGeekyNimrod
Reserved because you never know when you might want that second post spot.
Here we go...booting as I type...
desteele said:
Here we go...booting as I type...
Click to expand...
Click to collapse
Woo hoo!
Sent from my SAMSUNG-SGH-I747
TheGeekyNimrod said:
Woo hoo!
Sent from my SAMSUNG-SGH-I747
Click to expand...
Click to collapse
OK, I don't have a BT device, but almost everything seems very smooth and functional. USB connections/transfers seem fine, and mobile data almost seems fine. I can download web content in the browser, but never could get the playstore to download any apps. It pulled up and went through the steps to say it was downloading, but the app never actually got pulled down.
Pretty good stuff to this point though...
Also, it didn't set up my google account when I was setting it up, that's usually an included step. I didn't realize it til I opened the Play Store and then it went through the Google setup.
Edit: rebooted and a playstore download started up... it just seems a little finicky about beginning to pull. I don't have full signal at home, but was getting 3 of 4 bars most of the time.
That sounds more like just a bum install of Gapps. Especially if it didn't ask for Google Account right off the bat. I've had that happen before. Usually not a rom or Gapps package issue, but just something hanging in the flashing process.
Glad to hear everything else went fine. I'll do another fresh install on mine in the morning and see if the same issue crops up.
Sent from my SAMSUNG-SGH-I747
desteele said:
OK, I don't have a BT device, but almost everything seems very smooth and functional. USB connections/transfers seem fine, and mobile data almost seems fine. I can download web content in the browser, but never could get the playstore to download any apps. It pulled up and went through the steps to say it was downloading, but the app never actually got pulled down.
Pretty good stuff to this point though...
Also, it didn't set up my google account when I was setting it up, that's usually an included step. I didn't realize it til I opened the Play Store and then it went through the Google setup.
Edit: rebooted and a playstore download started up... it just seems a little finicky about beginning to pull. I don't have full signal at home, but was getting 3 of 4 bars most of the time.
Click to expand...
Click to collapse
For network I am always on 2g unless i do want to use the phone data( which i mostly never use, always on wifi). Sure 3g signal is not so strong from within your room.
When done with rom flash, I made it boot first. Then went ahead to set it up without google account, when back to recovery and flashed gapps.
Finally, after changing to "art" runtime I launched playstore then did setup my google account.
So far, so good............just about to pull my battery stat, to be sure it last as it should be. All my apps are running great so far.
NOTE: be sure to wipe/factory reset 3 times. Since previous gapps could be left untouched. I again make sure i wipe data, cache, dalvik cache again respectively, so to be certain.
Let me know how the battery stats look. I haven't really tested that, but mine is running with the RB11-Shift kernel so it would be different than if I had the stock kernel with it.
Sent from my SAMSUNG-SGH-I747
Well, baking overnight and possibly stronger signal downtown seems to have cured whatever mobile data issue I was having. I've done a couple of d/l's here at work, and it jumped on them fairly quickly, and the transfer rate seemed in line with what I normally get.
Did they include Heads-up?
TheGeekyNimrod said:
Let me know how the battery stats look. I haven't really tested that, but mine is running with the RB11-Shift kernel so it would be different than if I had the stock kernel with it.
Sent from my SAMSUNG-SGH-I747
Click to expand...
Click to collapse
Had I decent amount of random screen lighting up lol. I have a logger running now so we'll see what happens. Other than that I've been pushing this thing
desteele said:
Well, baking overnight and possibly stronger signal downtown seems to have cured whatever mobile data issue I was having. I've done a couple of d/l's here at work, and it jumped on them fairly quickly, and the transfer rate seemed in line with what I normally get.
Did they include Heads-up?
Click to expand...
Click to collapse
Yeah!, heads up is included though there is no "personal" settings for it anywhere. To enable pull down the notification drawer look at the top right. The first icon before the tiles icon.
Working perfect even for non-intrusive calls here.
edwin270 said:
Yeah!, heads up is included though there is no "personal" settings for it anywhere. To enable pull down the notification drawer look at the top right. The first icon before the tiles icon.
Working perfect even for non-intrusive calls here.
Click to expand...
Click to collapse
You can disable it for specific apps from Settings>Apps ... Go over to all apps. Select the app you want to disable it on, select blacklist, and select blacklist from hover.
Sent from my SAMSUNG-SGH-I747
rogersb11 said:
Had I decent amount of random screen lighting up lol. I have a logger running now so we'll see what happens. Other than that I've been pushing this thing
Click to expand...
Click to collapse
I've noticed that with Carbon on my S3 too. Let me know if the logger turns up anything helpful and I'll do some research and see what I can do for it. I'll be running another build off on Friday.
Sent from my SAMSUNG-SGH-I747
TheGeekyNimrod said:
I've noticed that with Carbon on my S3 too. Let me know if the logger turns up anything helpful and I'll do some research and see what I can do for it. I'll be running another build off on Friday.
Sent from my SAMSUNG-SGH-I747
Click to expand...
Click to collapse
Hmmmm............how come i have never seen anything of such.
Guess must be the lockscreen notification stuff, i reconfigured mine to turn on only when i have a notification, by default it is on and guess that has a sure trigger..............just my thought.
Have no screen issue. Even turn off screen animation is disabled
edwin270 said:
Hmmmm............how come i have never seen anything of such.
Guess must be the lockscreen notification stuff, i reconfigured mine to turn on only when i have a notification, by default it is on and guess that has a sure trigger..............just my thought.
Have no screen issue. Even turn off screen animation is disabled
Click to expand...
Click to collapse
Pocket mode is a lot of what's behind it I think. Using the proximity sensor and turning the screen on. I disable it right off the bat.
Sent from my SAMSUNG-SGH-I747
Pocket mode it was. Thanks for pointing that out, I had no clue
Sent from my SGH-I777 using XDA Premium 4 mobile app
rogersb11 said:
Pocket mode it was. Thanks for pointing that out, I had no clue
Sent from my SGH-I777 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Perhaps I should change up the OP and second post and leave a list of features and such? For granted, the link in the current OP will take you to the Carbon website where it's all listed.
It didn't hit me until I messaged you about the pocket mode. It took me a while after first porting it to realize what was going on. By habit now I always automatically disable it right off the bat when I flash it.
I'm going to be running off a build tonight that, if everything goes as it should, means the ROM will be built with Sabermod toolchain. Thanks to @rogersb11 once again for helping me get the necessary changes done to be sure it's going to build right. I'll test it on my own device tomorrow and if all is good I'll post it up sometime tomorrow afternoon.
TheGeekyNimrod said:
I'm going to be running off a build tonight that, if everything goes as it should, means the ROM will be built with Sabermod toolchain. Thanks to @rogersb11 once again for helping me get the necessary changes done to be sure it's going to build right. I'll test it on my own device tomorrow and if all is good I'll post it up sometime tomorrow afternoon.
Click to expand...
Click to collapse
Don't start just yet
Sent from my GT-N7105 using XDA Premium 4 mobile app
rogersb11 said:
Don't start just yet
Sent from my GT-N7105 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
- I haven't yet. Won't start it till later tonight. I let it run while I'm catching my Zzzzs.
Disclaimer:
Code:
[FONT="Book Antiqua"][SIZE="4"]All the firmwares, custom ROMs, official firmware updates, mods and tools mentioned here belong to their respective developers/owners.
You will be doing everything at your own risk.
We nor the developers cannot be held responsible if you end up damaging or bricking your device.[/SIZE][/FONT]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction:
MoKee OpenSource is based on the Google AOSP. We update our source code frequently to keep up with the latest development, and not forgetting to merge in special features of our own at the same time.
A small group of people from around the world who are interested in Android launched this project on the 12th of December 2012, and is committed to make this ROM better and better. Like most contributors of open source projects (Omni, CyanogenMod, Slim AOSPA etc), we are doing all these in our free time as our passion...
Since this project is open source, anyone interested can participate in the development (maintain new devices, contribute code etc). Newcomers are always welcomed!
Features:
-- Odexed for faster performance (only in official releases, nightlies are deodexed)
-- Incremental updates
-- OTA updates - update on the fly!
-- Native exFAT support (Samsung devices only)
-- ListView animations
-- Calendar - with lunar and solar calenders
-- Bulk SMS recipients
-- Adjustable SMS font size
-- SMS sending delay
-- Smart dialing
-- Speed dialing
-- IP dialing
-- Custom carrier name
-- Network speed in status bar (upload and download!)
-- Built in timer in Apollo - determine when to stop playing music
-- Unique Power Saver functions!
-- Custom screen off animations
-- Lockscreen notifications
-- Multiuser support
-- Smart Lock
-- Many more! Since we are constantly adding new features, see changelogs to keep updated!
Screenshots
The screenshots below gets outdated very fast!
Links:
-- Official website
-- Google Plus Community (join us for faster response!):
-- Statistics
-- Official Build Status
-- Bug Tracker
-- Changelogs
-- MoKee Github
-- MoKee Code Review
Downloads
-- ROM - UnOfficial - n7100
-- ROM - UnOfficial - t0lte
-- Latest Google Apps for Lollipop
Donations:
-- All donations will be used for build server.
You can scan this QR CODE to donate me by Alipay.
Installation Instruction
-- Make a backup of your ROM
-- Wipe data/factory reset
-- Format /system
-- Flash ROM
-- Flash Gapps
-- Reboot
Notes/Faqs
-- First boot might take a while around 5 to 10 minutes so don't panic, it will boot fine.
-- This ROM has not been tested with dual sim, so flash it by your own risk.
-- Working and Not working list is as same as CM12 unofficial Build
-- Restore from 4.4.4 rom is not recommanded (Do it at your own risk).
-- Download google camera for photos and video.
-- Use search button for your errors first and than put a query in here.
-- Do not ask ETA, it will not make release any faster than what it is.
Credits:
-- MoKee Developers
-- CyanogenMod
-- AOSP
-- Koush for open-sourced SuperUser
-- Slim Roms
-- OmniROM
从我的 iPhone 发送，使用 Tapatalk
Great to see new lollipop rom for n7105
---------- Post added at 05:24 PM ---------- Previous post was at 05:00 PM ----------
[/COLOR]Downloading now. Will report
Oh I do wish devs would write their own list of what's working instead of me having to have to research other ROMs threads for answers.
King Kaze said:
Oh I do wish devs would write their own list of what's working instead of me having to have to research other ROMs threads for answers.
Click to expand...
Click to collapse
So... It's not enough for builders/maintainers/developers to provide to you a free ROM on their own time and their own dime, but they should also be responsible to spend even more of their free time to dig up every issue/problem/bug and provide a specifically catered list for you, on demand, so that you can save a few minutes researching them yourself or installing the ROM to find out for yourself what may or may not work as you would like? Seems like a very reasonable and not at all selfish demand to me. Thank you for your most useful and helpful input.
Have a good one!
AzraelsKiss said:
So... It's not enough for builders/maintainers/developers to provide to you a free ROM on their own time and their own dime, but they should also be responsible to spend even more of their free time to dig up every issue/problem/bug and provide a specifically catered list for you, on demand, so that you can save a few minutes researching them yourself or installing the ROM to find out for yourself what may or may not work as you would like? Seems like a very reasonable and not at all selfish demand to me. Thank you for your most useful and helpful input.
Have a good one!
Click to expand...
Click to collapse
I'm glad you said what I was thinking.
AzraelsKiss said:
So... It's not enough for builders/maintainers/developers to provide to you a free ROM on their own time and their own dime, but they should also be responsible to spend even more of their free time to dig up every issue/problem/bug and provide a specifically catered list for you, on demand, so that you can save a few minutes researching them yourself or installing the ROM to find out for yourself what may or may not work as you would like? Seems like a very reasonable and not at all selfish demand to me. Thank you for your most useful and helpful input.
Have a good one!
Click to expand...
Click to collapse
Excuse me?
Its common practice to list the bugs with THEIR ROM in THEIR THREAD. Who cares if it is free? Its like providing screenshots for your ROM.
Imagine if all devs that made AOSP looking ROMs put under their screenshots; "same as CM11/12" and you had to go on a wild goose chase looking for CM screenshots? Its simply bad practice and an inconvenience. Hence why I don't flash ROMs as much as I used to because these new devs make sloppy threads compared to the Devs back in CM7/9 days.
'tis up to you. I know I wouldn't use a ROM, no matter how good it is, if it's XDA thread was sloppy. That is, after all, the most important thing when it comes to ROMs. I mean, if a builder insists on spending so much time to perfect the build that they cannot cater the thread to anyone and everyone, they shouldn't even bother.
Have a good one.
Features I didn't like...
Lot of Asian characters in settings and in some popups ..
Packaged with some search engine in Asian language.
really keen to try this LP Build.
not keen on as the previous user posted,
I cant read any other language other than english.
not to sound harsh but, i dont want to see asian characters and stuff popping up, I cant understand them.
if there is a way to rid of them or change to english. all good.
R0B3RTF1SH3R said:
really keen to try this LP Build.
not keen on as the previous user posted,
I cant read any other language other than english.
not to sound harsh but, i dont want to see asian characters and stuff popping up, I cant understand them.
if there is a way to rid of them or change to english. all good.
Click to expand...
Click to collapse
Not a asian language. this is chinese. and I agree with that because the third party app comes with chinese. third party app in AOSP rom...well...
Guys just freeze the Chinese apps or uninstall. I'm sure you guys knew that. The KK version of Mokee was nails. I'll wait for more features to start using this build, but I'm looking forward to it.
In Samsung the word Note 2 is pronounced t0lte.
King Kaze said:
Excuse me?
Its common practice to list the bugs with THEIR ROM in THEIR THREAD. Who cares if it is free? Its like providing screenshots for your ROM.
Imagine if all devs that made AOSP looking ROMs put under their screenshots; "same as CM11/12" and you had to go on a wild goose chase looking for CM screenshots? Its simply bad practice and an inconvenience. Hence why I don't flash ROMs as much as I used to because these new devs make sloppy threads compared to the Devs back in CM7/9 days.
Click to expand...
Click to collapse
Truly spoken like someone who has never built a ROM or had to support one. Well said Entitled One, well said.
It disturbs me how many devs will stay awake at night, knowing you will not flash their rom.
dicksteele said:
Truly spoken like someone who has never built a ROM or had to support one. Well said Entitled One, well said.
It disturbs me how many devs will stay awake at night, knowing you will not flash their rom.
Click to expand...
Click to collapse
Their sleep does not bother me tbh.
It's as simple as highlight>right click>copy>click>right click>paste
How does me wanting a Dev to take an extra 15 seconds when making a thread for everybody's convenience make me entitled? Who wants to trawl through thread after thread looking for a bug list?
It also has nothing to so with developing a ROM either.
King Kaze said:
Their sleep does not bother me tbh.
It's as simple as highlight>right click>copy>click>right click>paste
How does me wanting a Dev to take an extra 15 seconds when making a thread for everybody's convenience make me entitled? Who wants to trawl through thread after thread looking for a bug list?
It also has nothing to so with developing a ROM either.
Click to expand...
Click to collapse
Indeed sir ! You have convinced me.
How dare they not take an extra 15 seconds outside of the hours they have spent compiling, doing backups to test their build, flashing their build, fixing any issues, doing more backups and flashes. Coordinating with testers, gathering their input, doing more builds, backups and flashes.
How dare they not spend the extra time indeed. Unbelievably selfish, I agree.
dicksteele said:
Indeed sir ! You have convinced me.
How dare they not take an extra 15 seconds outside of the hours they have spent compiling, doing backups to test their build, flashing their build, fixing any issues, doing more backups and flashes. Coordinating with testers, gathering their input, doing more builds, backups and flashes.
How dare they not spend the extra time indeed. Unbelievably selfish, I agree.
Click to expand...
Click to collapse
actually, he has a point.
1. only if you used the other roms would know the bug/change lists. therefore. the rom is dependant.
2. some devs ive seen with postings saying "i do not own a note 2, but this should work, im not responsible for bricking your device"
---------- Post added at 10:50 PM ---------- Previous post was at 10:47 PM ----------
can you tell me, what baseband your using on this, in the screenshots it says
msm86bp_1032,365.70.00R
Click to expand...
Click to collapse
R0B3RTF1SH3R said:
actually, he has a point.
1. only if you used the other roms would know the bug/change lists. therefore. the rom is dependant.
2. some devs ive seen with postings saying "i do not own a note 2, but this should work, im not responsible for bricking your device"
---------- Post added at 10:50 PM ---------- Previous post was at 10:47 PM ----------
can you tell me, what baseband your using on this, in the screenshots it says
Click to expand...
Click to collapse
The screenshot does not come from a N7105, but from a MotoG
I had this ROM installed for one minute. Could not get the keyboard showing at all.... Uninstalled and moved on..... Flashed another lollipop rom
ddaazzzzaa said:
I had this ROM installed for one minute. Could not get the keyboard showing at all.... Uninstalled and moved on..... Flashed another lollipop rom
Click to expand...
Click to collapse
skip all. goto input settings, keyboad, advanced, enable hardware keyboard.
Where is N7100 one?
NisseCool said:
Where is N7100 one?
Click to expand...
Click to collapse
i think if u have a n7100 modem and kernel handy u can use any n7105 rom. dont quote me but im pretty sure.