yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] nadiros:
Yup the COS12 camera doesn't work on Omni, however as I said the v22 works great. [emoji6]
[ONE Original Android Development] daryelv:
COS camera works for me.
[ONE Original Android Development] schaggo:
This is not CyanogenOS camera. I don't know what camera this is, but it is definitely not COS. Stop spreading FUD.

General note: Cyanogen OS specific camera functionality depends on hooks which can only be found in CM based roms. Slow shutter, raw capture etc doesn't work outside CM.
[ONE Original Android Development] maxwen:
Guys - please stop using the term COS for CM!

COS always was and always will be

ColorOS :)

And yes COS camera works fine

---------- Post added at 12:20 PM ---------- Previous post was at 12:15 PM ----------

Not really - 99% is simply CAF

And last time I tried CM next camera it worked fine
[ONE Original Android Development] schaggo:
Well, I'll STFU then ?

CameraNext of course works, but some functionality AFAIK goes missing when off of CM. Either way, thanks for clearing up.
[ONE Original Android Development] maxwen:
So can you please link me to a camera next apk and tell me whats not work then I can take a look.

From the features listed above there is no real reason why they should be CM only
[ONE Original Android Development] clyder:
I am using the one from here. I am not on Omni though. I am on CM 12.1 but planning on trying this rom soon.
[ONE Original Android Development] schaggo:
Not on Omni ATM, so this holds true for me as well:

Took my info from "bug" (hmhm...) reports in the thread of said camera mod. Features allegedly don't even work on CM kangs such as Bliss-/Vanir-/Euphoria-/Whatever-OS... (don't keep track of 'em).
[ONE Original Android Development] maxwen:
Well - if you all here are a little bit nice I will make it work :)
[ONE Original Android Development] Maarren:
That new v10 version with build in libs crashes on omnirom for me. But the old v22 one on http://xdaforums.com/oneplus-one/themes-apps/app-cameranext-modded-t2999275 works fine. The cm12 zip version has also working panorama mode.

---------- Post added at 10:15 PM ---------- Previous post was at 10:09 PM ----------

Another question, the double tap to wake function does not seem to have prevent accidental wakeup using proximity sensor? Or am I doing something wrong?
[ONE Original Android Development] maxwen:
No we dont support that - and before you ask - we will also not add it cause its known to cause

all sorts of strange side-effects and issues.

---------- Post added at 11:15 PM ---------- Previous post was at 11:14 PM ----------

Just to make it work is easy - exposure time is more work
[ONE Original Android Development] Maarren:
Thanks for the answer. Double tap to wake is then also not usable for me,since my phone started to being operated in pocket. But small price to pay for stability.

For me the old v22 version is fine. No problems with using that. So as far as i'm concerned no work needed.
[ONE Original Android Development] maxwen:
No phone belongs in a pocket without a pouch or flipcase :)
[ONE Original Android Development] _ASSASSIN_:
Ew. I like running mine naked with my bamboo back. Feels good and doesn't take up nearly as much space as does a case.
[ONE Original Android Development] nadiros:
Just an FYI, as I'm running the "unofficial" Omni version and it has proximity preventive wake up. Works well too.
[ONE Original Android Development] maxwen:
You are using it wrong :)
[ONE Original Android Development] Yvan12:
Lollipop is for when please? :)
[ONE Original Android Development] maxwen:
Then
[ONE Original Android Development] maxwen:
But could actually happen faster then you thought :)
[ONE Original Android Development] baddelay:
I think he has thought one week.
[ONE Original Android Development] schaggo:
[MENTION=4683552]maxwen[/MENTION] I have a couple questions regarding Smartmax, and I believe it is your governor, so I hope I'm not doing any wrong in asking in here for a couple explanations :)

Would you mind explaining a bit on how the various tunables are interconnected? And possibly, or even more importantly even, which one have the largest influence on the overall system? I'm interested in UI fluidity, not gaming performance, with the lowest consumption achievable for the level of performance needed.

I ask this, as I have a kernel at hand which - to my understanding - has rather peculiar default settings. awake_ideal_freq is set to min. freq (146), max_ resp min_cpu_load is 55 resp 5. From my understanding, ideal freq should be higher, say around the 700-900MHz mark and cpu load should be higher, around 80-90 respectively dunno, maybe 20 or so. On that note: am I correct, the ramp up happens above max load and ramp down happens below max load-min load (eg. 85 and 65 [85-20=65] in the example) and not below min load?

