yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] Renosh:
Small bug I'm experiencing, when you put the menu key long press function to open/close menu, it doesn't work properly. It however works if set to single tap of menu key. The menu shows up but as soon as you lift your finger off the button, it disappears. Normally the menu UI remains so you can use it. Not a big deal at the moment I'm just using the virtual menu keys as I prefer menu key to open recents, but just FYI
[ONE Original Android Development] maxwen:
But I can say that we are making good progress for 6.0 on find7 and find7op

Broken radio is the most noticable problem at the moment.

Aside from that proper testing needs to be doen before we are

going to provide first test builds to you.
[ONE Original Android Development] lokesh.3440:
Count me in as a tester for your builds.
[ONE Original Android Development] maxwen:
Yeah known issue - the fix was never merged into 5.1 thanks for reminding me.
[ONE Original Android Development] Renosh:
Noticed it's already merged so its either in today or tomorrow's nightly. Thanx again
[ONE Original Android Development] Renosh:
[MENTION=4683552]maxwen[/MENTION]

Found another small bug involving torch. If you turn on torch while at the lock screen using the QS tile and turn off screen. The torch will never turn off (using tile or gestures). Likewise if you use the v gesture while at the lockscreen, unlock phone and lock it, it will never turn off unless you reboot the phone.
[ONE Original Android Development] maxwen:
wut?
[ONE Original Android Development] Renosh:
lol

I'm not using any mods just ROM +TK gapps + SuperSU

So nothing that could invalidate my bug reports
[ONE Original Android Development] maxwen:
the problem is that I dont understand what the problem is :)
[ONE Original Android Development] theCroh:
[MENTION=4683552]maxwen[/MENTION] Do you think Omnirom Marshmallow will be dirty flashable over Lollipop Omni or will it require a clean flash?

Lähetetty OnePlus Onesta Tapatalkilla
[ONE Original Android Development] dafonehacker:
It's the charging while the device is turned off. Don't know about the bug though.
[ONE Original Android Development] CtlAltDefeat:
Well then what happens if your battery goes to 0%, you aren't able to charge anymore? o.O

Sounds like a pretty devastating bug.
[ONE Original Android Development] samstone86:
I mean that if the phone is off and you charge it, the screen lights don't turn off.

And yes it's the only bug I know :D. Maybe some small background things but I use it since I started every day ... And thats over a month now. ( Today I ask for official nightlys )
[ONE Original Android Development] samstone86:
No ... It works pretty good but like i wrote ... The screenlight doesn't turn of. :D
[ONE Original Android Development] CtlAltDefeat:
I'm confused, if you're talking about charging while the phone is off, how would screen light turn on?

Unless by off charging you just mean charging while the screen is off, not the phone.
[ONE Original Android Development] dafonehacker:
When you plug the phone in while it is turned off, it will go into a separate mode for charging, while not booting the whole OS. The screen wil turn on and show an animation, and the bug seems to be that that screen doesn't turn of after a specified time (eg. 15 sec)

Try to plug your phone in while it's off and you'll understand.
[ONE Original Android Development] samstone86:
We now have official nightly builds :cool:
[ONE Original Android Development] dafonehacker:
May I just ask why it's still called find7op? The real codename for the OPO is bacon. Shouldn't it be called bacon? Sounds tastier too ?
[ONE Original Android Development] maxwen:
Because it is just a find7

Why call it something different then it is?
[ONE Original Android Development] dafonehacker:
Because it's kind of confusing if it's called bacon on all roms and find7op on this one
[ONE Original Android Development] maxwen:
Welcome to enjoy the difference :)
[ONE Original Android Development] samstone86:
Sorry :D but the name will stay :angel: check the default Bluetooth name :D
[ONE Original Android Development] maxwen:
You dont want to accept that this is actually an oppo device right? :)

BTW what's wrong with " "Oppo Find 7 OnePlus Edition""???
[ONE Original Android Development] Setting.Out:
(Sarcasm). I am having really smooth scrolling issues, where's the lags?.. The stock kernel is also providing too much performance, making other ROMs I've used jealous.. Are there any plans in the future to add more lags and reduce performance.?. ;)

I am genuinely impressed by this build.. It is very fluid, fast without sacrificing too much battery.. ;)
[ONE Original Android Development] newellj79:
Where are the official night builds ?
[ONE Original Android Development] CWick4141:
I would say the link in the op that says download.. It's not called Bacon it's find7op
[ONE Original Android Development] tmotard:
Hi,

