yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] ZenR2:
thanks buddy fr the confirmation :)

hows the rom any serious issues still left as in call bug ??

where is the 31 build i can only see 30th build on op ??

https://www.androidfilehost.com/?fid=24052804347851085 is this the latest build ??
[ONE Original Android Development] tarun kambala:
will this work on oppo find 7
[ONE Original Android Development] ZenR2:
no no , its for oneplus one , u will end up bricking your device
[ONE Original Android Development] tarun kambala:
thanks
[ONE Original Android Development] Huntation:
While using the phone(not booting).

Im experiencing random black screens of death that can only be fixed by force rebooting.

I have searched the thread and found nothing, am I the only one experiencing this?

I have clean flashed and tried both slim gapps and banks gapps. How would I log this?

Hold the power button right after it happens and get last kmesg?
[ONE Original Android Development] Japseyz:
I, like many else are experiencing troubles with re-mapping the hardware keys.

I am a stubborn user of the HW keys and would prefer to use them over the Softkeys, any ETA on a fix?
[ONE Original Android Development] aznracer62:
Try going into developer settings and keep mobile data on.
[ONE Original Android Development] evronetwork:
It's in a good path, but still not as stable as I'd like to be, has some minor bugs one that probably most will know is if you press the 1st hardware key and open settings ...instant problem :P ..languages are not translated 100%(put my language and some are English some are in my language heh) and manage to get a couple more minor ..nothing major, still prefer to have a more stable OS as daily driver and have one language not English and partially translated Greek. Still as said good one and I believe it will become better - didn't have the time to check how's the battery as I use the rom for less than 3 hours.

Restore my nandroid backup and I got a nice surprise... lost IMEI smooth :P ..I do have modem files as I'm a careful guy but didn't need them, flash CM nightlies and then restore my nandroid backup(which is based on cm-check sig) and everything went back as it was

P.S. I love a feature that it's in the devs option(probably a cm thing), termination if you hold back for a while ...when some app freezes or goes SO SO slow and you want a fast way to shut it down(not just leave it running in the backround), you press the back and hold and after a couple of secs ..terminated!! I love this, just love it..
[ONE Original Android Development] NoobInToto:
You using multirom? I experienced sod even when I didn't have a vsecondary rom. This was on another rom. Clean flashing solved the issue.

[MENTION=2225255]herna[/MENTION] is the buttons menu being added in next build?
[ONE Original Android Development] Huntation:
Yeah I have this rom as primary right now with 1 secondary 5.1.1 rom, so with clean flash you suggest removing multirom and clean flashing again?
[ONE Original Android Development] CoBfan1987:
Thank you to the 1 or 2 people that said to turn off Wifi by searching in settings "scan". Then disabling Wi-fi scanning and Bluetooth scanning. Wifi was draining my battery all day even with it shut off, this fixed the issue :) Thank you again to the 1 or 2 people that suggested it.

Also, I found that by doing a setting search for "button" that it brings up the old options for changing nav buttons. This easily enables nav bar and you can turn off the lights (but the buttons still remain active) for capacitive buttons. Unfortunately none of the button remapping functions work yet but I know that is already know. Just was disappointed after finding that and then they didn't work :P No worries, definitely stable enough for my DD for the last few days.

Also I was getting fairly lousy service on T-MO the last few days and when I checked the APN it only had T-MO's IPv6 APN, not the standard IPv4 one. So I manually added that in and service seems to be much better now for any one else that might be having the same problem.

Loving the development so far and can't wait to see what the next few builds will bring.
[ONE Original Android Development] NoobInToto:
By clean flash,I meant wiping system and in the process,wiping multirom completely. Backup that secondary rom first.

Do clean flash(wipe system, data,cache and dalvil cache).

Flash omnirom+ gapps(preferably banks dynamic gapps (link in op)) and SuperSU 2.52(for tibu and whatnot)

Restore your stuff.

Check if sod occurs. If it doesn't, you have 2 options:

1. Give up the secondary rom and live without multirom: if you are keen on staying on this rom.

2.Leave this rom if you cannot afford to lose multirom.

BTW how are you using multirom on this? This rom doesn't support custom kernels! It doesn't have kexec hardboot patch either... So my guess is you are on ak kernel which is causing all your issues.
[ONE Original Android Development] Huntation:
Wait, /system wipe wipes multirom? I always clean flash including /system and multirom is still there. Do i have to uncheck the "inject multirom" checkbox ?

