yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] solar666:
Almost the same for me. Can't confirm any problem with MRA here.
[ONE Android Development] fmc000:
Ok, maybe it was a false positive then. I rolled back to OmniBear and will perform other tests.

I'm beginning to suspect that the bug may be the other way around: stock kernel not reporting the mobile radio activity at all.
[ONE Android Development] indian84:
I was reading somewhere that Omni has a cosmetic fix for MRA.
[ONE Android Development] abhibnl:
Well not all my videos lag, but most of them do. The videos that work fine on Sultan's rom, stock CM13 and Slimsaber LP 5.1.1 CAF. So it must be this rom. That's why i asked F4uzan if he can suggest any fix or any log that i can provide. I'll try to make a video of it and will upload that.

Regarding MRA - I'm still seeing that in the battery stats but it's not as prominent as it was on CM 13. But this rom too has problem with the battery readings. The battery fell from 45% - 12% within seconds. i'll share the screenshots later.
[ONE Android Development] abhibnl:
Okay, so as promised, here's the ss from today' battery readings. Either it's MM or the most recent firmware. Can anybody else confirm the same behaviour if he/she is on the same firmware.

Sent from OnePlus One
[ONE Android Development] Natakranta:
Thanks! That solved the latest build clean flash package installer Force Close I was getting. As you said, I extracted packageinstaller.apk for previous build and pushed to current one location, check permissions and reboot.

Now I can install .apk's

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] indian84:
All right boys and girls, I am here to seek some help.

For some reason, I had to Fastboot Latest Cyanogen OS to my phone last night. After completing the process, I flashed TWRP and then flashed 23rd/24th Jan build. Now, I am unable to boot SAOSP. It remains on boot animation. As a matter of fact, I cannot boot any Onmi based ROMs. Tried official Omni and FusionJacks SlimSaber Omni. I tried flashing below firmwares using TWRP and fastboot.

1. bacon_firmware_update_2015_05-15_DI.3.0.c6-00241

2. bacon_firmware_update_2015_12-30_.4.0.1.c7-00011

3. bacon_firmware_update_2016_1-25_.4.0.1.c7-00011

Tried different TRWP versions official latest, and Unofficial materialized to flash the ROM too. I am on CM13 nightly at the moment. Any help would be highly appreciated..
[ONE Android Development] deepaklunked:
Try flashing older cyanogen os and then flashing S-AOSP..
[ONE Android Development] fmc000:
PackageInstaller working fine here, just tried it with the latest WhatsApp update from APKMirror.
[ONE Android Development] indian84:
I am going to flash Oxygen OS with Stock OP recovery. Will try and do something about getting back to SAOSP later when I am home. At work now.
[ONE Android Development] deepaklunked:
Sounds good. Just try and let us know.
[ONE Android Development] indian84:
Sure thing. Will report.
[ONE Android Development] Anghirrim:
Hey, when I first got my OPO (second hand), I fastboot flashed the following COS.

cm-12.1-YOG4PAS3JL-bacon-signed-fastboot.zip

Then never had any issue with Omni based roms.

But maybe (not sure) before trying Omni based MM roms I flashed the first CM 13 nightly.

That will be a good test for me then, to test battery life impact I fastboot flashed COS 11 this WE (and I must say I am impressed how fast all my apps restored so fast compared to LP or MM roms). When coming back to MM I'll let you know.
[ONE Android Development] indian84:
I flashes Oxygen OS 2.1.4 with Stock Recovery.

Flashed Latest TWRP and the Flashed SAOSP with Open Pico GApps and SUperSU 2.67. And Boom, the phone booted fine.

I guess, Cyanogen came to know that I don't like their ROMs and was trying to screw me. :P

Hehehehehe..
[ONE Android Development] deepaklunked:
Lol. Great that you got it working.. BTW did you use oxygen os for a while? How was it? Planning to try it..
[ONE Android Development] indian84:
Had it running for an hour or so. Feels buttery smooth and stable. I miss customizations on SAOSP though.
[ONE Android Development] deepaklunked:
Oh.. Thanks for the info. Will download it soon and test it for a while..
[ONE Android Development] indian84:
Dropping in to report, the screenshot issues I was having are gone now. Finally I can screenshot Snapchats. :P
[ONE Android Development] jimmmaras:
Which firmware do you guys suggest ? For the 01-14 build ?
[ONE Android Development] fmc000:
SuperSU in systemless mode

Being at home with a sick daughter and nothing much to do, I decided to upgrade my SuperSU to the latest 2.67 coming from 2.52. To my surprise it decided that it had to be systemless and so it went.