Anyway, I played around but can't seem to manage to keep the freq around 1400-1500 max, it spends quite some (not much, but too much) time on 1800-2000 and even a bit above. As 1500 is the 801 sweet spot and 1200-1400 is enough to keep the UI fluid, I wonder how I could make it not exceed these freqs except absolutely needed, and get back to them or preferrably below ASAP.

Also how would I disable the included touch boost? Set freq to 0 or set timer/duration to 0? The kernel has a cpu boost driver hardcoded, thus the governor and the cpu boost driver interfere, I imagine.
[ONE Original Android Development] maxwen:
Kernel CPU boost is disabled by default

EDIT:

or do you mean - you have your own kernel?
[ONE Original Android Development] schaggo:
well, not "my" kernel but another devs kernel, yes.

My inquiry was not so much about Omni, it was more about how to get Smartmax to do what I want ?
[ONE Original Android Development] tmotard:
Hi, you did it, thanks a lot

It seems that camera next works fine with last build :D
[ONE Original Android Development] BitEE:
Including slow shutter?
[ONE Original Android Development] maxwen:
older version always worked

latest version dont work - there is a fix on gerrit but I dont know

if this has been included in your build or not

---------- Post added at 03:55 PM ---------- Previous post was at 03:55 PM ----------

no - does not really work even it it looks like
[ONE Original Android Development] scanno:
The build I uploaded yesterday, has the transparent layer commit.
[ONE Original Android Development] maxwen:
Good :) Then latest version works.
[ONE Original Android Development] nadiros:
Hey maxwen. Do you plan on implementing this as well?
[ONE Original Android Development] maxwen:
whatever you mean with that? :)
[ONE Original Android Development] nadiros:
Oops, wrong thread, I should have been addressing eagleyetom for the "unofficial" build.
[ONE Original Android Development] Maarren:
On 14-06 build the new v10 cameranextmod now works. However the camera preview now had some artifacts. Like a small vertical bar sometimes flashing on different positions in the preview. Happens also on stock camera and coloros camera.

All taken pictures are fine.
[ONE Original Android Development] 69gm:
From what I heard, this happens if you use CM camera libs.
[ONE Original Android Development] Renosh:
Only issue I've encountered with CameraNext is HDR freezes camera on subject your focusing on when a photo is taken otherwise the picture is taken. All other camera modes work perfectly
[ONE Original Android Development] samstone86:
No official omnirom has superuser integrated so ... No sorry. And I will may change the device name ... Its called find7op because it is nearly a find7a ;) and op stands for oneplus.

I don't recommend to use another kernel but if you find a kernel which is made with omnirom oppo kernel it should work :)

And about the touchscreen I don't have issues but I try to add another firmware in next build (maybe today or tomorrow)
[ONE Original Android Development] buzzqw:
ok, fair answers.

