yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II SGH-I777] MO11:
it works

thank you for sharing this with us, i have been trying to just see/try android 5.0 on my device and with your rom its working . i didnt fully test everything but overall seems fine to me :)
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
[MENTION=6306501]coolerboyj[/MENTION], I just tried it. I turned off the wifi, then rebooted, and the device booted into android as expected.

I have not tried shift with Omni 5.0, but it should work well.
[AT&T Samsung Galaxy S II SGH-I777] MO11:
i have had some random reboots and the call bug as you mentioned but other than that all is good. just wondering about any future fixes for the call bug ?
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
...I sure hope so. This is where you can all help me out. If you notice that another 5.0 firmware (for i777 or i9100) doesn't have the call bug, let me know, and I will look into what fixes they applied, and attempt to apply them to OMNI.

-Cyril
[AT&T Samsung Galaxy S II SGH-I777] MO11:
yeah, absolutely hope soon it would be fixed as its pretty hard to go back to kk after trying lollipop
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
**2015/02/10 build posted**

multiuser enabled

ambient display enabled (settings > display > ambient display)

a few other fixes
[AT&T Samsung Galaxy S II SGH-I777] desteele:
Can you give specifics? Just curious as to what you like best about it.
[AT&T Samsung Galaxy S II SGH-I777] squiglybob13:
When trying to flash Gapps from here, I keep getting "Error Code: 70". I tried it with both Stock and Micro versions and it sayd "Error executing updater binary in zip". Does this mean it's just a bad zip? Or is there another issue I'm missing?
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
Tried Pico? I've only tested with Pico.
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
I like the refreshing nature of the interface. I'm eager to see what the big three add as customization.

This device doesn't handle the animations very well yet though. Maybe device tree refinements will improve it, maybe succeeding versions of Android, or both. Either way, only time will tell.
[AT&T Samsung Galaxy S II SGH-I777] squiglybob13:
Ah I didn't realize pico was one of the packages [emoji14] I'll give that a shot thank you :)

EDIT: Success! :)
[AT&T Samsung Galaxy S II SGH-I777] AlmasSD:
good job!!!)))

Big thanks for LoliPop In our device!)
[AT&T Samsung Galaxy S II SGH-I777] mmystere68:
Does this have cm12 theme engine ??
[AT&T Samsung Galaxy S II SGH-I777] AlmasSD:
No, does not have the engine СМ12, but without it everything is just perfect;)
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
CM theme engine? No.

Omni will be making use of RRO layering, a different approach to theming.

http://xdaforums.com/android/apps-games/official-layers-bitsyko-apps-rro-t3012172

https://github.com/deadman96385/RRO-WIKI/wiki/About-RRO
[AT&T Samsung Galaxy S II SGH-I777] SteveMurphy:
Layers is the future, the implementation is getting better with each update and causes zero drag on the system. Very happy the Omni team is choosing this method.
[AT&T Samsung Galaxy S II SGH-I777] mmystere68:
but still, there are more themes for cm12 than rro

BTW: I am running a totally working lollipop rom on my i777. i used rogersb11 latest shift kernel, i9100 ressurection remix 5.3.4 and googlecamera4.3 apk. zero bugs so far. HD recordings works like charm!!
[AT&T Samsung Galaxy S II SGH-I777] rogersb11:
Just thought I would note that I include ES with my rom and it works without issue. I still haven't read the whole thread just yet as I just got in here. I see you have the same incall bug I do, what kernel are you using? Do you have any idea what's the deal with that? Do you think it could be in the way we ported up the 777? Your repo is similar to mine other than the ROM and recovery differences but I don't even build a workable recovery with L, just the CM one. I build the kernel separate as we know that's why I ask about the kernel. Apparently it is happening to 777 users using my new kernel on i9100 roms that don't report this issue. I just odn't have a ton of time to work on this device anymore as mine is keeping me busy and I have to maintain s2 and m8 as well and higher demand, blah blah so if you have any input so when I am working on this I can be useful and focused in an area. I appear to have gotten my ROM going for this other than the incall speaker issue and then sound settings has an fc OF COURSE but same exact build doesn't on my N2 so no idea there. Was hoping to drop one stable rock solid build and retire but alas and as usual that did not work out. But the fact I finally got that thing going after so many random issues and then wifi for over a month was a nightmare to diagnose. Why omni as well? I love the stability NO DOUBT but I think most of them are really busy so development has been slow, same with slim. I'm just saying you could maintain mine HAHAHA which I don't expect as I will get ift fixed and it is so loaded that I can do random month at a time updates for stability without much issue. Seriously has so many features that a year from now cm still won't have that many if I stopped today LOL. BUT anyway, why not build CM? they are doing a GREAT job on L, and have stepped the feature scene up for them