Installation went smoothly, it rebooted twice (the first time even before reaching the bootanimation stage) and now everything seems to work fine even though every root-enabled app had to granted the privileges again.

So now my question is: what will I have to do when the next ROM update is released? Is it enough to just flash the update or will I have to reflash SuperSU again (the backup script is in place, BTW)?

Thanks in advance to everyone who will eventually answer.
[ONE Android Development] indian84:
Strange, when I did a clean flash today with SuperSU 2.67, and it went smooth.
[ONE Android Development] fmc000:
It went smooth for me too, My only concern is that I don't know how to handle further ROM upgrades with SuperSU in systemless mode.
[ONE Android Development] indian84:
When I do ROM updates, I wipe Dalvik, Cache and System. And then Flash ROM, GApps and SuperSU. Have been doing this for few years now, unless Clean Flash is mentioned by the dev.
[ONE Android Development] deepaklunked:
He is particular about the systemless SuperSU. He is asking is it necessary to flash systemless SuperSU again after a dirty flash, and AFAIK. Yes you need to relfash, though I consider you better wait for info from someone experienced.
[ONE Android Development] abhibnl:
It needs to be reflashed because it patches the boot.img of the rom. Tried it but it doesn't survive a dirty flash.

Sent from OnePlus One
[ONE Android Development] fmc000:
I ended up with formatting /system and reflashing ROM, gapps and SuperSU. A couple of minutes of effort but now I feel "safer".
[ONE Android Development] solar666:
Anyone on the new modem can check if the proximity sensor is working?
[ONE Android Development] fmc000:
I use the latest H2OS firmware and it works perfectly.
[ONE Android Development] Anghirrim:
Ok, fastboot flashed the following COS version:

cm-12.1-YOG4PAS3JL-bacon-signed-fastboot.zip

I confirm that flashing the latest SAOSP build (24th of January) on the top of it works well and boot without problem.

Note that I did not flash any supersu zip neither any gapps package. I just wanted to test it quick and dirty.

[MENTION=4751327]F4uzan[/MENTION]

Thanks for having enabled the installation of apk's in the built-in explorer.

But unfortunately it FC's. Am I the only one?
[ONE Android Development] lmux93:
clean flashed c1.11-00004(latest h2os fw) and rom with twrp 2.8.6.0, and proximity sensor wasn't working, so i flashed the c7-00011(latest cm fw). With c7-00011 it was working fine. Few days ago i flashed the materialized twrp 2.8.7.0.5, and clean flashed c1.11-00004 firmware with the rom again, and this time the proximity sensor is working without any problem.
[ONE Android Development] solar666:
Thanks.

I cannot get proximity sensor working with any new modem than c6.241 on this ROM.

Strange. But even for you it seems more hit and miss.

On other cm based ROMs there is no problem to use new modems. [emoji21]
[ONE Android Development] taufiqs:
MRA stat only present when you are mostly using mobile radio data. If you either dont have or small value then I believe that you are on wifi at most. Cmiiw

---------- Post added at 05:42 AM ---------- Previous post was at 05:38 AM ----------

Then I assume that you are on wifi mostly. Please try with mobile data for full days and you'll see the mra magic.
[ONE Android Development] Maestropcxp:
Anyone can rec a video with the nextcamera modded V22? i can take a pictures, but the video doesn't work.
[ONE Android Development] abhibnl:
Has anybody tried flashing the MaxxAudio zip on this rom? Just wanted to check before experimenting myself.

Edit: Working fine. Flashed myself.

Sent from OnePlus One
[ONE Android Development] indian84:
The explorer works fine here.
[ONE Android Development] tekanina:
No force close but still can't install apks. Open Gapps flashes the google package installer. I wonder if that's the issue.
[ONE Android Development] qbanlinxx:
Replace the package installer with the one from the previous build and fix permissions. Installs should be fine after this
[ONE Android Development] tekanina:
Nope I'm an idiot, just realized I restored a nandroid of the previous build this morning and haven't updated yet. I really need to lay off the bud. Don't do drugs kids. Ha.

Edit; I'll update and report back.

Update; Okay updated latest build and no force close in file explorer and googles package installer from open gapps works as expected. S
[ONE Android Development] deepaklunked:
Lol bro. This happens to many of us..! [emoji23]
[ONE Android Development] praveen7682:
After long time came back to this ROM..Excellent ROM..No doubt abt it..Good battery backup, smooth and fast..Good job dev..
[ONE Android Development] indian84:
There is nothing called battery backup on a ROM. It's called ballery life..