could you anyway update the updater script to allow device named A0001 to be installed ? (cwm will refuse to install the zip since isn't for this device...)

waiting for next builds

thanks again

BHH
[ONE Original Android Development] acuicultor:
Nope

Sent from E.P.D.Center
[ONE Original Android Development] samstone86:
I change that in my next build.

But TWRP is the recommended recovery for omnirom.
[ONE Original Android Development] Coug76:
Thanks for posting the ROM. It inspired me a bit and I just got OmniRom to build on my box. Can't wait to goof around with it.

Coug

-Hastily spouted for your befuddlement
[ONE Original Android Development] samstone86:
Updated build 20140924 online under Downloads section.
[ONE Original Android Development] buzzqw:
thanks samstone86

changed Touchscreen Firmware
changed Device Name

going to download and test

is the touchscreen firmware the same as CM11 nightly ?

any hope for

?

thanks again!

BHH
[ONE Original Android Development] samstone86:
yes its from the cm sources
[ONE Original Android Development] buzzqw:
sorry pal, unable to test the build

you haven't changed the the /META-INF/com/google/android/updater-script

(getprop("ro.product.device") == "find7op" || getprop("ro.build.product") == "find7op" ||
getprop("ro.product.device") == "bacon" || getprop("ro.build.product") == "bacon") || abort("This package is for \"find7op,bacon\" devices

i have a "A0001" device...

(i must edit manually the line for install and test... and so will do!)

BHH

---------- Post added at 05:37 PM ---------- Previous post was at 05:25 PM ----------

EDIT: unable to activate wifi, wan't turn on :(

well it seems to be on but is off...

EDIT2: touchscreen seems responding good!
[ONE Original Android Development] samstone86:
Restart your device and see if it fixes Wifi. (does it sometimes to me)
[ONE Original Android Development] buzzqw:
yes , rebooting fixed the wifi

and.. found "enable sun light display enhancement" under Active Display

on lock screen i cannot select how much row/column select on sequence lock screen

i will use this build as daily driver for tomorrow

BHH

---------- Post added at 07:51 PM ---------- Previous post was at 07:09 PM ----------

EDIT: i am unable to set dpi (to 480), on reboot it reset to default

EDIT2: texdroider_dpi fails editing.. manually edit build.prop is working (adding sf.lcd...desity=480, otherwise string is missing)
[ONE Original Android Development] samstone86:
It's missing ? I upload another build from today ( no fixed scrip ) that I used to test a commit for off charging . Should be with updated firmware.
[ONE Original Android Development] samstone86:
Removed

omni-4.4.4-20140924-find7op-HOMEMADE.zip

MD5: 88c1ee1071e64ae7ad5913b1180ed0a6

(dpi was not right, maybe some compiling issues)

upload a new one now
[ONE Original Android Development] samstone86:
New build is up 20140924 please use TWRP to flash it!
[ONE Original Android Development] samstone86:
New build up!

20140925:

fixed install for other recoverys

(I am not at home until next week so don't go crazy if there is no response from me :D )
[ONE Original Android Development] buzzqw:
confirm working with Philz, also dpi is set to 480

good work!

BHH

EDIT: please integrate SuperSu/Superuser...

EDIT2: very very strange.. attached phone to USB cable (from pc, for charging), the display keeps on, don't go off. Even if i press the power button to blackout the screen after few seconds the screen is on!?!?!?
[ONE Original Android Development] samstone86:
SuperSU... yea... no not me and not now ^^ ... it's in none Omnirom build integrated. ^^

And provide me a logcat please because I have not this problem ... is it with the build from my PM too?
[ONE Original Android Development] buzzqw:
holy cow!

rebooted and now the phone blank screen correctly...

(after an hard shutdown...)

sorry pal, but there are some strange issues..

i installed "catlog"... at next problem you will have the log

BHH
[ONE Original Android Development] samstone86:
Hm the strange thing is it works fine in my device -.- but if you want ... Try to install the ROM with twrp recovery .

If more people have such problems it would be good to know ...
[ONE Original Android Development] ilpolpi65:
Stupid question: where is the download section ?

---------- Post added at 04:52 PM ---------- Previous post was at 04:47 PM ----------

Ah...ok sorry !![emoji6]

---------- Post added at 04:52 PM ---------- Previous post was at 04:52 PM ----------

Ah...ok....sorry [emoji6]
[ONE Original Android Development] webore:
gerrit.paranoidandroid.co/#/c/193

Add T9 lookup please.

And I need an option to merge call logs from same contact badly .
[ONE Original Android Development] vTape:
Hi dev, any idea of how get HydrogenOS launcher apk work for your beautiful Omni?

It worjs on OxygenOS and I was wondering if it could work anyway in your rom because they are both based on AOSP, don't they?

Thanks in advance
[ONE Original Android Development] maxwen:
ATTENTION!!!

Switching from one of the test builds to nightlies requires a clean flash!
[ONE Original Android Development] baddelay:
There is no data in \sdcard via ES Explorer...wonder where my data has gone. I can see all in recovery. There is another path called emulated\0. But empty too. Seems to be new...

Apollo shuts down after reboot.

EDIT: Instagram too.

EDIT2: After second clean install Apollo works, but not Instagram. Still nothing in \sdcard via ES Explorer.

Welcome back, my dear nightlies! Thanks, guys!
[ONE Original Android Development] maxwen:
Try

su

restorecon -RF /data/media/0

---------- Post added at 10:52 PM ---------- Previous post was at 10:06 PM ----------

Link?
[ONE Original Android Development] baddelay:
Where to enter that?
[ONE Original Android Development] vTape:
Here: https://drive.google.com/folderview...&usp=sharing&tid=0B4ioXB8-gN5GOEVGWDRmcm1LTTA

Is the one called "Trebuchet" but is the H2 launcher.

Here the flashable zip ("Launcher Ok"): https://drive.google.com/folderview...&usp=sharing&tid=0B4ioXB8-gN5GOEVGWDRmcm1LTTA

Currently, both works only on OxygenOS but I'd love the H2 launcher in your ROM.

Thanks in advance,

vTape
[ONE Original Android Development] maxwen:
Trebuchet is the CM launcher - so build from source

Other then that - we dont support closed source apps that are not available on the playstore
[ONE Original Android Development] vTape:
No. Don't misunderstand me. It was renamed Trebuchet in order to overwrite the real Trebuchet in CM roms trying to get it works. Actually, despite of the name, it is H2Launcher. Take a look.

Thanks
[ONE Original Android Development] maxwen:
root shell on the device

or root adb shell

---------- Post added at 12:17 AM ---------- Previous post was at 12:16 AM ----------

if its not open source or on the playstore - sorry no
[ONE Original Android Development] baddelay:
Thanks! It worked. Instagram works too! Now again: Welcome back, nightlies! :thumbup: :)
[ONE Original Android Development] abhibnl:
Is the issue fixed in the latest nightly? I mean no data showing in file explorer? I want to test omni nightlies since i've heard so much about the cleanliness of this rom and no code messups like cm. But my monthly allowed data is limited. Could anyone please comfirm so that i can go ahead and download it?

Sent from OnePlus One
[ONE Original Android Development] 69gm:
Just curious...do any issues with the new nightlies go here? I wasn't sure since this "Official" thread predates the actual nightlies.

BTW, I like the OTA on the nightlies! Works great! Are these auto-builds by jenkins? Where can I find a changelog between builds?
[ONE Original Android Development] Renosh:
Look at the OP next time but here is a link to the OPO gerrit:

https://gerrit.omnirom.org/#/q/project:android_device_oppo_find7
[ONE Original Android Development] baddelay:
Should I do a clean install after that or is everything "normal" after that restorecon command? I don't have any issues as I can see but don't know if there is deep down some trouble. :)
[ONE Original Android Development] schaggo:
It was SELinux which you reconfigured/recreated. It simply was an access rights problem. If it works, no need to do anything.
[ONE Original Android Development] abhibnl:
I tried it and it works fine! The rom is smooth and fluid. However, it's too plain for my tatse and usage but i'm definately looking forward to try an Omni based ROM. I guess the only choice i have is Darkobas, right?
[ONE Original Android Development] Evil Eye:
Does this rom feature split view? Thanks :)
[ONE Original Android Development] 69gm:
Yeah I can't really read that and understand. I was hoping for plain English for us non devs. :)

