Related
I have a big question that is been floating around in my mind.
We have CM7 which is based on ginngerbread and we got Eagle blood 1.03 which is gingerbread as well.
Why does it seems like eagle blood developers seems to develop way faster and have a more stable rom than CM7?
Is it because they had to port gingerbread to the G2x? If that its the case, wouldn't it be easier to grab the gingerbread leak and develop using that as the source?
eagle blood is from gingerbread leak and cyanogen isn't?
Also does it takes longer for CM7 to develop because they are adding more features to the ROM?
The reason I'm asking is because I had this questions and is nothing against CM7 directly at all, I just want to understand how they are doing it and see the benefits.
Thanks
Sent from my LG-P999 using XDA App
Eagle Blood is based on the existing gingerbread leak with added tweaks.
Cyanodenmod is build completely from the ground up using the AOSP source code. It has features not found in ROMs released by manufacturers.
It's like modding an engine vs building an engine.
regP said:
Eagle Blood is based on the existing gingerbread leak.
Cyanodenmod is build from the ground up using the AOSP source code.
It's like modding an engine vs building an engine.
Click to expand...
Click to collapse
That clears up some of my doubts.
So basically they are using a gingerbread AOSP from google?
And what are the advantages of doing it this way instead of just grabbing a leaked ROM and tweak it.
Sent from my LG-P999 using XDA App
Once they get the device-specific stuff ironed out, feature updates can be added easily across multiple devices.
For example, if you look at the CM7 changelog the unlabeled changes are to all GB devices and the entries labeled "p999" are changes specific to this device.
moshe22 said:
That clears up some of my doubts.
So basically they are using a gingerbread AOSP from google?
And what are the advantages of doing it this way instead of just grabbing a leaked ROM and tweak it.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Better performance. Manufactures ROMs often end up with bad coding which results in a device suffering from things such as bad battery life, lower performance, etc. Also with official ROMs you can't do much with it until they release the source code. And even then (at least with samsung) some things like driver source never get released which means the devs cant fully optimize the ROM. AOSP means full control over the ROM to make it do what you want it to do the way you want it to be done. It does take much longer to complete though which is why CM has nightly updates. Makes it easier to put out a nightly than to put out a whole new ROM for every bug they fix. I'm sure someone can explain this better than me.
r4d14n7 said:
For example, if you look at the CM7 changelog the unlabeled changes are to all GB devices and the entries labeled "p999" are changes specific to this device.
Click to expand...
Click to collapse
Oh good to know, thanks
regP said:
Better performance. Manufactures ROMs often end up with bad coding which results in a device suffering from things such as bad battery life, lower performance, etc. Also with official ROMs you can't do much with it until they release the source code. And even then (at least with samsung) some things like driver source never get released which means the devs cant fully optimize the ROM. AOSP means full control over the ROM to make it do what you want it to do the way you want it to be done. It does take much longer to complete though which is why CM has nightly updates. Makes it easier to put out a nightly than to put out a whole new ROM for every bug they fix. I'm sure someone can explain this better than me.
Click to expand...
Click to collapse
Wow, this really answers my question as to why it takes them longer. Thanks
So it means that cyanogen even develop their own drivers?
Sent from my LG-P999 using XDA App
You mentioned that you feel eaglesblood is more stable than CM7. Is this from personal experience or from reading the forums? In my experience, CM7 as of around nightly #11 has every significant bug worked out.
MWBehr said:
You mentioned that you feel eaglesblood is more stable than CM7. Is this from personal experience or from reading the forums? In my experience, CM7 as of around nightly #11 has every significant bug worked out.
Click to expand...
Click to collapse
I must disagree. I LOVE CM 7 and ran build 11 and 13 and found it rather buggy right now. Sometimes the touch screen didn't recognize touches on the right side(I consider this a significant bug). When you call a number and have to punch in numbers (like a VM password or when dialing an extension) did not work for me(which I consider another significant bug). I also heard there are issues with it sticking APN settings(cant comment because I didnt really check that when I had cm 7 installed) I just dont think cm 7 is stable enough at the moment. Eagle Blood is running pretty well right now. I would say a lot better than cm 7 but that will change once CM gets the bugs worked out
MWBehr said:
You mentioned that you feel eaglesblood is more stable than CM7. Is this from personal experience or from reading the forums? In my experience, CM7 as of around nightly #11 has every significant bug worked out.
Click to expand...
Click to collapse
Yes, personal experience. Been running eb 1.02 and is been great.
I Just flashed CM7 #15 just to test it out and is buggy for me
-When i receive a call i don't get any sound from the ringer even though is not muted
-Sensors are like in auto brightness even though they are not
-The performance of the whole system isn't the best.
I am sure it will be the best ROM out there but as for now still only and nightly and is buggy
Sent from my LG-P999 using XDA App
One significant difference for me, which is due to the fact that Cyanogen has built their own rom with their different bluetooth stacks (as opposed to LG's custom ones), is that bluetooth controllers actually work with CM7. Useful for using a wiimote on emulators through HDMI
Just something to consider, no bluetooth controllers on EB.
Sent from my LG-P999 using XDA App
regP said:
Eagle Blood is based on the existing gingerbread leak with added tweaks.
Cyanodenmod is build completely from the ground up using the AOSP source code. It has features not found in ROMs released by manufacturers.
It's like modding an engine vs building an engine.
Click to expand...
Click to collapse
Right, and not only that, cyanogen has many different phones he and his dev team have to work on.
Sent from my LG-P999 using Tapatalk
Build #16 is out today and supposedly the TouchTones in the dialer and the backlight is fixed (thank god!)
But yes. Cyanogen builds their own kernel and drivers, which is why it usually is more compatible with stuff like WiiMotes and stuff. But once they get the Kernel working properly (which they are doing now) it is just a matter of updating the core OS then it can be pushed to all devices pretty seamlessly (I guess).
There are lots of benefits of using CM over standard stock Gingerbread. For one, Stock is 2.3.3 where CM7 is 2.3.4 so it supports lots of Googles new apps like Video in Google Talk and the new Cloud Music player.
Also there are tons of tweaks like Notification menu toggles, System Themes, Sound Profiles, Black-List calling, Several Lockscreen types and Widgets with Gesture support, etc the list goes on and on.
Between the Notification Toggles and Themes which you can install from the market, I'm hooked.
Plus it is the only Gingerbread rom that doesn't cause my phone to lockup/reset/Black Screen of Death/whateveryoucallit
MWBehr said:
You mentioned that you feel eaglesblood is more stable than CM7. Is this from personal experience or from reading the forums? In my experience, CM7 as of around nightly #11 has every significant bug worked out.
Click to expand...
Click to collapse
It has tons of bugs like inaccurate battery readings
Sent from my LG-P999 using Tapatalk
my concern is that is the g2x able to do 1080p video recording and high resolution picture like the stock rom? THis is the only reson why I'm still sticking with the stock rom.
MWBehr said:
CM7 as of around nightly #11 has every significant bug worked out.
Click to expand...
Click to collapse
u must be high
jdaclutch said:
my concern is that is the g2x able to do 1080p video recording and high resolution picture like the stock rom? THis is the only reson why I'm still sticking with the stock rom.
Click to expand...
Click to collapse
+1. I take a lot of photos and videos of my kids and would rather stick with 2.2 than have a gimped camera.
r4d14n7 said:
+1. I take a lot of photos and videos of my kids and would rather stick with 2.2 than have a gimped camera.
Click to expand...
Click to collapse
Yeah, i take alot of pictures and videos too
Sent from my LG-P999 using XDA App
What are the differences between these two sources or whatever they are? Still confused what differentiates whitehawkx's AKOP based rom from the Eaglesblood AOSP rom?
Sent from my LG-P999 using XDA
AOSP = Android open source project.
source from google. Nothing added other then what is needed to make it work on the phone. (drivers)
AOKP = Android open kang project
Close to aosp but with many enhancements added behind what is needed to make it work on the phone.
Cyanogen mod would fall into the same category as AOKP.
Hope this helps.
painter_ said:
AOSP = Android open source project.
source from google. Nothing added other then what is needed to make it work on the phone. (drivers)
AOKP = Android open kang project
Close to aosp but with many enhancements added behind what is needed to make it work on the phone.
Cyanogen mod would fall into the same category as AOKP.
Hope this helps.
Click to expand...
Click to collapse
Thank you, that cleared up alot.
Sent from my LG-P999 using XDA
That's what i thought thanks for the confirmation
painter_ said:
AOSP = Android open source project.
source from google. Nothing added other then what is needed to make it work on the phone. (drivers)
AOKP = Android open kang project
Close to aosp but with many enhancements added behind what is needed to make it work on the phone.
Cyanogen mod would fall into the same category as AOKP.
Hope this helps.
Click to expand...
Click to collapse
as would all the other ROMs on here? hellfire, eaglesblood? they are made from CM7/9 correct? unless otherwise noted?
dodgefan67 said:
as would all the other ROMs on here? hellfire, eaglesblood? they are made from CM7/9 correct? unless otherwise noted?
Click to expand...
Click to collapse
not really, AOKP uses some CM9 stuff, but its definitely a proper ROM on its own.
Any rom that says AOSP in its name is generally Built from google source code, with little to nothing from CM7/9 other than what might be necessary to get things running.
MIUI is another rom that, while built from CM7/9 is VERY different.
ROM's like Hellfire, and others similar to it, are mostly just a proper CM7/9 ROM with tweaks, and small fixes put into it, and more recently (to my annoyance) other kernels too.
Overall, CyanogenMod was probably the greatest thing to happen to android modding as a whole, they provide a base for most things to branch off from (and they don't even complain when everyone and everything uses their source!) The only reason its in everything is because if its something that the user will not see, and it works, why spend the days/weeks/months to develop it when its sitting right on CyanogenMod's GIT.
this explains alot
Klathmon said:
not really, AOKP uses some CM9 stuff, but its definitely a proper ROM on its own.
Any rom that says AOSP in its name is generally Built from google source code, with little to nothing from CM7/9 other than what might be necessary to get things running.
MIUI is another rom that, while built from CM7/9 is VERY different.
ROM's like Hellfire, and others similar to it, are mostly just a proper CM7/9 ROM with tweaks, and small fixes put into it, and more recently (to my annoyance) other kernels too.
Overall, CyanogenMod was probably the greatest thing to happen to android modding as a whole, they provide a base for most things to branch off from (and they don't even complain when everyone and everything uses their source!) The only reason its in everything is because if its something that the user will not see, and it works, why spend the days/weeks/months to develop it when its sitting right on CyanogenMod's GIT.
Click to expand...
Click to collapse
binded2 said:
this explains alot
Click to expand...
Click to collapse
yeah it does, thanks Klathmon!!
thanks alot its so cleared now
Klathmon said:
not really, AOKP uses some CM9 stuff, but its definitely a proper ROM on its own.
Any rom that says AOSP in its name is generally Built from google source code, with little to nothing from CM7/9 other than what might be necessary to get things running.
MIUI is another rom that, while built from CM7/9 is VERY different.
ROM's like Hellfire, and others similar to it, are mostly just a proper CM7/9 ROM with tweaks, and small fixes put into it, and more recently (to my annoyance) other kernels too.
Overall, CyanogenMod was probably the greatest thing to happen to android modding as a whole, they provide a base for most things to branch off from (and they don't even complain when everyone and everything uses their source!) The only reason its in everything is because if its something that the user will not see, and it works, why spend the days/weeks/months to develop it when its sitting right on CyanogenMod's GIT.
Click to expand...
Click to collapse
That's almost true. Even though it's AOSP and all from Google's Android source, they still used CM's source tree because they put everything together. No point in spending an enormous amount of time to put it together yourself if CM already did it. So technically it's still a large portion of CM's work.
ok, i got it...
Klathmon said:
not really, AOKP uses some CM9 stuff, but its definitely a proper ROM on its own.
Any rom that says AOSP in its name is generally Built from google source code, with little to nothing from CM7/9 other than what might be necessary to get things running.
MIUI is another rom that, while built from CM7/9 is VERY different.
ROM's like Hellfire, and others similar to it, are mostly just a proper CM7/9 ROM with tweaks, and small fixes put into it, and more recently (to my annoyance) other kernels too.
Overall, CyanogenMod was probably the greatest thing to happen to android modding as a whole, they provide a base for most things to branch off from (and they don't even complain when everyone and everything uses their source!) The only reason its in everything is because if its something that the user will not see, and it works, why spend the days/weeks/months to develop it when its sitting right on CyanogenMod's GIT.
Click to expand...
Click to collapse
Thanx for this information but i need to know more about the layers of the ROM that are there in AOSP and AOKP (i heard this from a friend that AOSP have 7 layers and AOKP has about 10 is that true? and the AOSP makes the interaction easier then that of the AOKP).
miku3191 said:
Thanx for this information but i need to know more about the layers of the ROM that are there in AOSP and AOKP (i heard this from a friend that AOSP have 7 layers and AOKP has about 10 is that true? and the AOSP makes the interaction easier then that of the AOKP).
Click to expand...
Click to collapse
What do you mean by "layers"?
Sent from my Nexus 7 using xda app-developers app
There seems to be quite a few jelly bean roms right now, and without an official leak, I am sure each one has its ups and downs at this point.
I am coming from synergyrom, and want to give JB a try. Since theres is still "beta" I am not sure I wanna try that right away.
Which is the most stable at this point??
Definitely liquid smooth...I've tried others and always revert back to touch wiz stock based roms, and i despise touch wiz...liquid smooth jb is the best I've flashed
Sent from my SCH-I535 using Tapatalk 2
liquid smooth is awesome for aosp JB, but touchwiz there's not much thats super stable imo
thanks for the input so far!
Please note if there are known issues, that might help make decisions too.
Thanks all!!
I like codename. Super smooth, frickin' fast and barely believable battery life! Some apps don't stream audio over bluetooth and you have to enable a couple of Developer options to address screen flickering, but those are truthfully very minor annoyances you'll be happy to overlook when you get a taste of that ROM.
Seriously, try it. http://forum.xda-developers.com/showthread.php?t=1900479
I've tried both liquid and codename. They are both very very similar. I can't find cant difference in customization between the two.
Codename ran a little warm for me, not saying liquid runs cool but still.
The reason I jumped to liquid is because in codename (for me anyway) the 160 character MMS bug still persisted, it does not in liquid.
Sent from my SCH-I535 using xda app-developers app
duarian said:
I've tried both liquid and codename. They are both very very similar. I can't find cant difference in customization between the two.
Codename ran a little warm for me, not saying liquid runs cool but still.
The reason I jumped to liquid is because in codename (for me anyway) the 160 character MMS bug still persisted, it does not in liquid.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I can respect that. Haven't tried liquid as the CNA ROM got posted around the time I got this phone. I've heard the 160 character error msg is a bit of a red herring, that the msgs actually do get sent but just say they didn't. Was that your experience or did they actually not get sent?
One of the biggest issues with JB roms is if your not in a 4G area then be prepared for some non stop 3G data drops. Also I've noticed weaker signal strength in both service and wifi.
Sent from my SCH-I535 using xda app-developers app
bc760 said:
One of the biggest issues with JB roms is if your not in a 4G area then be prepared for some non stop 3G data drops. Also I've noticed weaker signal strength in both service and wifi.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Well said.
Sent from my SCH-I535 using Tapatalk 2
bc760 said:
One of the biggest issues with JB roms is if your not in a 4G area then be prepared for some non stop 3G data drops. Also I've noticed weaker signal strength in both service and wifi.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
There is a fix for this now but just has not made it's way into all AOSP roms yet. There are in most of the newer AOKP builds right now.
The biggest issue still is the low volume when recording video's. This is an issue in all AOSP roms and has not been fixed yet. I know I also read a lot about speakerphone and in call volume problems but not sure to much about the actual issue.
This is why I am still sticking to an ICS TW Rom. I like knowing everything on my device just works.
The only major thing that keeps from moving to CM10, or Liquid Smooth is the lack of USB Audio. I leave my phone on my dock at work and stream Pandora through the dock's usb audio. I've been using SynergyROM for awhile now, and will probably stick with it until the USB Audio issue is fixed.
AOKP's new build has been great for me. No real issues to report yet...been on it since 3 came out a week or so ago?
i haven't been too impressed jb at all tbh.
Well there's two routes you can go to get your JellyBean fix, and that's either AOSP or TouchWiz.
Touchwiz: You've got two choices.
- You could go with Synergy JB 0.2 beta which is based off the AT&T leaked JB touchwiz build. I personally have not ran it so i can't comment on how well it works, but i use synergy as my touchwiz choice of roms, and was never disappointed by there work, so i'm sure the JB build is working great.
- There is also Jellywiz which is made by Incubus, he's been basing his off the latest leaks, and has a few builds out. One of them is a custom build which just has a few theme changes, and a few other things added in/changed. There's a lot of praise in that thread for his rom, the only bug i had when trying it was that i could not get voice and data to work at the same time (phone calls and web browsing at the same time) But that is because its not based off a verizon leak and until then probably will not work.
AOSP: We'll you've got a lot of options, there's a few here on XDA and then some more on Rootzwiki, so i won't be giving detail on all of them, just a few. But they will all generally 'look' the same, by that i mean because they are all based on AOSP source it'll have the same look to it, since source looks the same.
-CM10: Well it's your basic CM that you've grown to love (or hate ) you can expect nightlies, and things to get fixed in a timely matter. If you used CM7 or CM9 on previous devices then you'll know exactly what to expect. Its built directly from source and you can expect it to be speedy quick.
-AOKP: It's built from source as well just like CM10, but has more options in it, and generally more customization as well. If you use it it'll look a lot like CM10, but it'll have added in bonuses
-CodeNameAndroid: Again built from source, but with codename you've got a ton of customization thrown in, there's a lot of stuff from different AOSP options thrown into it. Right now the Navbar doesn't work without flashing a separate file, but that's not a huge problem since its just a little file to flash. I personally am using it right now and its been great to me, can't really complain about it at all
-LiquidSmooth: Built from source, those that have used a liquid rom before will know exactly what to expect. It will be speedy quick and smooth as hell. You'll find plenty of butter in it as well, they've got there own liquidsettings that'll allow you to do even more customization, and i give them major props, i've currently got them going on my old thunderbolt which is my backup phone, but also used them on my OG Droid and i can vouch that they will provide an amazing rom for users
There are more AOSP Roms over on rootzwiki, but its again the same general thing, each AOSP rom comes from source, but each developer will theme/modify/add/remove/customize to there own liking to provide you with what they feel is the best user experience. The biggest difference between the Touchwiz JB roms and AOSP is that with AOSP you'll have a lot more options going and it'll be stock jellybean, no touchwiz nonsense to hold you back. Some people love the touchwiz stuff and that's fine, but some will love having pure jellybean on there phone and being able to take advantage of that. I'll tell you honestly 100% that AOSP will be faster no matter what touchwiz rom you run.
Oh and kernel wise, i fully stand behind imoseyon's lean kernel for AOSP roms, i've always used imoseyon's kernel's and have always gotten amazing battery life on my GS3 and thunderbolt.
Phew i really hope this helps you with any decision you may have
***If i missed any Touchwiz or AOSP roms i do apologize, i don't know them all off the top of my head, so please don't think that just because i left yours out that i meant it in a bad way***
What are the general downsides with using these JB roms weither it be TouchWiz or AOSP. I'm going to take the jump soon but whats fixed or unfixable? I hear some people say screen flicker and no 3G etc.
Neverendingxsin said:
Well there's two routes you can go to get your JellyBean fix, and that's either AOSP or TouchWiz.
Touchwiz: You've got two choices.
- You could go with Synergy JB 0.2 beta which is based off the AT&T leaked JB touchwiz build. I personally have not ran it so i can't comment on how well it works, but i use synergy as my touchwiz choice of roms, and was never disappointed by there work, so i'm sure the JB build is working great.
- There is also Jellywiz which is made by Incubus, he's been basing his off the latest leaks, and has a few builds out. One of them is a custom build which just has a few theme changes, and a few other things added in/changed. There's a lot of praise in that thread for his rom, the only bug i had when trying it was that i could not get voice and data to work at the same time (phone calls and web browsing at the same time) But that is because its not based off a verizon leak and until then probably will not work.
AOSP: We'll you've got a lot of options, there's a few here on XDA and then some more on Rootzwiki, so i won't be giving detail on all of them, just a few. But they will all generally 'look' the same, by that i mean because they are all based on AOSP source it'll have the same look to it, since source looks the same.
-CM10: Well it's your basic CM that you've grown to love (or hate ) you can expect nightlies, and things to get fixed in a timely matter. If you used CM7 or CM9 on previous devices then you'll know exactly what to expect. Its built directly from source and you can expect it to be speedy quick.
-AOKP: It's built from source as well just like CM10, but has more options in it, and generally more customization as well. If you use it it'll look a lot like CM10, but it'll have added in bonuses
-CodeNameAndroid: Again built from source, but with codename you've got a ton of customization thrown in, there's a lot of stuff from different AOSP options thrown into it. Right now the Navbar doesn't work without flashing a separate file, but that's not a huge problem since its just a little file to flash. I personally am using it right now and its been great to me, can't really complain about it at all
-LiquidSmooth: Built from source, those that have used a liquid rom before will know exactly what to expect. It will be speedy quick and smooth as hell. You'll find plenty of butter in it as well, they've got there own liquidsettings that'll allow you to do even more customization, and i give them major props, i've currently got them going on my old thunderbolt which is my backup phone, but also used them on my OG Droid and i can vouch that they will provide an amazing rom for users
There are more AOSP Roms over on rootzwiki, but its again the same general thing, each AOSP rom comes from source, but each developer will theme/modify/add/remove/customize to there own liking to provide you with what they feel is the best user experience. The biggest difference between the Touchwiz JB roms and AOSP is that with AOSP you'll have a lot more options going and it'll be stock jellybean, no touchwiz nonsense to hold you back. Some people love the touchwiz stuff and that's fine, but some will love having pure jellybean on there phone and being able to take advantage of that. I'll tell you honestly 100% that AOSP will be faster no matter what touchwiz rom you run.
Oh and kernel wise, i fully stand behind imoseyon's lean kernel for AOSP roms, i've always used imoseyon's kernel's and have always gotten amazing battery life on my GS3 and thunderbolt.
Phew i really hope this helps you with any decision you may have
***If i missed any Touchwiz or AOSP roms i do apologize, i don't know them all off the top of my head, so please don't think that just because i left yours out that i meant it in a bad way***
Click to expand...
Click to collapse
thanks a bunch for the big write-up. I do live in an area that is partly 3g, part 4g, so I am a little concerned about these data drops.. Has this been fixed in the AOSP roms mentioned above?
I would hold out a few more weeks for a touchwiz based rom - I tried Incubus' and got a number of random reboots. Cleanrom 2.5 has been working great!
Currently, all the AOSP roms have the same issues -
- data drops, esp on 3g/4g handoff. There were some recent commits that claim to have fixed this, I'm not sure if it did and which rom's include it
- potential for IMEI loss or brick. Again, you should back up IMEI before any flash, I don't think these issues are present on TW
- TW camera is better. There's an AOSP JB camera mod but hasn't been updated for the newer builds yet
- GPS locks. I keep reading about this in the AOSP rom's, I don't know how common this is.
AndyMan386 said:
thanks a bunch for the big write-up. I do live in an area that is partly 3g, part 4g, so I am a little concerned about these data drops.. Has this been fixed in the AOSP roms mentioned above?
Click to expand...
Click to collapse
your welcome. It ended up being a lot longer than I had originally planned. As for data drops, I'm testing a fix right now and I can confirm it works fine
ECrispy said:
Currently, all the AOSP roms have the same issues -
- data drops, esp on 3g/4g handoff. There were some recent commits that claim to have fixed this, I'm not sure if it did and which rom's include it
- potential for IMEI loss or brick. Again, you should back up IMEI before any flash, I don't think these issues are present on TW
- TW camera is better. There's an AOSP JB camera mod but hasn't been updated for the newer builds yet
- GPS locks. I keep reading about this in the AOSP rom's, I don't know how common this is.
Click to expand...
Click to collapse
Data drops were indeed fixed
Imei issues can happen when flashing anything from radios to kernels to roms both touchwiz to aosp. It can also easily be restored.
Tw camera only has a few more features, but in terms of quality their both equal to me. Once the aosp mod is updated it'll be even better.
GPS lock is simple, just get a full lock before flashing aosp and then while having it locked boot into recovery and do your thing.
Neverendingxsin said:
your welcome. It ended up being a lot longer than I had originally planned. As for data drops, I'm testing a fix right now and I can confirm it works fine
Data drops were indeed fixed
Imei issues can happen when flashing anything from radios to kernels to roms both touchwiz to aosp. It can also easily be restored.
Tw camera only has a few more features, but in terms of quality their both equal to me. Once the aosp mod is updated it'll be even better.
GPS lock is simple, just get a full lock before flashing aosp and then while having it locked boot into recovery and do your thing.
Click to expand...
Click to collapse
link to CM10 data fix?
I've been wanting to give an aosp based Rom a try onthis phone. My main concern is stability and battery life. I know battery life is more of a kernel issue so I will address that later on. I've noticed some roms in original developement don't even specify which android version there based on, but which is currently most stable and 4.2? I need lte calls/sms/mms and camera to be working.
I'm basically looking for what has the LEAST issues. Has any developers gotten past the screen tearing yet?
And I know there are probably 100 of these threads, but none are current
the official cm10.1 by h8rift will usually be the most stable, as a lot of the other ones are based on that (i think). you should basically look for the most recently updated one. that'll have the newest features and latest bugfixes.
you can't go wrong with a bpear ROM, that guy is awesome and has released some of my favorite ROMs for this phone. link: http://forum.xda-developers.com/showthread.php?t=2212825
he always updates them quickly and squashes all major bugs. that one is new so it may have some bugs, but i'm sure they won't be there for long. then once he fixes them, you won't have to delete everything and clean wipe and all that, you'll just have to flash over it with the new one.
bugs vary from phone to phone, so the only real way to figure out what you like is to flash them and check
they are all pretty stable other then known issues. screen tearing is a general issue with 4.2.x roms that use cm10.1 as a base. i would say try liquidsmooth, aokp, or carbon bpear96 aosp build.
Running liquidsmooth Stable and its great. Using it as a daily driver.
Sent from my One X using xda app-developers app
DvineLord said:
they are all pretty stable other then known issues. screen tearing is a general issue with 4.2.x roms that use cm10.1 as a base. i would say try liquidsmooth, aokp, or carbon bpear96 aosp build.
Click to expand...
Click to collapse
Running official 10.1 nightly with vz oc linaro kernel and disable HW overlays on I get ZERO tearing. I put it at standard clock speeds to and its great and very stable. Only time it freezes is every once in a great while after a phone call. Other than that I'm extremely happy.
Sent from my One X using xda app-developers app
I'm running the Bpear CarbonRom 1.6 source build, underclocked to 1134mhz and still running smooth and stable.
Sent from my One XL using XDA Premium
my personal experience
the most stable tend to be the ones that are more popular/bigger like CM 10.1, AOKP, etc.. at least in my experience. Though I personally love jellybam. I highly recommend it especially if you're a person who loves great audio. Though the only kernel that would work it is Rohan's beta as far as I know
There is no "most stable" ROM. Everyone uses their phone differently, and your mileage can and will vary. Same thing with battery life (and probably has as much, if not more to do with other factors, such as your geographic location and radio).
Its easy to look through the ROM threads to see what specific issues people have, known bugs, etc. Aside from that, just pick some that look like they fill your needs/preferences and try them out.
Since every device handles software a little differently, you need to try it out for yourself and see if you like it. Thats the beauty of XDA, you get to try it out yourself and see if YOU like it.
So since everyone has different options, Im going to close this before it becomes a BEST ROM THREAD... and we dont allow those.
Hi guys,
I am curious to know if the kernel used in Sense ROMs (stock, ElementalX, BeastMode) be made to work in the CM/AOKP roms?
Here's my problem - I personally like the look and feel of CM. However, one big problem is the fact that there is a lot of lost functionality in these roms as compared to sense roms.
Now, I dont mean things like transparent status bars, etc - but core features like HDMI out, headset buttons, usb tethering, battery life, etc.
The focus of the developers is also around cool new features and not around fixing hardware issues. For example someone posted yesterday that wired headset buttons have been broken all the wsy from kernel 3.0 to 3.4.
Im wondering if one can leverage the fully working Sense kernels to run CM.
Sent from my One X using Tapatalk 4
sandys1 said:
Hi guys,
I am curious to know if the kernel used in Sense ROMs (stock, ElementalX, BeastMode) be made to work in the CM/AOKP roms?
Here's my problem - I personally like the look and feel of CM. However, one big problem is the fact that there is a lot of lost functionality in these roms as compared to sense roms.
Now, I dont mean things like transparent status bars, etc - but core features like HDMI out, headset buttons, usb tethering, battery life, etc.
The focus of the developers is also around cool new features and not around fixing hardware issues. For example someone posted yesterday that wired headset buttons have been broken all the wsy from kernel 3.0 to 3.4.
Im wondering if one can leverage the fully working Sense kernels to run CM.
Sent from my One X using Tapatalk 4
Click to expand...
Click to collapse
Sense kernels cannot run be used to run cm10 or later based roms. IF you like the look and feel of stock android but still want all the working features why don't you download one of the sense roms and desense it? I know viperxl offers desense option in the aroma installer.
ImagioX1 said:
Sense kernels cannot run be used to run cm10 or later based roms. IF you like the look and feel of stock android but still want all the working features why don't you download one of the sense roms and desense it? I know viperxl offers desense option in the aroma installer.
Click to expand...
Click to collapse
Yes - I thought about it, but I like the CM roms for all the added functionality (remote wipes, themes, etc.). Also, in the longer term Kitkat is only going to be possible on our phones via the AOSP/CM route.
I wonder if there is any possibility to fund a bounty to fix hardware compatibility for all the AOSP/CM based roms.
sandys1 said:
Yes - I thought about it, but I like the CM roms for all the added functionality (remote wipes, themes, etc.). Also, in the longer term Kitkat is only going to be possible on our phones via the AOSP/CM route.
I wonder if there is any possibility to fund a bounty to fix hardware compatibility for all the AOSP/CM based roms.
Click to expand...
Click to collapse
What hardware compatibility do you mean? I don't know whether a bounty is going to work, the devs we have working on these ROMs are already doing their absolute best to bring us the best software possible. Also, some of these issues are caused at an upstream level and are completely out of their control.
Sent from my Evita