yashsingh1/xdaforums huggingface dataset:
[Optimus One, P500 Android Development] Dovidhalevi:
Yeah. Unfortunately (or not), Omni will not work with dexopt-data-only=0. Boots up with numerous android.phone failures. Tried on two different occasions. Lucky to get back to recovery. Cm-11 flashers have had better luck with this.

This mod would give me enough data space left to avoid the link2sd "Achilles heel." To get around this, I need to remove a bunch of larger dex'd apps and then restore them after flashes. So I am reluctant to flash very often.

Moving the system dexes to cache manually is an option but that must be redone with each upgrade. Additionally, this mod, from what I have read, is not reallly desirable because can leave too little headroom on /cache, lead to problems. But if it does work without a hitch, go with it.

---------- Post added at 09:59 PM ---------- Previous post was at 09:48 PM ----------

I see no GooglePlay or Phonesky or anything like that on priv-app. You must have flashed them yourself. (Actually I remove the system format from the updater script so I will still have all this stuff around! I never reflashed gapps on all my ICS upgrades.)

8MB will do you just fine. More than enough. First time in SuperSU UI, create the script. Root will be be persistant, bootup option on all reflashes.

I did the thing for USB once on omni and never had to repeat it. Unlike cm-11, "usb storage" and debugging are available simultaneously.

How is version doing on the battery?
[Optimus One, P500 Android Development] rharshit:
Haven't done anything for battery yet. I will just implement build.prop tweaks for now
[Optimus One, P500 Android Development] Dovidhalevi:
Keep us informed!
[Optimus One, P500 Android Development] Dovidhalevi:
Flashed beta-5 ROM. Besides spending half the afternoon futzing around to get link2sd symlinks and free data space back to where it was (finally succeded), boots up, runs fine. Some widget settings changed, not changeable back, minor stuff.

I found no interface for split screen. The proposed one is from omniswitch but I found nothing at all like that. There are various sidebar UIs for this, don't like them. The webOS implimentation exercised from omniswitch was supposed to be used, whatever ...

I set halo to white-list to keep it out of the way. I have floatifications set to use halo so tried that. Black screen exercising K9 mail, problem persisted once I got screen back and tapped K9 mail directly. K9 was not actually running either time, apparently. Omniswitch becomes unstable, FCing and when it comes back, has a different recent app that has not been run recently. So halo is a source of instability (or was it something else or combination?).

Meanwhile restored the backup to Feb 27 build.

Again, Halo does not belong on these ROMs because of the 0x20000 flag conflict. Minimally, give us control of which one to use and interfaces for it. I have seen postings about Omni ROMs with both split screen and floating windows (Halo style but not Halo). Maybe they combined them or split the flags, i.e. 0x20000 for Halo, 0x10000 for split or such. Xposed module XHalo is a complete floating window-manager but the ROM takes the 0x20000 flag so this will/should not work. All this, except for simplest split view interface, becomes but marginally useful on a small screen device such as ours. I nice big tablet would be another story.
[Optimus One, P500 Android Development] rharshit:
I'm not sure about the trimming and modifying thing you did. Maybe that caused the error

As fas as halo and split view are concerned, I'm changing split view flags because the xHalo thing also uses 0x00002000
[Optimus One, P500 Android Development] Dovidhalevi:
Could well be. I am heavily into Xposed and this itself can cause problems.

However, the exact same trimming and modifications are with the current Feb 27 build and the April 6 build I also tried. Both work 100%

Good idea, but check how other omnirom devs have done this.

Also, UI to control these options is needed. In settings to enable each one individually, and also how splitview will be triggered. Would prefer gestures rather than yet-another-sidebar. Sidebars tend to get in the way--I am a big fan of homeflip but am using omniswitch instead, same functionality. There are two sidebars around on the threads for splitview, one allowing a choice between spitview and halo. Would rather see such functionality in omniswitch as intended, or have these sidebars do recents as well as chosen apps. Homeflip and omniswitch are both compact and effective implementations of similar functionality, good bases for this.

How might a gesture UI work? From omniswitch or sidebar or ... launcher!? click& flip to side for splitview (on that side or webOS way), squeeze to floater, expand to whole screen again. I have not seen any of the other omnis in action to see what has been implemented.

{I assume you mean regular Halo. Xhalo is an xposed module.)
[Optimus One, P500 Android Development] rharshit:
I didn't find ot in omni rom.