;)

Sorry for being Grammar/ Spelling Nazi. It was just for fun.
[ONE Android Development] praveen7682:
Lol..thanks for correcting me..I was mentioning about standby time..I got 5 hrs sot with 24 hrs standby time..I am sure that's not a big deal for this ROM..???
[ONE Android Development] resetreflectt:
Hey guys, I just bought a OnePlus One off eBay and I was looking through to see what ROM I might install when it arrives. Was gonna do Oxygen 2.1.4 until I realized it's still Lollipop. I just wanted to ask though, does this ROM support 4k DCI? if not, does it at least support 4k UHD? Sorry if that's been answered but there's 98 pages and I don't have the patience to sift through all of that.
[ONE Android Development] solar666:
Don't have WiFi in office and was on mobile mostly LTE and 3G for more than 12 hours a day without any MRA showing up!
[ONE Android Development] indian84:
The ROM does not have a built-in camera app. I'm using ColorOS Camera port found in Apps section of OPO Forums. And it does show 4K and 4K DCI..
[ONE Android Development] taufiqs:
It is on the latest build with omnibear right?

Alas, i have this huge mra
[ONE Android Development] Anghirrim:
Sorry I meant I am getting FC's only when trying to install an apk file. Else I can browse my ohine without issue.

---------- Post added at 08:53 AM ---------- Previous post was at 08:51 AM ----------

Thanks for the tip but finally it's way easyer to me to copy my regular file manager apk directly in /data/app through TWRP file manager.

This works like a charm and then, using this file manager, I can install anything (I am using Amaze).
[ONE Android Development] indian84:
I just installed an apk using built-in explorer. Didn't see any FC.
[ONE Android Development] Anghirrim:
Ah.... Strange. Which build? Thr 24th?
[ONE Android Development] indian84:
Yes. The FC issue was fixed in 24th build. The FC was present in earlier builds.
[ONE Android Development] indian84:
Even though Radioactive kernel title says it supports AOSP and Omni, the issue is due to OPPO camera libraries.
[ONE Android Development] pa1281:
Is it possible to remove the tiles from notification drawer? And how to remove brightness switcher next to the slider?
[ONE Android Development] WhiteWashed:
Thanks guys, I'll try Donkey Kernel and report, hopefully today :)
[ONE Android Development] F4uzan:
Developer Options -> SystemUI Tuner

I'll see whether I can link the SystemUI Tuner to the main ROM settings on later build.
[ONE Android Development] pa1281:
Okay, Thank you. I think,we can just move around the tiles in SystemUI Tuner. and Can u provide a switch to enable/disable brightness switcher next to the slider?
[ONE Android Development] F4uzan:
Which brightness switcher ? May I have a screenshot for an example ?

On the other news, the update release will be slightly delayed since I'll be trying to compile the ROM with CM tree (yay for more build issues !), update will come slower but I can see it's somewhere soon.
[ONE Android Development] indian84:
No rush for the build dude. I'm happy with the current build. I'm at 74% battery with 2 Hours SOT and almost 15 hours up time.

Only missing thing is DT2W..

Quick question, if the new build will compiled with CM trees, will it remove the built-in layers support of 6.0.1? I hope not.

And please don't add CM theme engine.
[ONE Android Development] Parisaurus:
Moving to SAOSP, lets see if you did a good work here :p

Im really in love with AOSP ROMs, i was using CM based ROMs for years, couple of weeks ago i tried an AOSP ROM and i'm realy in love with the battery of it, so, lets see! :D
[ONE Android Development] F4uzan:
Nope, it won't, I removed CM Theme Engine stuff so it won't build the theme engine. Layers will be there since I don't use CM's framework.
[ONE Android Development] indian84:
You are the man.

Thanks. I finally found my ROM, since SlimLP development stopped/ slowed down for Bacon, I have been struggling to find MY type of ROM. And this is what I wanted.
[ONE Android Development] Luc.Nex:
Great rom!!The only thing i can't find is to disable the navigation bar..Nothing critical though..other than that everything is working as it should:)
[ONE Android Development] Parisaurus:
In the first post is the fix i think.
[ONE Android Development] F4uzan:
Flash the hardware keys enabler in the first post, then disable nav bar in ROM Build Tweaks (although this will disable recents clear all button). The ROM isn't optimized for device with actual hardware keys (it needs some extra polishing), so expect so breakage when using hardware keys.
[ONE Android Development] Parisaurus:
There is only one think to make me move to this ROM, and it's the configuration of Hardware keys. I was trying it and without this feature i can't move :/ Hope you add soon and i could come :p
[ONE Android Development] F4uzan:
So, like rebinding and reconfiguration of hardware keys ? Consider it fixed, next build will include it (I have lots of plan for the next build anyway). I'll also include some fixes for hardware keys later on (currently hardware keys doesn't lit up for no apparent reason).
[ONE Android Development] Parisaurus:
I'll be waiting for the next build! Really liked the ROM the 5 minutes i was (i think was enought to notice it's a good and clean ROM) so, when you add the hardware keys options ill come.

