yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] Renosh:
You have to decide for yourself by checking the Themes and Apps section for this device.

Go to developer options>system UI tuner
[ONE Original Android Development] samaritan16:
Thanks!
[ONE Original Android Development] hellcat50:
Omni ROM has some problems with my panel. Everytime I activate my screen it has 1-2 or 3 frames of glitched screen (like when you don't have a signal on a tv, those white-grey screen)

I have this panel:

<6>[ 0.297763] mdss_dsi_panel_init: Panel Name = LG R63315 1080p cmd mode dsi panel
[ONE Original Android Development] :
Can you share the zip you are using, none of the ones I've flashed seem to make a difference.

Nope, hasn't been merged yet, and I'm not going to do a build in my old PC just for that I'm just grateful he took the time to submit a fix.
[ONE Original Android Development] turdbogls:
It's decent...color OS and camera next are better and faster IMO
[ONE Original Android Development] Renosh:
Did you change the SE Linux to permissive? I remember that being a requirement. One of the reasons I don't use it
[ONE Original Android Development] :
Actually, I had read that it was no longer necessary. Though I may be wrong.
[ONE Original Android Development] Renosh:
Definitely wrong there's never been any updates to V4A since KitKat days so the same requirements persist. So switch to permissive, enable module and reboot then test again, it should work
[ONE Original Android Development] :
This is what I'm referring to,

http://xdaforums.com/showpost.php?p=62086581&postcount=2359

http://xdaforums.com/google-nexus-5/development/viper4android-mmb29s-cm-13-0-cm-13-0-caf-t3289340

http://xdaforums.com/note-4-tmobile/general/viper4android-stock-kernel-easy-steps-t3130806

http://xdaforums.com/google-nexus-5/themes-apps/discussion-viper4android-t2543796

Though these are all for other devices, maybe that is the issue.

But I honestly don't care is SELinux is set to permissive/enforcing, so I will just change it. Thanks!!
[ONE Original Android Development] deepaklunked:
[MENTION=5972963]Renosh[/MENTION] is right. You must change SELinux to permissive using SELinux changer from XDA, and then flash lolliviper zip from nexus 5 forums. Both can be obtained from google..
[ONE Original Android Development] webore:
Hi everyone, can you successfully flash the new zip via opendelta ?

I just get a fail to sysMapfile error .

This also happened when I was on omni official lollipop nightlies.

The log is here :

twrp version : 2.8.7.0

I:operation_start: 'OpenRecoveryScript'

I:Script file found: '/cache/recovery/openrecoveryscript'

I:Copying file /cache/recovery/openrecoveryscript to /tmp/openrecoveryscript

Processing OpenRecoveryScript file...

I:command is: 'set'

I:value is: 'tw_signed_zip_verify 0'

Setting 'tw_signed_zip_verify' to '0'

I:command is: 'install'

I:value is: 'OpenDelta/omni-6.0.1-20160127-find7op-NIGHTLY.zip'

I:Trying to find zip 'OpenDelta/omni-6.0.1-20160127-find7op-NIGHTLY.zip' on '/data/media/0'...

I:Looking for zip at '/omni-6.0.1-20160127-find7op-NIGHTLY.zip'

I:Looking for zip at '/data/media/0/omni-6.0.1-20160127-find7op-NIGHTLY.zip'

Unable to locate zip file 'OpenDelta/omni-6.0.1-20160127-find7op-NIGHTLY.zip'.

Installing 'OpenDelta/omni-6.0.1-20160127-find7op-NIGHTLY.zip'...

Checking for MD5 file...

Skipping MD5 check: no MD5 file found

sysutil: Unable to open 'OpenDelta/omni-6.0.1-20160127-find7op-NIGHTLY.zip': No such file or directory

E:Failed to sysMapFile 'OpenDelta/omni-6.0.1-20160127-find7op-NIGHTLY.zip'

E:Error installing zip file 'OpenDelta/omni-6.0.1-20160127-find7op-NIGHTLY.zip'

Done processing script file
[ONE Original Android Development] photobix:
Yes!

Today, I did the update via OTA without any problem.

TWRP from 20160101
[ONE Original Android Development] Renosh:
Yes did an update this morning using TWRP 2.8.6.0

Check Settings>More>Other

There's a new option if you manage to upgrade to latest build
[ONE Original Android Development] `SBR`:
Sorry if it's offtopic, is anyone successfully rooted in multirom. Evrytime flash the latest supersu 2.66/7 it failed.

ROM is working in multirom, only problem with flashing supersu.
[ONE Original Android Development] :
Do you have a folder named OpenDelta in the root of your SD card, and is the nightly zip in it?
[ONE Original Android Development] maxwen:
How should we know? ?

Hardslog needs to answer this. I won't merge it just to try ?
[ONE Original Android Development] scanno:
Lol, there are some people that make homebuilds themselves :)
[ONE Original Android Development] :
The column settings were already available on the 26th build.
[ONE Original Android Development] baddelay:
Without permissive didn't work here. But after changing that, flashing viperlolli and installing the drivers viper4android is running. Let's see how it works.

