OmniROM is now booting on Android 5.0 (and a friendly reminder about contributing)

Search This thread
By:
Advanced…
pulser_g2

pulser_g2

Admin Emeritus / Senior Recognized Developer
Nov 27, 2009
19,544
11,630
Well, it's time to make the announcement - the first build of OmniROM, based on Android L, has now booted.

In the spirit of "pics or it didn't happen"

hwVooxw.png


This is running on the N7 2013 (flo).

Hang fire on syncing though - we're still getting everything sorted to bring an amazing experience with Android 5.0. There's a few bugs still being sorted out, so you will need a fair few patches and tweaks to get builds going.

Just thought I'd let everyone know that "it's happening" :) A big thanks to @XpLoDWilD for doing all the ninjamerging of the new repositories.

Contributing to Omni

As a reminder, devices without an active device maintainer won't be receiving L, as the core Omni team are currently working beyond capacity. We'll be adding more folks where possible to do this, but this is where we need *your* help - this is the time to try to encourage your device maintainer to get involved. We've struggled by with keeping Android 4.4 going, and without more contributors, it will take a lot longer to get to where we want to be with Omni.

We've got a huge roadmap of ideas and features, much of it on our wiki, but without contributors, much of it gets nowhere. Omni is a ROM inspired by what YOU want, but we can't make that happen without contributions from people like YOU. :)

We're looking forward to getting Android 5.0 out and in the wild as part of a custom ROM, as soon as we can, but this needs a lot of hard work, and more hands always help! Interested developers can find us on #omni and #omnirom on IRC.
 
  • Like
Reactions: VENESOLANITO, BlueFlame4, gbman54 and 175 others
[AltaiR]

[AltaiR]

Senior Member
Feb 20, 2013
60
106
Great news! Why am I the first one replying?

I've read your article on the homepage about the poor quality/buggy state of Lollipop. Now we all know how Omni is about good, clean code and stability rather than being the first to release something that isn't ready for prime time(for eg Theme engine/multi-window) using hacks or "fixing" stuff by simply treating the symptoms, not the cause (pardon the analogy).
What is your opinion/solution about this issue?
 
  • Like
Reactions: jorv976, RossFixxed and thiruanand
itouchables

itouchables

Senior Member
Jun 26, 2013
279
109
Great jobs guys, what devices are you planning on porting first ? :D:cool:

Sent from my XT1032 using XDA Premium 4 mobile app
 
You must log in or register to reply here.

Similar threads

Gandalf
  • Locked
  • Sticky
OmniROM for Various Devices - MegaList
Replies
386
Views
158K
Gandalf
Gandalf
XpLoDWilD
The OmniROM SoundPacks MegaThread
Replies
160
Views
90K
scoobyjenkins
scoobyjenkins
P
[Bug report] Music player stops playing music from sd after some time
Replies
930
Views
195K
Twiq
Twiq
XpLoDWilD
[ANSWERS] All the answers
Replies
733
Views
166K
Y
YasuHamed
XpLoDWilD
  • Sticky