Anyways, good job with the ROM, really :D
[ONE Android Development] F4uzan:
Thanks for testing and trying :D I'll do my best for the next build.
[ONE Android Development] pa1281:
No rush for the build bro. Take ur own time and give us an awesome build.

Just a suggestion , it would be more simple if u just push ur tweaks similar to 12.1 settings instead of build tweaks section.

It would look more organised and stock. Been waiting for a rom like that (just aosp + CM settings) without any additional sections added in settings menu.

I have attached a screenshot.please check it out.
[ONE Android Development] Parisaurus:
I know it, just need that featuro to move to the ROM :p
[ONE Android Development] rogi19:
I tried your rom and its awesome, really snappy but i would also like to see button remapping so i can use google now on tap, and if its possible a lockscreen wallpaper changer, so i can have separate wallpapers on lockscreen , it was included in omni so maybe it wouldnt be much of a problem to include it? Thank you anyways, these are just my suggestions, i think with these two things implemented this will be a perfect rom, thank you very much for your great work and for providing one more great rom for our beloved bacon :D
[ONE Android Development] Anghirrim:
Ok, will re-test.
[ONE Android Development] F4uzan:
Hello everyone, I've been monitoring the thread for bug reports (and yes, there's a *lot* of them). I'll be releasing an update sooner (sooner than the normal weekly schedule, if I can), because most of the issue I see is either severe or major.

Here's the list of bug (or issue) that I've collected from the thread :

- Package installer force closing

- Mobile radio active

- No clock app

- Slow charging

I haven't developed (or found) a fix for all of them but I plan to fix them all in a single build. The MRA (mobile radio active) issue is a little bit random(ish), it might took a while to fix.

Thanks for all the test & bug reports !
[ONE Android Development] fmc000:
FWIW, my phone charges quickly (it even says "fast charging" when plugged with the OEM cable). The package installer works perfectly fine using pico gapps from 20160115.

Finally, I strongly suspect that the MRA is not present. A quick test I just performed:

google services increased the MRA of 30 sec in 10 minutes - which is perfectly normal IMHO;

tapatalk and whatsapp did not icrease their MRA in the same period of time.

My idea is that the stock omni kernel does not report the MRA correctly whilst onmibear does but I don't have any proof of this :p
[ONE Android Development] F4uzan:
Thanks for the detailed reports :D I was just referring to the users that encountered the issue I mentioned. I, myself, didn't encounter any issue that some user(s) reported, so it might be a little bit hard for me to check whether the issue is fixed or not.
[ONE Android Development] solar666:
No slow charging, no MRA or package installer issues here as well.

[emoji106]
[ONE Android Development] indian84:
Same here. No issues. I had Screenshot issue. But after a clean install, it's solved.
[ONE Android Development] deepaklunked:
No issues here too, except for faster battery drain. Not able to find out why? It is draining quicker than previous builds. I am on previous Build's omni kernel, with the old wlan module also. Will try to investigate further on the cause. Other than that, this ROM serves all that I need. Can't say much. Really satisfied and happy with this ROM. Downloaded Oxygen OS 2.1.4, but didn't get the heart to flash it yet. ;)
[ONE Android Development] fmc000:
[OT] Especially now that there's an OPX 2.2 port available for the OPO [/OT]
[ONE Android Development] indian84:
I won't be bothered going back to Lollipop. :)

EDIT - I am having good battery life. I have 48% remaining with 03:20 hours of SOT and almost 18 hours of uptime.
[ONE Android Development] taufiqs:
I second that!
[ONE Android Development] abhibnl:
Bro i'm still facing the video bug. I tried playing an HEVC video today and it only played the audio and no video at all and MX player refused to play the video on HW mode. The movie is "The last witch hunter" and the codec is also new. Can you look into it? Here are the screenshots for the video format. They are mkv.