---------- Post added at 03:22 AM ---------- Previous post was at 03:13 AM ----------

the animations are total crap stock if you ask me, they need tweaked in the framework bad. Does omni have quick settings customization yet? I thought about adding it for them and submitting to gerrit

---------- Post added at 03:27 AM ---------- Previous post was at 03:22 AM ----------

New theme engine actually uses a lit of RRO. I agree layers COULD and probably will be better but we will see. It gonna be a total nightmare for devs to maintain as it still needs a ton of work. I'm anxious as well but I already chose theme engine so I doubt I would be willing to make all the necesary reverts by when layers iswhat it is claimed to be. I'm good with the decision tho as like I said CM is using a lot of RRO and once they unlock all of the necessary styles and arrays you can already tell the things that you will be able to do more as a themer than before. Idhave never themed and still managed to develop and early stage badass theme for my rom after reverting back to material light for the theme engine which sucked LOL. Sorry for any typos as my machine is building and the typing is lagging pretty bad. Running at -j16 so to be expected lol
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
I'm building with Omni's kernel (& modified defconfig) . It builds inline, boots, and uses TWRP.

The in-call/speaker-toggle issue is beyond my scope. I had not yet realized that it was only an i777 issue until I read it in your thread this morning. That makes things trickier, because YOU are the only active developer left in this community, and as much as you love us, your attention is elsewhere (and I don't blame you). As a builder (not a developer) I am limited by what I can make sense of, and assemble, based on others' working models. I have a few friends to ask though, at least for guidance...

I'm actually not using very much of my repo right now, just the devices (for Omni and Slim). I'm about to fork an s2-common though because everyone seems to have pieces of what I need, but no one has one that I can blindly follow (Duvall, android-armv7a-belalang-tempur, bauner, lysergic-acid, marco9333, rogersb11) . I'll post my local_manifest once things make more sense, so that everyone can see exactly what I'm using, and what I've chosen. I need to learn to use GIT better so that everyone gets proper credit.

Regarding my preference for OMNI and SLIM, I like the design path and motto that they both follow, which (in my opinion) leads to the stability they're both known for. I agree that they lag behind CM, but I'm alright with that for the result.

I'm honored by the offer, It would be nice to have the big-three covered, but I have my hands full right now, mainly considering that my device-base is still not quite right.

I don't believe that Omni or slim has quick-settings customization yet. They're waiting on you :)

I'm not a big fan of theming, but I have seen that many users will turn down stability for themability. To-each-his-own. I'm glad to see that OMNI and SLIM are holding out for something that they think is worth their time, and I'm glad that they haven't implemented it at a pre-mature stage. It's all anyone can talk about right now, we'll see where it takes us.

Thanks for checking in!

-Cyril
[AT&T Samsung Galaxy S II SGH-I777] chowland1967:
Can I ask how you got a 9100 rom on the phone? I tried this and got the complimentary status 7 message.

I have the recovery that rogerb has in his shift (phils touchwiz/cmw) . does twrp let you by-pass this?
[AT&T Samsung Galaxy S II SGH-I777] mmystere68:
I used cwm 6.0.4.5 kitkat compatible recovery. I flashed i9100rom,shift kernel and pico gapps and then i777ucll6 modem. Only bug was outgoing call issue. I had to revert back because battery life wasnt that great....
[AT&T Samsung Galaxy S II SGH-I777] chowland1967:
Thanks! Maybe I'll try this later since we're having yet another storm up here in the northeast (Ma, usa) so I won't be going

anywhere again this weekend.
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
Another method is to remove the assert lines from the updater script of the i9100 firmware, then flash it using any recovery. Then flash Rogers kernel.
[AT&T Samsung Galaxy S II SGH-I777] chowland1967:
Thanks, I think I'll try this method since I have some programming knowledge and I'm to lazy to connect up my phone to the computer and put the other recovery on it. I see the lines where it checks the model of the phone and then spits out the error if it doesn't see the correct model. I'll remove all that stuff and the first line will be to mount then install.
[AT&T Samsung Galaxy S II SGH-I777] omar71693:
Is MMS working properly for you on i9100 roms? Data doesn't cut on automatically when sending MMS messages for me.
[AT&T Samsung Galaxy S II SGH-I777] mmystere68:
I dont use MMS...never even used it. I cant test it cause i am back to my old shostocké
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
I should have a new build in a few days that should fix several issues...