New to this ROM, i've installed it yesterday (first OTA this morning)

Very smooth, no problem at all for the moment.

Omniswitch is a great feature.

Thanks for your work.
[ONE Original Android Development] Heisenberg:
But it isn't an OPPO Find 7 at all. Just because it uses the same device trees doesn't mean it's the same device.

Transmitted via Bacon

---------- Post added at 09:01 PM ---------- Previous post was at 09:01 PM ----------

May I ask why? It isn't the correct name for this device.

Transmitted via Bacon
[ONE Original Android Development] acuicultor:
We have a code name and it is "bacon" why create confusion changing this code name to an ambiguous code like "find7op"? This is nonsense for me. Just my two cents.

Sent from my crispy bacon
[ONE Original Android Development] deepaklunked:
Different Android versions can't be dirty flashed bro.

Sent from my Oxygenated One
[ONE Original Android Development] maxwen:
In theory yes

In reality - no

We needed to revert a lot of features for the moment witch will make an incremental update very unlikely :)
[ONE Original Android Development] lokesh.3440:
I would love to test your M builds. Would you mind sharing your build link ?
[ONE Original Android Development] deepaklunked:
Bro, there's a dedicated thread for experimental MM Omni builds, in the same, original dev section.

Sent from my Oxygenated One
[ONE Original Android Development] lokesh.3440:
Thanks. I was just checking out this thread and found omni 6.0 immediately after it...[emoji2] [emoji2] [emoji2]
[ONE Original Android Development] natheux:
ignore this
[ONE Original Android Development] Gabeloooooo:
Anyone has issues with Lock Screen becoming unresponsive from time to time?

I often wake up my phone and find I can't unlock the screen. It's like it can't recognize my fingers anymore (the camera and phone shortcuts move randomly when I try to unlock).

Can't even press the items in shut down menu when I make it appear. Only solution is to power down phone by holding power button long enough and rebooting.

Happens maybe every 2-3 days?
[ONE Original Android Development] lumufei:
in some App the image is reversed ?how to fix ?
[ONE Original Android Development] Bongofriend:
Are you using a custom kernel? If yes just dirty flash the ROM and the issue should be fixed.
[ONE Original Android Development] lumufei:
no. clean flash and stock kernel
[ONE Original Android Development] evertking:
Could some one help me out? I can flash every ROM in the forums but when it comes to omni/omni based I can not vet it to boot.. 5.1.1-6.0.0 same problems.
[ONE Original Android Development] Arju:
What firmware version do you have? What is the recovery you are using and which version?
[ONE Original Android Development] cesarp3791:
I have the same problem, installed several ROMs without a single problem, but Omnirom never booted (at least the 5.1.1 one), just got stuck on OnePlus logo bootlooping and never showed the Omnirom logo...

Right now i'm using SlimSaber CAF with latest HydrogenOS firmware (previously had the 241 one, Omnirom didn't booted with that one anyways).. TWRP 2.8.7.0.4 materialised, which can install firmwares correctly..

I've been wanting to install Omnirom to get to know the AOSP stability and battery friendly status (that i've read, anyway, correct me if i'm wrong)..

What do you suggest to do to get it to boot Omnirom properly?

Thanks!
[ONE Original Android Development] Arju:
What error do you get in twrp. I think it could be firmware incompatibility. Try to flash firmware version 241 and then reboot into slimsaber caf and then reboot into twrp and then flash omni again. That should make the ROM flash. After that you could flash hydrogenos firmware if that's your preferred firmware.
[ONE Original Android Development] maxwen:
It's a known issue that it won't boot on certain devices. Exact reason has not been found yet
[ONE Original Android Development] cesarp3791:
Thanks! I thought that i was missing a step or not following correctly installation instructions. Will check after a while if it gets solved ;)

Will do at some moment, right now testing HydrogenOS firmware.. Calls are definitely better, before both ends struggled to hear each other normally, now it doesn't.. Thanks for your instructions, they'll be helpful later :)
[ONE Original Android Development] johhnyred23:
I did a clean wipe and I been rocking this rom for weeks, and as new release come out, I dirty flash them with no issues. On 12/01 now
[ONE Original Android Development] fajabird:
I'm affected too. Already tried a few things:

1. clean flash (factory reset before/after flashing omnirom)

2. different omnirom versions (latest 5.1.1 and 6.0-Homemade)

3. resetting device (cm12.1-YOG4PAS3JL) which includes bootloader and radio images via fastboot

