yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] indian84:
No..

But to be on safe side make efs backup...
[ONE Original Android Development] natheux:
Okay thanks, I ask this question because the Oppo find7 and the Oneplus One haven't

exactly

the same config.. And the Omnirom nightlies are made for the Oppo find7, right?
[ONE Original Android Development] indian84:
Not exactly.. Even though this build is labelled as find7, it is specifically made for OnePlus One...
[ONE Original Android Development] jonathan413:
Does omni ROM still do multi window? Can't find the setting if so and multi window on xposed doesn't work all that well with certain apps I use.
[ONE Original Android Development] scanno:
[MENTION=5965253]samstone86[/MENTION] [MENTION=4683552]maxwen[/MENTION]

For those people who would like to have omnirom lollipop pretty nightly builds for the oneplus one, you can try this one: https://www.androidfilehost.com/?fid=95916177934521299

Flashing instructions :

Make sure you have a bootloader / radio from cm11s. If you flashed a cm12 version, you have a bootloader / radio combination that causes some problems with omnirom (proximity sensor will think you are holding your phone to your ear and locks your phone until the calls ends).

For root, flash the latest supersu. Regarding gapps, the PA gapps are working fine for me.
[ONE Original Android Development] lolzballs:
The OnePlus One is the find7op(OnePlus edition) in omnirom
[ONE Original Android Development] anishz:
There are no nightlies after 28th. Any possibility for lollipop nightlies? :D

Sent from Bacon
[ONE Original Android Development] scanno:
Not yet.

But I will be posting a build now and then.
[ONE Original Android Development] anishz:
Thanks! I am using 31st build by lolzballs. Looking forward to the next ones.
[ONE Original Android Development] fermasia:
Hi guys, I've made an unofficial homebuild synced up to today's modifications (you can check omni's gerrit to see what's new). It's straight and pure sourcebuilt omni 5.0.2 without any modifications. Many thanks to [MENTION=905572]scanno[/MENTION] for helping get everything straight to achieve a working build.

Here's the link: https://www.androidfilehost.com/?fid=95916177934524918

I'll try to build once or twice a week (unless our devs do it before) in case that helps the team anyhow, letting them concentrate on coding if that's their desire.

Cheers :good:
[ONE Original Android Development] anishz:
Thanks [MENTION=905572]scanno[/MENTION] for the 0209 build. Is it OK to flash?
[ONE Original Android Development] scanno:
NO!!!

It is an experimental build and will get you a nasty bootloop.
[ONE Original Android Development] anishz:
Hahahaha,

You were 3 mins late, I was too impatient. It bootlooped like a bit#h. Anyways I am back from nandroid [emoji13]

Keep em coming. Just read the omni blog update. Am excited for the LP night lies.
[ONE Original Android Development] scanno:
If there is a build worth flashing i will put it or mention it here.
[ONE Original Android Development] kripz:
Is 4.4 going to be worked on? I wont be upgrading to LP until there's xposed or equivalent.

Does OmniRom have the latest touch firmware? Touchscreen seems to be a bit dodgy at times.

Also where can i check the 5.0 branch?
[ONE Original Android Development] anishz:
Thanks, will check the thread for that and won't jump on flashing.

You can check nightly changelog here. Lots of commits were added on 25th, though whether anything related to firmwares i have no idea.
[ONE Original Android Development] fermasia:
Afaik, 4.4 developement has been dropped (not 100% sure). So sit tight, xposed for lolliopop will probably take some time.
[ONE Original Android Development] scanno:
We are all busy with 5.0. There is no time to work on 4.4.
[ONE Original Android Development] knuspertante:
[MENTION=1553639]kripz[/MENTION] for xposed see this post:

http://xdaforums.com/showpost.php?p=58751037&postcount=37
[ONE Original Android Development] fermasia:
New Omni 5.0 unofficial build

Guys, here I'm sharing a new build. Up-to-date with latest changes (check gerrit for details) and straight from Lollipop 5.0.2 Omni source (with just a small cherry-pick from a still open gerrit entry about materializing apollo's look, so please don't blame Omni for any inconsistency, it's all me being too curious and trying that out before it's propperly released).

Here's the link: https://www.androidfilehost.com/?fid=95916177934527641

Cheers :good:
[ONE Original Android Development] scanno:
Is anyone using the test builds posted here?

I would like to know about battery drain and radio issues.
[ONE Original Android Development] scanno:
Well there are more nice features on the way :)