Oh and my secondary rom has kernel with kexec so if i want to use it, i just swap the secondary with internal. Not really efficient but it works.

Edit: I have ak on my secondary rom, that doesnt do anything does it?
[ONE Original Android Development] NoobInToto:
Yeah,uncheck inject multirom. It's by default unchecked for me lol.

Forget ak and stuff.

Just try the rom without multirom, just to confirm if its multirom issue :)
[ONE Original Android Development] hasnol143:
Wait how did you lose IMEI? doesn't make sense if you're just restoring a backup
[ONE Original Android Development] codyedmonson:
EFS partitions are funny things, they can get corrupted over the smallest things.
[ONE Original Android Development] hasnol143:
Well then, good thing I have them backed up
[ONE Original Android Development] SchmilK:
I'm using an app from playstore "device id changer free"

Take note of your old device id when titanium opens, then use that app to change it. Sat there for about a minute after I submitted the change then it was good.

It also stayed as is after dirty flash.
[ONE Original Android Development] alebcay:
Dealing with a new issue on the 11/03 build: I used to be able to manually disable the hardkeys (capacitive) by setting /sys/class/leds/button-backlight/brightness and /sys/class/leds/button-backlight/max_brightness both to 0. After updating, the changes I make in those two files get re-written to their default values on every reboot.
[ONE Original Android Development] SchmilK:
I have the same problem, seems less bad after enabling data mode, restoring device id, setting APN to the lwaactivation or what ever, let it sit until your bars are full, then go airplane mode, change back to att phone, urn off airplane mode, then I can get and reply group mms. After a few hours of doze, I need to activate airplane on and off then good for a while again.

Before doing all that I'd have to go airplane mode for every message.

---------- Post added at 08:26 PM ---------- Previous post was at 08:23 PM ----------

DO NOT restore modem on point 7 twrp backup. I lost IMEI that way and had to manually flash.
[ONE Original Android Development] erad1:
Wasn't sure if it's in this thread that I read custom kernels don't work, but just the same, has anyone wanting multi-ROM tried varund7726's cm13 kernel, which has kexec hardboot support?
[ONE Original Android Development] Huntation:
Ok I have done what you said, and so far, no SOD yet. It has been 40 mins or so, and before I would get SODS roughly every half hour. I'll let you know if I get one, but so far it seems like the issue is resolved.

Thanks man ;)
[ONE Original Android Development] NoobInToto:
Hope it stays that way. I did the same and I'm sod free :)

Multirom can be buggy sometimes. If you are interested in a fix, you should contact kingbabasula.

---------- Post added at 02:49 AM ---------- Previous post was at 02:46 AM ----------

No use of backing up efs when wrong modem will mess up imei/persist .

If you ever lose imei/Mac address, use twrp 2.8.6 since twrp 2.8.7 will not flash modems properly. Learnt it the hard way :D
[ONE Original Android Development] hasnol143:
I have actually been using materalised TWRP 2.8.7.0-04 (https://forums.oneplus.net/threads/materialised-twrp-for-oneplus-one.305017/) the OP specifically fixed the issue for 2.8.7.0 not flashing modems properly in his build. Works like a dream for me and has the most updated TWRP.
[ONE Original Android Development] NoobInToto:
Yes that twrp works fine too. I've used it too.
[ONE Original Android Development] SchmilK:
[MENTION=2225255]herna[/MENTION] 11/03 build is fantastic!

3 of those hours of screen time is streaming neyflix on the train!

http://imgur.com/PiHEbTO
[ONE Original Android Development] herna:
Hello guys! As always, new build is available with the next changelog:

* Fixed MAC Address : No more random MAC addresses, as well as probably less Wi-Fi drain.

* Modified panels with Oxygen OS stuff: added some stuff from Oxygen OS for improving smoothness and other minor stuff.

* Fixed statusbar silent icon: no more double icon when the phone is in only alarms option.

* Updated default wallpaper: added one wallpaper I want to add as default for Omni(waiting your comments about it).

* Updated icon for Snapdragon Camera: made by me with a friend collaboration.

Download link at OP!

Enjoy!
[ONE Original Android Development] KenjiHannya:
Omni is the best ?
[ONE Original Android Development] Sayed Khadri:
Thanks for another build.. Anyway to configure hardware buttons to now on tap?
[ONE Original Android Development] LLStarks:
Car bluetooth is weird. I don't have call audio until a good few seconds after I expect it.
[ONE Original Android Development] codyedmonson:
I can't get this to boot for some reason, I flashed the recommended twrp and it boots and gets stuck at the 1+ logo
[ONE Original Android Development] ZenR2:
woh woh woh , another build your so fast in solving and sorting out bugs , hats of t you respect man :)

