yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] freshgiammi:
That'll take time, but we all hope to have that soon. I'm just not very good at writing SELinux policies haha

I hope I can hit where OxygenOS didn't... :p

EDIT: Gah I forgot to add Substratum's App! But masquerade is installed, so you can get the app from the play store in the meanwhile, i'll make sure to add it in the next build.
[ONE Android Development] Spider-Vice:
Does this use AOSP's original camera blobs or Sultan's modified ones?
[ONE Android Development] freshgiammi:
CM. I've tried Sultan's, but I still need to work on his kernel.. A few incompatibilities.
[ONE Android Development] capitanouncino:
Great!! Is it necessary a full wipe if I come from updateing's build?
[ONE Android Development] freshgiammi:
Shouldn't be needed, but I'd recommend a clean install. Make a backup first if you're going for a dirty flash.
[ONE Android Development] Fataldose:
And new Nougat for opo. I think this device is not gonna die for 2 years ;) you guys are awesome. Thanks..
[ONE Android Development] C4SCA:
Any bugs encountered yet? Other than the issues stated in the OP
[ONE Android Development] beatbrot:
Currently setting it up..Pico TTS crashed once (and only once, so veeeerrry minor). I'll edit the post if i find more bugs :)

Edit 1: Whenever I tried to setup whatsapp without profile picture, it got into a endless loop. However, adding a picture and then removing it via settings worked just fine. (This is probably just a whatsapp-thing as I am also whatsapp-beta-tester)
[ONE Android Development] freshgiammi:
Pico TTS crashes on my side too. Gapps issue I guess.

WhatsApp works fine here. (Stable, not beta)
[ONE Android Development] rudolf895:
Shouldn't this be in android development?
[ONE Android Development] shadekh:
The GPS issue is solved then? Have been using the OPO as my primary driver, and it was near impossible to use ride hailing services and google maps with the last few builds.
[ONE Android Development] Lore2317:
Nane of Wetaher app in status bar/notification?
[ONE Android Development] Бахрам Байрамза:
Can you build Nethunter Kernel for this Rom?
[ONE Android Development] ramosroger:
Can you
[ONE Android Development] vivekchamoli:
Can anyone upload the boot.img of the latest build ... thanks.
[ONE Android Development] freshgiammi:
Never tried multirom but someone used it as secondary. Search the thread, you need to change a line in the updater-script inside the zip.

haha yeah, the good ol' days... used to clean build in 3h on the same machine with Lollipop.

I'll include the fix in the next update.

EDIT: Looks like it's working fine for me. However, i'm missing a lib required on 7.0, so that might fix it for you.

It has been reported not to be working (yet).

Weather Timeline

https://play.google.com/store/apps/details?id=com.samruston.weather&hl=it

Managed to get SnapdragonCamera to work!

There are a few issues (like JPEG Qualities showing 55%, 65% and 75% while the values that are applied are 55/85/100).

720p@60 and 720p@120 works fine now. 1080p@60 doesn't work (I don't know what's wrong, logs are clean). HSR works on 1080p but not on 720p. (If someone used CM14.1 or LineageOS: are HFR and HSR working there?)

Camera's a bit messed up still but it's getting better.

Next build should have it included (1-2 days).
[ONE Android Development] Gawd:
Just flashed this ROM a while ago and completed setting it up. This is, hands down, the SMOOTHEST NOUGAT ROM out there. Consider this from a person who has tried every other nougat ROM.

Props to you man [MENTION=4986658]freshgiammi[/MENTION]

#NeverSettle
[ONE Android Development] Gawd:
Here mate :)
[ONE Android Development] Бахрам Байрамза:
I can't
[ONE Android Development] Gawd:
Split screen issues.

Noticed similiar //bug in early 7.0 builds by updateing.