There is work done on ambient display, OTG mount / unmount notifications for instance

I am trying to get omni to work with the newer blobs because i have a very huge battery drain on omni and the camera quality is low. Hopefully the new blobs will solve these problems and eliminate the need to use the kitkat radio.

So there is still a lot of work te be done
[ONE Original Android Development] anishz:
Ambient display sounds good. Cm hasn't got it right, keeps coming on even when device is still.

I was using the previous one fermasia posted for about 2 days and then went back to cm12. You are right about the battery drain. I lost almost 20% overnight. Camera, frankly didn't notice much as I dont click much photos. But I did like the slowshutter on KitKat omni.

Dont like theme engine much so if omni solves battery and adds only few features like KitKat had it will be great.
[ONE Original Android Development] fermasia:
About features, yeah, I noticed several nice things being worked in gerrit, but didn't want to mention them not to sound like I'm asking for ETAs :p I'm specially fond about the idea of getting full layers support, and when possible, get back tiles customization options (specially LTE and network type toggles). But well, it's taking it's time and we will patiently wait for even more awesomeness - lol

About performance, I didn't notice that kind of drain, but I usually clean up many native apps, change govs and IO schedulers (interactive/noop) and use greenify over almost anything... What I did notice is after some time online (half a day, usually) I get a bit of stuttering on transitions. Haven't measured overnight drain, but I'll pay attention and report back.

About radio signal, I'm having some signal drops (using CM11s radio), but I'm not positive that my carrier isn't to be blamed about them.
[ONE Original Android Development] anishz:
Hmm. Haven't tried greenify.

Yes I forgot to mention about that stutter, but I get it on the default settings, ondemand but when I change to interactive its OK for me. Haven't tried changing the gov.

I installed slim gapps and used same settings as on CM12 but here google services suck like Dracula.

Radio seemed fine for me, calls were good similar to new CM12 radio.
[ONE Original Android Development] anishz:
Any possibility of a new build in the weekend with the new swipe options commit, its been merged :D.

Active display looks good too but hasn't been merged yet
[ONE Original Android Development] fermasia:
I can build tomorrow, I think :D
[ONE Original Android Development] anishz:
Waiting eagerly, till now i have been hopping around as i like to flash roms.

But next weekend am leaving for my job at sea, where i won't be able to get online much at all, maybe 3-4 times in the whole trip of 6 months, its terrible without internet. So i want to stay on something good. Hopefully this build works great. :fingers-crossed:. Or my fallback is going to be omniKK.
[ONE Original Android Development] scanno:
Then do not use omni5 yet. Battery drain is terrible
[ONE Original Android Development] anishz:
Yes, guess I will have to go onboard with omni KK.
[ONE Original Android Development] störte:
What do you think about layers instead of cm themeengine? I like the layers a lot

Send by Hyperdrive on one+One
[ONE Original Android Development] fermasia:
Layers it's true GPL, lightweight and far from cm's bloatware theme engine... and luckily OmniROM is already working on it :good: If you dig in gerrit you'll find it's progress.
[ONE Original Android Development] störte:
Great. As soon as it is implemented i will try omni then.

Send by Hyperdrive on one+One
[ONE Original Android Development] 530farm:
You say CM Theme engine is bloated. Do you see it having negative effects on ROMs even if you don't use it?
[ONE Original Android Development] fermasia:
Bloat and negative effects are not the same. I'm using the word bloat as in "I can't choose to remove it". Besides, there are less intrusive options -like layers- to do the same, and what's more important, it's not there just to empower our experience, but for Cyanogen to make money (you can find free themes or make one yourself, blah, blah, true, but that's not the reason why they developed it). CM theme manager is a monetization strategy from Cyanogen Inc, and that's no secret.