Thanks for the hints.

---------- Post added at 07:41 PM ---------- Previous post was at 07:38 PM ----------

I have read that after flashing another nightly v4a should still be available because off some scripts. That would be fine.
[ONE Original Android Development] :
I'll see if I can manage to build it and report back.
[ONE Original Android Development] baddelay:
Should I change the permissive thing back after installing? Enforcing?

And most important: Please bring back the circle battery status. :D
[ONE Original Android Development] Renosh:
Look for SE Linux changer app (not in play store). You'll have to make sure its set to permissive after every update or reboot else it won't be working. You can put V4A and SuperSU in the OpenDelta > FlashAfterUpdate folder so they're always flashed with deltas automatically
[ONE Original Android Development] scanno:
You can also use:

- setenforce 0 (permissive) or

- setenforce 1 (enforcing)

As root on a command line
[ONE Original Android Development] baddelay:
So now that v4a is working, should I switch back to enforcing? And only for flashing a new nightly using permissive?

The 'FlashAfterUpdate' sub-folder doesn't exist in my OpenDelta folder. Is it ok to create it by myself?

EDIT: Worked very well. Only question left: Should I switch to enforcing after a nightly flash?
[ONE Original Android Development] HJerem:
Stuck in boot

Can't succeed to boot into OmniROM, I don't know what I'm doing wrong. Tried with latest nightly, SuperSU 2.66 and latest OpenGAPPS....
[ONE Original Android Development] :
Where you coming from CM13? Maybe you need a newer firmware?
[ONE Original Android Development] HJerem:
Came from latest official COS12, so yeah maybe, what do you suggest ? CM13?
[ONE Original Android Development] :
Flash the latest CM nightly, after that wipe system and flash Omni. Maybe you are lucky.
[ONE Original Android Development] Renosh:
Seems COS12.1.1 does something that screws things up when attempting to flash from it to Omni. Try flashing CM13 it might work but I don't think it has anything to do with the firmware

Did you fastboot flash COS12.1.1?
[ONE Original Android Development] HJerem:
Wipe system only ?

---------- Post added at 10:42 PM ---------- Previous post was at 10:39 PM ----------

Yes I did
[ONE Original Android Development] deepaklunked:
Not necessary

Let it be permissive.
[ONE Original Android Development] Renosh:
That's the issue it seems. You'll have to download COS12.1 (YOG4PAS3JL or earlier COS12) fastboot zip and do this command to wipe the internal storage:

fastboot flash userdata userdata_64G.img

use the userdata_64G from an older build not COS12.1.1

Make sure you backup all your data to a PC first and copy them back later. I think CM did something on latest fastboot images that's screwing things up.

You should be able to boot Omni and other AOSP based ROMs then after a full wipe & install
[ONE Original Android Development] RajRockyBalboa:
Ambient display does not work for me on this rom...Can anyone test the same?
[ONE Original Android Development] HJerem:
So :

1. fastboot zip COS12.1 YOG4PAS3JL

2.

fastboot flash userdata userdata_64G.img

(where do I find this?)

3. Flash TWRP 2.8.6.0

4. Flash Omni + Open GApps + SuperSU 2.67 ?
[ONE Original Android Development] Renosh:
1. Backup up data to PC

2. Fastboot COS12 from http://xdaforums.com/showthread.php?t=2906746

3. Flash TWRP 2.8.6.0

4. TWRP Backup COS12

5. Wipe system, data, dalvik & cache

5. Flash Omni + Open GAPPS + SuperSU
[ONE Original Android Development] HJerem:
I fastboot which version of COS12 ?
[ONE Original Android Development] Renosh:
Any of the YOG4 COS12.1 Versions
[ONE Original Android Development] HJerem:
Thanks, do I need to reboot to COS12 before flashing Omni ?

---------- Post added at 07:21 AM ---------- Previous post was at 06:39 AM ----------

Well it's working but rotation doesn't work...
[ONE Original Android Development] Renosh:
That's probably a firmware issue you'll need a different one.
[ONE Original Android Development] HJerem:
Any idea which one ? I'm tired of flashing again and again... :(
[ONE Original Android Development] Renosh:
You can try the 241 or c7-00011 (01/25)