20160903
Fixed HW encoder and camcorder (they are different issues, though related) (and switched to CM13 media HAL)
Fixed display corruption while rotating screen with video playing (by switching to CM13 display HAL, don't know which lines of code fixed that)

20160906
Switched back to AOSP HALs to increase performance, but screen recording is broken again. You can choose CAF HALs listed above to fix that. Camcorder and HW encoding work with both variants, no need to worry.

Updateing's thread
[ONE Android Development] freshgiammi:
Weird. Tried to but can't reproduce. Does it happen every time? I often multitask and never saw that.

However I'm using the CM13 HAL (Which, to be honest, are just plain CAF).

AOSP Hal breaks Screen Recording, video uploading and ambient display. That's why I trashed it

It doesn't even have much better performance.. tbh i felt CAF to be smoother.

EDIT: Now that i think of it, it happened once but all it needed to fix was to lock the phone and unlock it again. It fixed itself that time. Weird.

If it happens again, send me while replicating it.
[ONE Android Development] se7enlyn:
No similar issue with my OPO
[ONE Android Development] Gawd:
Happens when rotating the phone (portrait to landscape and vice-versa in YouTube). And yes, due to earlier experiences I knew that locking and unlocking it fixes the issue (I was on updateing's since the beginning, haha)

Do you need a log or something? Thanks.
[ONE Android Development] freshgiammi:
Yeah I do. Kept trying this morning but I can't reproduce.. please list me the steps also, maybe something is triggering it.
[ONE Android Development] freshgiammi:
Tee-hee, Snap camera in all his glory...

HFR/HSR doesn't work yet (I'm on it), everything else works fine. It's gonna replace AOSP Camera in the next update.

EDIT: Not relevant, just using this post as a placeholder

HSR 720@60fps ok
HSR 1080@60fps ok

HFR 720@60fps ok (Slowing down on final cut)
HFR 720@120fps ok (Slowing down on final cut)
HFR 1080@60fps not working
[ONE Android Development] Gawd:
Tee-hee
[ONE Android Development] TVJS:
After installing the ROM first boot the phone.

Then again go into recovery and flash gapps.

Enjoy!
[ONE Android Development] PlayingPoise:
Looks awesome!!! Can't wait for the next build to test this out :)

Just curious, have you figured out SELinux yet?
[ONE Android Development] rphlfjrd:
Awesome. I'll wait for this update before flashing. :) (Already have latest build DLed but lazy to flash ;p)
[ONE Android Development] C4SCA:
Does adding the pixel navbar with the animations counts as going away from AOSP? :angel:

Since now launcher 3 looks like the pixel launcher.

Sorry for asking but im still looking for the aosp rom that fits to my likes but i dont have the time as of this month to backup, flash, test,... (A twrp backup of my current setup takes 30min even without compression!)
[ONE Android Development] SirSoviet:
From OP:

I think changing UI colors would be too much. That's what Substratum is for.
[ONE Android Development] fireflyv2:
ROM is practically perfect now. Once the camera is completely up and running with all its features, it'll be all set.

Just one request, if you don't think we're straying from AOSP too much, would be to unlink the ring and notification volumes. I get way too many messages, and I don't want my phone beeping loudly away to glory :crying: but I do need my calls to be loud enough to hear them even if I'm away from my phone.
[ONE Android Development] Gawd:
[it's obsolete now, don't flash]

Anyone want Pixel Navbar with animations?

Well, here you go. I made a flashable .zip for that. Enjoy!

Just flash the attached .zip file in recovery~

Images-
[ONE Android Development] freshgiammi:
Nope, haven't looked much into it... I'm working alongside with Evolitist and he said he will take care of SELinux policies. Snap is almost ready, next step i'm gonna take is adapt the hal so it builds without blobs.

Read my previous message

Cool! I'm gonna link your post to the OP when i'll upload the new build, so that people can see it.
[ONE Android Development] daltonhrrll:
So I flashed latest build. I didnt realize I needed to flash SU. I now don't have root and I apparently have no recovery to flash it. Help lol
[ONE Android Development] Gawd:
ADB lol

Fastboot lol
[ONE Android Development] freshgiammi:
lol

connect it to your pc and do "adb reboot recovery", then flash SuperSU. Or shutdown your device and then power it pressing power+vol. down

EDIT: well this works if you still have the recovery. My rom doesn't overwrite it.

Otherwise power+vol.up is fast boot. Flash a recovery there if you have none
[ONE Android Development] daltonhrrll:
I just used adb to flash tuga recovery and now I'm good lol
[ONE Android Development] LucentBirch:
Had a couple of random freezes and reboots. Not sure if related to lowered max frequency and lowered boost freq. Raised the boost frequency to see what that does
[ONE Android Development] Gawd:
[MENTION=4986658]freshgiammi[/MENTION] check pm bro
[ONE Android Development] freshgiammi:
Never got a reboot since my first build. Send me a last_kmsg if you still have one
[ONE Android Development] LucentBirch:
It's been too long probably - happened yesterday afternoon. No issues since I increased the boost.
[ONE Android Development] freshgiammi:
I have 1036mhz as touch boost. In case you get a reboot, make sure to post a last_kmsg.
[ONE Android Development] LucentBirch:
Kk will do!
[ONE Android Development] fabio.pagliuca:
What frequency do you suggest as sync threshold? I changed it so I can't remember which was it
[ONE Android Development] freshgiammi:
Default is 1728mhz. I'm trying 1497mhz since my boost is now lower.
[ONE Android Development] freshgiammi:
Time to deliver! AOSPlusone_bacon_160117 is here!

Finally replaced Camera2 with Snap to enjoy all the neat features from Sultan's HAL!

Also fixed Face Unlock and made UI a bit faster.

Hopefully even the split screen issue is fixed.

Changelog:

11 Jan. 2017 -> 16 Jan. 2017

[B]Replaced Camera2 with Snap: Enjoy all the functionalities of Sultan’s HAL![/B]
[B]Fixed HSR; Slow-Mo isn’t working yet.[/B]
Updated Camera Capabilities for a better HAL compatibility and features
[B]Updated Display-CAF with newer commits to fix the Split Screen issue[/B]
Fine tuned RT Scheduler priorities
[B]Enabled prefhint: (Layers are rendered faster now, resulting in a smoother experience)[/B]
Enabled “Moves” in Settings
[B]Fixed Face Unlock (Trusted Face)[/B]

*NEED TESTERS FOR F2FS: /DATA AND /CACHE ONLY, NO /SYSTEM*

EDIT: I've uploaded more up to date screenshots. And in case anyone wants that wallpaper.... here it is, shot with Snap ;)

*Full resolution version*
[ONE Android Development] LucentBirch:
What do you use for PIC processing?
[ONE Android Development] freshgiammi:
VSCO and Snapseed.

Adobe Lightroom on my Macbook if I take RAWs. (They can be taken with FreeDCam on the new HAL)
[ONE Android Development] LucentBirch:
Ah gotcha!

So I did have two reboots today. Couldn't upload the files for some reason, so here's a megalink to them:

https://mega.nz/#F!nVFnRLSS!74aWy8RKveAcgmBmJ3XuDQ
[ONE Android Development] rphlfjrd:
Really? Right after I clean flashed the previous build?! LOL :eek: Does the rom have gapps survival script?
[ONE Android Development] se7enlyn:
Is the 160117 build dirty flashable?
[ONE Android Development] Anghirrim:
While playing music, output on bluetooth device works ok, but if I plug a jack, then music keeps getting out of the phone's speaker and does not switch to the headset.

A search in the thread with "jack" gives me only results on "back"... Weird

Edit: looks like it depends on the jack used. On yesterday's build, my jack headset works fine but not my jack/jack in the car.

I restored a SlimLP backup and everything works ok. So looks like it's rom related.

---------- Post added at 08:15 AM ---------- Previous post was at 07:24 AM ----------

An "semi-dirty" flash worked for me. I just wiped /system and caches.
[ONE Android Development] Gawd:
Great :D

But you forgot to link my post in the OP haha
[ONE Android Development] fabio.pagliuca:
How did you manage that? I did the same thing and lost my Gapps, and had to clean flash again
[ONE Android Development] Anghirrim:
I just re-installed gapps (as they are part of the /system partition).

You still have this weird bug of a freshly flashed system not being recognized as Nougat 7.1 by the gapps package, but after a reboot, go into TWRP again and flash your gapps package.

So step by step is:

- wipe /system and caches

- flash the rom

- reboot the phone

- turn it off and get back into twrp to flash gapps

Doing so even preserves your google account setrings.

By the way, wiping system should not be necessary as the rom installation script should already wipe system before flashing. But as I was not sure if there was a "gapps survival script" in the rom zip, I just went the manual way.
[ONE Android Development] freshgiammi:
[32010.158057] type=1400 audit(1484279134.690:4545): avc: denied { getattr } for pid=18310 comm="tats_xdaedition" path="/data/local/RootToolsMounts" dev="mmcblk0p28" ino=2441219 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:system_data_file:s0 tclass=file permissive=1

[32031.990635] type=1400 audit(1484279156.523:4583): avc: granted { write } for pid=30062 comm="uncrypt" name="mmcblk0p21" dev="tmpfs" ino=7503 scontext=u:r:uncrypt:s0 tcontext=u:object_r:block_device:s0 tclass=blk_file

[32033.572938] Restarting system with command 'userrequested'.

Are you trying to decrypt/encrypt your device?

Also, it looks like one app of your is behaving weirdly trying to remount your /system partition..

lmao

Not yet, haven't managed to make it work

Yes, as always. Only major releases are advised to be clean flashed.

Thanks, I knew about this issue but my cables can't reproduce it. Got no reports so I thought it was fine.

Could you test a boot.img if I sent you one?

oops, I did! Thanks, i'll update it!
[ONE Android Development] Anghirrim:
Of course. Could the use of Arise Sound System impact it?

Thanks
[ONE Android Development] LucentBirch:
Any way to tell which app it is?
[ONE Android Development] freshgiammi:
Nope, should be kernel related.

boot.img is attached here, let me know if it fixes your issue

Hmm, name is not displayed... "tats_xdaedition" is all I know. Probably a Root app that comes from XDA. Do you have any? Otherwise your log looks clean.. It's not a forced reboot, it's more user induced...
[ONE Android Development] LucentBirch:
The only app that has xdaedition in the apk name that I install is BetterBatteryStats -- that must be where the s"tats" is coming from...Weird...I wonder what's happening there...
[ONE Android Development] Anghirrim:
Ok, I'll flash it and test later today.
[ONE Android Development] freshgiammi:
Yeah, weird indeed since I use it too.. Try removing it, and let me know if the reboot persist. Also, were you doing something in particular when it happened?

Technical side:

It looks like BBS opens "RootToolsMounts" (Never heard about this file..) which somehow tries to /system remount, which then triggers the service "clear-bcb". All of this tries to encrypt/decrypt the device.. and remounts some partitions (Should be radio, /system and recovery) But since encryption is broken, it just dies and reboots.

Why is it trying to encrypt, tho.... it's beyond me. The logs don't tell much. Probably SELinux Enforcing would block this, but I don't have the policies ready yet.
[ONE Android Development] Anghirrim:
[MENTION=4986658]freshgiammi[/MENTION]

Your boot.img fixed the jack issue for me.
[ONE Android Development] LucentBirch:
K removed. We'll see what happens. I was doing something different both times. First I was using Google now to get screenshot and the second it was just mounted on my dash as I was driving. Screen was off.
[ONE Android Development] judytankgirl:
Hi, I just wanna know if high frame recording 120fps is working. And can I use microg with this rom? Thanks.
[ONE Android Development] se7enlyn:
Yes working for 720p
[ONE Android Development] myshakugan:
It doesn't work at 120 fps, as of now it only works at 60 fps and 720p. The 90 and 120 fps options don't work in my case.
[ONE Android Development] fabio.pagliuca:
I'm getting this kind of messages in the logs, what could they be? Should I worry about them? [MENTION=4986658]freshgiammi[/MENTION]
[ONE Android Development] freshgiammi:
Nice, I'll add it to the next build. Thanks for testing!

Weird indeed. BBS seems to be what triggers it. Keep me updated.

I guess you shouldn't be. That's a qualcomm blobs that we've been shipping since launch.

I managed to get HFR(Slow-mo) to work at 90fps and 120fps, but i guess that 60fps is still borked. It doesn't slow down. I guess not, but was it the standard behavior? (i.e if I record a 10 sec video [MENTION=7825661]60fps[/MENTION] it is 10 seconds long, but if i do that @90/120Fps it is longer.)

Also, it looks like I broke HSR@120fps... Or my brain is playing with me and it's not working even in the latest build?

Also, I've managed to get the HAL to work without blobs, so now we're building it directly from sources, allowing us to do customizations and stuff. First job I was able to get done is to update our HAL to match the new libstagefright hardening, thus removing the reverts, patches and workarounds needed in frameworks/av.

Take that CM/Color OS blobs, how does improved security sound to you?

Hope to get a build up before 20 Jan., but I can't assure. Need more time to test.
[ONE Android Development] rshbhghelani:
does someone else notice this: hardware keys do not seem to be completely disable when on screen keys are enabled.

I mean clicking home/back/menu doesnt do anything, but if you are touching any of the capacitive buttons and simultaneously try to perform any touches on the screen, it doesn't register the on screen touch, most probably meaning the hardware keys are not really disabled.
[ONE Android Development] se7enlyn:
[MENTION=4986658]freshgiammi[/MENTION] just heard about the quakes in Italy, hope you are alright:good:
[ONE Android Development] Gawd:
Can confirm this
[ONE Android Development] myshakugan:
HSR at 120 fps doesn't work in the latest build, at least not in my case. Regarding the slow-mo at 60 fps, I don't remember the standard behaviour, but I think it did slow down.

On another note, anyone noticed that when you open an app and press home button to return to home screen, there is a slight pause before you're returned to the home screen? I don't think this was present in the previous version.
[ONE Android Development] freshgiammi:
I'll look into it. What's the behavior of other roms?

Yeah I'm fine thanks, a bit scared but I'm at a safe distance from the quake. Got a few friends there tho, but they said that it's all okay. Sadly, there's a lot of snow everywhere and they can't move.

Thanks. That means that so far, i've fixed half of HFR features... better than nothing.

And I get no pause here. Everything is smooth as always.
[ONE Android Development] Gawd:
Smooth as liquid. Keep up the good work :D
[ONE Android Development] myshakugan:
I'll try another clean flash then, probably will solve the slight lag I have. Thanks.
[ONE Android Development] anbinhv:
new build is up silently and I'm the first who download!

Thank you very much dev @ freshgiammi!!!
[ONE Android Development] rshbhghelani:
I can speak for COS and Sultan's CM13, where this issue was not present. I generally watch YouTube and hold the phone from the bottom chin. That's how i noticed this is a problem here.
[ONE Android Development] shubham1120:
Just an FYI for f2fs users.

/system ext4. /data and /cache on f2fs, twrp says no OS installed. So I guess f2fs doesn't work??

Man missing out on a lot of roms due to f2fs.

Thanks anyways to developer. Will definitely try this rom when I switch to ext4
[ONE Android Development] fabio.pagliuca:
If I remember correctly, try to boot it anyway, should boot fine (at least that's what I experienced with other Roms)
[ONE Android Development] arfasyrf:
When they said no os installed, just reboot the recovery. Nothing wrong there. Dunno if the latest zip works with f2fs. 2 build before the latest, it got stuck on oneplus logo on f2fs
[ONE Android Development] myshakugan:
Figured it out, turns out pixel launcher slows down after a while of use. Using the stock launcher now, no signs of lags or anything like that anymore.
[ONE Android Development] freshgiammi:
I hope you didn't flash it. It's a broken upload that got stuck, resulting in a 33mb zip file.

That's why you wait for official releases.

I won't even look into stuff that CM has, sorry. Too many dependencies, their rom is ****ed up, you can't use almost nothing without a huge rewrite due to dependencies in their custom sdk and vendor repos...

Also, my HW switch implementation is the one from AOSPA, which should be similar (if not the same) to OxygenOS.

Gonna check if I left out something, but that should be the behavior in OOS. And if that's the case, I guess i'll leave it the way it is.

That error comes up even with /ext4, you can reboot safely.

Was your /system on EXT4? F2FS isn't supported there. Also, please give me logs so that I can fix that at least... I can't put my device on f2fs.

Weird, I've got Pixel since first build and everything is at full speed. Still happy it fixed it for you tho.
[ONE Android Development] darjwx:
The behavior is the same on every other ROM I have tried. When you disable hardware keys, if you press one doesn't do anything, but the screen doesn't recognize the touch while doing it.
[ONE Android Development] se7enlyn:
I'm using the TWRP flashed pixel launcher and there isn't any lag. OTOH, nova launcher lags a bit compared with the pixel launcher.
[ONE Android Development] rphlfjrd:
It's like that for other roms for me as far as I can remember.
[ONE Android Development] rshbhghelani:
I can understand. Thanks for prompt replies though. As I see from others' comments, seems like the issue is present in other roms as well, so maybe its just the implementation of this feature that is faulty for this device.
[ONE Android Development] arfasyrf:
Yes, my system is ext4. Cannot give you a log since i format my data and cache back to ext4. Sorry. Everything is working perfectly now though. So good job!
[ONE Android Development] Gawd:
Nope

No "this feature is NOT faulty for this device".

It works perfect on other ROMs, CM based as well as AOSP.

[MENTION=4986658]freshgiammi[/MENTION] please look into this whenever you have time, this could be solved.
[ONE Android Development] rphlfjrd:
Granted I haven't flashed and tried ALL roms out there, almost ALL AOSP-based roms I have tried since Marshmallow had this problem.
[ONE Android Development] Gawd:
"Almost"
[ONE Android Development] rphlfjrd:
¯\_(ツ)_/¯
[ONE Android Development] Gawd:
▕▔▔▔▔▔▔▔▔▔▔▔╲┈┈

▕╮╭┻┻╮╭┻┻╮╭▕╮╲┈

▕╯┃╭╮┃┃╭╮┃╰▕╯╭▏

▕╭┻┻┻┛┗┻┻┛┈▕┈╰▏

▕╰━━━┓┈┈┈╭╮▕╭╮▏

▕╭╮╰┳┳┳┳╯╰╯▕╰╯▏

▕╰╯┈┗┛┗┛┈╭╮▕╮┈▏
[ONE Android Development] myshakugan:
Another correction, turns out it was slowing down due to the google calendar widget. Figured it out when the stock launcher was slowing down too. Haha. ?
[ONE Android Development] dragsterman:
Sorry for the n00b question, but what does actually mean that you managed to get the HAL to work without blobs?

So, we can use CM camera blobs with Sultan's HAL and for example have 1080p@60fps HSR mode? Or have a ROM with CM blobs and use Sultan's anti-shake algortihm?