About effects, we have several examples on how it might cause stability issues, but again, that was not the point of my comment.
[ONE Original Android Development] hughfollett:
Not sure about the money thing, as CM theme engine existed way before Cyanogen Inc

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] fermasia:
I disagree (it's like saying you are not sure google apps are meant to make money cause they existed before adswords) but I'm afraid we can't discuss this here, we already went too far OT (for which I apologize).
[ONE Original Android Development] Yvan12:
Lollipop is for when?
[ONE Original Android Development] theCroh:
Exactly and precisely at when Lollipop o'clock(ish)

Lähetetty Nexus seiska 2013:sta Tapatalkilla
[ONE Original Android Development] fermasia:
Official? I don't know.

Unofficial Omnirom Lollipop? http://xdaforums.com/oneplus-one/development/rom-omnirom-lollipop-unofficial-builds-t3032329

:D
[ONE Original Android Development] fermasia:
Is there any chance we could get Oppo Camera compatibility? I'd be interested in helping to achieve it if anyone's willing -and interested- to guide me a bit (or a lot). I think there might be some work to do on the app, that's been successfully ported to CM, but won't work on on Omni. I'm getting really poor performance of the Aosp camera, specially in low lights enviroments. Oppo's camera (and I mean ColorOs camera) is not heaven, but I've been doing some tests and the difference is noticeable.
[ONE Original Android Development] maxwen:
Link the commits needed
[ONE Original Android Development] fermasia:
Ok, I'm looking into it, I'll let you know when I have somthing that works for you to judge.
[ONE Original Android Development] fermasia:
Sorry, thought I could do something with it but it's a bit over my head, or I lack the needed time to invest into doing it, ot both. I'll give it another shot this weekend.
[ONE Original Android Development] scanno:
Time is the enemy of ROM development (just like family, work) [emoji52]
[ONE Original Android Development] maxwen:
And google
[ONE Original Android Development] scanno:
Ah yes, how could i forget about Google :)
[ONE Original Android Development] fermasia:
For what I've seen in gerrit... should we expect layer's support in the future or are we more on the dropped for good side? :confused:
[ONE Original Android Development] malavan:
Yes sum kind of theming would be nice please.
[ONE Original Android Development] fermasia:
Layers has been in the oven for some time now, so yes, it was planned to bring theming to Omni. But there are some comments in gerrit that seem to show some disagreement with the layer's team, so I think that might not happen. I just wanted to be sure about it.
[ONE Original Android Development] scanno:
From the comments i would say that the Layers implementation within Omni has been abandoned.
[ONE Original Android Development] smoki3:
Have someone tried to build 5.1 builds?
[ONE Original Android Development] lokesh.3440:
There is an unofficial build already available in "One Android Development Section". Take a look :

http://xdaforums.com/oneplus-one/development/rom-omnirom-t3055783
[ONE Original Android Development] evronetwork:
I'm still puzzled with it's called "find7op" instead of "bacon" :p
[ONE Original Android Development] Nexus5-32GB:
dont be :) OPO and find7 are extremely similar phones (same design as well), the find7 has QHD display and few more changes, otherwise it is same as OPO.
[ONE Original Android Development] _ASSASSIN_:
omni really likes Oppo... Just read this article.

http://omnirom.org/devices/finding-way-nightlies-oppo-find-7/
[ONE Original Android Development] evronetwork:
Yeah heared that before, still codename is bacon, why not name find7 to bacon7? :p (it will sound cool, also 7 bacons seems delicious)

Read what? I mean this doesn't tell me anything that I don't know already :D

Sorry for the OT we can move on, I was just wondering the why that's all
[ONE Original Android Development] webore:
find7op means a phone like find7 made by one plus

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

I flashed your new build on afh ,everything works ! many thanks !
[ONE Original Android Development] scanno:
https://www.androidfilehost.com/?fid=95916177934543405
[ONE Original Android Development] webore:
Well , it seems that my headset doesn't work on this build .:crying: didn't notice that before.
[ONE Original Android Development] maxwen:
Wired or Bluetooth?

And what's not working - mic only it also headphones
[ONE Original Android Development] webore:
I'm using wired heafsets.

The one without mic takes no effects when plugged and the one with mic works but the sound output is very Weird unless I press the button on it (regarding the difference between omtp and cita standards , it can make sense .)

---------- Post added 20th March 2015 at 12:03 AM ---------- Previous post was 19th March 2015 at 11:47 PM ----------

Problem solved .

Just Flash a kernel:D.

I saw that the donkey one kernel by fermasia can work on Omni and flashed it ,now my headset is OK .
[ONE Original Android Development] maxwen:
But that doesn't help me :)
[ONE Original Android Development] webore:
well I really want to help but don't know how to .
[ONE Original Android Development] scanno:
It would be helpfull if you could provide a logcat and dmesg so we can see what i going on when you plugin and use your headset.

You can provide a logcat and dmesg by using adb from your PC or using a terminal app on your phone.