And the only thing I should really be looking at is "merged", correct?
[ONE Original Android Development] baddelay:
Go for 'OmniROM Changelog' in Play Store. That's gerrit in nice and it shows you what has been merged since your last upgrade.
[ONE Original Android Development] maxwen:
No

---------- Post added at 07:52 PM ---------- Previous post was at 07:50 PM ----------

That's the point we like about it :)
[ONE Original Android Development] 69gm:
Thanks! Yeah I saw that but wasn't sure if it worked or not.

I'll give it a go! :good:
[ONE Original Android Development] abhibnl:
Indeed, for anybody who likes plain AOSP build, it sure is 10 times better than CM. Though i didn't test thoroughly, but as people report, Omni has no bugs that people are facing on CM roms simple because CM likes it too much to mess with the CAF code.
[ONE Original Android Development] 69gm:
Truth! :good::D
[ONE Original Android Development] ogrillion:
Just wanted to post I had issues with my screen not turning off on a phone call.

I searched and saw nothing and yes I did flash the latest firmware.

What ended up being at fault was TWRP. Switch to philz recovery and now my screen turns off NP.

Just wanted to share my problem and solution. ROM runs beautifully now

Edit: I wanted to add, it was strange I came from 44s and flashed omni in twrp. Rebooted and had a bootloop - realized I forgot to flash firmware/modem.

Flashed the firmware and the ROM booted right up - but the proximity sensor didn't work. So twrp is partially working or something. Idk
[ONE Original Android Development] Renosh:
[MENTION=4683552]maxwen[/MENTION]

I have an interesting problem. I use Xposed to give me volume keys skip tracks functionality. On every other ROM my volume keys on my Samsung earphones work perfectly for switching tracks. On Omnirom only the volume down works on the earphone. The phones volume buttons work but why is it not working on earphone themselves? It was working before on earlier test builds of Omnirom
[ONE Original Android Development] maxwen:
Go away
[ONE Original Android Development] Renosh:
What do you expect users to do while waiting for a native solution from Omni?
[ONE Original Android Development] maxwen:
I "expect" nothing - but it is a known problem.

