yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] thex2:
Thank you for your work. The ROM is awesome all around. One question though. Is there a way to modify the notification screen to make items more compact? For example, if I receive 4 emails through gmail, and I drag down to expand it, it takes up the entire screen. On my old ROM, CM 13.0-2016-08-18, Marshmallow 6.0.1, it had it really compact. Also, there is a decent amount of lag/skipped frames when expanding the notification as well. Wasn't sure if there was a way to disable the new look and go back to my old CM 6.0.1 look? Thanks.

Left is crdroid, Right is CM

https://i.imgur.com/ix5AVHw.jpg

EDIT: Also, on a different matter, I cannot access my USB OTG through ES File Explorer or Titanium Backup, but I can access it through my navigation bar drop down, where it's under "Android System" and it lets me click "explore" to go explore the drive. I've verified root with Root Checker. Magisk also shows Titanium Backup and Stickmount as Permant SuperUsers. Magisk has issues when the USB drive is plugged in and freezes to where the OS asks me if I want to wait or force close Magisk. I'm wondering if this ROM has another root/superuser app that's fighting with Magisk or Stickmount? Any help on this would be appreciated. Thanks.

EDIT 2: Additional info that may or may not be relevant. Magisk log shows 112 "Grants" to Stickmount for superuser access over a 7 minute time period of me playing around trying different things to see if I can get it working. One thing I tried was telling "Android System" in my notifications menu to eject the USB, while Stickmount still had it mounted. That didn't work either. I then tried to eject through Stickmount and then re-mount it, without unplugging the USB drive, to prevent the "Android System" from re-mounting it. That also wouldn't allow me to access the USB drive through ES File Explorer or Titanium Backup.

Additional Info: installed ROM yesterday after wiping everything except internal data. ROM is unencrypted on Nexus 6.
[Nexus 6 Android Development] Otakulad:
Anyone able to get Netflix to work? I downloaded from the Play Store and APK Mirror and both will not start the app. I was getting an error message saying that it can't start and needs to restart or device failure. Additionally, when I rebooted my phone, it would crash and reboot itself after about 30 seconds.

I had to go back to Stock since I need my Netflix.

I do want to say that it looks like you did a great job [MENTION=3795148]neobuddy89[/MENTION] based on the other comments. I look forward to trying the next build. Thanks for continuing to support the Nexus 6.
[Nexus 6 Android Development] Arju:
do this: https://xdaforums.com/showpost.php?p=73728895&postcount=73 and netflix will work.
[Nexus 6 Android Development] vinnyz007:
Sorry if i am being an absolute idiot, but I did everything as mentioned in the OP and I can't seem to get past the Checking for Updates screen. Can someone please help.
[Nexus 6 Android Development] Yasharkhan:
It takes a good 5-10 mins, wait for at least 10-15 mins, and if it doesn't move forward, clean flash the Rom again
[Nexus 6 Android Development] vinnyz007:
I did wait till about 10 mins and kind of gave up. I will reflash the ROM and try again. Thanks for the info. Oh! and I forgot to mention "Updates stopped!" popped up while this was happening.
[Nexus 6 Android Development] MrBrady:
Flashlight is working in my install, when activated from the Quick Settings.
[Nexus 6 Android Development] AlexX-DE:
Flashlight is 100% working
[Nexus 6 Android Development] buschris:
good to see you working on this! Great ROM. Rocking cr on my Nexus 7 tab
[Nexus 6 Android Development] neobuddy89:
Bluetooth sleep probably fixed for next release. *fingers crossed*
[Nexus 6 Android Development] AlexX-DE:
very good battery life [MENTION=3795148]neobuddy89[/MENTION]! Thank you
[Nexus 6 Android Development] neobuddy89:
Fix confirmed. Yay. I should be sleeping now.