Other devs have implemented a switch to toggle.

I really have see what to with this. It will take some time.

And i meant xHalo, the xposed one
[Optimus One, P500 Android Development] Dovidhalevi:
Switching the ROM's switch might make this ROM incompatible with other omni-centered mods, additions, etc.

If real Halo is burnt into the ROM, for what would be needed the xposed module? It does not provide chatheads. Foatification's chatheads-launched apps and apps launched from certain launchers and sidebars can come up in halo-style floaters. Either adjustable % of screen or full windows with grab-bars, etc. These apps can also make use of "real" Halo without the module. As I said, limited value on this phone plus screen realestate eaten by the windows stuff. Hover-browser also launches in windows with windows bars, closure, etc. without any halo or xhalo. Same problem with screen realestate but a nifty app!

What I thought for changing flag was: Leave one functionality with the 0x2, give 0x1 to the other, allowing their independent, non-interfering usage.
[Optimus One, P500 Android Development] rharshit:
For the flags, 0x1 n 0x2 are already assigned. That's why 0x000100 for spllit view
[Optimus One, P500 Android Development] Dovidhalevi:
A third flag?

Split view interface?

Beta 6?
[Optimus One, P500 Android Development] xu3sno:
[MENTION=3765078]rhar[/MENTION]****

TO DO List on Beta 6,

1. Working dalvik.vm.dexopt-data-only=0 script as on cm-11;

2. Off line charging;

3. USB mass storage without tweaking or type a command line on terminal;

4. Soft power menu (including option power off, reboot, and recovery) just by tapping clock on status bar;

5. Double tap status bar for screen off;

6. Brightness control by swiping across the status bar.

PRO

1. Faster and smoother compare to cm-11 (subjective) :), even apps reside on sdext2. Mine is Class 10 SDCard.

2. Rich features (split window), halo, dashclock;

3. Tethering (WiFi hotspot) works out of the box.

Thanks rhar**** :)
[Optimus One, P500 Android Development] Dovidhalevi:
Good list. You got split window working? How does one use it? Had problems with/due to Halo but could!? me my fault as well.

1. dexopt-data-only=0. If one's dalvik is up towards 60 meg, not recommended. Need more headroom. Mine is 46 meg so would give this another try. Some mod/script to get selected program caching that requires faster access to /cache might be good idea.

2. Would like it but can live without it.

3. I did that command once, never had to do it again, even after flashing new versions.

4. There is an Xposed module which did this with battery icon. Stopped working on Kitkat. Why? Because icon was replaced with code. Clock is also code (and I "hide" it). A tile on the quick-settings might be a better alternative.

5. Cool idea. There is a tile for this. And XGels (once again alive and well!) can do this from home screen.

6. This may be working--selectable option.
[Optimus One, P500 Android Development] rharshit:
All the list of features will be implemented in future versions, if not beta 6. Though, I doubt about the first and fourth.

The sixth feature is already in ROM. Go to Settings>Bars and the first option there is to enable this.