http://xdaforums.com/showthread.php?t=3300907
[ONE Original Android Development] HJerem:
Still not working, it's driving me crazy.
[ONE Original Android Development] indian84:
I have a suggestion for you. If you don't mind spending few mins with your phone and PC.

Flash Oxygen OS 2.1.4 using Stock OP Recovery. Search OnePlus Forums for the instructions.

Boot OxygenOS and then Use Latest TWRP to flash the ROM. That should work. I had similar issues and that's the only way I could get Omni or Omni based ROM to Boot and work without issues.
[ONE Original Android Development] HJerem:
Well, I'll will give a try after I return to stock my OPO.

Can you please tell me the best TWRP version ?
[ONE Original Android Development] Bobbi lim:
Either use official TWRP 2.8.6.0 or Materialized TWRP 2.8.7.0.5
[ONE Original Android Development] indian84:
I am using the latest official TWRP. But I am not on this ROM. I am using SAOSP which is based on Omni.
[ONE Original Android Development] HJerem:
My OPO is bricked now... :(

Something goes wrong during official OxygenOS install process...
[ONE Original Android Development] Renosh:
[emoji32] how exactly did you manage that?
[ONE Original Android Development] indian84:
The process is pretty straight forward. Did you follow the steps properly?

Check this thread..

https://forums.oneplus.net/threads/oxygenos-2-1-4-for-the-oneplus-one.425544/
[ONE Original Android Development] HJerem:
Fixed now thanks to this.

Didn't see "**Instructions below assume you are currently running OxygenOS or COS12 and

above. For other systems, please contact our customer support. " I'm so ashamed ! :D

So now I return to stock COS12.1 and I will flash OxygenOS. If it doesn't work, I think I'm gonna stay with another ROM, so annoyed!
[ONE Original Android Development] Bobbi lim:
I don't think you hard brick it. Probably just a soft brick due to your negligence.
[ONE Original Android Development] zjxpot:
you still have that problem? haven't you realize that your problem is local, you have to follow the OPs instructions, you are posting as though the OMNI rom is not booting, it booting on all other phone except yours, so OPs don't have to fix anything, it you who have to fix everything on your phone..
[ONE Original Android Development] evertking:
sorry

But your YOU are wrong and Omni team is said to know about it and working on it. Its not just me. Anyway....
[ONE Original Android Development] :
Yes, running it right now, coming from herna's
[ONE Original Android Development] :
Had a FC with Chromium when setting it up, on a dirty flash, seems to have settled in.

What benefits does Chromium have over Chrome?

Thanks for your work.
[ONE Original Android Development] wozn:
Awesome to go official, though herna's builds have been great. Thanks for Chromium, I for one would love to see it continue into the future builds,

Open source all the way where we can.

Worked well on clean flash.
[ONE Original Android Development] Vintage144:
I just dirty flashed and alls well
[ONE Original Android Development] webore:
well I will try and report later .
[ONE Original Android Development] stryker09:
Dirty flashed from herna's ROM and happy to say no issues. Chromium doesn't seem to be picking up existing Google accounts though.
[ONE Original Android Development] indian84:
Did anyone try manually switching network modes? If you switch to 2G within network settings, will it stick?
[ONE Original Android Development] david72262:
Took some work but i got it to work eventually deleted its data 3 times and enabled all its app permisions.
[ONE Original Android Development] ludskyrider:
Does this rom run splitview?
[ONE Original Android Development] Renosh:
Its the same on this ROM too, cannot change network, best way to test is to use *#*#4636#*#* switch from there no response whatsoever. In Settings>More>Cellular networks>Preferred network type it changes the text but if you check in Sim status it doesn't actually do anything. Try using that code and attempt to change. It's pretty much the main issue left for the ROM to be stable in my opinion
[ONE Original Android Development] pa1281:
Has launcher setting fc been fixed in the official build? How different is it from herna's build?
[ONE Original Android Development] imam.krismanto:
This ROM already support manual focus with oppo camera?
[ONE Original Android Development] matalon:
Smooth as butter. Loving OMNIRom
[ONE Original Android Development] Lisko:
Recording 4k videos with that camera doesn't work,any fix?
[ONE Original Android Development] kisman72:
No, not at me...
[ONE Original Android Development] :
Just go in to the app's settings, permission and enable contact access.
[ONE Original Android Development] HJerem:
My OPO wasn't booting at all...

So I return my OPO to stock COS12.1, then I followed official instructions for flashing OxygenOS 2.1.4

I flashed recovery TWRP Materialised 2.8.7.0.5. and then latest OmniRom build, and it's working fine (with sensors ok!).

Now I need to flash GApps and SuperSU, then I want to install Xposed Framework, is it recommended or not ?

I really don't want to mess everything...

Thanks for helping me :)
[ONE Original Android Development] Renosh:
You can install xposed but make sure its the latest version for Marshmallow, I think it should be v79 sdk23 arm zip (there might be a newer version but I don't use it). Search xda you'll find everything you need saves having to wait for answers from us. Make sure you use SuperSU 2.67
[ONE Original Android Development] Bobbi lim:
When your OPO wasn't booting, there's nothing on the screen or it's stuck on a screen showing something?

I wouldn't recommend you to flash Xposed straight away. Flash Omni ROM + Gapps + SuperSU for a few days or a week.

Play around and enjoy yourself before flashing Xposed so that you can familiarise yourself with the phone in case anything were to be messed up, you know how to fix them rather than going into panic mode straight away :)
[ONE Original Android Development] Renosh:
The Unbrick guide won't work unless you've properly bricked your phone and the screen is black and phone is completely unresponsive. Only response you'll get is if you fiddle around with power button and connect USB to PC it shows QHSUSB_Bulk in Device Manager.