Fingers crossed
[AT&T Samsung Galaxy S II SGH-I777] omar71693:
Great, can't wait. Your work is appreciated. After a little research, apparently Google made LP so that it does not allow 3rd party apps to enable/disable data. You now have to turn off WiFi to use mms, which is ridiculous.
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
**2015/02/27 build posted**

Stock camera HD recording works

Some OMNI additions

memory issues are still present, that'll be the next effort.
[AT&T Samsung Galaxy S II SGH-I777] kwmike:
Boot loop after 5-10 mins use.

Hi,

I have clean installed the 2/27 version twice and each time after 5-10 mins of running ok

the system has started rebooting over and over again. This seems to occur after my apps are

loaded so it may be an app/ rom incompatibility.

Will attempt to get a logcat but may be delayed.

Thanks to the dev for struggling to keep our S2 alive!!
[AT&T Samsung Galaxy S II SGH-I777] kingfiras:
Great and promising work man .. Giving life to my s2 .. Same problem as above though .. Keeps rebooting .. Not sure if related to a particular app I installed from the store or not.
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
If you just flash the firmware, and fresh apps, you won't get the reboots. It's the app data restoration that's causing the constant-reboot issue.

The core structure of each beta build is different right now, so that some apps (or their data) will trigger issues when restored. Best case is to restore apps from the play store, and leave the data behind. OR be very mindful of which app is triggering the issue, and avoid restoring data for that particular app.

-Cyril
[AT&T Samsung Galaxy S II SGH-I777] kingfiras:
In my case I didn't restore any data .. And apps were installed from the Play Store .. Next time I'll try to install one app at a time to find the bad apple .. This will have to wait until the weekend though :)
[AT&T Samsung Galaxy S II SGH-I777] TeutonJon78:
Does this kernel now include the FPbug fix?
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
Yes, The stock omni kernel includes the fpbug fix.

FEB 14 commits:

https://github.com/cyril279/android...mits/959d355912b8d365658fbc5226f25c973c0b6f86
[AT&T Samsung Galaxy S II SGH-I777] TeutonJon78:
So, I must have missed something. When I installed the ROM file and reboot to recovery, I end up with CWM and it thinks the phone is an i9100. When I go to flash the ROM package again, it won't do it because it have a device mismatch. If I then flash the kernel package and reboot to recover, it's back to TWRP and it can flash the package file again.

Is the ROM file actually just the same as the i9100 ones being build and all I have to do if flash the kernel image over them?

What are the exact steps to install? I had 4.4.4 working with no problems at all.
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
I didn't mean to upload that build. Use the April 1 build.

The firmware is close, but not the same as the i9100 version. In fact, Asimovi's builds include TWRP as well. I've been experimenting with different device source, and mistakenly posted a work-in-progress.

The recovery should always be TWRP, and the installation is as straight forward as 4.4.4

flash firmware, then GApps, then SuperSU.

my apologies to all affected

-Cyril
[AT&T Samsung Galaxy S II SGH-I777] TeutonJon78:
Ha, it was probably just me -- there wasn't too many downloads of it. NO worries. You hadn't posted anything about it, I just saw and grabbed. Other than a little frustration, not any problem. I just got it back and restored the back up I made prior to playing with it. ;)
[AT&T Samsung Galaxy S II SGH-I777] TeutonJon78:
How long should the initial boot be taking? I've tried multiple times leaving it sit as long as 30 minutes but I can't get past the boot animation. On 4.4.4 it would only take a couple of minutes before getting to "Android is upgrading...".

I did a full wipe of Davlik/cache/system/data before installing since I wasn't having any luck with a dirty flash.
[AT&T Samsung Galaxy S II SGH-I777] jroq8400:
I just went thru the same. Rebooted to recovery and did 2 wipes, then installed just the ROM without gapps or SuperSU. After that it booted in a few minutes then went back to recovery to install gapps and SuperSU
[AT&T Samsung Galaxy S II SGH-I777] TeutonJon78:
That's already where I'm at, unfortunately (trying just the ROM after wiping everything). The only thing I noticed in the install was that it had a problem on the mmcblk09 mounting (/system), but it then continues on with the flash and says it flashed it correctly at /system.
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
I suggest manually wiping /system, /data, and /cache before flashing the firmware.