And you missed a feature. To enable high-end graphics like transparent statusbar, and other effects. To be implemented soon
[Optimus One, P500 Android Development] xu3sno:
Well, unfortunately if the first could not be implemented. Since, all system@*.dex occupies ca. 60MB of /data and can not move to /cache, hence, only a limited apps can be installed and linked to sdcard (2nd extension) :( A bit weird in my opinion, since the script works flawlessly in cm-11, and omni as cm-11, is based on the same source of AOSP. Please correct me when I'm wrong :)

Will try the sixth feature. Thanks rhar**** :cool:

Can't wait any longer :). No, just kidding. Take your time, dev. :good:
[Optimus One, P500 Android Development] Dovidhalevi:
Cm-11 users are just about filling the /cache with this mod. Dangerous in my mind but apparently cm-11 can tolerate it while omni cannot tolerate this, even with my 46meg dalvik-cache.

Setting the ro.config.low_ram=false will enable lockscreen widgets and transparent-gradient bars. Designed to tailor Kitkat to lower memory devices but I noticed no problems setting false, wanted those widgets. Systemui can be modded to bypass this test for the gradients.
[Optimus One, P500 Android Development] rharshit:
Can be done so. But on examining the source code, I realized that it will help, but hinder the performance.

Omni has a built in feature to free RAM on low RAM devices by pausing, stopping or killing unused background apps.

So it would be better to force certain features than disabling low RAM property.
[Optimus One, P500 Android Development] Dovidhalevi:
Good idea so do it in systemui.apk (+elsewhere?) as suggested. Think mukulsoni has done this in his cm-11 ROM. Posted a zip to just replace this in existing ROM as well. Do not remember if that enabled the lockscreen widgets or just the gradient. Would want both, lockscreen widgets are a settings option if one does not want them enabled.

Note that in the performance settings, there is a pane of memory limits and presets on how aggressive the system will be in freeing RAM. I am using "light" and have rarely had any problems, even with build.prop item set to false. But best to allow in systemui.apk.
[Optimus One, P500 Android Development] rharshit:
Well, in there is an option already in CM11. The latest omni too has this option for high-end graphics. So this might be the better way
[Optimus One, P500 Android Development] Dovidhalevi:
Maybe, but not likely. There must be code in systemui.apk that tests that low_ram parameter. The gradients and lockscreen widgets if there would be removed from that if. The lockscreen widgets have a settings value so that would also be tested. Code may also be in keyguard.

Might be interesting to see what "high-end graphics" option would do, if anything, on our device. But must be left and option.
[Optimus One, P500 Android Development] xu3sno:
Once I had change value of ro.config.low_ram=false in build.prop in order to enable translucent bar, but after system rebooted, systemUI crash. :( , as it's happened also when running dalvik.vm.dexopt-data-only=0 script.

Hope rhar**** will fix it in the next update :good: TIA.

Assuming that issues have been fixed, prefer using this omni ROM over cm-11. :)
[Optimus One, P500 Android Development] Dovidhalevi:
Worked for me on three omni versions including this one. Dexopt-data-only=0 does not work correctly.
[Optimus One, P500 Android Development] rharshit:
Are the latest omni sources corrupt?

I'm constantly getting the same error. Even after resetting it to old ones.
[Optimus One, P500 Android Development] Dovidhalevi:
Definitely something amiss. Latest Jenkins timed-builds all failed.
[Optimus One, P500 Android Development] rharshit:
Yea. Have to wait until fixed.
[Optimus One, P500 Android Development] rharshit:
High-end option is available in current Omega ROM too. I just didn't notice.

Go to Settings>Performance and go to Advance tab. There you'll find a checkbox for it
[Optimus One, P500 Android Development] Dovidhalevi:
Anyone tried it? What did it do? (I do not expect high-end anything on this low-end device.)

However, if it would get latest Maps and Play Focal version to work smoothly, then would be useful.

And then, there is that "gl-tools" package--I do not even dare.
[Optimus One, P500 Android Development] rharshit:
High-end graphics basically enables translucent statusbar and some other animations like darkening on statusbar pull down etc.

Other demands are tough though. But this kernel has enabled lens blur in Google camera. Doesn't work though :P
[Optimus One, P500 Android Development] Dovidhalevi:
There are a number of Xposed modules to get these options. Had them going on cm-10.2.

Enables regardless of low_ram setting? (I am running older ROM and do not have the option to test it.) Actually, the translucent status bar should be its own option! Why? Running in immersive mode with swipe-status-bar, pulling it down over part of top row of icons or app's top can be barely readable. It is tinted enough right now, on previously had it too transparent.

I get a translucent/transparent hotseat/dock-bar using Xgels. Can have the same problem, icons over icons or text, so I keep it tinted as well.

Actually, only need the low_ram=false to get the lockscreen widgets. Workaround for that might be in order.

Experience side-loading that camera:

Comes up, can take one picture. Just one. After that get "cannot open camera" error. If I run the regular camera to reset that, thing will not come up again to take picture, get camera silhouette on black screen.

Lens-blur has to be the most awkward feature ever invented. Shooting a still life, one has the freedom of motion to rotate the view to above subject. Otherwise?

Might implement a step to the side and reshoot scheme to get parallax between the two pictures, work from there. Or overlay two or more shots with differing focus. Handle depth information the way color-definition handled in HDR mode. Processing will be slow on our sets.

Photosphere not offered by any of the camera apps on our device.
[Optimus One, P500 Android Development] rharshit:
I think I will have to pause the project for a while. Because of source error. Plus I'm going out for vacations for two weeks.
[Optimus One, P500 Android Development] xu3sno:
Okay, take your time. :)