Easiest way to replicate this is to use the flashall.bat from EddyOS in General section for fastboot flashing CM11S. He should really take those links down [emoji15] . It will guaranteed brick your phone
[ONE Original Android Development] Bobbi lim:
I've bricked my OPO a few times already in less than a year I brought it. I messed with the partitions and ended up having the phone behaving like a USB drive of 64GB and a lot of other stuff.

But my point is, he mention this "My OPO wasn't booting at all..." which doesn't signify anything. Whether the phone hang on boot OR it's totally bricked.
[ONE Original Android Development] cyril279:
He in-directly defined his brick-level by the method that he used to recover the device. Although he did not describe the phone's degree of impairment, the recovery method that he linked to in his post only works on a hardware bricked phone. Which, admittedly, isn't apparent until you click the link and read the OP.
[ONE Original Android Development] batwingnz:
I've just done a clean flash of the 28 Jan nightly. Notification shade doesn't show notifications and cannot get quick settings at all either, only back button works, home and menu vibrate and do nothing. When I turn soft keys on still only back button works.

I've flashed roms hundreds of times and never managed to end up with something like this before. Not sure what to do next!

I've checked permissions and everything is allowed to notify but I'm also not getting notifications, the phone vibrates but nothing shows in status bar.

I've no option to turn sync on for gmail or calendar, but inbox sync is available and turned. Full permissions for all three though.
[ONE Original Android Development] maxwen:
You have not flashed any gapps
[ONE Original Android Development] batwingnz:
Aka a few too many knocks to the head ;)
[ONE Original Android Development] Mt_cz:
Sometimes I turn on the screen but I cannot unlock. I cannot control the screen. It gives a wrong response. The only solution is to force power off. And this problem only appears on omni rom (6.0). Kernel: stock.
[ONE Original Android Development] webore:
I had this problem too . It happened twice yesterday ,the 0128 build .

But I didn't report that ,because I use xposed.
[ONE Original Android Development] Mt_cz:
But I don't use xposed at all.
[ONE Original Android Development] praveen7682:
I have been using this ROM for last 3 days..the rom feels great..I havent faced any major issues..I get 6.30 hrs sot with 16 hrs standby time..I just changed the governor to Smartmax and reduced the frequency to 1958...I would like to understand is it good or bad..but I could see WIFI draining baterry a lot..I deactivated WiFi scanning and changed location frequency to low but still I could see WiFi is 8hrs in the list..
[ONE Original Android Development] :
I use xposed, no issue.
[ONE Original Android Development] webore:
I'm still facing the fail to map file issue with twrp when I choose Flash in opendelta.

Screenshot :

http://imgur.com/C48MrvD

The log of recovery:

http://pastebin.com/CiLFSDa7

It's really annoying .

I have to install updates manually.

