{
"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"
}
Overview
OmniROM is pretty close to AOSP, as the 4.4.4 era comes to a close I've decided to post it.
This build has nothing to do with Nobe1976.
It is not his build on Droidrzr forums and was built by me, from source. Although it is likely the same (assuming configs for our device haven't changed much the past year)
Download
Feb/27/2015: OmniROM 4.4.4
KKBL only for now folks!!!
Source
Device
https://github.com/CyanogenMod/android_device_motorola_moto_msm8960/tree/cm-11.0
Kernel
https://github.com/CyanogenMod/android_kernel_motorola_msm8960dt-common/tree/cm-11.0
Vendor
https://github.com/TheMuppets/proprietary_vendor_motorola/tree/cm-11.0
Yes JJBL people, I will build for you, but I need someone to test so OmniROM aside; IF JBBL people want these firmware I will need a tester :<
Just flashed this on my XT926 and the only issue ive had is when going into Settings>More>Mobile Networks>Carrier Settings The process com.android.phone force closes.
nice rom, works fairly well on my razr m. feels lighter than cyanogenmod and other 4.4.x roms.
lol
Do you know about Lollipop? lol
Working really great on my XT925.. I love OmniRom.. Thanks @Tqr
The fact that this base appeared here means MIUI v6 comes soon
Edit: I'm NOT heading MIUI v6 I am only working as an assistant this is not my era to shine; with that being said if I can't get a JBBL volunteer It's not likely JBBL people will get MIUI v6
kkruglov said:
nice rom, works fairly well on my razr m. feels lighter than cyanogenmod and other 4.4.x roms.
Click to expand...
Click to collapse
A lot of people use my MIUI or other fork builds but don't really have the chance to use my source-builds which are almost always nearly 'perfect' (I don't usually post them)
Some compatibility takes a huge hit after I start chopping stuff to pieces so I just wanted to throw this up for people who are the opposite of the MIUI/Lewa/Whatever crowd and just want something as close to 'stock' android as possible.
Tqr said:
but don't really have the chance to use my source-builds which are almost always nearly 'perfect' (I don't usually post them)
Click to expand...
Click to collapse
why?
kkruglov said:
why?
Click to expand...
Click to collapse
It would annoy me if someone ported a ROM I had planned to work on using a base I built.
Tqr said:
The fact that this base appeared here means MIUI v6 comes soon
Edit: I'm NOT heading MIUI v6 I am only working as an assistant this is not my era to shine; with that being said if I can't get a JBBL volunteer It's not likely JBBL people will get MIUI v6
Click to expand...
Click to collapse
Looking forward to see MIUI v6! Loved MIUI even since my evo 3d. Hope it comes soon
Sent from my DROID RAZR HD using XDA Free mobile app
dulexetina said:
Looking forward to see MIUI v6! Loved MIUI even since my evo 3d. Hope it comes soon
Sent from my DROID RAZR HD using XDA Free mobile app
Click to expand...
Click to collapse
Me too but my build configs are currently not working correctly for some devices.
It's kind of problematic on my end at this point because the past two builds of (pretty much) AOSP have resulted in failure for some unknown reason; even with supported configs.
At the same time to bring a close-to-AOSP ROM to this firmware I had to make a lot of changes in source; changes which may have caused breakage upon building for some devices so I've had to revert everything for this specific build which will probably set the process back a day or two.
But I don't want to sound over-important; the person heading v6 could have(and has) done this fully on their own power without issue and I am really contributing nothing except for build related stuff which isn't even essential It's just to save them time because a lot of time was saved in my life during v5.
It's like they say, someone does something for you and you do something for them if you can; a capacity I'm kind of failing in right now because a lot of the devices I'd like to see get hit with v6 do not have proper source bases
Thanks, very smooth... can you add HDR feature?
ikromy said:
Thanks, very smooth... can you add HDR feature?
Click to expand...
Click to collapse
Maybe, I have to address JBBL right after I finished with the device I'm building for right now.
Like a true piece of scum I neglected the JBBL folks during v5 because I wasn't aware of the exacts surrounding it and frankly was too lazy/busy to produce it.
But from here out all of my builds will also accomodate JBBL now that I know how to deal with it.
I mean it's really like a friend of mine said; that it's better to release broken things at first because If you release something right the first time your topic won't have as many views and as much attention but I've always kind of been a black sheep with my preference for (nearly fully) functional first releases
Edit: I can do MIUIv5 for JBBL if people really still care about it but I'd rather focus on getting things ready for V6, and other projects I'm working on
It's really important that ANY errors with this code-base are brought to my attention , I really do not want to find out there is some inherent error in this when V6 is released It's really important that I do this right so I don't have to bother the developer of it to do yet another build on a rebase.
I feel like I've really annoyed people because I've had multiple peers/friends/co-workers/whatever download firmware that somehow 'wasn't right' this week
Do it. It's been awhile. And that miui phone overseas is killing em softly. I'm on jbbl now to start fresh but if you decide to put out v5 I'll try it. I am ecstatic about v6 to try out.. I will be trying the omni for now. I need a real stable ROM at the moment.
Get lolly miui for mb886.
manuski said:
Do it. It's been awhile. And that miui phone overseas is killing em softly. I'm on jbbl now to start fresh but if you decide to put out v5 I'll try it. I am ecstatic about v6 to try out.. I will be trying the omni for now. I need a real stable ROM at the moment.
Click to expand...
Click to collapse
MIUI v6 is now nearly fully functioning on moto_msm8960 JBBL & KKBL, including V6 camera, scanner and all the other stuff you'd expect.
Unlike being a PatchROM build this is a direct adaptation from a Xiaomi device so there is a level of exclusivity here.
I really don't have the right to release this, It will be part of a friends multi-base thread; It'll show up at some point next month, hopefully.
I wanted to let people who are really anticipating being able to use V6 know that the codebase is finished; it does have all the features you'd expect on true stock MIUI that have never been ported (In this era):
- MIUI camera (Everything, including filters, panorama, fast&slow-motion recording mode...)
- MIUI Scanner (Everything)
- Nearly full native Xiaomi drivers (!)
- Everything, all features
TecknoFreak said:
Get lolly miui for mb886.
Click to expand...
Click to collapse
It's being worked on as well, but 4.4 takes priority because it is literally almost finished.
Tqr said:
MIUI v6 is now nearly fully functioning on moto_msm8960 JBBL & KKBL, including V6 camera, scanner and all the other stuff you'd expect.
Unlike being a PatchROM build this is a direct adaptation from a Xiaomi device so there is a level of exclusivity here.
I really don't have the right to release this, It will be part of a friends multi-base thread; It'll show up at some point next month, hopefully.
I wanted to let people who are really anticipating being able to use V6 know that the codebase is finished; it does have all the features you'd expect on true stock MIUI that have never been ported (In this era):
- MIUI camera (Everything, including filters, panorama, fast&slow-motion recording mode...)
- MIUI Scanner (Everything)
- Nearly full native Xiaomi drivers (!)
- Everything, all features
Click to expand...
Click to collapse
This is great to hear man! Now I want to try it even more.Can't wait till next month...release it tomorrow MIUI 5 was great,simple and smart,just hope that v6 is gonna be same or even better.
Sent from my DROID RAZR HD using XDA Free mobile app
Honestly I straight up lied.
MIUI v6 boots with full function except RIL- Because of the nature of this work all builds have been kept closed. I will check with the head of development and ask if beta may begin.
If anyone here feels strong in development and can address RIL both the KKBL and JBBL can have this firmware in the very forseeable future. It's because we use some kind of fked up Generic RIL and I'm not sure where to play Xiaomis invasive code because It's so different.
I do not even know how this device handles RIL in the 4.4 era, if anyone has an understanding of this please be in touch.
Related
For all Porting discussions and requests hopefully they get answered. I think soon once a Dev knows what they are doing, this will be the case he will work with all the i9300 Rom Devs and work on porting them to I9305.
Hopefully. . Lol
I'm suspecting not that hard - in fact i am now porting ... seems to have good progress =]
it wont be long when devs start to play with I9305, we just need to keep this forum active and help people like Kazuni with their rom testing
_ray_ said:
it wont be long when devs start to play with I9305, we just need to keep this forum active and help people like Kazuni with their rom testing
Click to expand...
Click to collapse
I can't guarantee my promptly reply on debugging and feature requests, but they are welcome. After all I have a pretty hectic daytime job
kazuni said:
I can't guarantee my promptly reply on debugging and feature requests, but they are welcome. After all I have a pretty hectic daytime job
Click to expand...
Click to collapse
any chance of ASOP any time soon? in your opinion...
Hope so, will make rom development alot eaisier if they can just port them accross for us
had hypergalaxy ported to my device... now trying to get the FC out... and trying to figure out abt the signal lost...
with so much debate of whether the I9305 supports fm radio I wonder if anyone has ported the I9300 radio app/firmware to settle the argument. not that i really care about fm radio lol...
springah said:
any chance of ASOP any time soon? in your opinion...
Click to expand...
Click to collapse
AOSP would be a bit difficult for me, as I am not very good at working on AOSP materials however I will still investigate porting something like CM/MIUIv4 over when I got some time this weekend
cyborg24 said:
with so much debate of whether the I9305 supports fm radio I wonder if anyone has ported the I9300 radio app/firmware to settle the argument. not that i really care about fm radio lol...
Click to expand...
Click to collapse
ive tried few fm radio and is not working with our stock kernel..
kazuni said:
AOSP would be a bit difficult for me, as I am not very good at working on AOSP materials however I will still investigate porting something like CM/MIUIv4 over when I got some time this weekend
Click to expand...
Click to collapse
How about AOKP? Or is CM AOKP....?
Also, which part of the rom is it that is making things like the toggle switches big, green and ugly, and not a stock JB look of small and blue?
Like 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"
}
singlecell83 said:
How about AOKP? Or is CM AOKP....?
Also, which part of the rom is it that is making things like the toggle switches big, green and ugly, and not a stock JB look of small and blue?
Like this :
Click to expand...
Click to collapse
AOKP is a complete new set of material to work with - it requires custom kernel building and additional proprietary drivers, and fortunately samsung has provided I9305 as open source already; however, i am not familiar with kernel building on android, so I probably won't be working on CM based builds unless I can gain some more knowledge :\ Sorry.
Fm radio will not work if the kernel does not support it, and if the kernel that came with firmware which didnt have FM radio pre-installed then it wont be programmed to support it, Basically meaning no drivers. Mick.Wheels was working on compiling a kernel to support FM but he is now on holidays so gotta wait. This guy caled Weeeo was reveiwing a I9305 for his sponsor SamsungUK apparently, But I saw his video on youtube and it was showing the FM radio app , so i asked him if he could test it which he did and was working fine. so I am in the middle of asking him to create a nandroid for us to play with. He is currently waiting for a replacement phone as his screen was scratched. So will see what happens then when it returns. Exciting timessssss
btemtd said:
Fm radio will not work if the kernel does not support it, and if the kernel that came with firmware which didnt have FM radio pre-installed then it wont be programmed to support it, Basically meaning no drivers. Mick.Wheels was working on compiling a kernel to support FM but he is now on holidays so gotta wait. This guy caled Weeeo was reveiwing a I9305 for his sponsor SamsungUK apparently, But I saw his video on youtube and it was showing the FM radio app , so i asked him if he could test it which he did and was working fine. so I am in the middle of asking him to create a nandroid for us to play with. He is currently waiting for a replacement phone as his screen was scratched. So will see what happens then when it returns. Exciting timessssss
Click to expand...
Click to collapse
That would be great. On one hand we have a dev that would try to compile the kernel from source - which means we could (in future) adding overclocking support, init.d support, amongst a few things.
On the unfortunate part is that, I've contacted gokhanmoral and confirmed that works on LTE model will not be done since there are not enough time nor the actual hardware. It would be great if someone can pickup the source from git and see if there are anything we can do to make a branch.
I was also looking into porting CM. But as of today I haven't found time to get a new build environment up and running. Maybe I'll look into it later today. As far as I saw it shouldn't be too hard to port CM from 9300... But on the other hand I have less experience with Samsung phones than with their TVs Anyway, if I get some progress you will be the first to know about it.
Gesendet von meinem GT-I9305 mit Tapatalk 2
I have an i9300, and just stumbled onto this thread. If someone can give me a system dump there is a good chance I can compare both of them and see the differences between the i9300 and i9305. It shouldn't be too different, probably requiring some minor changes to get this working (the main difference here is only the radio to support LTE and the extra RAM)
Sent from my Transformer Pad Infinity TF700T using xda app-developers app
I will give you what you need, I have just PM'd you ... You have the Brain I have the Game (I9305) looll Letz Do dizzzz braaa Team LIQUID indhouse lol
hiemanshu said:
I have an i9300, and just stumbled onto this thread. If someone can give me a system dump there is a good chance I can compare both of them and see the differences between the i9300 and i9305. It shouldn't be too different, probably requiring some minor changes to get this working (the main difference here is only the radio to support LTE and the extra RAM)
Sent from my Transformer Pad Infinity TF700T using xda app-developers app
Click to expand...
Click to collapse
If that is all the differences are, and the 9305 parts can be implemented into a 9300 rom, does that mean we could convert any custom 9300 rom into a 9305 rom? Or am I just dreaming?
singlecell83 said:
If that is all the differences are, and the 9305 parts can be implemented into a 9300 rom, does that mean we could convert any custom 9300 rom into a 9305 rom? Or am I just dreaming?
Click to expand...
Click to collapse
Most of the time yes, because we just have to be careful about integrating the drivers for the modem. I'm not so sure about CM/AOKP roms since they have their own built drivers. I'm unfortunately not familiar with driver building so perhaps someone else can shed some light on this topic hopefully.
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums & Read the Forum Rules
Thanks ✟
Moving to Q&A
Original Thread Here: http://droid-hive.com/index.php?/topic/1752-rom-port-carbon-droid-razrmaxx-hd-unofficial/
This ROM requires an unlocked bootloader and is XT926 ONLY
TMC363 has successfully ported Carbon to the HD! ALL credit to him for the port. Here is what he has to say about it:
"This is a port of Team Carbons Rom for the VZW Razr/Maxx Hd. All credit for the creation of the rom is team carbons which is listed at the bottom of the page."
TEAM CARBONS ORIGINAL POST: http://androidforums.com/metropcs-g...649-rom-official-carbonrom-4-2-2-03-30-a.html
Thanks:
"Dhacker for fixing, creating, updating, and correcting and redoing my screw ups and making the changes to cause this beast to work even when his give-a-crap meter was at -60% and much more."
DONATE TO DHACKER29
https://www.paypal.com/cgi-bin/webs...bn=PP-DonationsBF:btn_donate_LG.gif:NonHosted
"DroidTh3ory for spending 2 straight days setting the **** up, trouble shooting with me, teaching me github step by step and much more."
DONATE TO DROIDTH3ORY
https://www.paypal.com/cgi-bin/webs...=PP-DonationsBF:btn_donateCC_LG.gif:NonHosted
WITHOUT THESE 2 GUYS THIS PORT WOULD BE NON-EXISTENT.
Bkjolly for helping with many different things both related to this and android in general.
CarbonRom is an aftermarket firmware based on the Android Open Source Project. The team is composed of former members of Team Liquid who have forked the code in an attempt to bring greater speed, better coding, and full authorship to code. We are in no way affiliated with Liquid0624. The rom was forked at Liquid beta 3.2.1 and has since undergone major code changes and modifications. Please note that on some devices the kernel is not yet linaro compiled.
Please feel free to look at, build, and use our code on CarbonDev GitHub
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.
{
"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"
}
Features:
Here are just a few of the features!
Android 4.2.2
PIE
Xposed Framework (May cause stability or performance issues - use at your own risk!)
Comprehensive speed enhancements, including Linaro -O3 and processor-specific optimizations
Unofficial Voodoo Sound support on Note 2 and i9300 devices.
Option to hide lockscreen hints
Carousel lockscreen
Customizable lockscreen buttons and sliders
Chronus clock widget
Customizable hardware and software keys
Transparent navbar and status bar
Customizable navbar ring
Navbar arrow keys
Navigation bar widgets
Customizable power menu
Notification power widget
Notification brightness adjustment
Customizable quicksettings panel
Statusbar mods including center clock and color
LCD Density
Theme engine
Quiet hours
Volume rocker music controls
Full Rotation
Customizable battery and notification light
More that haven't even been mentioned, and more to come!
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!
-http://imageshack.us/a/img11/4425/facebookicont.jpg
-https://www.twitter.com/carbonrom
-https://plus.google.com/103315278250477995368/posts
Download:
As requested by the developer please go here to download the ROM: http://droid-hive.com/index.php?/topic/1752-rom-port-carbon-droid-razrmaxx-hd-unofficial/
For the best support please ask questions in the original thread
Bugs:
Anything that the official carbon/cm roms currently have
Who is Team Carbon?
andros11
BigShotRob
dg4prez
Kejar31
mattmanwrx
morfic
nocoast
pixeldotz
slick_rick
ToxicThunder
winner0
DONATE:
http://droid-hive.com/index.php?app=donate&module=display§ion=display&do=donate&goal=5
** Again I am just the messenger. All credit for this Port goes to TMC363 and the Carbon devs alone.**
Reserved
Downloading now
So....video recording will not work on this ROM I assume? This is the only thing I'm holding out on before I unlock my bootloader and load any 4.2.x ROM
There is an 11 page thread with 200+ replies about this ROM over on Droid-Hive. There's a link to the thread in the OP. The recurring problems I've read about over there are difficulty with GPS lock, lack of screen brightness control, lack of video recording capability, overheating. From what I've read the only one of those issues that seems widespread (rather than some having the problem and others NOT having the problem) is lack of video recording. I'm still running stock ROM 4.1.2 rooted with unlocked bootloader but I'm reading all the time about custom ROMs. Haven't found the one I'll take the plunge on as I need the functions that typically are problematic (Bluetooth, camera, etc) but from what I've read Carbon seems like a solid choice.
lesdense said:
There is an 11 page thread with 200+ replies about this ROM over on Droid-Hive. There's a link to the thread in the OP. The recurring problems I've read about over there are difficulty with GPS lock, lack of screen brightness control, lack of video recording capability, overheating. From what I've read the only one of those issues that seems widespread (rather than some having the problem and others NOT having the problem) is lack of video recording. I'm still running stock ROM 4.1.2 rooted with unlocked bootloader but I'm reading all the time about custom ROMs. Haven't found the one I'll take the plunge on as I need the functions that typically are problematic (Bluetooth, camera, etc) but from what I've read Carbon seems like a solid choice.
Click to expand...
Click to collapse
It's the best choice there is.. Battery isn't stock but it's worth it trust me
Sent from my XT926 using xda premium
lesdense said:
There is an 11 page thread with 200+ replies about this ROM over on Droid-Hive. There's a link to the thread in the OP. The recurring problems I've read about over there are difficulty with GPS lock, lack of screen brightness control, lack of video recording capability, overheating. From what I've read the only one of those issues that seems widespread (rather than some having the problem and others NOT having the problem) is lack of video recording. I'm still running stock ROM 4.1.2 rooted with unlocked bootloader but I'm reading all the time about custom ROMs. Haven't found the one I'll take the plunge on as I need the functions that typically are problematic (Bluetooth, camera, etc) but from what I've read Carbon seems like a solid choice.
Click to expand...
Click to collapse
I've been running Carbon for about a week now and from personal experience here are the issues I've encountered.
1) No video recording
2) The phone can run hot when used for a little bit
3) Random reboots have increased. I didn't have one until about day 3 in and yesterday I had 3.
4) I would say the data signal is not quite as strong.
5) I can't personally send MMS. I was able to for about a day but after a random reboot, i was unable to get it to work again. But no one else seemed to have that issue.
I personally had no difficulties with GPS or Brightness. There is a new build out released yesterday but for me the brightness was stuck at 100% so I reverted back to the older version until that's fixed. Just thought you guys might want to hear from someone who's been using it as a DD. It's awesome - probably the best ROM out for the HD right now. But of course it has it's flaws.
Been running this since late last week and so far it's the best 4.2 rom I've used. I've not seen a single random reboot, GPS and MMS work fine and battery life is comparable to the other 4.2 roms I've installed. I have seen some sluggishness that required a manual reboot (wiping caches for good measure) to fix. I did noticed the phone running a bit hot a few times, but nothing much worse than other custom roms. Overall it's smooth and responsive with great customization options.
Sent from my Carbonized RAZR Maxx HD
hickmanje2 said:
I've been running Carbon for about a week now and from personal experience here are the issues I've encountered.
1) No video recording
2) The phone can run hot when used for a little bit
3) Random reboots have increased. I didn't have one until about day 3 in and yesterday I had 3.
4) I would say the data signal is not quite as strong.
5) I can't personally send MMS. I was able to for about a day but after a random reboot, i was unable to get it to work again. But no one else seemed to have that issue.
I personally had no difficulties with GPS or Brightness. There is a new build out released yesterday but for me the brightness was stuck at 100% so I reverted back to the older version until that's fixed. Just thought you guys might want to hear from someone who's been using it as a DD. It's awesome - probably the best ROM out for the HD right now. But of course it has it's flaws.
Click to expand...
Click to collapse
I agree it is probably the best choice available. According to the dev, the update was just a new link...not an actual update. I was going to flash it until I read that. I've had the reboot issue but considering where this phone was a month ago, I am happy.
Also there is a new CM10 over at the Razr site. I am going to give it a try this weekend but it will have to be flawless for me to leave Carbon.
Sent from my XT926
I went back to Nexusque today. After nearly a week with perfect GPS on this rom it just decided it did not want to lock even though it had a fix on 14 birds this morning.
After a reboot the GPS would not work at all. Booting into recovery and wiping cache and dalvik made no difference either. Oh well, next time it's updated I'll give it another look.
animez said:
I went back to Nexusque today. After nearly a week with perfect GPS on this rom it just decided it did not want to lock even though it had a fix on 14 birds this morning.
After a reboot the GPS would not work at all. Booting into recovery and wiping cache and dalvik made no difference either. Oh well, next time it's updated I'll give it another look.
Click to expand...
Click to collapse
I had the same problem. I had to install from a stock based ROM (I used the 4.1.2 stock). Now GPS is working after each reboot (which unfortunately is like 3-4 times a day) I get if you want to wait for an update, but wanted to let you know there is possibly a solution out there if you really want to use this ROM.
nweaver11 said:
I had the same problem. I had to install from a stock based ROM (I used the 4.1.2 stock). Now GPS is working after each reboot (which unfortunately is like 3-4 times a day) I get if you want to wait for an update, but wanted to let you know there is possibly a solution out there if you really want to use this ROM.
Click to expand...
Click to collapse
Yeah, I'm sure the GPS stock-lock boogie would get it fixed, but I'm kinda past wanting to bother with it. I love this rom, but if things are just going to spontaneously break like that I would just as soon camp on a stock based rom till Hashcode gets the 4.2 kernel done.
the ROM sounds nice, i downloaded it and tried to set it up, but i have a question, i am using the phone overseas, so i am not on Verizon, how can i add APN settings please? and how to select GSM only? thanks in advance
beboo55 said:
the ROM sounds nice, i downloaded it and tried to set it up, but i have a question, i am using the phone overseas, so i am not on Verizon, how can i add APN settings please? and how to select GSM only? thanks in advance
Click to expand...
Click to collapse
Download the gsm version at DH
Sent from my XT926 using xda premium
triskropf97 said:
Download the gsm version at DH
Sent from my XT926 using xda premium
Click to expand...
Click to collapse
Thanks for your reply, but actually i have xt926, the verizon one, i dont think the GSM version would work with it, the phone was working normal on stock and almost all the other ROMs
if just i can find how to enter the APN settings, it used to be under the access point name
ok i found the APN settings, i entered the APN, the same i used to use all the time on other ROMs but there is no internet, i think it is ROM related, i dont know why i cant post on DH till now, i posted on post, after that i cannot post that is why i am posting here
dw
Can I use it on the xt 925?
Enviado desde mi XT925 usando Tapatalk 2
No, this one is xt926 only.
Sent from my XT926 using Xparent Cyan Tapatalk 2
is it going to be to xt925¿
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.
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.
Screenshots
{
"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"
}
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 goo.im page.
http://goo.im/devs/carbon
Changelog
For a detailed changelog, check out the changes made each night here:
Change Log
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 goo.im page linked above. It's new, but expanding fast. Just like us!
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?
Andros11
BigShotRob
Bionic Beast
dg4prez
Kejar31
mattmanwrx
morfic
nocoast
pixeldotz
slick_rick
winner00
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!
Buglist
Some (not all) seem to experience issues with GPS. If you have issues with GPS, please flash the official JB from Moto/your provider and then flash Carbon. GPS should work now. (I've also heard you can just flash back to stock, get a lock, then flash Carbon again...)
While capturing a picture to send via MMS, ensure HDR is deselected - Gallery will cause a force close if HDR is enabled!! (Note - HDR works for normal still photos, just not MMS.)
Update Google Search (manual update), or else any voice searches will fail with FC. Update the app, and it is resolved.
Please use the provided gapps below. They are the official Google ones for 4.3.
gapps-jb-20130813-signed.zip Mirror #1 Mirror #2
Alright folks! I have submitted the merge requests, I really hope they make it for tonight's run of nightlies... I can upload the build I rolled as a test if needed, no worries!
What are the chances of gps working? And blue tooth audio lol.
Sent from my PACMAN MATRIX HD MAXX
It's nice to see some official development going on here. I'll download to test tomorrow after school.
Sent from my MB886 using xda app-developers app
deeje00 said:
What are the chances of gps working? And blue tooth audio lol.
Click to expand...
Click to collapse
Seconded on the BT audio. I don't have an aux hooked up in my car, and USB audio isn't a thing with this phone, so BT audio is how I listen to my music. Must have for me!
This ROM looks pretty nice though! Can't wait to give it a try!
deeje00 said:
What are the chances of gps working? And blue tooth audio lol.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
thedeany said:
Seconded on the BT audio. I don't have an aux hooked up in my car, and USB audio isn't a thing with this phone, so BT audio is how I listen to my music. Must have for me!
This ROM looks pretty nice though! Can't wait to give it a try!
Click to expand...
Click to collapse
You guys are going to have to tell me... I don't have the device (see the OP), and thus I cannot test.
What I can tell you is my device (Photon Q) is the same SoC... so in theory it should work the same. BT audio streaming and GPS both work great here.
If you folks have run the CM10.1 build from epinter, the buglist there basically applies here.
arrrghhh said:
You guys are going to have to tell me... I don't have the device (see the OP), and thus I cannot test.
What I can tell you is my device (Photon Q) is the same SoC... so in theory it should work the same. BT audio streaming and GPS both work great here.
If you folks have run the CM10.1 build from epinter, the buglist there basically applies here.
Click to expand...
Click to collapse
Well, from what I've understood from other posts, the BT audio is dependent on the kernel, correct? And since we don't have an official 4.2 release, and thus no kernel, BT audio is dead right now. Would the Photon still be the same kernel?
thedeany said:
Well, from what I've understood from other posts, the BT audio is dependent on the kernel, correct? And since we don't have an official 4.2 release, and thus no kernel, BT audio is dead right now. Would the Photon still be the same kernel?
Click to expand...
Click to collapse
Well a lot is dependent on the kernel. BT audio depends on many things, there are some aspects of the kernel that do depend on BT audio... the kernel is basically the interface between the OS and the hardware, so the kernel definitely touches a lot!
Perhaps I should make this more clear. If you have any issues with this CM10.1 ROM, then you will probably have the same issues with this ROM.
Again, I do not have an Atrix HD, I am only supporting this device because the SoC is identical to a moto device I do own... So help me out, run it, let me know what's wrong with it... and I can certainly try and fix it, but unfortunately without the device it won't be easy. I will do my best!
arrrghhh said:
Well a lot is dependent on the kernel. BT audio depends on many things, there are some aspects of the kernel that do depend on BT audio... the kernel is basically the interface between the OS and the hardware, so the kernel definitely touches a lot!
Perhaps I should make this more clear. If you have any issues with this CM10.1 ROM, then you will probably have the same issues with this ROM.
Again, I do not have an Atrix HD, I am only supporting this device because the SoC is identical to a moto device I do own... So help me out, run it, let me know what's wrong with it... and I can certainly try and fix it, but unfortunately without the device it won't be easy. I will do my best!
Click to expand...
Click to collapse
Thank you for the explanation! It's pretty late tonight, but I'll try to flash this tomorrow and let you know what's working and not working for me!
Thanks for the rom. Funny thing is I almost compiled this Sunday. I've seen that branch in the repos and was curious as to what it was. Gonna try it out later.
Also, thanks for the GPS tip. I was on ICS before I started playing with custom roms so I'll flash stock (ugh) and see if that helps. Probably later tonight, I just got up and need to see what needs to be done today. I don't play with my phones when crap might need to be done.
Same problem as other 4.2.2 roms, bluetooth audio does NOT work
tvd0405 said:
Same problem as other 4.2.2 roms, bluetooth audio does NOT work
Click to expand...
Click to collapse
Any issues in the CM10.1 ROM are likely going to be present here.
Interesting tho that my device, same SoC does not suffer from this bug. Will see what I can unearth.
skeevydude said:
Thanks for the rom. Funny thing is I almost compiled this Sunday. I've seen that branch in the repos and was curious as to what it was. Gonna try it out later.
Also, thanks for the GPS tip. I was on ICS before I started playing with custom roms so I'll flash stock (ugh) and see if that helps. Probably later tonight, I just got up and need to see what needs to be done today. I don't play with my phones when crap might need to be done.
Click to expand...
Click to collapse
Actually I've found going back to stock ICS fixed GPS whereas stock JB did not.
Sent from my Atrix HD using Tapatalk 4 Beta
Youngunn2008 said:
Actually I've found going back to stock ICS fixed GPS whereas stock JB did not.
Sent from my Atrix HD using Tapatalk 4 Beta
Click to expand...
Click to collapse
Its never fixed it for me. Are you doing fast boot flashes? I got laid off and no data cord so i have to wait
Sent from my MB886 using xda app-developers app
TTLayland said:
Its never fixed it for me. Are you doing fast boot flashes? I got laid off and no data cord so i have to wait
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
Yeah you have to fast boot all the ICS files from the sbf except of course the getvar and first line in the XML. That way you get all the proper drivers rolled back. Then flash the cwm recovery IMG in fast boot and boot to recovery and flash a custom ROM, usually after this it'll work at least with the xt925 ROMs.
Sent from my Atrix HD using Tapatalk 4 Beta
arrrghhh said:
Any issues in the CM10.1 ROM are likely going to be present here.
Interesting tho that my device, same SoC does not suffer from this bug. Will see what I can unearth.
Click to expand...
Click to collapse
tvd0405 said:
Same problem as other 4.2.2 roms, bluetooth audio does NOT work
Click to expand...
Click to collapse
So has this been beaten to a dead horse? Logs? Anyone made headway with it?
I've poked around a bit, but haven't put a ton of time into it yet. Any info will help shorten my task, thanks!
Running carbon right now. I lowered the CPU speed. Does the performance setting effectively control both cores? I ask because OCs make my device reboot. I'm in no need for the over clock. I recommend setting the default speed to stock speed for compatibility with options to over clock.
Update still getting the reboots. How can I provide error logs for you? FYI I am currently without any micro USB data cable.
Sent from my MB886 using xda premium
arrrghhh said:
So has this been beaten to a dead horse? Logs? Anyone made headway with it?
I've poked around a bit, but haven't put a ton of time into it yet. Any info will help shorten my task, thanks!
Click to expand...
Click to collapse
There is some info about GPS in slimbean thread...thats more like all we have now, i dont think anyone is working on BT audio...let me know if i can help...
I know that build a rom it's not that easy, and make it stable and fully working it's even harder. I also know that drivers and blobs are closed-source, so it's hard to make a device fully working.
But I wanna give some advice, because who want to mod his phone finds about 30/40 roms all unstable and full of bugs.
In my opinion, it's useless to release a rom if it isn't finished, wifi or bluetooth doesn't work, apps force-close, phone reboots randomly or maybe drinks the battery in 2 hours.
Lags in games, the home screen lags with 3/4 widgets. Maybe after a clean install the rom performs well but then you discover that it's not so good.
Let's not forget also that despite the roms are not finished, many times they aren't update any more to solve the bugs, or they are updated but the bugs remain.
I don't mean that ALL the roms have ALL the bugs, but each rom has at least two of those problems.
Some people may say that there are hardware limits to justify the bugs. Or maybe that the battery has to be changed. But those are only excuses considering that on three pages of roms, ONLY one performs well.
I have always been told “you have to change the battery”, or “the phone has got few ram” to justify the bugs. But why with the FluidRom gType (an Italian rom) I manage 24 hours with a normal usage (mobile data always on, wifi, background apps, little playing with games, several calls, facebook and whatsapp)? No lags in games, home and browser. So I assume that “change the battery” and “we have few ram” are only excuses.
If you release a rom only to show that you are able to develop something but then it’s full of bugs, stop. Don’t release it. Or release it when it performs really well.
The 4X it’s a 2012 flagship phone, but the roms are badly developed. So let’s not blame the hardware.
Some people may say “who forces you to change rom?” People try new roms because modders promise improvements.
Maybe this topic will be closed to restrict freedom of speech. But mine are only suggestions.
Serial67 said:
I know that build a rom it's not that easy, and make it stable and fully working it's even harder. I also know that drivers and blobs are closed-source, so it's hard to make a device fully working.
But I wanna give some advice, because who want to mod his phone finds about 30/40 roms all unstable and full of bugs.
In my opinion, it's useless to release a rom if it isn't finished, wifi or bluetooth doesn't work, apps force-close, phone reboots randomly or maybe drinks the battery in 2 hours.
Lags in games, the home screen lags with 3/4 widgets. Maybe after a clean install the rom performs well but then you discover that it's not so good.
Let's not forget also that despite the roms are not finished, many times they aren't update any more to solve the bugs, or they are updated but the bugs remain.
I don't mean that ALL the roms have ALL the bugs, but each rom has at least two of those problems.
Some people may say that there are hardware limits to justify the bugs. Or maybe that the battery has to be changed. But those are only excuses considering that on three pages of roms, ONLY one performs well.
I have always been told “you have to change the battery”, or “the phone has got few ram” to justify the bugs. But why with the FluidRom gType (an Italian rom) I manage 24 hours with a normal usage (mobile data always on, wifi, background apps, little playing with games, several calls, facebook and whatsapp)? No lags in games, home and browser. So I assume that “change the battery” and “we have few ram” are only excuses.
If you release a rom only to show that you are able to develop something but then it’s full of bugs, stop. Don’t release it. Or release it when it performs really well.
The 4X it’s a 2012 flagship phone, but the roms are badly developed. So let’s not blame the hardware.
Some people may say “who forces you to change rom?” People try new roms because modders promise improvements.
Maybe this topic will be closed to restrict freedom of speech. But mine are only suggestions.
Click to expand...
Click to collapse
Haha, there are so many angles i can take on this.
I and the other 4x developers and users don't owe you ANYTHING, dont like our roms? dont use them, Simple. It amazes me some people are so entitled...
Go and make some Roms by yourself we'll see how good they would be .
For your information bringing roms to device in long chain of more people than just our devs
Sent from my LG-P880 using Tapatalk
Serial67 said:
I know that... TL;DR
Click to expand...
Click to collapse
{
"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"
}
Wow ! Never thought I'd read something like this on the 4X forum !
You're so wrong. So so wrong !
Do you realize that when a dev releases a ROM he does this on his time and (most of the time) he doesn't expect anything in return.
Have you ever tried to build a ROM from source ? To compile ? To fix bugs ? To spend hours developing ? I really doubt since you don't realize what this is and the time it takes.
Moreover, our device is "special". The last official update we had was 4.1.2 and thanks to the dev you criticized we are now at 4.4.2 !!! I'm not sure you realized the work of these devs.
Also you say that we don't have any stable ROM but you're wrong ! For me, "stable" means that you can use the ROM daily and profit of all basic and important features of the ROM therefore there ARE stable ROMs ! Since I'm in charge of Beanstalk 4.4.2 I won't give any name but for having personally tried many customs ROMs I can say that we do have stable ROMs.
Everybody has its opinion but man... You're wrong and some devs may understand your post as an offence.
I hope you see what I'm trying to explain.
Sent from my LG-P880 using XDA Premium 4 mobile app
ectoplasma22 said:
Wow ! Never thought I'd read something like this on the 4X forum !
You're so wrong. So so wrong !
Do you realize that when a dev releases a ROM he does this on his time and (most of the time) he doesn't expect anything in return.
Have you ever tried to build a ROM from source ? To compile ? To fix bugs ? To spend hours developing ? I really doubt since you don't realize what this is and the time it takes.
Moreover, our device is "special". The last official update we had was 4.1.2 and thanks to the dev you criticized we are now at 4.4.2 !!! I'm not sure you realized the work of these devs.
Also you say that we don't have any stable ROM but you're wrong ! For me, "stable" means that you can use the ROM daily and profit of all basic and important features of the ROM therefore there ARE stable ROMs ! Since I'm in charge of Beanstalk 4.4.2 I won't give any name but for having personally tried many customs ROMs I can say that we do have stable ROMs.
Everybody has its opinion but man... You're wrong and some devs may understand your post as an offence.
I hope you see what I'm trying to explain.
Sent from my LG-P880 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Don't worry ecto, we are talking about it in the italian forum where this kind of discussion began.. And we are composing it saying exactly what you're saying right here..hope that it'll stop as a great mistake, and to go on..
Sent from my LG-P880 - Beanstalk 4.4.2 - Iodak 9.95 kernel - using XDA Premium 4 mobile app
one word, ridiculous
We should change abit this letter and sent it to the LG dev-update department so they can ask @Demetris @laufer @adam @Ectoplasma @JoinTheRealms @SnXo (and many other talented and good people) for help next time they decide to push or even make any software for any LG phone.I know.this guyment to say official software not custom one so i am just correcting his type mistake.
Послато са LG-P880 уз помоћ Тапатока
whoa, easy there, mate...
First of all, I haven't seen an unstable ROM on our phones up till now. I am personally using CM (unofficial) and SlimKat as my daily drivers, and both are rock stable. The only bugs I have personally encountered are the camera (which is extremely hard to properly fix) and the broken reboot into recovery on Slim. And that's it.
All ROMs you find on xda are made for free, you don't need to pay anything, which means you also can't demand anything. Bringing a ROM to a device can take several hours (disregarding the time the pure download of the sourcecode takes), as every ROM needs its special treatment.
Furthermore, do you have any idea how long the pure compile process takes? On my new machine (which I upgraded for development only) needs ~75min for a clean build. Before that, my lappy was working over 8 hours for a clean build...
Saying we devs wouldn't maintain our ROMs isn't really nice, nor what XDA stands for. We do our best to provide you with the best/fully functional stuff, but there are things we can't fix/improve simply because we don't experience these issues. As an example, I am debugging my kernel ATM, and @FunkyRasta and I both run the kernel, however, FunkyRasta is experiencing lags, that I never experienced. So without his reports, I wouldn't even know about that until someone else might encounter it after the release.
@Serial67, nobody forces you to use "unstable" ROMs, but please don't just complain, but rather give some helpful feedback (logs) to help solve the issues. If you're not willing to provide such info (you don't have to), please don't complain.
Thread closed.
OK so I know everybody had different experiences but I thought I'd share mine and see what others are experiencing .....
Currently running Multirom
Primary -- Android N
Secondaries Tried -- Pure Nexus, Stock Lite, UberStock, and couple others
The N ROM is just a bit buggy and although there are apparently work arounds I can't get many apps to work. Fairly fluid but not "snappy".
Stock Lite has interestingly been the most steady but requires Cat mod to get the bare minimum Moss that I like.
Weirdly enough despite Pure Nexus being so popular, it and a few other AOSP builds have just not been as reliable. I just got a phone call on PN and the screen wouldn't come on until several power button pushes.
UberStock was snappy but it just irritates me to not have a text percentage battery.
The CM builds of various authors usually have their bugs.
Any thoughts? Or share experiences ..... Not necessarily of a specific ROM but more of thoughts Stock, vs AOSP, vs CM etc
Certainly don't want to insult any developers .... Their shared work is appreciated
jcrompton said:
OK so I know everybody had different experiences but I thought I'd share mine and see what others are experiencing .....
Currently running Multirom
Primary -- Android N
Secondaries Tried -- Pure Nexus, Stock Lite, UberStock, and couple others
The N ROM is just a bit buggy and although there are apparently work arounds I can't get many apps to work. Fairly fluid but not "snappy".
Stock Lite has interestingly been the most steady but requires Cat mod to get the bare minimum Moss that I like.
Weirdly enough despite Pure Nexus being so popular, it and a few other AOSP builds have just not been as reliable. I just got a phone call on PN and the screen wouldn't come on until several power button pushes.
UberStock was snappy but it just irritates me to not have a text percentage battery.
The CM builds of various authors usually have their bugs.
Any thoughts? Or share experiences ..... Not necessarily of a specific ROM but more of thoughts Stock, vs AOSP, vs CM etc
Certainly don't want to insult any developers .... Their shared work is appreciated
Click to expand...
Click to collapse
running pure nexus myself. generally, I like staying with aosp builds. but, user experience can be heavily effected by whatever the user installs or mods. like your power button issue, that can happen because of an app, a theme, or a mod. not because the ROM doesn't like it, but becauseany apps, themes, or mods are not made by professionals, but by amateurs.
stock, I usually am on for the first hour to a max of a couple days after getting a nexus. then its usually an aosp build. CM, or CM based ROMs I stay very far away from. I used to be the biggest CM fanboy years ago, but CM is not the CM that used to be. now they are different, as are their goals.
stock+xposed+gravity box and other modules? you don't really need custom roms anymore, having said that I prefer aosp, cm not even once
sgloki77 said:
stock+xposed+gravity box and other modules? you don't really need custom roms anymore, having said that I prefer aosp, cm not even once
Click to expand...
Click to collapse
Do you ever have or feel like xposed slows things down .....? It's been a while since I've tried
simms22 said:
running pure nexus myself. generally, I like staying with aosp builds. but, user experience can be heavily effected by whatever the user installs or mods. like your power button issue, that can happen because of an app, a theme, or a mod. not because the ROM doesn't like it, but becauseany apps, themes, or mods are not made by professionals, but by amateurs.
stock, I usually am on for the first hour to a max of a couple days after getting a nexus. then its usually an aosp build. CM, or CM based ROMs I stay very far away from. I used to be the biggest CM fanboy years ago, but CM is not the CM that used to be. now they are different, as are their goals.
Click to expand...
Click to collapse
Thanks
have all these modules working on pure nexus, snappy as usual
{
"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"
}
Sent from my Nexus 6 using Tapatalk
Since the introduction of Lollipop, I really haven't felt the need to flash a custom ROM.
Stock ROM has always worked great for me, I use root for a few things like Greenify and Xposed, but I stopped using those as well.
On my N6:
Stock ROM - Best so far. Sometimes I don't even use root. Excellent battery life, no bugs and great performance.
PureNexus - Great ROM, however the CMTE version was a bit buggy when I used it. No disrespect to the devs, they're doing an excellent job.
CyanogenMod - My second choice, always. Nightly builds are stable in most ways, I'm using one right now and it's working great with a custom theme and a few mods installed.
---------- Post added at 11:42 AM ---------- Previous post was at 11:41 AM ----------
simms22 said:
I used to be the biggest CM fanboy years ago, but CM is not the CM that used to be. now they are different, as are their goals.
Click to expand...
Click to collapse
Can you elaborate a bit on this?
Everything seems the same to me.
I got my Nexus last year. I ran several kind of custom roms. Most of them dont last longer then a few hours. The one i am using the most and always go back to is Lite Rom. It has everything that i need and is stable, good battery life and just works. Sometimes i feel like the builders just try to put too many things into the rom and it can be confusing. I like to keep it simple and clean.
@murtaza02: I'm not @simms22, but I can provide some insight here. Back before Android hit version 4, Cyanogenmod was "king of custom ROMs". They were on the cutting edge, with lots of features that simply weren't available in Google's stock Android. This was done not for money, but out of love of Android. A few years ago they incorporated and now offer a commercial alternative to Android. Afterward they pretty much stopped innovating, especially after the Focal fiasco.
Cyanogenmod strayed from its roots, looking to get paid money rather than respect.
Strephon Alkhalikoi said:
@murtaza02: I'm not @simms22, but I can provide some insight here. Back before Android hit version 4, Cyanogenmod was "king of custom ROMs". They were on the cutting edge, with lots of features that simply weren't available in Google's stock Android. This was done not for money, but out of love of Android. A few years ago they incorporated and now offer a commercial alternative to Android. Afterward they pretty much stopped innovating, especially after the Focal fiasco.
Cyanogenmod strayed from its roots, looking to get paid money rather than respect.
Click to expand...
Click to collapse
Yes I recall during the time that this was going on there were several very heated discussions that took place here on XDA. The bottom line though 4 those of us not in the know basically I just noticed that cm ROMs definitely changed
Once they incorporated is when the innovation stopped, as that is when they changed focus away from what brought them to the attention of everyone in the Android community. Instead of making a "better" Android, they settled for simply making Android. The Focal fiasco cost them, in that they lost many of their freelance developers, and lost a lot of respect from the community at large.
To this day I don't put Cyanogenmod on my devices, because Cyanogenmod left the building a long time ago.
To be honest I stopped using CM and CM based roms years ago. While it has a little o do with their business model it was mostly due to the fact that there are bugs that have been around for years that were never fixed. Then they merge in code without testing it which has been known to cause huge issues.
I prefer roms built from AOSP which there are very few. I also never go for what is popular. To be honest to many people are sheep and follow the crowd. (yes even in android) I prefer to try some out and make up my own mind. And then I stick with it.
Honestly, I ditched Cyanogenmod because they stopped being innovative. It goes hand in hand with them incorporating, because the profit motive overrides everything else. Profit first, last, and always.