non worked!
[ONE Original Android Development] maxwen:
Have you ever tried if you get a last_kmsg when you force reboot the device?
[ONE Original Android Development] fajabird:
My device absolutely won't boot with any omnirom version - don't know hot to get some logs.

Additionally I did the following today, because in addition to omni-rom I have the problem that I'm not able to revert back to any TWRP version before 2.8.6.1 (only 2.8.6.1 and 2.8.7.0 are booting on my device).

1. reverted back to stock CM11S-factory-image including all radio/modem partitions

2. installed twrp 2.8.6.0

Now twrp 2.8.6.0 was booting and I tried to flash omni 5.1.1 which again failed to boot (modem dependencies not met), but a different way than before. After updating radio/modem to CM12S twrp 2.8.6.0 was not starting anymore and I had to update TWRP to at least 2.8.6.1.

The TWRP-problem seems very similar to what I see from omni-rom - simply does not boot. And again - its not affecting ALL bacons, right?
[ONE Original Android Development] maxwen:
Get me a kernel log of a TWRP boot please - newest possible version
[ONE Original Android Development] fajabird:
I attached the content of /proc/kmsg after booting into TWRP 2.8.7.0.5
[ONE Original Android Development] webore:
running good on my device .

But I'm anxious about the next build ,you have notifications filters on lock screen finally!
[ONE Original Android Development] logg84:
see 6.0.1 new build...anyone tested it?
[ONE Original Android Development] baddelay:
Runs fantastic on my find7op.
[ONE Original Android Development] maxwen:
Thread deprecated - please continue here http://xdaforums.com/oneplus-one/orig-development/rom-omnirom-weekly-testbuilds-t3264899

and thanks to xda for creating confusions :)
[ONE Original Android Development] kenruige:
Hello, Omnirom nightly 20160221, 22, 23, there were double-click the bright screen failure BUG. Tested result is xposed-v80. CM and previous versions did not have this problem.
[ONE Original Android Development] webore:
Do you mean dt2w ? Oh I use xposed too and have the same problem .May be that's the side effect of dexpreopt ?
[ONE Original Android Development] maxwen:
LOL
[ONE Original Android Development] adlx.xda:
Hi,

Could anyone with Omnirom on an OPO and a Chromecast confirm if Google Photos can cast photos to ChromeCast ?

There's a bug in CM12.1 & CM13 that apparently prevent this to work (https://jira.cyanogenmod.org/browse/BACON-4279), but someone on the Jira ticket says it works on Omnirom. Can anyone confirm? (if you do, could you please say which Omnirom build (or better build date) you have?

Thanks in advance.
[ONE Original Android Development] maxwen:
Works on find7 therefore it will also work on find7op
[ONE Original Android Development] adlx.xda:
Sorry, I meant a OPO as in Oneplus One, not Oppo, my bad.
[ONE Original Android Development] Bobbi lim:
In Omni terms, find7op is actually OnePlus One.
[ONE Original Android Development] Cesaragus:
I know people have said something about video being upside down, but my whole UI is upside down when I turn screen rotation on. If I rotate the device 90 degrees (landscape) it rotates as the top was the bottom. I want this to make it clear... If I open an app (i.e. a messaging app) and rotate the screen to landscape, the keyboard appears on the top and the status bar appears on the bottom, and everything is upside down.
[ONE Original Android Development] Heisenberg:
Project has been discontinued, thread closed.
[ONE Original Android Development] maxwen:
Who is "we"? :)
[ONE Original Android Development] acuicultor:
Bacon is the code name that one+ or google (dont know) assigned to one+one and we are the rest of users and developers using this code name daily.

Sent from my crispy bacon
[ONE Original Android Development] scanno:
Sigh. Why such a discussion about a name you will only find in the settings tab and developers use to make breakfast, brunch or lunch ?.

Just enjoy OmniRom on the OPO.

Verstuurd vanaf mijn Nexus 10 met Tapatalk
[ONE Original Android Development] Deadpool253:
Why is this named find 7? Isn't this device bacon? I'm confused... Is this thread in the wrong place? People are going to brick their phones.
[ONE Original Android Development] CWick4141:
Actually its find7op for omni.. and who really cares what they decide to call it.. just be happy they brought us omni
[ONE Original Android Development] tmotard:
I think if that's the only "problem" in this thread then we're all happy with this ROM :angel:
[ONE Original Android Development] Deadpool253:
Well I just flashed it on multirom and it didn't boot so I think its in the wrong section. I mean what are you guys flashing because I didn't see anything A0001 or Bacon in the download link in the op. Did I miss something?
[ONE Original Android Development] Heisenberg:
People care because that isn't the right device codename for this device, it's the codename for the Oppo Find 7. The right codename for this device is Bacon. The only reason it's being used as the codename on this ROM is because they use the same device trees and the dev hasn't corrected it like every other OnePlus One dev does.