I prefer snapdragon camera if it can be improved just as you said :)

The only things missing from this Rom is

-- Double tap on status bar/home key to turn off screen ( or any other workaround , just don't wanna mess up with the physical button to turn the screen off :D

-- Custom button actions

-- Custom DPI ( can be achieved through build.pro ) still an option would have been good (just a suggestion )

will update this build and report soon thanks :)

---------- Post added at 09:41 AM ---------- Previous post was at 09:39 AM ----------

It takes a bit of a time to boot say 10-15 mins some users reported more then 20 mins so just wait it will boot for sure :)
[ONE Original Android Development] shail139:
There r two 4-11 build, which one to go for ?
[ONE Original Android Development] _ASSASSIN_:
go use a different ROM or use xposed when it comes out, because the features you see here, give or take a few, has been what Omni is about since JB

(HW binding, however, will come soon)
[ONE Original Android Development] codyedmonson:
Thanks for the info, I hard bricked my 1+1 before trying to install this rom, turns out I used the wrong twrp and well... boom goes the dynamite. There's a workaround for your custom buttons. Download and install this app from the play store https://goo.gl/8tld53 The rest is self explanatory. Let me know if it works out for you. I havent been able to get this version of M to boot but on the others it works flawlessly as a temporary work-around.

EDIT: What is the process you do to install this rom? I mean, flash the rom zip, then gapps then supersu? or rom, supersu, reboot then gapps? I'm unsure on the install order and "Tricks"
[ONE Original Android Development] david72262:
Thanks for the new build. Dirty flashes just fine.
[ONE Original Android Development] ZenR2:
Go and mess with someone else , and don't try to be an unknown/unwanted guest no one asked or your opinion or suggestions ,

that was just a general statement , I didint asked for those features, just mentioned it because the Rom is so dam perfect that I only miss those nothing else ,

so before saying anything to others try to give some respect to others everyone is free to express there own views
[ONE Original Android Development] _ASSASSIN_:
I'm just saying that I've seen Omni develop for 2 years, nothing much has changed in feature set. Not to mention the features you want can be done by apps/xposed/build.prop edits.

I'm not here to pick a fight, I really don't know why you have to reply with such aggression.
[ONE Original Android Development] ZenR2:
Thanks buddy will surely give that app a try :)

Process :

1 make a backup

2 wipe data,system, cache, dalvik

3 intsall Rom

4 gapps ( banks/benzo)

5 supesr su

wipe cache/dalvik

reboot

wait fr say 5-20 mins :P

---------- Post added at 10:00 AM ---------- Previous post was at 09:54 AM ----------

"go use a different ROM or use xposed when it comes out"

wasnt that a rude way to say . even am not here to fight , i was just expressing my views buddy i wasn't complaining or was against anyone ,

and as you said in your current post that those an be achieved in different ways i know that bro , but anyways lets stop it and keep this thread clean

no aggression no hard goings just stay Omni :good::D
[ONE Original Android Development] codyedmonson:
For your DPI issues, couldn't you edit the build.prop to make the dpi what you wanted it to be?
[ONE Original Android Development] webore:
OP said justonthis page .

One is with oxygen camera blob and the other oppo blob .
[ONE Original Android Development] threetwentyfizzle:
[MENTION=2225255]herna[/MENTION] can you look at the display panel drivers used for this ROM? Only reason im asking is because I have a Truly Panel, and am experiencing graphical glitches when turning the screen on(looks like white noise on a tv), and the panel flickering when displaying certain colors.

Ive had these same issues in the past on Sultan's CAF ROM, before he patched something in his kernel (im assuming display drivers) to make more compatible for the few other users that have the same LCD panel as me.

But man, is this rom smoooth and snappy!

Edit: didn't see that you posted another update, i was referring to yesterdays build (11/3) I will try out the new build and see if it helps with my display panel glitches. Thanks for providing us with this ROM, definitely loving it otherwise! [emoji3] [emoji106] [emoji106]
[ONE Original Android Development] drishd:
follow this procedure & it worked for me