[EXPERIMENTAL] Semi-official builds of Omni
Replies
313
Views
104K
I
iqbal budiman

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 178
    pulser_g2
    pulser_g2
    Well, it's time to make the announcement - the first build of OmniROM, based on Android L, has now booted.

    In the spirit of "pics or it didn't happen"

    hwVooxw.png


    This is running on the N7 2013 (flo).

    Hang fire on syncing though - we're still getting everything sorted to bring an amazing experience with Android 5.0. There's a few bugs still being sorted out, so you will need a fair few patches and tweaks to get builds going.

    Just thought I'd let everyone know that "it's happening" :) A big thanks to @XpLoDWilD for doing all the ninjamerging of the new repositories.

    Contributing to Omni

    As a reminder, devices without an active device maintainer won't be receiving L, as the core Omni team are currently working beyond capacity. We'll be adding more folks where possible to do this, but this is where we need *your* help - this is the time to try to encourage your device maintainer to get involved. We've struggled by with keeping Android 4.4 going, and without more contributors, it will take a lot longer to get to where we want to be with Omni.

    We've got a huge roadmap of ideas and features, much of it on our wiki, but without contributors, much of it gets nowhere. Omni is a ROM inspired by what YOU want, but we can't make that happen without contributions from people like YOU. :)

    We're looking forward to getting Android 5.0 out and in the wild as part of a custom ROM, as soon as we can, but this needs a lot of hard work, and more hands always help! Interested developers can find us on #omni and #omnirom on IRC.
    View
    20
    pulser_g2
    pulser_g2
    I shall now try to reply to as many posts as I can :)

    [AltaiR] said:
    Great news! Why am I the first one replying?

    I've read your article on the homepage about the poor quality/buggy state of Lollipop. Now we all know how Omni is about good, clean code and stability rather than being the first to release something that isn't ready for prime time(for eg Theme engine/multi-window) using hacks or "fixing" stuff by simply treating the symptoms, not the cause (pardon the analogy).
    What is your opinion/solution about this issue?
    Click to expand...
    Click to collapse

    My view is that we try to fix as much as we can - I suspect Google will release another iteration of AOSP before big-time launch, hopefully to resolve some of the issues. Most of the crashes aren't insurmountable. In terms of moving to the more modern, material-inspired design (hopefully minus the badly matched colours they seem to love), that's going to take time and effort. That's where the more help we can get, the better.

    Every ROM will benefit if we, as a community, can get a proper, material-designed SMS app sorted out - stock is, as I gather, still left on the old UI. Same for browser etc. Talking of browser, it really needs a complete overhaul now that Google prefers their own Chrome browser.

    dhiru1602 said:
    Is that Omni with a prebuilt kernel? Or is it just an AOSP build with edited build.prop?
    Click to expand...
    Click to collapse

    Omni with prebuilt kernel - Google hadn't released the blobs or sources at that point, and the 4.4 one wasn't good enough to get it booting. Hopefully soon they will.

    MiroslavVitula said:
    ICS and JB are the abbreviations for multi-word titles, Ice Cream Sandwich and Jelly Bean. Therefore, it's shorted as ICS and JB. But Lollipop is only one word, right? And I'm writing this because the 5.0 was firstly announced as "Android L", becuase it had no name (or we weren't supposed to know it yet). But know, when the 5.0 is fully released and the guys from Omni had successfully compiled the (final, not beta) source, it's not L anymore. It's Lollipop. LOL-lipop.
    Hope it's clear now :p
    Click to expand...
    Click to collapse

    Yeah, but I will still abbreviate it to L, and I suspect a lot of others will as well. L is a nice, convenient name :) It's one single key-stroke. :)

    jacobnoori said:
    Why doesn't SM-N900T get any love? = /
    Click to expand...
    Click to collapse

    Presumably it doesn't have a device maintainer working on it - Omni is entirely a community ROM, but that does mean we rely on the community to port it to new devices, and then maintain these ports.

    Unfortunately one of the main reasons for devices going unsupported with L will be lack of maintainer attention. If there's no maintainer that is participating, it's difficult for them to do things, and keep their device up to the standards expected of a stable ROM. Omni aims to be (and from comments everywhere, certainly appears to achieve) incredibly stable, despite bringing forward new features.

    Muhammad Rihawi said:
    Great :)
    Please developers make Custom Rom to Note 3 Neo :(
    there is no custom Rom to this device :(
    Please help us we really need you :)



    My device model is Note 3 Neo SM-N7505
    Click to expand...
    Click to collapse

    See reply above.

    dhiru1602 said:
    And it doesn't build with KK kernel either.

    "Now, OmniROM has officially become the first large-scale custom ROM distribution to merge and successfully boot Android 5.0 Lollipop."

    With this statement it's quite evident that Android Development is "now" all about supremacy and achievements rather than working together in a collaborative manner and producing something good. I have never heard a statement from developers of a linux distro saying "We have become the first linux distribution to officially support KDE 5 Plasma".

    With so much hate towards other "Un-named ROMs" and knowing for sure that the L-Preview kernel is outdated and KK kernel doesn't work, It doesn't take a genius to differentiate between a showoff and an accomplishment. Anyways, Good work! :good:
    Click to expand...
    Click to collapse

    I didn't say those words at any point in my post, though? Actually, something I've been quite keen to encourage is greater collaboration between ROMs. Unfortunately not many are interested, but going forwards, with Google apparently intent on closing down Android, it would be beneficial for people to realise this is not a case of petty squabbling, rather that they can do better than Google.

    Omni isn't about trying to add more buttons or switches than another ROM - it's not in competition with another ROM. It's about making something that is more stable, and reliable, than AOSP. It's about taking AOSP, and making it usable on a day-to-day basis. It does that while being an unfunded community project, contributed to by developers in their spare time.

    Actually, it's quite nice to see the number of developers from other ROM projects that drop in to chat about things, and bounce ideas around. :) Given the number of devices likely to be cast off by Android 5.0, I think there's a lot of scope to have a supported Android 4.4 long-term support branch. These things would all need significant cross-ROM cooperation, which is something we're very keen to encourage.


    JoeSyr said:
    Having a hard time finding what this refers to; what's on the wiki seems to be less "ideas and features" and more of a memo to maintainers for bringing older devices up to speed for basic Lollipop support.

    I don't mean to be critical of people working on the basics first, just wondering if there's anything that I haven't found. Eager to see how Omni is going to evolve with this jump.
    Click to expand...
    Click to collapse

    That isn't necessarily the "roadmap" as such - that's just basics that max was writing up. Here's a rough example of "roadmap" kind of ideas with regard solely to security - http://docs.omnirom.org/Security_features. The ideas are there, but it's very difficult to get motivated people involved.

    It's scary that these days, iOS8 is actually ahead of Android in terms of protecting user privacy in a number of ways.

    JoeSyr said:
    Well, there's that and the Features page, but they're last updated in April and May, so in the sense that we "have" those, we have goals built around KitKat's base.

    Now, it's my sense that Omni is built pretty heavily on the concept of "Have an idea? Submit a patch for it!", but eventually there has to be a point where someone makes the executive decision. To me, a roadmap is the difference between "We're always open for suggestions" and "Here's what we're specifically aiming for, we're open to contributions to get us there."

    I guess that for my part I don't feel like I have much to contribute in this realm (I'll happily be filing any bug reports once there are builds out), but the OP gave me the impression that there's been various levels of less-technical consensus that have been reached that specifically apply to the 4.4->5.0 bump.
    Click to expand...
    Click to collapse

    Well, the general consensus on the bump towards 5.0 is that user experience is key. This isn't about quickly porting forward features, rather about carefully considering the best way to make them fit in with the new way of Android 5.0. For example, Quiet Hours is now not the way forward - there's a system-level do-not-disturb. Omni's goal remains about taking stock Android, and making it more usable, while remaining rock-solid on stability. No crash is acceptable, no regression should go unchecked. It's about taking AOSP, fixing the things they didn't get right, making it more usable, adding customisation where needed, and making it work on all devices, like Android should be.
    View
    19
    E
    Entropy512
    Testraindrop said:
    Hey guys from omni, any progress on lollipop?

    No ETA, just want to know how everything is going ;)

    Maybe we can get some Christmas presents at least for nexus devices... :p

    Gesendet von meinem Nexus 5
    Click to expand...
    Click to collapse
    To be honest, we're way behind where any of us would like to be.

    One of the big things we need to finish up is ifdefing CAF stuff so it doesn't screw up non-Nexus devices. It's at the point where it SEEMS to be working OK but it still needs work. I was the primary person doing the work on this, but I've been pretty much tied up with non-Android issues to the point where I've been lucky to do one build a week...

    Definitely not before Christmas, I MIGHT be able to get some work done over the holiday break. Also I hope I'll be able to resolve the other issues I'm dealing with in January and maybe I'll be able to catch things up then...
    View
    15
    E
    Entropy512
    ahmedelhofy said:
    Which one of these posts am I supposed to belive ?
    Click to expand...
    Click to collapse
    I think xplodwild jumped the gun here. The truth is, he nor I have the time for the 4210 devices any more. I've touched my N7000 maybe 3-4 times in the past year, he has done even less work on the 4210s. He says he wants to do a bringup - but I don't think doing a bringup is a good idea if the device won't get touched for the rest of the Android release cycle.

    I will say, they will definitely not come back to nightlies until:
    1) A maintainer other than plodey or I is regularly active on IRC and working on the device
    2) Someone figures out the root cause to the floating point register corruption issue that causes issues with the sdcard fuse daemon and other things. Workarounds/hacks that involve moving the FP registers are not sufficient here - the root cause itself needs to be found and solved.

    jacobnoori said:
    Why doesn't SM-N900T get any love? = /
    Click to expand...
    Click to collapse
    It's a Samsung. Developers have grown to hate Samsungs over the years. Even the Qualcomm-based Samsungs are a pain in the ass to support

    Someone has been working on hlte, but he's a college student so frequently doesn't have enough free time.

    abhiparab23 said:
    any hopes for note n7000?:confused:
    Click to expand...
    Click to collapse
    See above regarding 4210 devices

    Sandivisi said:
    hope this build will arrive on moto g (2013)
    Click to expand...
    Click to collapse
    Maybe. I simply didn't have time to get that cleaned up with 4.4. There's another guy doing some work on it (Squadzone, who is one of our primary UI/UX guys) - but he's still learning the hardware side of things.

    Mnt-XDA said:
    When find 7 QHD and 1+1 will get omni lollipop love...?
    Click to expand...
    Click to collapse
    We don't do ETAs. All I will say is that Find 7 (all variants, including find7op) is likely to be one of the first non-Nexus devices supported since many of the Omni founders run Oppos as their daily driver. (Find 7 is likely going to be the pilot device for all Qualcomm 8974-based devices that use CAF repos - e.g. all Qcoms except for Nexus devices.)

    arismelachrinos said:
    is this going to be available for xperia z - yuga ????
    Click to expand...
    Click to collapse
    Probably, it depends on how much free time myself, humberto, oliver, and the other guys who own fusion3 devices have. I intend to try and avoid dropping these devices if at all possible because of the wonderful support Sony has given many community developers over the years.

    sizzlingtycoon said:
    Great news...
    Hope it arrives sson to GT-i9300
    Click to expand...
    Click to collapse
    Unlikely. I9300 hasn't had a maintainer to fix bugs in many months. It's going away with 5.0 for this reason.

    lazyinsect said:
    will oppo find 5 receive an update of lollipop???:confused:
    Click to expand...
    Click to collapse
    Very likely, almost guaranteed. We love Oppo, and we have numerous workarounds for the issues that have prevented Oppo from officially updating the device.

    freekzak said:
    on what server are #omni channels on irc ?
    Click to expand...
    Click to collapse
    This should be covered in the FAQ in the Q&A section. irc.freenode.net - more details in the FAQ
    View
    14
    [deXter]
    [deXter]
    MiroslavVitula said:
    Let's just call it Lollipop, not L anymore :p Awesome job!
    Click to expand...
    Click to collapse

    It's easier to type L than Lollipop. Did you also complain when people were talking about ICS and JB?
    View

New posts