Have a great vacation :cool:
[Optimus One, P500 Android Development] anhsmile:
Not feature Theme in this Beta5 version:(
[Optimus One, P500 Android Development] rharshit:
Yea. Because its OmniROM. AOSP based.

You can use Xposed modules like xTheme Engine
[Optimus One, P500 Android Development] Dovidhalevi:
Successful 5.17 "nightly" build so source issue possibly fixed. Trying it now.
[Optimus One, P500 Android Development] rharshit:
Thanks for the update.

I'll try to finish the current update and then A vacc
[Optimus One, P500 Android Development] Dovidhalevi:
Enjoy the vacc! Will be more to write home about :)

Seems nothing significant new in this version. Was hoping the omni split screen would be implemented. Omniswitch now has a system settings instead of omniswitch settings button and a button to toggle immersive mode. They no longer fit horizontally across screen in portrait. Unchecked the settings and immersive since I use that all the time and swipe in the bars if I need them.

As with the last upgrade I tried, must jump through flaming loops to get link2sd's symlinks all back. Battery life will be the deciding factor. I stayed with an older cm-10.2 for ages until taking omni because no changes or fixes worth going through the trouble of upgrading. May well end up doing the same with the Feb 27 build. Unless your version really does the trick.
[Optimus One, P500 Android Development] xu3sno:
Hope you fixed the dalvik.vm.dexopt-data-only=0 script, before you go for vacation :)

Thanks.
[Optimus One, P500 Android Development] rharshit:
Don't expect any miracles in the upcoming build. It'll just have high-end graphics and custom widget in lockscreen. And a bit of other stuff for omega branding (not at all useful)

So, better I'll build a kernel for battery issue. But not anytime soon. Have to learn first
[Optimus One, P500 Android Development] Dovidhalevi:
Good question: Since I made upgrade attempts with enough data space to "optimize" all the dexes, and still had all the problems, data-only=0 will give more data space, more room for apps before ... but might not make upgrading any easier. Need to find out why the ROMs repeatedly redo this "optimize" regardless. At least in the end, I can get it working now. Just a big frustrating bother.

I have seen stuff about "omega" ROMs. It this version related to the others? What (not at all useful) features are involved?

The "chocolate-perf" 3.08 seems to be adequate. I am more than satisfied (finally) with battery life, at least for that Feb 27 build. Might contact Sweetnsour about his kernel tricks because he was nicely successful on cm10 ROMs. Also adds a newer smartassH3 governer and a "zen" i/o scheduler.

Getting the options for "high end" graphic effect and lockscreen widgets without setting the build.prop low ram to false would be a big plus, to be shared with main source tree for omni and cm-11.
[Optimus One, P500 Android Development] rharshit:
They aren't features. They are the rebranding stuff like platlogo, etc

Yea. sweetnsour's kernel was epic! Need his help

That was the only thing i didn't like about omni. I may share it soon. Good idea
[Optimus One, P500 Android Development] Dovidhalevi:
Then, what's the point in rebranding it? I see postings on the Google+ list about various "homemade"--labeled omni ROMs. Some have features such as yours implemented. If there were some great features like in Paranoid, would make more sense.
[Optimus One, P500 Android Development] rharshit:
I have added some features. The other things are rebranding n stuff.

Porting paranoid's useful features are tough. But I'm thinking of implementing gesture for camera like moto x.

Beta 7 maybe.

Beta 6 is built, btw
[Optimus One, P500 Android Development] rharshit:
Beta 6

Beta 6 built. Delay due to omniarmv6's source error

Changelog:

Updated to latest Omni build

High-end graphics option in Performance>Advance

Option to add lockscreen widgets

Added Omega animations and platlogo (partially)

A few more things which I don't remember :P
[Optimus One, P500 Android Development] Dovidhalevi:
Cool. Screenshots of Omega stuff?

Lockscreen widgets without change to low_ram=false? Have the "high-end" graphics option in i/o pane of performance on recent Omni builds.

Status of the Halo and split screen?
[Optimus One, P500 Android Development] rharshit:
I haven't yet tested the build. will test and report the screenshots.

Well, i have to use the same flags for halo and split-view or it breaks either of em. Will implement a switch, which would be a better option
[Optimus One, P500 Android Development] Dovidhalevi:
Afraid of that. BTW, the xposed splitview works over the Omni (the xhalo does not).