If you google it you will find a lot of guides how to do this. Personally i think using a terminal app is the easiest way (no driver setup / setting up adb on your PC).

1. Install a terminal emulator app from the Play Store

2. Open the terminal emulator app

3. At the linux command prompt run su (you get root access)

4. At the root command prompt type: dmesg > /sdcard/dmesg.txt

5. At the root command prompt type: logcat > /sdcard/logcat.txt

6. Wait a few seconds and press ctrl-c to quit the logcat (or close the terminal session)

7. Find logcat.txt and dmesg.txt in the root of your internal storage

8. Send the logcat.txt and dmesg tot Maxwen [emoji2]

Oh yes before you do all this, make sure you have tried the things you do with your headset. Also a reboot of your phone before doing this is also nice because the logcat will be smaller (there will be less logging from other apps etc)
[ONE Original Android Development] webore:
I've emailed to you the logcat and dmesg.

The logcat seems messy so I can do a full wipe if needed .
[ONE Original Android Development] fermasia:
[MENTION=4683552]maxwen[/MENTION] & [MENTION=905572]scanno[/MENTION]

Not sure I'm actually helping, but in case it helps you pinpoint what's wrong, all what I've touched in my custom kernel that's sound related can be found here: https://github.com/fermasia/kernel_opo_omni/commits/test2?page=1 from 1745a72 to 2a9323f ; it's basically about including Faux Sound engine but it modifies some codecs and permissions (they are picks from other devs, only that I've made some minor adaptations for Omni). Still if there are some logs and you think I can help (you are far more capable of solving this than I am) I'd be happy to look at them.

Edit: I'll probably get some time this weekend to flash Omni 5.1 and test it myself.
[ONE Original Android Development] maxwen:
Thanks - I have a few ideas to try.

For me the original Oppo headset works fine as usual but a custom headset don't although this one has never worked not even with 4.x
[ONE Original Android Development] maxwen:
Does that headset worked with Omni 5.0? 4.4?
[ONE Original Android Development] webore:
that should work because I've never noticed the problem.
[ONE Original Android Development] 1Nexus:
[MENTION=905572]scanno[/MENTION]

Just been trying your most recent 5.1 omni builds and everything actually runs very well!

The only problem is that the phone doesn't detect a proximity sensor (therefore auto rotate does not work) because of the find 7 modem (flashing another modem over doesn't change the modem). The camera also works but the quality is very grainy.

Thanks!
[ONE Original Android Development] scanno:
Thanks for your comment. Flashing the firmware from CM11S solves the proximity sensor problems. The camera being grainy is also known. No solution for the grainy camera yet.

What i am curious about is battery drain.

---------- Post added at 09:37 PM ---------- Previous post was at 09:33 PM ----------

@All

You do realize that when you download a build from my TestBuilds directory over at androidfilehost that there is a chance that the build will not work....

I do not mind that you flash those builds, but do realize the risk.
[ONE Original Android Development] darkobas:
[MENTION=905572]scanno[/MENTION] do you use native and av caf? any other picks? My build gets stuck on boot anim
[ONE Original Android Development] scanno:
Yes i am using the android-5.1-caf branch of native and av.

No additional commits are needed.

Did you include the blob files from DonkeyCoyote?

https://github.com/DonkeyCoyote/proprietary_vendor_oppo/tree/android-5.1
[ONE Original Android Development] darkobas:
Yeah... i think ill have to look at omni vendor one more time since i am using my own vendor.

thanx for the info. Should really make troubleshooting much narrower

thanx
[ONE Original Android Development] scanno:
I have tried to look at the cm vendor repo, but was not successful to build a working omni with the updated blobs. If you manage to build a fully working build with newer blobs then we have now, please share
[ONE Original Android Development] scanno:
New testbuild uploaded.
[ONE Original Android Development] malavan:
Any theme engine
[ONE Original Android Development] maxwen:
Nope
[ONE Original Android Development] fermasia:
Do you know if there might be any difference between these buids and those eagleeyetom is doing? I'm not saying you must know or anything, just wondering if you are working together. Thanks :good:
[ONE Original Android Development] scanno:
There is no big difference. As far as i can see they are all commits from Gerrit. But there are people working on stuff and as long as name are not not equals to xda nicks I cannot say who is who
[ONE Original Android Development] maxwen:
Fix available
[ONE Original Android Development] scanno:
Build available also.. Will upload later
[ONE Original Android Development] scanno:
[MENTION=535343]all[/MENTION], [MENTION=5217288]webore[/MENTION]