Some of these boot issues can come from survival scripts of previous app installations, and firmware versions.

Otherwise, I'm not sure, I get a clean easy install each time. the initial boot time isn't short, but it's definitely not thirty minutes. I haven't timed it, but i'd be surprised if it lasted longer then five minutes.

Perhaps I should include the manual wipe suggestion in the op...

-Cyril
[AT&T Samsung Galaxy S II SGH-I777] TeutonJon78:
Weird, I've done all those. Maybe I should just run that ROM clean script from Cook. I can't believe anything would really survive that process of manual wiping though, which is what is so strange. I've never had this kind of problem flashing anything before.

Edit: running the ROM wipe script got it up and working correct. I'm not sure what was getting left over.

Wow, it's way fast. Great job to everyone involved. Can't wait for it to hit actual nightlies.

Edit 2: Is my understanding correct that this rom supports F2FS for data, but not trim?
[AT&T Samsung Galaxy S II SGH-I777] TeutonJon78:
Bug on 2015-4-1 Build: unable to format the internal SD card (UMS partition): if you go to setting and tell it to format the SD card, it will unmount and start to erase as expected, but the erasing takes too long and then the device reboots.

The functionality works correctly on the 4.4.4 builds. It also works correctly from TWRP.
[AT&T Samsung Galaxy S II SGH-I777] coolerboyj:
Which Kernel do you Recommend? [MENTION=5294352]cyril279[/MENTION]
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
I haven't tested that at all, and I'll need to back-up my internal storage before I try it for myself. I'm interested to see whether the behavior is correct when using shift kernel.

We don't have much choice. If you like to tweak, then use Shift.

The benefits of a custom kernel are the same as the drawbacks. You can tweak your device until it's perfect. You can also tweak your device until it's unusable.

Stock kernels are much less exciting, but typically more reliable.

Edit: [MENTION=4141005]Lanchon[/MENTION] could probably bang-out a trim kernel for us, but last I spoke with him, he didn't seem the slightest bit interested in Lollipop :p
[AT&T Samsung Galaxy S II SGH-I777] TeutonJon78:
Oh well, just curious. I assume it didn't since none of the stock kernels seem to due to the stupid bugs. I just upped my data partrition to 6G to give it some more room (and hence finding the UMS formatting bug :) ).
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
Welcome to 5.1

**2015/04/04 build posted**

Memory issues seem to be fixed

Fixed shifty wifi toggle

Fixed Apps crashing while execute over wifi

switched common-device base to [MENTION=6159291]Lysergic Acid[/MENTION] 's code source. Massive thanks to him for the help and support thus far.

There are still plenty of issues, including the in-call bug, but functionally, this is a massive improvement over 5.0.

regarding the empty "interface" in settings: https://plus.google.com/112182842915561753561/posts/DZn24UyJ5Tj

-Cyril
[AT&T Samsung Galaxy S II SGH-I777] Lysergic Acid:
I'm glad the commit I pointed you for the apps crash worked.

Do you know why the "in call" bug is happening on the i777? We don't have it on i9100 but I could try to help.
[AT&T Samsung Galaxy S II SGH-I777] yosmokinman:
^I don't think anyone knows. It has to be with the kernel and/or the i777's yamaha audio chip. Or I could be totally wrong.

I'll post a log of it if you wan't but I'm guessing cyril already has that.