Switch is the best idea. Halo))), Floatifications, Bubble-launcher and many others work with the Halo flag would now feed whichever is selected. I would want to use them from Omniswitch (proposed an xposed module for this until implemented inside!) or even the launcher as I described. I think that Omniswitch will/should have a popup item to choose on long press. Problem with all the other UIs (mostly sidebars) is that one must pre-select apps rather than use recents or current app.

Fuller window managers like the xhalo and maybe more developed versions of halo itself are overkill and of limit value on a small screen device.
[Optimus One, P500 Android Development] Dovidhalevi:
As reported on Google+ group, some folks have had trouble answering calls on latest nightly. Delay in the UI to answer a call until caller has hung up.

Had been a sporadically recurring bother on most recent ROMs on our device. Omni has a dialogbox rather than an animation and I did encounter the problem on the Feb 27 build. Did have it on current nightly. If this recurs consistantly, back to Feb 27, but as of now, still testing. Battery life is fine.
[Optimus One, P500 Android Development] rharshit:
Beta6.1

An update to Beta6 is out.

Basically fixes of bugs which were created due to Beta6 changes

Changelog:

Fixed HALO)))

Fixed Split-view and HALO))) conflict with flags and intents

Added a a switch to choose between HALO))) and Split-view

Added OmegaROM PlatLogo (now multiple taps on Omega Version will bringup Omega PlatLogo)

Other minor fixes
[Optimus One, P500 Android Development] Dovidhalevi:
How (UI) does one exercise the chosen Halo or Split-view?

Halo))) is an app for pinning notifications for Halo, compiled in the ROM, the functionality of chat-head notifications launching windowed apps. Kind of confused about what you are posting :)
[Optimus One, P500 Android Development] rharshit:
Actually, the current ROM had a bug. If you opened notification from HALO))), it opened up in Split-View (because of flags), So this switch kinda helps rectify it. Not fully, but the full change has to have this switch. So this switch is the kind of partial fix.
[Optimus One, P500 Android Development] Dovidhalevi:
Same thing would likely have occured using floatifications, bubble launcher, one of the sidebars, or halo))) (the app from Play) from the notifications drawer.

Because Omni was designed for one functionality, the split-screen. Having both is confusing. So the switch is quite necessary. An alternative to have neither active (there are some who do not want the bother) would also be desirable.

Except for notifications, ability to launch in halo windows or split screen should be available from omniswitch (intended UI). As I said, I would like to see it in the launchers across the board, either by gestures I described or long press->remove/uninstall/launch-in-window or such. Requested for XGels. Launcher3 is opensource.

The 6.1 update zip: Does this contain all the changes implemented over the Omni nightly? In other words, could I flash this (possibly adding a few items if need be) over the nightly and avoid the whole out of internal space/re-symlinking saga? Might just wait for completly correct flags implementation and useful UI.

BTW What sets an Omega ROM apart from its basis ROM?
[Optimus One, P500 Android Development] Dovidhalevi:
News flash: dexopt-data-only=0 officially merged. So now we need to get this to work here!
[Optimus One, P500 Android Development] anhsmile:
[MENTION=3765078]rhar[/MENTION]****; you can share GAPPS for this rom?:)

Beta 6.1 cannot flash with TWRP 2.7.0.0:(
[Optimus One, P500 Android Development] Dovidhalevi:
Beta 6.1 is not the ROM, but is an update. Flash Beta 6 as usually done, then flash 6.1 and GAPPSlight.
[Optimus One, P500 Android Development] anhsmile:
Ok. But i flashed beta 6.1 use TWRP 2.7.0.0 but FAIL:(

And system partion do not size to flash GAPPSlight:(
[Optimus One, P500 Android Development] Dovidhalevi:
You must trim the ROM before flashing (or do it on the phone before flashing GAPPSlight, beta 6.1). There is also a windows app to help do this. One needs a few meg free on /system after including the GAPPSlight and anything a bit larger in the beta 6.1 (this replaces some files) for things to work correctly.

If there be a particular problem flashing that 6.1 zip, extract the files on the PC and adb push them to their locations. But get beta 6 and the gapps working first, backup just in case.
[Optimus One, P500 Android Development] rharshit:
As [MENTION=4708203]Dovidhalevi[/MENTION] said, you can push then via adb. Sorry if the update was not packaged fine.

Can you please send me the log of error? So that I'll try to fix it from here. Hopefully, it's just updater-script issue.

And if gappslight is pudding problem, install camera and gallery app as user app and then flash gapps