Here is the build with the fix maxwen was talking about:

https://www.androidfilehost.com/?fid=95916177934549412

Have fun.
[ONE Original Android Development] webore:
Downloading now .thanks !
[ONE Original Android Development] webore:
the new build works fine , but I can hear small jitters from my headst while listening to the music if I plug the charger or open some heavy app .

---------- Post added at 10:52 AM ---------- Previous post was at 10:49 AM ----------

It happens with poweramp,I will test Apollo later
[ONE Original Android Development] webore:
Apollo seems to be fine ,and poweramp works fine if I changed the audio thread priority.
[ONE Original Android Development] darkobas:
[MENTION=4683552]maxwen[/MENTION] and co. . Just fyi if you dont know already. Maybe it comes helpfull. oxygenos kernel https://github.com/OnePlusOSS/android_kernel_oneplus_one
[ONE Original Android Development] :
the unofficial is really good and updated. In case people were missing the newest one
[ONE Original Android Development] :
Wondering what happened to the official builds.
[ONE Original Android Development] scanno:
There are new builds. I am uploading them here: https://www.androidfilehost.com/?w=files&flid=22231

Perhaps not that regular as on the unofficial thread.
[ONE Original Android Development] :
how about the nightlies :)

would be nice if development got going again for the community. Dont know the figures but that way others can submit fixes as wel and such
[ONE Original Android Development] maxwen:
Who said development has stopped?
[ONE Original Android Development] scanno:
Development has not stopped. It is just that omni does not have official nightly builds yet. All the changes are on Gerrit and being used also by the unofficial builds.

If anyone wants to submit fixes, they can. Just go to gerrit.omnirom.org and submit changes to the android-5.1 branch.
[ONE Original Android Development] :
didnt say stopped or mean to say that.
[ONE Original Android Development] schaggo:
If I got it right, its on [MENTION=591147]Entropy512[/MENTION] to get the buildbots going. He is/was busy with implementing the/a new themeing functionality as everybody is crying for that.

Omni hasnt got the manpower CM has. Things progress a little slower. So give the man a break and let him do his things. Be quiet, wait. It'll be ready when its ready.
[ONE Original Android Development] :
true,

hope entropy512 is doing fine, dont want to rush him. I think he should be redistributing some of those tasks. He busy enough as it is. Hope he got some peace after the whole cm ordeal.
[ONE Original Android Development] :
Multirom not working with this rom
[ONE Original Android Development] maxwen:
We know :)
[ONE Original Android Development] scanno:
New build uploaded. Build with the cleaned up defconfig.
[ONE Original Android Development] webore:
also with new blobs or not ?
[ONE Original Android Development] scanno:
Yes also with new blobs. So you should have the cm12s radio installed
[ONE Original Android Development] maxwen:
So actually:

Just use a custom kernel that has included the required kexec patches

We dotn support this with stock kernel
[ONE Original Android Development] tombassi:
4.4.4 folder is empty ! any mirror for latest omni kat? please share any one.
[ONE Original Android Development] :
Have you tried with multirom?
[ONE Original Android Development] maxwen:
Holy crap!!!

I have already answered this!
[ONE Original Android Development] fermasia:
And you did it two posts ago... LOL
[ONE Original Android Development] :
lets break this akward silence

loving how the official and unofficial blend toghether.

super rom guys
[ONE Original Android Development] taufiqs:
Whats the difference betwen them?
[ONE Original Android Development] NuLLV01D:
Apart from being official and unofficial? I don't think any are
[ONE Original Android Development] mammenj:
Multi window still wip?
[ONE Original Android Development] Maarren:
I was getting really annoyed by two issues on cm12.1.

https://jira.cyanogenmod.org/browse/NIGHTLIES-1327

https://jira.cyanogenmod.org/browse/BACON-3397

But on omnirom these issues are not present,it just works and is stable. Thank you!
[ONE Original Android Development] hp13:
Grainy camera is the only issue I am facing. I can't use this as daily driver till then. Good ROM otherwise.
[ONE Original Android Development] nadiros:
Did you try the flashable Camera Next Mod v22?

I get excellent pics with it. Its in the Oneplus themes and apps thread.
[ONE Original Android Development] hp13:
I haven't tried it yet. I installed other next camera mod.apk installed and it kept crashing .