Thanks though. We can use all the help we can get.
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
Thanks for checking in. I have only taken one log, and posted it in another thread ( http://xdaforums.com/showthread.php?p=59243748 ).

The issue : when placing an outgoing call, you can't hear any audio (ringing or someone answering the call) until [speaker phone] is toggled. Then everything works as expected. Two people mentioned an audio routing issue, but I'm not code savvy, so I wouldn't know what to do if the problematic code was staring me in the face.

The only differences in between the i777 and i9100 are NFC, key layout, and the mc1n2 mic address swap. Those have all been accounted for.

Just to be sure that we're comparing apples to apples, maybe I should set up a cm12.1 build from your source...

Any help is thoroughly appreciated.

Regarding the app-crash issue, that was huge, and I saw so focused on looking to see if you had done anything to the sock.c file that I skipped over that giant commit. Thanks for taking the time to look at that.

-Cyril
[AT&T Samsung Galaxy S II SGH-I777] Lysergic Acid:
Just to make sure, a headset doesn't work while attempting an outgoing call? Because look at this:

E/HeadsetStateMachine( 6721): terminateScoUsingVirtualVoiceCall:No present call to terminate

It may be indeed a wrong routing issue.

I'll look at the i777 yamaha configs and then I tell you if I find the culprit.
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
When a headset is plugged in, the outgoing call exhibits the same undesired behavior. No sound until toggle speaker.

:fingers-crossed:
[AT&T Samsung Galaxy S II SGH-I777] TeutonJon78:
Another small bug, although might be related to the state of Omni 5.1.

Setting > Date & Time has no entry for Date Format. It is usually underneath "Use 24-hour format".

Also, I tested with TKruze's last PA Gapps release for 5.1 (Stock) as well, and it seems to work correctly on 4-4 build. I did have some odd lag on every screen on first boot, which seems to have gone away after while.
[AT&T Samsung Galaxy S II SGH-I777] benjamingdelacruz:
Aside from Shift kernel is there any other that is compatible with this ROM? Currently on Omni KK and would like to switch over but my phone can never get past the blue meter logo using Shift kernel.
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
https://www.androidfilehost.com/?fid=95916177934546032
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
It seems that the future of Omni + RRO layers is questionable...

https://plus.google.com/105066388701995848460/posts/QU7eHXhncpJ
[AT&T Samsung Galaxy S II SGH-I777] syrkles:
Will this rom work on i727 skyrocket??
[AT&T Samsung Galaxy S II SGH-I777] yosmokinman:
^No.
[AT&T Samsung Galaxy S II SGH-I777] Quicksilver13:
Mass Storage

Looking for the mass storage selection in settings. Can't seem to find it. :confused:
[AT&T Samsung Galaxy S II SGH-I777] TeutonJon78:
I might be wrong, but I don't think Omni has that. OmnitROM tends to not add many features above AOSP, and AOSP definitely does not have UMS for internal storage.
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
**2015/04/26 build posted**

RIL updated to v11 (updated data connection management)

Other device updates, & Omni firmware updates

Built using the UBER Toolchain

More thanks to [MENTION=6159291]Lysergic Acid[/MENTION] for updated, stable device-base, & for humoring my noob-ness.

-Cyril
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
I'm not sure.

- 5.x is much more geared toward security, and the lack of mass-storage choices may be a result thereof.

- Omni does tend to respect AOSP as intended, so they will respect this choice.

However

- Omni is still early in development, and the feature may show up in the future.

-Cyril
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
OP updated to always link to most recent version of superSU

http://download.chainfire.eu/supersu

[MENTION=2773890]TeutonJon78[/MENTION], outdated su versions could certainly affect re-bootability, and I mistakenly had the OP hard-linked to a specific version which was NOT the latest.
[AT&T Samsung Galaxy S II SGH-I777] TeutonJon78:
I was using the latest 2.46.
[AT&T Samsung Galaxy S II SGH-I777] TeutonJon78:
Does anyone here use FreeOTP? I can't get it register a barcode for some reasons. It worked fine on 4.4.4 and on other devices with 5.1 (Nexus 4).
[AT&T Samsung Galaxy S II SGH-I777] rogersb11:
Hey [MENTION=5294352]cyril279[/MENTION] how hard is it to commit to slim gerrit? Omni is simple but slim looks like cm, kind of a pain the is a$$ but I would like to submit slimpie for them. I compiled a working build for my note 2 last night with my own device trees, didn't even look at theirs but it runs fine but is just way to bare for slim
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
I've never used the method that slim shows on their manifest page.

I use the same method to push to Slim, OMNI, and CM.

git push ssh://cyril279@review.slimroms.eu:29418/<project> HEAD:refs/for/<branch>
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
There's an issue with this device and i9100 firmwares, that qr-scan apps don't work correctly. Everything installs, and the app launches, but when scanning, the app never detects the code. It's apparently working on i9100 nameless, but the dev/maintainer isn't (yet) sharing his device code.

-Cyril
[AT&T Samsung Galaxy S II SGH-I777] rogersb11:
AH, awesome. That way is much easier. Thanks man, I'll try to get that pushed as soon as I have time to commit and fix recents action
[AT&T Samsung Galaxy S II SGH-I777] Quicksilver13:
[MENTION=5294352]cyril279[/MENTION] .. appreciate your work and devotion to the i777 .. Your Omni build is the 1st stable LP Rom I have been able to install on my i777