Fix is unlikely from my side cause that would require me to have the same headset to test
[ONE Original Android Development] nadiros:
Why should/would Omni provide a solution? As an xposed user please note that troubleshooting in ROM threads is not invited, at the very least. Does it make sense to you that ROM devs would alter their work just so we can mod it or use it other than intended?
[ONE Original Android Development] Renosh:
Thank you for stating the obvious. Point is there's something different about Omni that makes volume keys on wired earphones not work. That's what I wanted the dev to note. Never asked him to fix Xposed for me. If maxwen or the other devs feel like looking into it they will, if not I can't blame them
[ONE Original Android Development] maxwen:
Dont beat him too much :)

Not working wired headset buttons are really a known issue in our kernel - something that has been pushed over the TODO line multiple times :)

the fact that Xposed is used is a side-effect in that case
[ONE Original Android Development] nadiros:
What's obvious is how rude your post is. No one "expects" you to to anything, especially to use a ROM that is a nightly with bugs and such.
[ONE Original Android Development] Renosh:
My guess was right so its you that's being a pain right now. I'm not interested in your opinion so keep it yourself. Next time you feel an urge to post where your input wasn't requested, don't.
[ONE Original Android Development] nadiros:
Your guess was right! Yay, have a cookie. I was straight up, and gentle about it. Go on, have the last word. Maybe check your tone towards those who share freely with you. Good day [emoji6]
[ONE Original Android Development] baddelay:
Does that mean every headset with buttons could work if the code finds its way into the kernel?

I have two of those headsets and have bought them for soundquality reasons. Would be great if the buttons will work someday. Or next week. ;)
[ONE Original Android Development] 69gm:
Just wanted to report that the OTA doesn't seem to be working anymore. I saw there is a new build but when I had my phone check for updates, it said I was on the latest build. I am on 6/22. Latest is 6/23 I believe. Prior to this OTA worked great.

Just reporting in case anyone else was wondering...:)
[ONE Original Android Development] webore:
I don't know why but opendelta seems to be very slow and laggy .

it says 23M/s and finally 300K/s when signing the zip .

I'm on 0619 build .
[ONE Original Android Development] maxwen:
as said on g+ :)

OTA is not functional at the moment
[ONE Original Android Development] 69gm:
Thanks...but where did you see that? All I see are old posts on g+ page for Omni...:confused:

Bummers...OTA was working well up to a couple days ago...
[ONE Original Android Development] szetmk:
Hi dev,

I want to know what firmware suitable for this build???

Thanks!
[ONE Original Android Development] :
You rock guys. This ROM is just awesome. I've had only heard about this ROM until now but never flashed it on any of my phone.

I got this phone 2 weeks back and since then i've been trying various ROMs but none of them were as good as this. All of them which are on 5.1.1 has few bugs and one is very annoying that is 'Graphic Glitch' which appears in few of my games, mainly Clash of Clans.

Yesterday, i was browsing Google+ and read that OmniRom is finally back on 5.1.1 and i thought why not give this a try as well to see if has those bugs or not.

And guess what, just flashed it and there are NO BUGS at all. Not even those graphic glitch which i had in previous roms.

Excellent work guys. keep it up.

Btw, is there an option for double tap on status bar to sleep? or is it coming in future ?

Thanks
[ONE Original Android Development] scanno:
Double tap on the status bar is not something that will be implemented. But you can assign a double tap activity to the home button. One of the activities you can choose from is sleep.
[ONE Original Android Development] baddelay:
Omni Community on G+
[ONE Original Android Development] maxwen:
I not only see that - I wrote that :)

https://plus.google.com/+MaxWeninger/posts/GTthNNtUD6v

---------- Post added at 03:25 PM ---------- Previous post was at 03:23 PM ----------

Can you describe that glitch please so that I know what to look for in future testing
[ONE Original Android Development] Renosh:
The graphics glitch isn't there on Omni only exists in CM based ROMS for 5.1.1. There are streaks and discolorations that obscure the view of menu items in the game. I can give some screenshots if you're interested to see it?
[ONE Original Android Development] maxwen:
yes please

and if you could come up with a easy way to reproduce on those ROMS that would be golden :)

The point here is that this could come from properitary blobs and I want to avoid that

we pull in the problem anytime when we update our blobs too. Which we do rarely

but sometimes its necessary.
[ONE Original Android Development] :
Well, i took screenshots earlier when i was on other ROMs and now i lost it while flashing.

But i can direct you to the image showing that graphic glitch. Below are the few images