Anyone can help ?
[ONE Original Android Development] maxwen:
Logcat when you do check for updates and download or build - so before flashing
[ONE Original Android Development] Galactus:
Does encryption work or is it borked? I tried last night, battery at 100% and charger plugged in. Left it for 2 hours whilst I played Destiny then just rebooted figuring I 'd need to start my device from scratch. Rebooted fine, which tells me if wasn't actually doing anything the whole time?
[ONE Original Android Development] scormax:
how is it comparing to latest cm13 nightlies... are there major bugs or random reboots or any battery drains? any specific gapps or opengapps will do?? thnx
[ONE Original Android Development] DerRomtester:
flash it and you will know that (:
[ONE Original Android Development] erikieperikie:
For the record...

I've encountered a problem and its solution.

When I went into Settings->Advanced, the Settings app crashed. After thinking for a while I found that I had disabled the ‘Advanced’ app that came pre-installed as a system app with this ROM; I froze it using Titanium Backup. I often do this with apps I know or suspect I don't need. Freezing them can break a lot, but often not too much to undo again. It is better than immediately uninstalling a system component.

To fix it:

I defrosted the app again and things went back to normal again! I did have to go into Settings->Advanced and disable all check marks, reboot, back to the settings and enable them before they worked again.

I hope I helped anybody who encounters this problem.

---------- Post added at 05:22 PM ---------- Previous post was at 05:20 PM ----------

I used the Open GApps nano package.
[ONE Original Android Development] Renosh:
Rock stable and good battery life. Don't expect the same features as CM13 its a great ROM with some nice additions. Use Opengapps
[ONE Original Android Development] maxwen:
No - don't use opengapps!

Only use banks

---------- Post added at 05:53 PM ---------- Previous post was at 05:52 PM ----------

Logcat or GTFO
[ONE Original Android Development] :
I'm using Opengapps and have not had issues.

But if you say so, I will move to banks gapps from now on.
[ONE Original Android Development] maxwen:
Don't change if it works

But consider before reporting issues that are gapps related ?
[ONE Original Android Development] Renosh:
I'll definitely consider it if I get issues but only ROM I've ever had issues with related to gapps is Dirty Unicorn. It only boots with banks gapps for some reason
[ONE Original Android Development] erikieperikie:
Why? I've used the Open GApps nano package without any problems, the few included features work. What are the differences between the various GApps packages that can be found throughout the interwebz? Why are BaNkS' GApps recommended/necessary? I thought the Open GApps were made to satisfy all tastes and flavours.
[ONE Original Android Development] maxwen:
LOL - I have answered this already

Just don't use opengapps if you report problems.
[ONE Original Android Development] Akath19:
Open GApps needs a certain commit to be added to the ROM in order for the setup wizard (and other apps) to work.

Not all ROM developers consider that a good practice, that's the reason some of them suggest banks or slim gapps.
[ONE Original Android Development] joefso:
In addition, cm has integrated this into their roms, most AOSP rom devs havve not
[ONE Original Android Development] ArobeeTV:
So, I just flashed this ROM with the BaNkS dynamic gapps and SuperSU 2.65, wiped dalvik/cache, rebooted, and it's been sitting showing the boot animation for over 20 minutes now. I did do a full wipe and everything as I normally would with any other ROM. Is there any reason it should be taking this long?
[ONE Original Android Development] indian84:
I guess you need to use SuperSU 2.67 Beta.
[ONE Original Android Development] Binford6000:
I'm using 2.65 stable version and everything works fine. At first I pressed install root because I didn't see the hint during the installation, but in the 2nd try it works

Gesendet von meinem FIND7 mit Tapatalk
[ONE Original Android Development] indian84:
OK> Glad you got it working. Sometimes we get complacent and do not read on-screen instructions properly. :P
[ONE Original Android Development] Binford6000:
Good morning gentlemen,

first of all I woukd like to say thank you for your hard work and sharing this ROM with us. It is realy impressive. Searching for customisation stuff is not recommended at the moment, cause ther are only some minor possibilities due we are in nightlies? Doesn't matter because my battery is alive and alive and alive.. ?

Thanks a lot. I was in many harbors but now I think I'm at home.

I red some pages before one of us is using XPOSED. Do you recommend to not use it? Because it is a big hack to Android.

Kind regards

Binford

Gesendet von meinem FIND7 mit Tapatalk
[ONE Original Android Development] indian84:
Xposed should not be a problem if you know what you are doing. But the devs have mentioned not to report any bugs when you have Xposed flashed. Enjoy.
[ONE Original Android Development] maxwen:
No idea what you want to say with this but please notice that omni is not one those "we cherry-pick **** x or **** y from ROM a or ROM b because ROM c has it" projects. so just dont ask about such things ☺ omni is a developers project and developers dont like to cherry-pick
[ONE Original Android Development] ArobeeTV:
I've also been doing everything exactly as it's been laid out in the OP, saying OH HELLS NO when TWRP asks if I want to install root, etc. Still borked.
[ONE Original Android Development] maxwen:
install TWRP3 - it will no longer ask ?