yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] indian84:
Great to see OmniBear Kernel in today's build. Weekend in Dubai over today and we back to work tomorrow. So I can flash the update as I have time today. :good:
[ONE Android Development] fmc000:
Couldn't agree more, in my case everything works, I really mean everything I tried. This rom is simply amazing, let's hope that omnibear maintains its promises.
[ONE Android Development] indian84:
I'm with you on this. Everything works as it should. Stable, fluid, battery friendly. OnmiBear feels slightly better to me at least. And as [MENTION=4751327]F4uzan[/MENTION] mentioned in the poll, it's updated more frequently than stock Omni Kernel. [MENTION=1228651]fusionjack[/MENTION] the dev of the kernel is also amazing. I used his SlimSaberLP builds and they were amazing.
[ONE Android Development] photobix:
Hi [MENTION=4751327]F4uzan[/MENTION],

great to read, that you'll provide an update tonight!

I mentioned only one problem: The start/stop button from my headset (wired) is not working properly:

sometime, the button changes the audio volume, like the minus-button.

The plus-button is working. Is this fixed in the 23/01 version?

Thank you :)
[ONE Android Development] indian84:
I don't use a headset to listen of music. But your issue can be related to a defective headset. It's just my guess. I may be wrong.
[ONE Android Development] F4uzan:
Weird, my headset button (the start/stop and volume button) works fine. I'll see if I can find a fix for it, probably won't be fixed on the next release (since I'm already preparing the zip for an upload), but we'll see :) Thanks for reporting the issue !
[ONE Android Development] photobix:
Thank you :)

The headset is working fine with other ROMs and, at least, 2 computers.

I'll check it again with the version from tonight.
[ONE Android Development] F4uzan:
Can you try flashing the hardware key enabler ? There might be some issue with the key hook I disabled. Thanks !
[ONE Android Development] photobix:
I'm always using the HW keys, so it's enabled already

Edit: Sometimes it helps to replug the headset, than all buttons are working fine
[ONE Android Development] F4uzan:
I see, I've noted the issue. I'll see whether I can fix it or not, I can also confirm the issue here on my side since I just encountered it after randomly plugging & replugging my headset :)
[ONE Android Development] fmc000:
And I can also confirm the same issue with my bluetooth headset. Sometimes the next track/previous track buttons don't work until you turn off and back on the headset (similar to unplug/replug a wired headset). The volume keys are always working fine.

BTW, I have also flashed the hardware keys enabler (something I really hope it will included in the next release :) )
[ONE Android Development] F4uzan:
New update (2016/01/23) released. Here's the things that has changed from previous build :

* Improved built in file manager (Settings -> Storage -> Explore)

* Fixed layout errors in Settings app

* OmniBear kernel returns

* Added sync tile (more tiles will be added soon)

* Code optimizations (won't be noticeable, tho)

* Merged several bugfixes (mostly UI & under the hood)

* (EXP) Out-of-sync audio fixes

* (EXP) Keyboard swipe fixes

Unmerged features that I haven't merged for some specific reasons :

* Hardware key toggle (enable / disable hardware key)

* Disable power menu & quick settings on secure lockscreen

Issues that still persist on current release :

* None for now

Additional notes :

* This build is still considered testing until further notice

* I know the changes might be a little bit dissapointing, but as I stated earlier, I plan to minimize adding feature(s) and start fixing issues reported here

* The headset button issue should be fixed, but due to the issue being a little bit random-ish, you may still encounter it

* GPS / location tracking issue is untested but it should be fixed, use Faster GPS app if the issue persist

* My build system kinda messed up the time / clock, the ROM is built at 23-01 but the clock is incorrectly set so the zip shows '24-01'

Download, just in case you missed it in the first post :

saosp_find7op-2016-01-24 (MD5 : b52bca90f89e4207438010f88f513b97)
[ONE Android Development] indian84:
[MENTION=4751327]F4uzan[/MENTION]. Thanks for the build. You are the man. I'm expecting a payment tomorrow for 6 months of work. Would like to buy you a coffee. Hook me up with your donation link.
[ONE Android Development] F4uzan:
The builds should always be ready, I should not have the thank for it since that's what I should do, if there's an user there will always be a build :) I am thankful of your kindness, we can talk about this in PM (to keep the thread tidy and more on topic), again, I am really thankful and I would not be able to repay the kindness of the user(s) here (sorry if that became too sentimental xD)
[ONE Android Development] indian84:
Sure thing dude. Expect a PM from me tomorrow.

By the way, I'm unable to boot the build.