I use TWRP Recovery

* Clean Dalvic, System , Data & cache.

** Flash the ROM, Gapps (SLIM or Banks Or any of ur choice)

*** Super SU 2.52 Zip

Then Reboot in to system.

1+ logo appears & after sometime phone swiches off.

Then Hold the power button till it vibrates, Now the phone starts, 1+ logo, then Omni boot animation appears.

Relax & sit for 5-10 mins, till setting (Language) appears.
[ONE Original Android Development] siddardha21:
Hey. Can just someone please tell me if now on tap works with capacitive buttons? I prefer using capacitive buttons to on-screen ones. Thank you!!
[ONE Original Android Development] ZenR2:
am doing it way only buddy , :) hope you succeeded in flashing the ROM :D
[ONE Original Android Development] drishd:
Not working 4 me.
[ONE Original Android Development] codyedmonson:
Still sitting on the 1+ logo, going to watch some youtube videos while I wait for it to boot. I ended up re-flashing because I thought I screwed something up. Will update when/if it boots.
[ONE Original Android Development] mankidavu:
Tried with multirom as secondary. Didn't boot.

Swapped internal rom with omni and it booted well.

Inbuilt browser FC while trying to download files. (gapps).

Installed supersu 2.5xx and Banks Gapps. Looks like a daily driver build at this stage. Thank you very much for releasing 6.0 based omni so fast.

Reboot from recovery doesn't boot the device.Many times, I have to long press power key and boot again. Not sure if it is a bug of TWRP+ omni combo.(using 2.8.6.x based modified TWRP of multirom)
[ONE Original Android Development] KenjiHannya:
Me too lol ???
[ONE Original Android Development] ZenR2:
Dirty flashed todays build then reboot from recovery,

And volla no more black screen no power button press :D it went on normally :D
[ONE Original Android Development] codyedmonson:
Been sitting for 35mins on the 1+ screen and nothing. Going to try and force reboot it a few times and see if it boots.
[ONE Original Android Development] ZenR2:
You waiting on the black screen or on one plus logo, if you see a black screen then you have to go for force reboot
[ONE Original Android Development] codyedmonson:
Waiting on the 1+ logo. Its been stuck here for 35 minutes. Am I doing something wrong? I flashed this straight after updating to COS12.1. What firmware are you on?
[ONE Original Android Development] shail139:
One more issue....Device not getting detected in MTP mode when connected through USB with USB debugging enabled/disabled, while on all other ROM this issue is not there

Anyone else having this issue.
[ONE Original Android Development] praveen7682:
I downloaded the coloros camera blob build and first i tried to dirty flash and stuck in omni logo for almost 30 mins and didnt boot..then i tried to clean flash and still the same issue..unfortunately couldnt boot the build..????..I am back to 0311 build..Will give it a tey again tonight..Thanks for sorting out issues quickly..Just a suggestion can you please update keyboard so that we cam fix the dictionary..
[ONE Original Android Development] mammenj:
Just flashed today's normal build, it's flawless for an experimental build. Trying it as DD.
[ONE Original Android Development] threetwentyfizzle:
Edit2: looks like my display is still flickering with certain gamuts, and the graphical glitch still occurs when the display turns on. Ive observed that it also glitches and flickers white noise upon bootup after the splash screen before the boot animation loads.

Hope any of this is helpful.
[ONE Original Android Development] ZenR2:
Try flashing latest cm nightly and then go for a fresh Omni install, just a suggestion, because 35 mims is way to long :o
[ONE Original Android Development] codyedmonson:
Thats what I meant, I updated from cm11s to cos12.1 them flashed latest cm12.1 nightly.
[ONE Original Android Development] Renosh:
Change the USB type from charging to MTP mode in the status bar. You'll see a prompt in the notifications panel when connected via cable do it there
[ONE Original Android Development] ZenR2:
which version of TWRP you are using, go for the latest one or the one in the OP

---------- Post added at 11:26 AM ---------- Previous post was at 11:25 AM ----------

hey buddy go with the oxygen os blob one that boots fine ..:)
[ONE Original Android Development] parker09:
Anyone having problems with the editing of the DPI, the navigation bar stays the same size as stock (480) even when I edit the build.prop and make the DPI 400 - and everything else changes as it should.
[ONE Original Android Development] shail139:
I know how to select, MTP