Should go for update tomorrow... Let's see.
[Nexus 6 Android Development] dramalicious:
Looking to make it Ddriver :)
[Nexus 6 Android Development] kidhudi:
has anyone been successful in installing the google phone/dialer app with the search feature?

i tries 3 and all force close.

thanks
[Nexus 6 Android Development] Aerys:
Same error. Tried installing from play store and apk.
[Nexus 6 Android Development] Akhilesh S V:
Apparently Google Phone doesn't work on N6 O, so try patched Google Dialer

https://xdaforums.com/android/apps-games/app-google-dialer-t3557412/page101
[Nexus 6 Android Development] fzcdfz:
Good Job, I've got to say.

Haven't found anything not working but Trusted Face (Smart Lock) It keeps FC (while being about to record face)

Also there's a serious problem which is the battery.

Almost 70% gone within 6 hours.

Anyway it's a great ROM but still have problems. Looking forward to the coming realise.
[Nexus 6 Android Development] def1003:
i haven't dove in yet but damn thanks for your hard work work neo porting oreo to our beloved nexus 6!
[Nexus 6 Android Development] sms2000:
Installed on clean. Did not take 15+*minutes, finished after just a couple of.

Every hardware element works as promised (didn't test video recording).

The ROM never goes to Deep Sleep when BT enabled. When disabled - it does enter Deep Sleep.

AFAIU this behavior is expected with the current BT driver.

Trusted Face does FC. OK, not a big deal for BETA.

I have two questions for the esteemed community if you please?

1) Is it possible to set SELinux enforced?

2) How can I unlink Notification volume and Alarm Volume? I prefer to set it separately.

Thanks
[Nexus 6 Android Development] mrk2815:
heres my question will we still have to use those unofficial open gapps oreo, or will there be a fixed open gapps for oreo or bean gapps that will work eventually for oreo for our nexus 6. its just a question and no rush to do so. just wondering.
[Nexus 6 Android Development] AlexX-DE:
Use the recommend gapps: https://androidfilehost.com/?fid=745425885120757579
[Nexus 6 Android Development] Myself5:
1) in order to get BT working, the way Android/the drivers talk to the hardware has been changed (It's using IOCTL calls now). That fix is the cause for the wakelock and I havn't been to look into it yet, but I'm happy to see that [MENTION=3795148]neobuddy89[/MENTION] might have fixed it already.

2) TrustedFace is part of the GApps, so it shouldn't be a ROM issue.

3) Yes, but not yet. There were a lot of SELinux changes between N and O, and the devicetrees need yet to be adjusted for those. Thats always done last after all things work (so basically its the next and final thing to take care of in case of shamu). However, if you'd set it to Enforced now (without fixing remaining denials), there will be issues.

4) Thats a ROM feature, so I assume thats coming sooner or later.

[MENTION=3795148]neobuddy89[/MENTION] knowing that its a kernel wakelock, and assuming that this is not what fixed it, can you link me to the fix please :P ? would be awesome.

EDIT: You said DT2W doesn't work for you, but its working fine here without any mandatory changes that I am aware of. The only thing I could imagine is the powerhal binder adaptions I did. Check them out:

https://review.carbonrom.org/#/c/2797/

https://review.carbonrom.org/#/c/2798/
[Nexus 6 Android Development] sms2000:
I used "su -c setenforce 1" from Terminal and apparently it did set Enforced. But in Settings SELInux is still Permissive.

It's OK for now.

I'm pretty satisfied how it goes with Android 8 in 32bit domain, N6 especially. Many compliments to all out hardworking devs.
[Nexus 6 Android Development] neobuddy89:
The BT fix lies in the kernel. The commit you linked here is general clean up of BT that we don't require. Yes, I understand what you said about IOCTL. I even tried porting hci_bcm driver from 3.18 - but that requires more backport. So, existing drivers have been worked upon and BT sleep works. But I ran into another issue where my voice couldn't be hear on the call - something in fix broke call. I should be able to upload proper fix tonight once I am home.