By the way, I used updated TWRP 2.7.8.1 released today. I wiped System, data, cache and dalvik. The wipes took a long time. So of anyone faces the same issue, be patient. It will eventually complete the process.
[ONE Android Development] F4uzan:
That's strange, it booted fine here (on OmniBear and Donkey kernel), I'll do a quick check now and see whether the fault is on my side. Thanks for the report !

EDIT : Booted fine here, I'm on TWRP 2.8.7.0, I did a clean wipe (/system, /data, /cache), with no other zip (other than GApps) flashed.
[ONE Android Development] gamal001:
Also here not boot it.
[ONE Android Development] indian84:
No problem booting. It just took long time to wipe and flash. I'm in a process of data restore.

EDIT - I did a clean install. Just for the sake of it. I was at home with nothing to do. So clean flashed.
[ONE Android Development] F4uzan:
Can you please list your flashing order ? I tried to replicate the issue, but the build boots and works here. Thanks for the report !
[ONE Android Development] indian84:
Yes the build boots fine.
[ONE Android Development] gamal001:
Dirty flash , flash ROM, gapps, su . as usual but not booted

Tomorrow I will make clean flash and I will report but now I go to my backup.

Edit : clean flash boot it okay .
[ONE Android Development] pa.pn2:
Dirty flashed. All fine. Wiped system and caches before. Su 2.67.

Can confirm the audio whatsapp bug is gone now

Thx fauzan
[ONE Android Development] F4uzan:
Glad it worked out well for you :) Thanks for reporting the out-of-sync audio issue and thanks for testing as well.
[ONE Android Development] pa.pn2:
Thx to be a tester. Btw omnibear kernel is silky smooth for me with smartmax/1024 fiops
[ONE Android Development] indian84:
Glad [MENTION=4751327]F4uzan[/MENTION] did a poll and most of the users voted for OmniSaber. Even for me it feels smooth and better than Stock Omni Kernel. I am using all stock settings except for Scheduler. I'm using fiops and 512.
[ONE Android Development] solar666:
[MENTION=4751327]F4uzan[/MENTION]; clock apk is missing in the new update.
[ONE Android Development] pa.pn2:
noticed too

http://www.apkmirror.com/apk/google-inc/clock/clock-4-2-1-2383161-android-apk-download/
[ONE Android Development] F4uzan:
I forgot to include it in the zip package xD Sorry ! You can use Google Clock app if you still need the AOSP Clock app.
[ONE Android Development] Luc.Nex:
[MENTION=4751327]F4uzan[/MENTION] ever thought about tracking snap camera from cm since it works for our devices better than aospcamera ?
[ONE Android Development] abhibnl:
Noticed that as well. I took the apk from last update and pushed it to the system, working like a charm. [MENTION=4751327]F4uzan[/MENTION]

I noticed that there's no file manager by default, not even the documents app. Is if on purpose? Not that it's a deal breaker, just out of curiosity.

Sent from OnePlus One
[ONE Android Development] F4uzan:
It is on purpose, because Marshmallow (or probably Lollipop) have included a built in file explorer (Settings -> Storage -> Explore) ;)

Yes, I have plans to release it as an add-on, I might release it sooner or later :)
[ONE Android Development] tekanina:
I took your browser zip and replaced it with deskclock from the previous release.

https://drive.google.com/file/d/0B7LK0pBcBH_QVng4VGsxd25BWE0/view?usp=docslist_api
[ONE Android Development] `SBR`:
Anyone has battery slow or not at all charging issue... With this rom. I using one plus one charger
[ONE Android Development] indian84:
Nope. Charged fine here.
[ONE Android Development] F4uzan:
It charged normally here, it might be hardware issue and not software issue. However, if it is software issue, I would need more details to reproduce the issue, thanks !

Thanks for this ! I shouldn't have let my stupidity break the ROM once more later on xD
[ONE Android Development] venky61:
I do face this but not exactly the same. I connect the phone to the charger and leave it realizing later that it did not charge at all. The battery stays steady at same value for the whole time. I have to disconnect and replug in for it to charge. Its highly inconvenient some times when you have to go out and you have limited time to charge. [MENTION=4751327]F4uzan[/MENTION] Can you throw some light on this issue.
[ONE Android Development] F4uzan:
I have never encountered the issue here, I'm using the stock OnePlus charger. I probably will search around and see whether the issue can be fixed or not, I'm also unsure whether the issue is caused by bad software or hardware. Anyway, thanks for the report !
[ONE Android Development] :
Anyone here coming from CM13 latest firmware ? I had no luck with using Omni based ROMs with the previous CM firmware, I have tried with the current one as well with Slimsaber, booting never finishes, anyone moved from CM to the latest SAOSP ?
[ONE Android Development] abhibnl:
I think all this work is affecting me, lol. I totally forget that. Thanks! If you could add a "Reboot" tile and Switch to last app in home button double tap options, the rom would be perfect for me. Already loving the latest release with omnibear. One thing i love the most about this rom is that the boot times are crazy low.