Sent from OnePlus One
[ONE Android Development] F4uzan:
I'll take a look at it, the issue is not new on the table, I've been searching for fixes but I haven't found one. I should probably fix the issue in the next release (considering the issue already lasted several releases). Thanks for the bug report :)

Edit : I tested a 720p HEVC video (x265, HEVC) from this site, it plays the video normally. However, I could be wrong, so I'll keep my results until other user points out that it works fine in their side.
[ONE Android Development] abhibnl:
Well that's strange. I believe the issue is with mkv format. I'm using stock kernel so that can't be the problem. Just to be sure, does AOSP has native mkv support? One more thing that might help you with the issue, Two and a Half Men mkv video plays fine with MX Player's HW+ mode, not HW. However, the other movie(HEVC x265) mkv doesn't play with both HW and HW+ :confused:

Edit: Can you add the codec support commits from CM? I know it could take a while but i have no idea how to search on gerrit so i might not be of a good help there.
[ONE Android Development] F4uzan:
I have some plans to merge the stagefright-plugins and ffmpeg from CM, it won't take long to do it. Thanks for the suggestion(s) :D
[ONE Android Development] abhibnl:
Great! Hope it would resolve the issue. PM me if you would want to test a test-build first for the video playback.
[ONE Android Development] gamal001:
[MENTION=4751327]F4uzan[/MENTION] can you add one overlay option : show system info under developer option this it will show the cores and the speed of each cores
[ONE Android Development] Anghirrim:
OK..

So seems that no gapps no apps.

I clean flashed again the 24th build, but with gapps this time.

And now apk's can be installed using the built-in explorer.

Is that normal that this function is gapps dependant?
[ONE Android Development] F4uzan:
Nope, it's just a silly mistake I made, I was testing some modification on PackageInstaller, it seems to work with GApps (or it's the other way around), but apparently I just breaks everything with a single test. It should be fixed in the next release :D
[ONE Android Development] Anghirrim:
Ah ah!!! Seems that I am gapps dependant anyway. My weather forecast and bank applications both don't work without gapps package installed
[ONE Android Development] tekanina:
Open Gapps includes Google's Package Installer, so it overwrites the aosp package installer included in the ROM. I haven't flashed without gapps to test but this what I've concluded to why it doesn't work without gapps but the version from the last build apparently works fine.
[ONE Android Development] Anghirrim:
Is anyone able to use the MTP mode on a PC?

That's strange, on the 24th build my phone does not show up on my pc, whatever the connection mode I use is.

As a test, I installed quickly crDroid 6.0 and it works without problem. That's weird....

[MENTION=4751327]F4uzan[/MENTION]

Would you mind adding the stock clock app in the available zip files you link in the OP? That would be great thanks!
[ONE Android Development] solar666:
Have you disabled USB debugging by any chance?
[ONE Android Development] tekanina:
Also experiencing faster battery drain and google play services is going wild with MRA bug. 13 hours off the charger and 1 hour 10 mins MRA. Chrome is at 50 mins. Not as bad as lollipop but I did not have this issue on previous build and battery was fantastic. Also not digging omnibear, had better results with stock omni kernel.
[ONE Android Development] miesfu:
Dirty flash...with Email & Calendar Zip, xposed, supersu

works great and no MRA issue

video play is OK
[ONE Android Development] Anghirrim:
Yep I did.
[ONE Android Development] fmc000:
Is a bug in this rom, I forgot about it. You have to connect the cable and then select mtp or whatever from the drop down menu. The default is "charge only" and even if you select mtp in the developer options it doesn't stick.
[ONE Android Development] Anghirrim:
Yep but for me even if I select mtp (with adb on/off) it does not work.
[ONE Android Development] fmc000:
Works fine here.
[ONE Android Development] Anghirrim:
I'll test with another computer at work.
[ONE Android Development] taufiqs:
Yeah mtp isn't the default option. You have to switch it to mtp first. Remove safely the unplug and plug it back after switching to mtp.
[ONE Android Development] Anghirrim:
Ok, seems it comes from my personnal computer. Switching to mtp while being plugged works well and I can access my phone storage when I am using my work computer.

Both W7 64 bits, home edition for mine and pro edition for the office.

I'll check the drivers I have installed. The office computer is using the basic Microsoft generic one. I think I have the universal android driver on my personnal laptop.
[ONE Android Development] fmc000:
I use the drivers that are included in the virtual CD-ROM that shows up when you connect a phone where you flashed H2OS. They work perfectly under W10, not only with the OPO but also with a kindle fire and with an old ASUS tablet HD.
[ONE Android Development] Anghirrim:
Ok, will try maybe. Thanks.