Transmitted via Bacon
[ONE Original Android Development] scanno:
Find7op means find7 OnePlus edition. The device is almost the same with a few differences (camera being one of them). This message is written on my bacon/a0001 with the omni find7op device tree. So to be short: it is in the correct section.

But I can understand that people can get confused by this.

Verstuurd vanaf mijn A0001 met Tapatalk
[ONE Original Android Development] Deadpool253:
Anyways... The 1013 build doesn't boot on multirom. I don't know if the link in the op is to our device but if it isn't can someone link the correct one for our device so I can try it?
[ONE Original Android Development] scanno:
The download link is to the correct device.

Verstuurd vanaf mijn A0001 met Tapatalk
[ONE Original Android Development] nickdoherty:
Doesn't boot here either, but I used most recent phillz instead of twrp. Is that really an issue or is it ROM related?

Clean install, no multi ROM.
[ONE Original Android Development] newellj79:
No version I have tried has worked with multirom. That said, it does say in the multirom OP that it just a big hack so you get what you get.
[ONE Original Android Development] TheShoxter:
Actually, it's because this is indeed Omni developed for the Find 7, but it does work on OPO. If I'm not mistaken, OmniROM team has said they won't officially support the OPO.
[ONE Original Android Development] CWick4141:
https://plus.google.com/116747335830141635325/posts/JzqFnG3mTRK

I would also assume the thread title wouldn't say official if it wasn't
[ONE Original Android Development] TheShoxter:
Because they are official nightlies, but for the Find 7. They just work on OPO because they have same device trees. So OP isn't wrong, but it's slightly misleading. And if it means anything, the latest nightly isn't booting.
[ONE Original Android Development] hughfollett:
It's not simply a name. It has a different baseband and it connected to another (stranger) carrier and my pc needed to install different drivers to recognize the phone..
[ONE Original Android Development] buzzqw:
yep, not booting here too

BHH
[ONE Original Android Development] samstone86:
Hey guys ... First ... Its totaly official omnirom ! The bacon download on dl.omnirom.org is find7op and its named like it is!! If you flash it on find 7 you may have bugs like camera upside down. Please report bugs to jira with logcat ... But i dont care now on multirom ... AND use the recommendet recovery... The one and only TWRP :laugh:

I may be a bit unresponsive because studies started :cool:
[ONE Original Android Development] samstone86:
So 20141014 is not booting ? There shouldn't be any relevant changes ... Maybe a compiling issue. Please wait for next build.
[ONE Original Android Development] Heisenberg:
Ok, but can you please answer the question (that's been asked by multiple people), why are you not using the correct device name?

Transmitted via Bacon
[ONE Original Android Development] buzzqw:
13/10 (14/10 isn't landed for download..)

BHH
[ONE Original Android Development] Coug76:
I finally got it to build at home once I included the donkeycoyote github in my manifest. It runs well. I've had a soft place in my heart for OmniRom ever since it launched.

Thanks for your efforts.
[ONE Original Android Development] rippernz:
Any chance of double tap to wake up (unless its already included and i cant find it).
[ONE Original Android Development] buzzqw:
check "Advanced"

btw.. any hope for "quick boot mode ?"

BHH
[ONE Original Android Development] rippernz:
got it, thanks :D
[ONE Original Android Development] samstone86:
Does the 20141014 work ? If not wait for next build ... There are some issues with the build server
[ONE Original Android Development] buzzqw:
the 14/10 isn't ready to download yet

BHH
[ONE Original Android Development] Setting.Out:
I had zero issue, except when I accidentally froze the keyguard.. lol. I think the issue is with kernel comparability in multi-rom twrp.. This kernel doesn't seem to play nice with other custom kernels, but on regular twrp it boots fine for me...
[ONE Original Android Development] DespairFactor:
I am building a kernel for this using SM4.9.2 toolchain. I am currently looking for testers;)
[ONE Original Android Development] Deadpool253:
Good luck in your studies. I need something stable so it's on to the next one I guess.
[ONE Original Android Development] scanno:
Did you make any modifications to the kernel to make it build with the SM 4.9 tool chain?

Verstuurd vanaf mijn A0001 met Tapatalk
[ONE Original Android Development] DespairFactor:
Yes, I am currently adding more features, I have a test build up with just the new toolchain being used.
[ONE Original Android Development] Heisenberg:
Why are you dodging the question about why the device is incorrectly named?? You've been asked several times now.

Transmitted via Bacon
[ONE Original Android Development] Coug76:
I think it was an OmniROM leadership call. IIRC Entropy512 didn't have much good to say about the device. Could it stem from baggage?

Why is it so important?
[ONE Original Android Development] TheShoxter:
It's because this isn't a bacon build. It's a Find 7 build. It just works on bacon as well.
[ONE Original Android Development] Heisenberg:
Do I really need to explain why naming a device correctly is important?

Transmitted via Bacon
[ONE Original Android Development] Setting.Out:
Link.. ;)
[ONE Original Android Development] TheShoxter:
Check this. He'll update new link soon. http://xdaforums.com/showthread.php?p=56020845
[ONE Original Android Development] infrag:
Some people have OCD :cyclops:
[ONE Original Android Development] samstone86:
Like written under your post ... Its a internal thing I ask for next version of android to rename it ..
[ONE Original Android Development] samstone86:
The build on the server doesnt look good for 20141015 build but ill try it out when its done ... Please stay on 20141012 build until i wrote if its working or not.
[ONE Original Android Development] samstone86:
The next build should work again (20141016) ... We hope it
[ONE Original Android Development] :
What was wrong with 10/15 build?
[ONE Original Android Development] samstone86:
There is something failed during creating the boot.img file on the buildserver
[ONE Original Android Development] samstone86:
20141016 should be good :)
[ONE Original Android Development] maxwen:
its back working on find7 so its expected also to be fine on find7op when it arrieves
[ONE Original Android Development] :
Just confirming 10/16 works.
[ONE Original Android Development] indian84:
Flashed 20141016.. Super smooth.. Its my first time on Omni on any device...
[ONE Original Android Development] NexusPenguin:
Hi,

Coming from another ROM I clean installed the 20141016 .zip of OminROM.

All I can say is : "NOGO"...

Phone remains on the "One+" screen :(

Regards.
[ONE Original Android Development] CWick4141:
You did something wrong on your end then.. Check md5..redownload.. Did you try to flash Franco or AK kernel cuz neither will work.. Build is running perfectly fine for me and others
[ONE Original Android Development] NexusPenguin:
Hi,

I might have done something wrong on my end cause I tried several other build, and NONE works.

Maybe it's recovery related ? I use Philz...

And NO, I did not install any kernel. And even if... installing the new ROM will wipe the kernel and reinstall it anyways...

The really weird thing is, the ROM installs in about 6 seconds. I know the process isn't long, but that seems really short !

Regards.
[ONE Original Android Development] Setting.Out:
Did you flash a custom kernel?.. This rom only can use 1 custom currently (Sensei), others will make it not boot.. Also it could be your recovery..
[ONE Original Android Development] NexusPenguin:
Hi,

Please see my above post.

KERNEL is irrelevant : flashing the ROM will flash the kernel. And I did not managed to reboot...

Did a FULL wipe of everything... so no more kernel whatsoever...

Regards.
[ONE Original Android Development] Setting.Out:
Please read my full post, I also mentioned your recovery.. ;)

As you failed to mention your steps, I was thoroughly covering possibilities.. I have no issues with (unofficial) TWRP 2.8.0.1.. Try another recovery, or check that your download is not corrupt/incomplete..
[ONE Original Android Development] NexusPenguin:
Hi,

Thanks for your help... but trying to flash this has simply bricked my phone. Not unrecoverable... but will be a mess to do.

I think that's nothing to do with the ROM itself.

It's just the timing... flash at the wrong time.

Now,I can reboot into recovery, but each ROM goes to the end of the boot process and then reboots immediatly.

Tried with SlimKAT and Liquid.

I swapped recoeveries.

No luck either.

I reinstalled Cyanogen from scratch.

Boots but gives a "AudioFX has stopped" that pops up rending the phone unusable.

So I now have to remove the app I guess and will have to follow a tutorial todo it...

Regards.
[ONE Original Android Development] Setting.Out:
Hopefully, you have a backup.. It's saved me a few times, as only with this phone, I've had similar issues when flashing..
[ONE Original Android Development] samstone86:
Please use TWRP RECOVERY link is in OP post