Yup! Working totally fine here.

Sent from OnePlus One
[ONE Android Development] :
That's the previous firmware, currently CM has reverted back to baseband version 241 ... I'll try flashing with both of them, at least it looks like working with the previous one.
[ONE Android Development] fmc000:
Are hw keys included or is flashing the add-on still needed?
[ONE Android Development] abhibnl:
Well since omni doesn't include any firmware changes from themselves, so i believe it should work. You can try.

It's still required.

Sent from OnePlus One
[ONE Android Development] `SBR`:
I tried replug it will start charging..but very slow. It will display charging rapidly (4 hrs until full charge). @43% battery level. And if u start working on the phone with plugged in battery will start depleting.

When I powered off and charging it will charge normally (not fast nor slow) using multi rom now and cos12.1 as the primary.

I
[ONE Android Development] photobix:
I tried it yesterday, with the same error.

After plugging in the charger, the status LED was yellow for seconds, than the LED was off and the device was not charging.

Tried it with Sultans CM, it is charging.

Sounds like a problem in the ROM, not the HW, I'm sorry [MENTION=4751327]F4uzan[/MENTION]
[ONE Android Development] indian84:
Some users have been reporting in Stock Omni thread as well. I guess it affects only a few OnePlus One devices. I don't think MultiROM has something to do with the issue.

If it is possible for you, and you don't mind, clean flash the ROM using normal TWRP and see if that helps. Again, I have never used MultiROM, so I am not sure how long and difficult the process is.
[ONE Android Development] :
[MENTION=4296062]abhibnl[/MENTION] nope, no luck. It starts to input for password for encryption, shows data partition is corrupted and asks to reset phone, goes to twrp, formats /data, then goes back to the same point all over again. Tried even manually wiping /data, nothing works. Its clearly an incompatibility with CM, cause I can use CM based ROMs without any issue what so ever.
[ONE Android Development] photobix:
I did a clean flash, without multiROM.

TWRP: The nightly one from 20160101

Firmware: Latest from CM, flashed separate.
[ONE Android Development] indian84:
Possibly your device is one of the OPOs that doesn't like Omni/ Omni based ROMs.
[ONE Android Development] fmc000:
So, I'm a little confused. Some users say that the latest build doesn't boot, some say it does, some say it does only after a clean flash. I suggest that everyone that has already tried this build posts his/hers experience. Boots of not, clean or dirty, which gapps, which supersu, multirom or not, which recovery and so on.
[ONE Android Development] indian84:
1. Clean Flash. I did not try dirty flash, as i was at home and was bored. So just to kill time I did clean flash.

2. I used latest TWRP from here. http://build.twrp.me/twrp/twrp-2.8.7.1-bacon.img It takes very long time to perform wipes. Especially System, it tokk around 5 mins. Be patient, if you want to use this TWRP. It is bug with the recovery. You can always use Materialised TWRP or latest TWRP.

3. Used Open Gapps Pico.

4. Super SU 2.66

ROM running beautifully here. No issues with charging or anything that I noticed.
[ONE Android Development] `SBR`:
Same it's charging with cm13 sultan... Didn't try other rom

Will try a clean flash without multi ROM and check it. But seems like the issue with this ROM only. Latest herna omni ROM is working fine no issue with charging.
[ONE Android Development] photobix:
1. Clean Flashed

2. I used TWRP from here: https://www.androidfilehost.com/?fid=24352994023703439

3. Used Open Gapps Pico from 20160123

4. Super SU 2.52
[ONE Android Development] solar666:
Dirty flashing here even with xposed. No problem. Currently running open gapps pico and SuperSU 2.67. No charging problems at all. Using 241 baseband.

[emoji106]

Better than ever ...

Using newest TWRP form kamujaya:

https://www.androidfilehost.com/?fid=24367857647223599
[ONE Android Development] fmc000:
Just curious: why SuperSU 2.67 when systemless is not needed for SAOSP? The OP says that 2.52 is recommended because of this.
[ONE Android Development] indian84:
For me, I just wanted to see if the latest SuperSU works. I have not had a single issue with my Root apps like, Ad Away, Greenify, Titanium Backup.
[ONE Android Development] abhibnl:
Sorry but i have never used encryption on my device. I wish i could try this rom with older firmfirmware for you but i just clean flashed this and have no time for clean flash or to solve soft bricks anymore since i only get to do these things on sunday and sunday is almost half passed here in India.

