Related
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
ROM:
http://www.mediafire.com/download/0f12tn2klc66v52/cm-11-20141231-UNOFFICIAL-ovation.zip
MD5:
http://www.mediafire.com/download/u1xdu2d85851nw8/cm-11-20141231-UNOFFICIAL-ovation.zip.md5sum
Compiled with ArchiDroid optimizations & "Yellow Kernel"
https://github.com/JustArchi/android_build/commit/1125f60a15194e08fdf18feacefb47696647e05b
(-o3, gcc4.8, openjdk 1.7... lollipop's version)
Odexed, ext4 for now (a little hacking could accomodate for F2FS), not rooted. If flashed with a current TWRP recovery, TWRP will offer to root it (which works).
I removed the proprietary terminal from the build (with the intent of compiling one from source eventually. Until then, one can be downloaded from f-droid), prepared for USB camera support (rather than a 'camera stub'), & audio_policy.conf changes (USB headset,etc- which probably isn't supported in the audio_hw.c file... yet), and a few other experimental changes.
After the first boot, this has the fastest boot time I've seen of any ROM I've tested.
****source****
Device:
http://www.mediafire.com/download/hcffj8p6atb8kyo/device_bn_cm.tar.gz
Kernel:
http://www.mediafire.com/download/ja828194riarf81/omap_123114.tar.gz
Thank you very much for all the work you are doing to make this piece of hardware working so good!!
Since this is odex it will be really fast... I hardly wait to flash it!!
It would be great to have a f2fs build too!!
Odex + F2FS = super smooth!!
Can't wait to try f2fs cm11 build!
Sent from my SM-N900V using Tapatalk
Flashed this rom yesterday, so far so good. Complete wipe and flash. No gapps just side-loaded desired apps and running well. Feels like a current CM11 nightly
I am running this rom and i confirm that it works really well.
Great work!!
A F2FS version would be really the perfect rom.
@OT
frantisek.nesveda created this tool for Nexus 7 grouper, maybe it can be useful for Ovation too, with proper modifications:
http://forum.xda-developers.com/showthread.php?t=2748975
I can't get the download to work. Is anyone else having an issue with notbeing able to see the target captcha??
Nevermind, I got it on my laptop.
Will you make a hummingbird (Nook HD) version?
Many thanks, Jon! Requesting F2FS version as well...
I'm having a problem charging. If I use a higher capacity charger, ( iPad) it shows a green charge light and not charging, even though it's at 18%. If I use a lower capacity charger from my phone, it shows a blinking orange and doesn't charge. I used the same twrp 2.8 I used before for Slim.
I've never seen this before.
Update, it looks OK on a third charger. Who knows?
Switching to ART causes bootloop for me. Anyone else facing this issue?
infra_red_dude said:
Switching to ART causes bootloop for me. Anyone else facing this issue?
Click to expand...
Click to collapse
Yup, same here.
infra_red_dude said:
Switching to ART causes bootloop for me. Anyone else facing this issue?
Click to expand...
Click to collapse
I haven't tried ART on this device, but from my experience with other CPUs (tegra 3 and old Exynos) I think that Google started developing ART on Qualcomm Snapdragon (Nexus 4, 7 and 5). So, unless you have Snapdragon processor, I think that on Kit Kat is better to stay with Dalvik, especially if you have an odex Rom like this.
Only with Lollipop ART became mature to work quite well also with other architectures.
Monfro said:
I haven't tried ART on this device, but from my experience with other CPUs (tegra 3 and old Exynos) I think that Google started developing ART on Qualcomm Snapdragon (Nexus 4, 7 and 5). So, unless you have Snapdragon processor, I think that on Kit Kat is better to stay with Dalvik, especially if you have an odex Rom like this.
Only with Lollipop ART became mature to work quite well also with other architectures.
Click to expand...
Click to collapse
I'm using ART on my Nook HD without any problems. I run CM11 nightly fully installed to EMMC but with F-Droid and Amazon app stores and no Gapps (except Earth and an old version of Youtube which don't require Play Services). I switched to ART over the Christmas holiday. It takes a little while to rebuild the installed apps but it does work perfectly OK. I have experienced zero bugs with it and it does seem to make for a better experience.
@julian67
Are you running This build with Jon Lee's Yellow kernel or a CM nightly with the stock kernel. Art has always work for me with the CM stock kernel
Stock kernel, CM11 nightly (hummingbird on HD). I hope my experience and yours shows that ART working (or not) doesn't depend on system architecture/CPU. It is definitely worth switching runtime. If it doesn't work then it's probably just exposing deficiencies already present in omg_funroll-loops_optimilized-4-speed-ultraaar-stable-buttery-smoo......*crash* kernels and configs.
This is running great John.
Thank you, Jon.
I used all your roms.
All your roms are great.
This rom is really good, too.
But I'm sad that exFAT external memory doesn't work with this rom.
Please consider supporting exFAT external memory.
julian67 said:
I'm using ART on my Nook HD without any problems. I run CM11 nightly fully installed to EMMC but with F-Droid and Amazon app stores and no Gapps (except Earth and an old version of Youtube which don't require Play Services). I switched to ART over the Christmas holiday. It takes a little while to rebuild the installed apps but it does work perfectly OK. I have experienced zero bugs with it and it does seem to make for a better experience.
Click to expand...
Click to collapse
I'm running ART as well with the nightly from 1/5/15, the things I have tried have been working fine. Too bad BN got out of the tablet business, these are great little tablets.
Perhaps a bit of a rant here....
I'm sure the ART issue is a consequence of this build being odexed.
The exfat issue is a consequence of the archidroid optimizations (there is a patch for it which I failed to apply). All of my builds have been experimental in one way or another...
CM10.1.3 with the "Yellow Kernel" was perfectly long term stable (for me). I can't really speak for Slimkat because I didn't try it out that long, but Liquidsmooth and this CM11 are somewhat less than stable (for me). As another poster humorously pointed out, it's probably part to do with compiler "optimizations".
I'm quite glad that Hashcode came out with CM12, as it was mostly beyond my ability. I was tired and fed up with trying. So he saved me the effort....
This CM11 build may have some ffmpeg video codecs that the normal CM11 builds don't include (which would be one of the few advantages of using it).
Right now I'm working on compiling CandyKat (which is based on Slimrom). I'm learning as I go and the best I can hope for is that each subsequent build is an improvement over the last. Technically my true aim is long term stability. With that in mind, perhaps I should stick with CM10.1.3... or perhaps an AOSP build. I'm not content with leaving things well enough alone though. Behind the scenes I have more broken builds than builds that actually work.
Anyway.... /rant over.
Jon Lee said:
Perhaps a bit of a rant here....
I'm sure the ART issue is a consequence of this build being odexed.
The exfat issue is a consequence of the archidroid optimizations (there is a patch for it which I failed to apply). All of my builds have been experimental in one way or another...
CM10.1.3 with the "Yellow Kernel" was perfectly long term stable (for me). I can't really speak for Slimkat because I didn't try it out that long, but Liquidsmooth and this CM11 are somewhat less than stable (for me). As another poster humorously pointed out, it's probably part to do with compiler "optimizations".
I'm quite glad that Hashcode came out with CM12, as it was mostly beyond my ability. I was tired and fed up with trying. So he saved me the effort....
This CM11 build may have some ffmpeg video codecs that the normal CM11 builds don't include (which would be one of the few advantages of using it).
Right now I'm working on compiling CandyKat (which is based on Slimrom). I'm learning as I go and the best I can hope for is that each subsequent build is an improvement over the last. Technically my true aim is long term stability. With that in mind, perhaps I should stick with CM10.1.3... or perhaps an AOSP build. I'm not content with leaving things well enough alone though. Behind the scenes I have more broken builds than builds that actually work.
Anyway.... /rant over.
Click to expand...
Click to collapse
You did really an extraordinary job on this device: you succeeded in bringing F2FS (which I consider a great improvement) and you compiled among the best Roms available here.
This CM11 is near perfect, since its target is to bring more optimization and more performance, and I consider Odex+Dalvik smoother than Deodex+ART (which on KitKat is still experimental).
Only thing I would add is a F2FS version.
For next project I suggest to try a vanilla AOSP ROM, maybe also in Odex and F2FS version, since usually more functions means also more ram and CPU needed.
CPU and GPU are quite OK on this device, but the real problem is RAM.
Also Roms based on Slim should be fast and efficient.
Of course doing experiments can also disappoint someone, but from my point of view you reached great goals with your work on this device.
The purpose is to give users more choice: this ROM offers a different compiling approach than standard CM11, and if someone is disappointed can run standard CM11.
But this ROM gives the option to other users to try something different.
So I think that majority of users here are supporting your work and anxiously are waiting what you will bring next to Ovation.
Keep up the good work!!
Now that Paranoid Android. 2016 has been released yesterday for OPO, would you make the switch to Paranoid Android? and why?
To help flasholics make informed choices
Paranoid Android just for the different experience than the stock roms. CM is almost stock. After using for sometime battery charging is slow. TOugh call to make with Dirty Unicorns or Darkobas roms. with PA.
I vote for different experience hence PA.
I vote for CM. Its got a blotch of features and no...those nose breakdowns didnt happen to me.. PA's accountability in this period is very bad. They left us and now when android N is almost out, they turn their nose into first PA MM build. kinda late to win win i would say,. but i have to agree they are very stable interms of battery.. if only they stick to custom roms, i would have been on PA.
I would go for CM13 (Sultan) over Paranoid Android. I've been on CM Nightlies for ages and Sultan's ROM is CM with better camera, kernel and based on a more stable branch from CM. Paranoid is just coming back after a long hiatus and it won't have any of the features you've come to enjoy on a daily basis on other custom software.
A lot of people have commented PA has charging issues. I assume that's cause they used the Oxygen kernel. I also had issues on latest Oxygen OS with charging (took like 4+ hrs to charge), it can't be a coincidence. If PA are still dishing out builds, check them out in a couple months when the OS has matured (with more features)
What about the just launched Cyanogen 13.1 into the mix? Would anyone be considering switching to that?
The charging issue on PA is keeping me from trying it, although my battery life on the official CM13 nightlies hasn't been fantastic
xtremez said:
What about the just launched Cyanogen 13.1 into the mix? Would anyone be considering switching to that?
The charging issue on PA is keeping me from trying it, although my battery life on the official CM13 nightlies hasn't been fantastic
Click to expand...
Click to collapse
I did just that, I've switched over from the nightlies. So far almost everything is just like CyanogenMod, but kind of worse in a way, and the only reason I'm saying that is because I have a very specific setup and like having Google versions of the apps, which aren't all included in COS. The features from the newest update are rather useless to me at this point in time, it might be a different story if something more interesting gets released though. Other than that it's smooth and fast and due to the lack of root I can finally try out android pay. I'm thinking that if I have no reason to stay on it I will switch back to CM nightlies, or maybe try out Paranoid android when some of the issues (such as the theme engine) get fixed.
I would Prefer COS 13.1. I really found the MODs (Skype and hyperlape) useful for myself. Except for these mods everything is more or less like CM 13 except the camera here is better. I tried PA for a day. It had Slow charging, no extra feature over CM 13. Infact lacks a great deal of features when compared to CM or COS 13.
Hi all,
Over the past few months I have been building CyanogenMod (now LineageOS) 13.0 for my personal use. It's based off Kumajaya's sources and was roughly parallel to emfox's builds. I'm doing this because I'm dissatisfied with the stability and reliability of existing ROMs. (I can't claim that mine is any better, however it does put me in a position to debug the issues.)
This is an interest check. I am considering publishing my nightlies for people to download. I know that everyone will give a blanket "yes" to the question "should I publish my nightlies for people to download?". So instead I would like to ask:
Given the other excellent Mi 4c ROMs, including @Hikari no Tenshi's LineageOS 14.1 builds, Resurrection Remix N and Team Superluminal CM13.0, what reason would people have to use Yet Another ROM?
(Long time reader, first time poster!)
This will sound kind of cliche but , the more options , the better . Maybe some of us will find your ROM more suited to their daily use or something .
So yeah definitely share it man
philipnzw said:
This will sound kind of cliche but , the more options , the better . Maybe some of us will find your ROM more suited to their daily use or something .
So yeah definitely share it man
Click to expand...
Click to collapse
I second this! More roms/more activity keeps this device alive longer too
1. Your development wil keep this device alive longer.
2.(maybe) attract other dev/team to build rom for this device.
3.it will make your rom better,by sharing and let many people using it, will helps you find problem faster and improve it.
so yes!
Always useful to have more I have an Aqua (mi4s) and the rom scene is very poor :/ a few Libra roms do support it but in recent months even the SD card support has gone making for quite a sad outlook for the device. If there were someone building nightlies, it would be ace as from time to time you might be able to dip into the aqua stuff too and we'd all appreciate that
Whatever you decide, it's a nice thing to even consider doing for the community. You have my thanks
honestly i think Marshmallow is waste of time, most of the people are interested only in newest Android and i don't see much interest since we have official nougat ROMs from Mokee, AICP and Resurrection remix
if you want to do something different there is Nougat AOSP ROM missing, blobs from Xiaomi are already available, Nexus 5X as well, so...
more roms, more options. i want my mi4c looks better than Nexus 5X
terence.tan said:
Given the other excellent Mi 4c ROMs, including @Hikari no Tenshi's LineageOS 14.1 builds, Resurrection Remix N and Team Superluminal CM13.0, what reason would people have to use Yet Another ROM?
Click to expand...
Click to collapse
It really depends on what you would have to offer. The available CM13 (or are we calling them LO13 now?) ROMs are TeamSuperluminal's and Emfox's builds which are really not actively maintained anymore, although they are pretty damn stable. Except of course the few bugs that seem to go unfixed -- the touchscreen bug, which appears to be really complicated to fix without newer Xiaomi's kernel sources, the 2% battery bug which is present in TeamSuperluminal's builds and isn't a gamebreaker, and the way the SoC uses its cores in most of the ROMs based on Kumajaya's kernel sources (always active big cores) which results in lower battery life.
If you solved some of these problems, expect users to flock to your ROM. If not, I wouldn't bother, since you'll just be flooded with requests for fixing stuff that isn't broken in the first place. In fact, expect the second even if you deliver on the first.
I don't maintain any ROMs so I'm not one to give advice, but it seems to me it's a lot of work, and that you're paid with criticism and demands for more of your time. Get in contact with a ROM author and ask them for advice on this
Thanks for the thoughts.
As far as I can figure, there are 3 things people want:
Features/being on the cutting edge
Performance
Stability/reliability
We want all 3 but unfortunately it is a trade-off. In particular it takes special effort to achieve stability when combined with the other 2.
The CM14.1 builds satisfy the people who want to live on the cutting edge. The Xceed ROM is built for speed for those who think that Snapdragon 808 should perform like the top-tier chipset that it is
But out of all the ROMs I've tried (haven't tried the CM14.1 builds yet but have tried most of the others) I've had the following stability problems:
Screen freezes, requiring reboot
Sleeps of death
Random reboots in the middle of the night (waking up at 3 a.m. to find my phone clicking at me on the "decrypt your device" screen)
Stuttering or hangups
OpenGL-based games crashing
And that's not including the well-publicised touchscreen and battery problems.
So my personal strategy is:
Marshmallow build. Sorry for those who want Nougat, but I don't consider it stable enough (yet). Plus, all the proprietary MIUI vendor blobs from Xiaomi are targeted at Android L, and getting them working on Android M is hard enough already...
For the kernel, track CAF closely. Probably take their Android N release on the assumption that it's stable
Use as few proprietary blobs as possible; build from CAF source where available. This is what most developers are doing already
Use the most recent proprietary MIUI vendor blobs from Xiaomi, on the assumption that they've been buillding this version of MIUI on Android L for such a long time that it's stable
Avoid importing proprietary blobs from other devices (Nexus 5X, Moto X Pure etc.) where possible for licensing reasons. I don't intend to try and make this an offical LineageOS build, but this might be important for whoever attempts in future...
All this is difficult and @ketut.kumajaya and friends put in some impressive hacks to get it to work in the first place. I can't promise that I can build on this! But if I ever get to a stage where it's fit for consumption, I'll publish something...
in my opinion this will be great for development on Libra devices, i think Nougat rom with clean source will be great for user like me sir. For now iam using RR Nougat and for me its stable for daily use, if we can make Libra official for Lineage it can open other rom change to get official build too. Best luck for you sir and cant wait for your contribution
Hello, I'm completely new to flashing on custom roms, but I recently purchased a Redmi Note 7 Pro with the full intent to flash on something better than the China MIUI rom.
However now that i'm finally allowed to unlock my bootloader, there are a lot more custom roms to choose from in the dev subforum for this phone, and I have absolutely no idea how to tell which one is right for me.
Originally I liked the sound of Oxygen OS for being almost entirely 'stock android' with a few good additions, but then became interested in LineageOS, which also seems to be largely stock android with some improvements, and the most well know community custom rom.
So I guess what I'm looking for is a clean "like-stock" rom with a good amount of customization so I can change things to my preference, but this being my first time ever flashing a custom rom, I would also appreciate stability and security.
Pretty much all of the roms ported in the dev subforum look like they're either modified versions of LineageOS, or based on AOSP.
Should I just play it safe and go with LineageOS, do the LineageOS based roms offer enough good improvements to try one of them instead, or should I look into one of the non-LineageOS AOSP roms?
Or if the "best option" is to try them for myself to see which one I like, is jumping between different roms easy to do, and will I lose any userdata doing so?
Some more info if it helps at all:
My previous phone was a Galaxy S4 running Android 5.0.1, so pretty much any custom rom will feel new and different to me.
Some of the things that bothered me about MIUI was the removal of the App folder/drawer and how notifications for things like emails seemed very delayed and arrived in annoying bursts.
I also disliked how the app vault was filled with crap, seemed pretty uncustomizable, and also can't be disabled in favor of wrap-around pages.
Any help with information on or deciding between custom roms is greatly appreciated!
Try the crDroid official rom posted on this forum. It's based on Lineage os but comes with a lot of custiomizations and performance improvements.
LonesomeTiger said:
Try the crDroid official rom posted on this forum. It's based on Lineage os but comes with a lot of custiomizations and performance improvements.
Click to expand...
Click to collapse
Wow, I just properly read into crDroid, and it sounds like it's only got improvements and more customization options over LineageOS.
I was worried that because it was largely based on another custom rom, it might be less secure and stable or be based on an older version.
But they claim that stability and security are a main goal of theirs, and that they try to keep up with LineageOS's source.
crDroid sound perfect, thanks so much!