Cheers.
[Nexus 6 Android Development] neobuddy89:
Enforcing not recommended. There are tons of denials which need to be fixed else it will affect functioning of the ROM.
[Nexus 6 Android Development] Myself5:
Awesome! Let me know if you need any help. So do you still use the IOCTL way or did you use a completely different fix for bluetooth?

The voice issue sounds more like some audio processing issue to me.
[Nexus 6 Android Development] tarsaljungle:
Flashed this rom yesterday night, feels great to have android O on my nexus 6, I'm using this phone as my daily driver but I don't really mind minor bugs. That being said I haven't encountered anything bad yet (I barely use Bluetooth) and the rom was smooth straight away for me and I will be reporting bugs if I get them. Great work devs!
[Nexus 6 Android Development] sms2000:
Yes, particularly BT will not work. Verified.

I use my Nexus for development and some apps require Enforced.
[Nexus 6 Android Development] fzcdfz:
I got the same problem
[Nexus 6 Android Development] gothy.gothy:
Go to Developer options and disable "Mobile data always active" It's a bug already known by Google
[Nexus 6 Android Development] fzcdfz:
I'll try. Thank you!;)
[Nexus 6 Android Development] athulele:
I'd already disabled that. Still having that problem.
[Nexus 6 Android Development] andrewjt19:
Does anyone know if Ok Google features are working? Thanks so much for the love to our beloved N6
[Nexus 6 Android Development] neobuddy89:
Ok, so here's what I am doing. I am porting Runtime Auto PM support for msm_serial_hs driver from CAF upstream. Nexus 6P uses bcm4358 and we use bcm4356 - so by taking care of DT, this works. However, seems to me serial driver is used by mic as well (yet to find hooks in driver, I believe hooks are in DT?) - with Runtime Auto PM, BT sleep, BT connection - works very smooth but breaks audio. Perhaps, you can have a look:

https://github.com/neobuddy89/shamu/commits/bt-dev

The commits in the end by Motorola folks are for testing - can be avoided as not present in angler. Cheers.

EDIT: I think BT SLEEP driver is useless now since /proc path is not used...
[Nexus 6 Android Development] Myself5:
Hum, I still wonder whats easier. Using the IOCTL workaround and fix the wakelock, or trying to figure out why BT is crashing when using PROC. Angler is still using proc on Oreo, so there has to be a fix for the issue.

EDIT: I experimented around with some of your commits. Got everything working, including InCall Audio and everything else, with deepsleep still working successfully.

All I did was pick your BT commits from yesterday up to this commit: https://github.com/neobuddy89/shamu/commit/258ffa5151a96d49429e5e1f2525bdff6cbdec4d

( also had to pick fs: Add TTY PM IOCTLs to compat table, but you had that already)

Cleaning up the uneeded part (which would be HCI_IBS) to see if it still works afterwards.

Anyways, great work you did :)

P.S. I also noticed that, during my last kernel rebase, I ****ed up the CONFIG_BT_HCIUART flag (I accidentally commented it out), which lead to the conclusion that its not required for some reason, although my previous tests always led to that flag being necessary.