Clean flashed, twrp 2.8.6.0, latest CM firmware(new one).

I flashed 2.66 and it's working fine.

Sent from OnePlus One
[ONE Android Development] solar666:
I am using always the latest available in order to see what's happening ... Just a habit [emoji2]
[ONE Android Development] pa.pn2:
Guys how do u change lockscreen wallpaper? I don't want to use exposed..
[ONE Android Development] F4uzan:
This app should be the one you're looking for, you can uninstall the app later on and the lock screen wallpaper would stick :)
[ONE Android Development] bclark:
Dirty flashed

Most recent unofficial TWRP

This Firmware

Flashed with Banks Gapps, ViperAtmos, HWKeys, UKM, SU 2.52

Booted no issue and was on Donkey One previously
[ONE Android Development] hewhomustnotbenamed:
Could you let me know why have they reverted? Does it make any difference in daily use?

Can you tell me the build date when they reverted so I will download a day prior build to get the new firmware back, if need be.

Thanks :)
[ONE Android Development] indian84:
I guess it had issues with T-Mobile US network. Again, my guess is 10Jan nightly has the new firmware. After that they reverted.

I am not even sure what firmware I'm using. Hehehehe. But the phone runs fine for me. If you don't have any issues with your mobile reception and sensors you can use the firmware you are using now.
[ONE Android Development] :
They were facing some issues, not sure exactly what, from 22nd nightly, I wasn't having any issues with the other firmware either, neither this one. The network drops are far too less compared to how it was back in Lollipop days.
[ONE Android Development] dreezz:
dirty flashed, no problems.
[ONE Android Development] bundys:
Clean install yesterday - here's my notes so far :

- ui is pretty fluid although I've experienced some stuttering in Chrome

- battery life seems good too, except for wifi usage, which seems high at 25% (see screenshot)

- stock camera software is pretty abysmal (would love the cm camera included or available as an addon)

Overall I'm pretty impressed
[ONE Android Development] deepaklunked:
CameraNext Mod is already available in the apps and themes section.
[ONE Android Development] kash_si:
:cowboy: [MENTION=4751327]F4uzan[/MENTION],

Latest build feels good so far. Just did a clean flash after installing systemless SU V2.67. Thanks for your builds & great ROM.

:good: :good:
[ONE Android Development] sax0406:
[MENTION=4751327]F4uzan[/MENTION] is there a way to reduce the brightness of the ambient display? I think it is displaying at the max brightness.
[ONE Android Development] venky61:
Hi,

Did a dirty flash. Works good.

1. Wipe cache and dalvik.

2. Flash the rom zip.

3. Flash Gapps.

4. Flash Supersu v2.46

Done.

So far so good. Will see if the battery charging issue is solved or not.

---------- Post added at 11:07 AM ---------- Previous post was at 11:03 AM ----------

Hey... can you link me to the viperatmos download. And how is it working with this rom?
[ONE Android Development] tmimaesk:
I have clean flashed the latest rom, but am I the only one that the package installer force closes?

I can provide log if it is only me.. or clean flash again..

Thanks!
[ONE Android Development] indian84:
If I understand correct, you cannot install any apks. Correct?? I don't have this issue. My wild guess here will be a layers theme your are running. Uninstall the layers and see if that helps.

On other note - I'm unable to take screenshots. I get an error saying limited storage or it isn't allowed by the app. Never had this issue before. Can anyone confirm??
[ONE Android Development] Minux31:
No problem with screenshots :

Envoyé depuis Tapatalk
[ONE Android Development] fmc000:
Dirty flash along with the clock and hardware keys zipfiles , no wipes, all good. Great work as usual.
[ONE Android Development] indian84:
Strange. Let me get rid of my layers theme and try again. If nothing works, clean flash calling again.
[ONE Android Development] myshakugan:
Was wondering, why doesn't the screen automatically turn off after receiving a call? Excuse my ignorance, haven't used omni/omni based roms in a while. Or has this been mentioned earlier?
[ONE Android Development] Minux31:
My config if you want to compare :