After that only I told its not detected.
[ONE Original Android Development] mankidavu:
It is becuase ,by default "charging only" option is enabled. Select MTP from the USB settings menu, to change it.

and that is an android 6.0 standard feature.

https://developer.android.com/about/versions/marshmallow/android-6.0-changes.html#behavior-usb
[ONE Original Android Development] :
New unmentioned bugs:

changing lock screen pin could make logging in impossible. first time it happened after an upgrade, factory reset didnt fix it. Second time a clean install it reoccured.

upgrade could cause gapps to not function. Fresh clean install to fix.

Been reported earlier: charging didn't work. No workaround known. Unless oxygen blobs require oxygen firmware. If that is the case it should have been mentioned before.

The black screen when booting can be fixed by clean install with the ops recommended recovery, other recoveries same twrp version number have me black screen. it can also be fixed by pressing power button till it reboots, then it boots fine.

Haven't tried encryption but noticed its not on by default even though Google requires it.

Battery life seems way better. Almost on September 2014 level. I account that to probably non working stuff. Would be awesome if m is actually the improvement l should have been
[ONE Original Android Development] Renosh:
It's a requirement for new phones that come out with 6.0 and whose hardware can meet certain performance targets. It's for OEM's not after market ROMs like Omni/Slim/CM etc. As well as devices that launched with Android versions prior to 6.0 are exempt
[ONE Original Android Development] 3rt41:
Thank you guys for this rom.

I know that this is app related, but i only have issues starting the facebook and messenger apps.

Other issue i have, i can't setup smart lock with my mi band, while i can with my lg urbane, no problem. The mi band works fine with any other scenario.

Doze seems to work and mobile active drain looks gone. While in standby tonight, the battery drain dropped faster for a while, then went back to normal doze mode drain. I don't know what actually happened but i will report.

Everything else is stable as far as i could take a look at, thank you for bringing android m to the opo.
[ONE Original Android Development] ghmail2:
Tank you herna.

I have a small issue to report. If i open the panorama mode in snapdragon camera,tue camera will fc,and you can not go back to other mode,every time you choose another mode(pic or video),camera will fc
[ONE Original Android Development] 3rt41:
Can i just dirty flash today's update over the clean installed rom? Thank you for your work!
[ONE Original Android Development] Sayed Khadri:
Yes you can, I just did everything working fine.

Recommended practice is to clean flash.
[ONE Original Android Development] NoobInToto:
I confirm this. Clearing app data is one workaround.
[ONE Original Android Development] ZenR2:
Don't forget to flash gapps
[ONE Original Android Development] Renosh:
[MENTION=2225255]herna[/MENTION]

Can you please comment on the network switching. I can't switch networks on M build, I switched to Omni 5.1.1 nightlies and I can change to 3G/LTE but not on these builds. Also if I want my APN settings included in future Omni builds what do you need?
[ONE Original Android Development] cossali98:
Hey guys,what about battery life ?
[ONE Original Android Development] jjrojo:
Try it your self please.
[ONE Original Android Development] Sayed Khadri:
Any suggestions how to map hardware home mey long press to open now on tap?

Really don't like on screen button, they eat up lot of space.

Tried All in kne gesture not working.
[ONE Original Android Development] pa.pn2:
Did not work for me

Google account was missing and yes i flashed gapps and rom. So i had to go clean. ****..
[ONE Original Android Development] mikel0679:
I'm using all in one gesture
[ONE Original Android Development] Sayed Khadri:
In All In One Gesture.. For Long press not getting search assistent selection..

How did you make it work?
[ONE Original Android Development] mikel0679:
home key/ long press / search / search key (long press)

It works for me
[ONE Original Android Development] Sayed Khadri:
For me it pops uo voice search, any specific settings you did?
[ONE Original Android Development] cossali98:
How is for you ? Sot ?
[ONE Original Android Development] Huntation:
Bad news, I woke up and the problem is back again. Do you think TRWP is the cause? I'm using the version he says that has problems.

I'm going to try the new build with the recovery he has linked and report back.
[ONE Original Android Development] NoobInToto:
Are you using banks dynamic gapps?
[ONE Original Android Development] bhatiagkb:
A bit of gaming, frequency set to 2Ghz, WiFi-3G 80-20, an hour of reading and the rest on social networks and forums. Not disappointed at all.