EDIT2: I got rid of all the HCI_ISB commits (so all that I picked is https://review.carbonrom.org/#/q/st...ernel_moto_msm+branch:cr-6.0+topic:btwakelock) and kept HCIUART disabled, BT works and Deepsleep is working fine (even with an headset connected, so I'd assume the same qualifies for Smartwatches).
[Nexus 6 Android Development] neobuddy89:
Wow. Can we safely disable BT_SLEEP driver?

One quick brainstorm --- we use Port 3 of UART for bluetooth, right?

So this

#define HS_UART_0 0

should be

#define HS_UART_0 3

https://review.carbonrom.org/plugins/gitiles/CarbonROM/android_kernel_moto_msm/+/72a383225f1dd11a4591db00208e0c1ef7b9918d%5E%21/

https://github.com/neobuddy89/shamu/commit/7ed4dfc904351fb60bbae6332826f9ce14d5e481

Cheers.

EDIT: I know HCI_ISB is useless -- it was experimental.

EDIT 2:

You should try patches till

msm_serial_hs: Modify the PM ioctl

EDIT 3:

https://github.com/neobuddy89/shamu/commits/bt-dev-2

https://github.com/neobuddy89/shamu/commit/a89027d11e99296280b83fa2c5f7c326bb567e91
[Nexus 6 Android Development] Myself5:
I'm fairly sure we never used bluesleep (see N sources), only MSM_BT_SLEEP, which is still enabled.

Also, as per google configs, we use UART 0.

If we're having it working now though, why would we want to pick additional commits to msm_serial_hs now? For completeness? I'd suggest to slim it down as much as possible and only use what really fixed the issue (I'm strongly suspecting your Handle UART clocks commit).

EDIT: If you want we can chat on hangouts for easier communication, my email is myself5@carbonrom.org
[Nexus 6 Android Development] vinnyz007:
Fixed.

Edit: I finally fixed the issue. I clean flashed the rom again and booted the device up. Then flashed the open gapps unofficial in the link and booted it up. Installed google framework apk, google play services apk, google account manager apk, google contact sync apk from a 3rd party website and all is fine now. The rom is very usable now and is my daily driver until something new turns up. Thanks for the help everyone .
[Nexus 6 Android Development] neobuddy89:
Thanks for UART heads up. That helps. :D

I am all in for slimmed down part. But since we are porting from angler, I think we should port with complete set. (i.e. excluding reverted parts.) Let me test new build - I will push slimmed down version to my new branch in few hours.
[Nexus 6 Android Development] Myself5:
Ah good point. should probably pick all of the angler stuff then indeed.

As said, hit me up on hangouts if there is something I can help with, I'll look into the pain that is SELinux denials now, as that seems to be the last missing piece of the puzzle.
[Nexus 6 Android Development] neobuddy89:
Already added. Cheers.

There are more missing bits, I will message you.
[Nexus 6 Android Development] mrk2815:
neobuddy, i am a blind flasher of custom roms.i have used twrp through command line using linux box and orca screenreader to flash this rom the way that you have suggested in OP . but when i start up the rom an then accessibility services, the accessibility services hangs with this rom and i cant go further unles i have someone sighted help me out. i have not experienced this with any other roms that i have flashed in teh past but i figured i would let you know so when the time comes you could fix this as well. so tha i can have accessibility services come up an then talkback which is part of the accessibility service. this has been documented and fixed in lineage commits and since this rom most likely be based off the lineage commits i figured i would let you know about this for final merged changes when you do have this in beta 2 or 3 of this rom. i dont mind flashing roms and figuring out whats wrong with them as a blind long time flasher of roms. So please if this could be given consideration i would truely appreciate it. I can then give you further feedback on how to improve things for the rom going forward.
[Nexus 6 Android Development] dparrothead1:
Hello??? Anyone in here????
[Nexus 6 Android Development] fzcdfz:
I have used this for days and everything seems work except trusted face, but maybe that's the gapps issue. Battery optimization is good, after turning off the"Mobile data always active" in developer options and the Bluetooth - yeah the battery runs out rapidly with Bluetooth on. Anyway this is a great ROM.
[Nexus 6 Android Development] dramalicious:
I.m waiting for a more polished build and than will be a daily driver :)
[Nexus 6 Android Development] enzoevo:
Next release sounds like it's going to be good enough for DD. Fingers crossed. Awesome work devs.
[Nexus 6 Android Development] cpnfantstk:
Appreciate what the developer is doing here. Lot of time and effort I'm sure. I also appreciate the devs patience with questions posted in this thread. Not being nitpicky and overly sensitive on what is posted or asked. I think most members have good intentions and are trying to help the process. Hopefully we can do this Dev right and provide LOGCATS to any bugs that we find. That's the only true way to help him further along in this. Thank you for bringing Oreo to our ? Shamu.
[Nexus 6 Android Development] neobuddy89:
Hey all,

Thanks for the patience. Appreciate that. I have been testing several stuff over the weekend and just to make sure what I am doing makes impact - I do clean build to personal test builds most of the time which takes nearly 2 hours.

It's good connect with [MENTION=3816568]Myself5[/MENTION] . Luckily, the BT deep sleep fix works for him without any side effect (unlike us). And to add on, the compress offload audio does work on Carbon beta which he posted while ago. The logs from crDroid beta for this crash is not helping much and I am checking at different levels what could have gone wrong.

There has been some progress and I am able to contribute missing pieces to the community slowly but will be able to post a new beta version when either of BT deep sleep or compress load audio gets fixed properly.

Reference - https://github.com/neobuddy89/android_device_moto_shamu/commits/lineage-15.0

Cheers.
[Nexus 6 Android Development] neobuddy89:
<< Removed >>
[Nexus 6 Android Development] DreamFX:
Maybe I'm just really sick and it's really late and I'm on too many meds. But did you by accident upload 9/10s beta 1 build again and post? File name and MD5 are the same.
[Nexus 6 Android Development] neobuddy89:
OOps... Re uploading new build. Damn.
[Nexus 6 Android Development] DreamFX:
Thank you we appreciate it. :good:
[Nexus 6 Android Development] mrk2815:
neo buddy, just wondering if you could see if the accessibility services works with the new build that you will be uploading soon. i want to flash this build but i want to make sure that the accessibility services set up wizard does work with accessibility service in mind as it was pointed to you in the lineage commits which i have a feeling that the rom is based on based on the reading that i was doing on CR droid. Is that correct. if so can that please be looked and made sure that the accessibility services do work as far as the rom when you have a build working. i am willing to try and to help you out.
[Nexus 6 Android Development] neobuddy89:
Please do elaborate what's broken (steps on how-to), I can check and revert accordingly. Thanks.

@ others:

Hang on... couple more mins... my upload sucks. Cheers.
[Nexus 6 Android Development] neobuddy89:
Patience pays off! Ready for some more goodness?

Here is new Beta build!

Beta 2 Release Notes:

* Fixed compress offload audio for Shamu

* Fixed BT deep sleep issue for Shamu

* New shiny blobs from NGI55D for Shamu

* Kernel security patches till Sept 2017 for Shamu

* New LED colors for notifications for Shamu

* Fixed keyboard swype/gesture

* More longpress-key shortcuts in keyboard

* Removed crDroidOTA (it's needs more polishing and bring up)

* Thinner and better Navbar

* Faster boot than Beta 1

* Added crDroidSettings placeholder in Settings

* Optimizations

I will share more detailed notes on my take on this build later. For now, this is it! Take it and profit. Thanks to @Myself5 for quick tip where to check compress audio failure.

There are new Bluetooth fixes altogether - bit different than one used in Carbon Beta. So, test out and let me know how it goes.

Installation steps remain same as that in OP. Clean flash recommended but not necessary if on Beta 1. Cheers.

DL: https://www.androidfilehost.com/?fid=961840155545596919

P.S. Never upload when you're sleep deprived.
[Nexus 6 Android Development] neobuddy89:
Not sure on this but no constant crashes in clean build. Likely to be gapps crash. Use one provided in OP. Will see how we can tame gapps going forward.
[Nexus 6 Android Development] sms2000:
I used the Gapps from the OP. Going to play around a little more and reflash clean if not succeeded.
[Nexus 6 Android Development] Yasharkhan:
Great rom man, is there anyway you can add Ambient tuner in system ui tuner?
[Nexus 6 Android Development] neobuddy89:
Features will come in later.
[Nexus 6 Android Development] Yasharkhan:
I dirty flashed beta 2 on beta 1,its still showing August security patch,,,
[Nexus 6 Android Development] neobuddy89:
I meant kernel has September security patches. Not ROM itself, not yet.
[Nexus 6 Android Development] Myself5:
Be aware that backuptools is broken as of now, which means you need to flash the GApps again after the ROM.
[Nexus 6 Android Development] Yasharkhan:
Face unlock not working, gapps installed it and it opens but force closes before setup
[Nexus 6 Android Development] Intel_ins1de:
Dirty flashed, first boot lags then all ok.

Nice job! Waiting crDroid features.
[Nexus 6 Android Development] neobuddy89:
I don't expect anything related to gapps work at the moment because all gapps so far are unofficial addendum. Also, this seems to be gapps issue of compatibility - I suppose.
[Nexus 6 Android Development] EternalFlame:
Sry to ask but that means BlueBorne vulnerability is fixed?
[Nexus 6 Android Development] neobuddy89:
Yes.

Issue: https://access.redhat.com/security/vulnerabilities/blueborne

Fix: https://github.com/neobuddy89/shamu/commit/06a014258989f43bf659d3ec1d75a3faecadd080
[Nexus 6 Android Development] athulele:
Great work, runs smooth and fast.

Dunno if anybody else noticed this but enabling MSM Limiter or Per-Core control in kernel adiutor mod keeps the CPU active at higher frequencies (>1GHz). Not really a big deal at all.
[Nexus 6 Android Development] neobuddy89:
Msm limiter will do what you configure. It's only job is to check mix max freq and gov tunables for each core during suspend and resume.

If you bring down max freq on one core - load will increase and thereby CPUs will be in higher freq state for longer amt of time.

This can be discussed in sigma kernel thread.
[Nexus 6 Android Development] athulele:
On LineageOS 14.1, I used msm limiter with per core control and set the cores to 2.4ghz, 2.2ghz, 1.9ghz and 1.7ghz resp.

and on idle state, all used to drop down to 300Mhz.

But on oreo, all cores stayed above 1ghz even when idling.
[Nexus 6 Android Development] andrea.under:
Do you know if substratum works fine?
[Nexus 6 Android Development] EternalFlame:
Ye i'm using SwiftBlack theme, all good.
[Nexus 6 Android Development] pmontu:
Is AdAway working it was not working on beta 1
[Nexus 6 Android Development] saintmonte:
Perfectly working with this rom
[Nexus 6 Android Development] EternalFlame:
Like a mofo, switched the preinstalled apk with this one "AdAway-release_Build-Nov.19.2016" and flashed "AdAway_systemless_hosts_v2.zip" via TWRP tho.
[Nexus 6 Android Development] Lagarde:
Anyone know if this ROM is working with Google Fi wifi calling? Didn't see it in the list of features.

Edit: Tested. Appears to be working after some tweaking of permissions.
[Nexus 6 Android Development] tembares:
Do you find that beta 2 is ready to be used for daily use?
[Nexus 6 Android Development] dictionary:
Everyone's daily use is different. Best way to find out is to flash. ROM may be stable, but everyone had different tolerances when it comes to daily use
[Nexus 6 Android Development] Yasharkhan:
Can any guy who knows how to edit systemui.apk add ambient display in system ui tuner using this guide?

https://www.google.com.pk/amp/s/www...google-pixel-2-always-on-ambient-display/amp/
[Nexus 6 Android Development] Lagarde:
Few minor issues:

- Getting some interesting double-reboots. If I ask it to reboot, it does, gets all the way to the desktop, then reboots again. Happens every time. Works fine after that.

- Google Phone doesn't work, only the one from Gapps. The Gapps one doesn't have all the features of the store one, but if I install the store one, it crashes constantly.

- Random wifi disconnects. Doesn't happen often, but when downloading apps, it sometimes drops wifi and immediately reconnects.