- TWRP Materialized version 2.8.7.0.5 ( https://forums.oneplus.net/threads/materialised-twrp-for-oneplus-one.305017/ )

- SAOSP-M 01/24 (I've dirty flashed all versions since my first install on 04/01 version)

- Open Gapps

- Super SU Beta 2.52 (so not systemless version)

- SkyBlue layers ( https://play.google.com/store/apps/details?id=bitsykolayers.SkyBlue )

Hope it will help :)
[ONE Android Development] indian84:
Thank bud. Will check once I go back home. I'm at work now.
[ONE Android Development] taufiqs:
[MENTION=4751327]F4uzan[/MENTION] and now MRA is resurfacing again. Going to monitor the first.
[ONE Android Development] fmc000:
Confirmed.

---------- Post added at 10:19 AM ---------- Previous post was at 10:13 AM ----------

[MENTION=4751327]F4uzan[/MENTION] : is it possible that OmniBear is the cause for the returning of the MRA bug? Do you think that it may be possible to flash the boot.img of the previous version over the latest?
[ONE Android Development] indian84:
Don't flash boot image from last release. You will loose WiFi.
[ONE Android Development] fmc000:
I don't understand, sorry. I am already running the last release and I asked if if was possible to flash the boot image from the previous release.
[ONE Android Development] indian84:
The kernel module for WiFi is different for OmniBear and stock kernel. You'll also have to replace wlan.ko in the "/system/lib/modules/" folder and chmod 644.

Credit to [MENTION=6056266]randallstevens[/MENTION] for this.
[ONE Android Development] PatrickMac:
I have the same problem. And it is not related to layers. Installing an apk results in package installer FC.
[ONE Android Development] F4uzan:
You can reflash the previous boot.img, just make sure you replaced the wlan module (wlan.ko) since WiFi would stop working if not.

Well, that was kind of unexpected. The issue is one that I didn't expect to show up again. I'll see whether I have made a mistake in the code. Thanks for reporting the issue.

Package installer works fine here, see the screenshot attached. Can you send me some logcat so I can identify the cause ?
[ONE Android Development] fmc000:
Ok, now I'm running the latest ROM with the stock omni kernel. Will report if omnibear is causing the MRA bug.
[ONE Android Development] PatrickMac:
Sure, here is the log. Hope it is helpful

http://pastebin.com/y3nRi2g1
[ONE Android Development] bclark:
http://xdaforums.com/showthread.php?p=57021246

It works fine, there are other configs to try too but I find this one gives me the best sound. Make sure to read the OP, there is a lot going on.
[ONE Android Development] abhibnl:
[MENTION=4751327]F4uzan[/MENTION]

Buddy, the video player bug is still not resolved. It was the reason i wasn't able to use this rom as daily driver. I have tried it on a total clean flash as well but the videos still lag and stutter. If i install MX and choose SW decoder, they work perfectly fine. Did you get some time to look into this issue? Would any log help? It happens on almost all of the videos i try to play. Could it be a codecs issue? I remember CM merged a lot of codecs support with CM12.1.

Sent from OnePlus One
[ONE Android Development] fmc000:
FWIW, I just tried playing a video with MX HW decoder and it worked fine. A 2.4GB mkv.

---------- Post added at 02:45 PM ---------- Previous post was at 02:33 PM ----------

I'm running the latest SAOSP release (saosp_find7op-2016-01-24) and flashed the stock Omni kernel found in the previous version (saosp_find7op-2016-01-14). Google Services Mobile radio active is 10m 22s, exactly the same number I had more than two hours ago.

So it seems that in my case the stock Omni kernel fixes the MRA bug. It would be nice if someone else could confirm of contradict this result.
[ONE Android Development] deepaklunked:
Thanks for the report. Will try and let you know.

Edit: Changed the kernel, now let the testing begin. ;)
[ONE Android Development] Xerosnow:
Deleted
[ONE Android Development] m0bstr:
Is there anyway to add a power toggle? Like the one CM13 has for Wifi, bluetooth, GPS brightness?
[ONE Android Development] thecuriousmate:
Have you installed GApps? I got force close when I clean flashed only ROM. But later I clean flashed ROM then GApps and package installer was working.
[ONE Android Development] tmimaesk:
Extract PackageInstaller.apk from Jan 14 from System/priv-app/PackageInstaller and replace it with the current PackageInsgaller.apk with correct permission.

Worked for me
[ONE Android Development] PatrickMac:
Thanks, will try that later. Seems like we are the only two people with that issue
[ONE Android Development] gamal001:
I'm faced same problem but I replaced the apk from previous release and solved
[ONE Android Development] solar666:
No MRA bug here at my end running Omnibear kernel everything looks good.

How do you identify yourself if the MRA is present or not?
[ONE Android Development] fmc000:
In the battery stats page, select an app that's using the most battery power and look for "Mobile radio active". Google services in my case.
[ONE Android Development] indian84:
Even I don't have MRA. 23 Hours uptime and Google Services show 17 mins of mobile radio active. I think this is pretty normal.