yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Developer Discussion [Developers Only]] zelendel:
He is wrong. The sdcardfs is a file system for sdcard enabled devices. Nothing to do with the nexus 6. It was even removed in most other builds for the device. The only people that added it were people that didn't understand what they were doing.
[Nexus 6 Developer Discussion [Developers Only]] Strephon Alkhalikoi:
Late reply here. :)

I have tried MicroG before - on a custom Galaxy S4 ROM - and I like MicroG about as much as I like Xposed. If MicroG is required I won't be upgrading.
[Nexus 6 Developer Discussion [Developers Only]] zelendel:
People are not gonna do that. Microg is known for causing its own issues.
[Nexus 6 Developer Discussion [Developers Only]] wrongway213:
It's been confirmed that gapps for arm are working since I posted that, so it's a moot point now, thankfully.
[Nexus 6 Developer Discussion [Developers Only]] Lawstorant:
Oh mate, you're so wrong. SDcardFS is a virtual FS for emulating /sdcard/ (/storage/emulated/0) and EVERY android device has it. It's just a replacement for vFAT (virtual FAT). One of the most important fixes is that the file timestaps won't get corrupted anymore (this bug existed in android for years).
[Nexus 6 Developer Discussion [Developers Only]] luciusfox:
vfat is a real filesystem for block devices. Think of it as being in between FAT and FAT32. What it adds over FAT is a virtual file NAMING convention in order to exceed the standard "8.3" filename format that FAT was stuck with. vfat is also the NAME of the linux implementation of FAT (FAT12, FAT16), VFAT, and FAT32.

What you are thinking of as being present on "EVERY" android device, is this; https://android.googlesource.com/pl...197870433386fb809d34b58b30fc0/sdcard/sdcard.c

You should pay attention to the README section of it starting at line 32.

When Android devices used to have an actual sdcard, it was formatted using vfat (the linux implementation of FAT32), with a mount point of /sdcard.

When they stopped including real sdcards, they started emulating sdcards using that FUSE simulated vfat I linked to above.

Now what sdcardfs is, is (a) a replacement for the FUSE filesystem I linked to above, and (b) a replacement for FUSE itself. Think of it as a scaled back and simplified FUSE+sdcard.c. The problem with FUSE is that it is too complex and with too high of an overhead. It causes performance degradation. And I'm not talking about the general userspace degradation that you would get with, for example, NTFS-3g compared to a native implementation, but rather the sdcard.c adds some problems because it is actually *abusing* FUSE. FUSE isn't designed or intended to wrap one filesystem with a simulation of a different one. FUSE is intended to actually implement a filesystem proper. What that means is that the kernel performs certain filesystem operations on the FUSE filesystem, which calls back to essentially perform the same operations on the base filesystem (ext4). Double the operations. Also double the caching, which is horrendous because it means that you are storing the same cached file in RAM twice. That is the kind of thing that sdcardfs is intended to solve.

Now personally, I completely disagree with this approach. Sdcardfs (as with FUSE+sdcard.c) is a backwards compatibility layer that really should be removed altogether. Instead, access controls to the data really should be by way of ACLs. Yes, this will break some very old software, but its the right way to move forward.
[Nexus 6 Developer Discussion [Developers Only]] luciusfox:
Well, the first thing that stands out is this;

03-13 02:38:08.029 0 263 W VendorServiceManager: failed to open binder driver /dev/vndbinder

Indeed, the factory kernel does not have any such driver. This is probably something related to "Project Treble", which is supposed to make it simpler to update the android platform while leaving the *vendor* platform unchanged. Sounds like this driver will have to be added to the kernel.

https://android-developers.googleblog.com/2017/07/shut-hal-up.html

There is also this, which happens immediately before the SIGABRT for surfaceflinger:

03-13 02:38:09.975 298 298 F Gralloc2: gralloc-mapper must be in passthrough mode

Mapper::Mapper()
{
mMapper = IMapper::getService();
if (mMapper == nullptr || mMapper->isRemote()) {
LOG_ALWAYS_FATAL("gralloc-mapper must be in passthrough mode");
}
}

That gralloc issue could be a consequence of the vndbinder issue.

Hmm... https://github.com/SiXROM/platform_device_moto_shamu/commit/86ebb7db1b0a23c4d0a09568a6414d3b9f140596

Note that their changes to the BoardConfig.mk are bogus, none actually apply to this hardware. But the additional PRODUCT_PACKAGES are possibly meaningful.

Might try a build using these three projects;

<project path="device/moto/shamu" name="platform_device_moto_shamu" groups="device,shamu,broadcom_pdk,generic_fs,pdk" remote="sixoreo" revision="oreo" />

<project path="kernel/moto/shamu" name="platform_kernel_moto_shamu" groups="device,shamu,broadcom_pdk,generic_fs,pdk" remote="sixoreo" revision="oreo" />

<project path="vendor/moto" name="platform_proprietary_vendor_moto" remote="sixoreo" revision="oreo" />

sixrom has also made a whole lot of other changes, but I suspect that they are more related to customizations rather than actual device functionality.
[Nexus 6 Developer Discussion [Developers Only]] kkozma:
I had seen the vndbinder thing the other day and added it to the kernel I'm using. I actually had it booting yesterday, but managed to hose it up trying to fix bluetooth and then ended up losing my boardconfig.mk and device.mk so I have to start over on those two.

I actually tried building with that sixrom repo and it wouldn't boot at all. I suspect it's because it's based on Lineage whereas mine is straight from AOSP.

Getting ready to play around with it some more, hopefully I can get back to a booting rom again!
[Nexus 6 Developer Discussion [Developers Only]] luciusfox:
How do you lose your make files? Did you forget to commit them to your git?

Commit often, ESPECIALLY when you have things (anything) working.

Then if you bugger it up, just roll it back, of git diff it to see what you changed.

I don't see any evidence of sixrom being based on anything besides aosp (certainly not lineage/cm)

Take a peek at their manifest, there's a few frameworks that they've messed with, a bunch of applications, but its mostly AOSP;

https://github.com/SiXROM/manifest/blob/oreo/default.xml
[Nexus 6 Developer Discussion [Developers Only]] kkozma:
Yeah, that was a real derpasaurus moment for me there, but I'm back to a bootable situation. :D

- Bluetooth is still broken

- No Cellular Radio

- WiFi connects but causes a reboot immediately

- Not able to view anything on the SD Card & Camera asks for an SD card to be inserted. Oddly enough I am able to play the music that's on my sdcard.

I'll get everything pushed up to my github later so if anyone else wants to tinker with it...

They probably haven't pushed the working updates to device to get to where they. As I said, I built directly from their repo and it didn't work at all.

Edit: my github is https://github.com/vwmofo

if you want to put together a local manifest and pull it down, feel free.
[Nexus 6 Developer Discussion [Developers Only]] luciusfox:
Huh, yeah, those first three points are pretty important ;)

For the third, which camera application? AOSP? Or Google Camera?

For RIL, might help to take a peek at what these guys did;

https://github.com/SiXROM/platform_hardware_ril
[Nexus 6 Developer Discussion [Developers Only]] kkozma:
I edited my last post with a link to my github...

Anyhoo, it's whatever camera pulls down from AOSP which worked fine when I had this booting from the preview sources.
[Nexus 6 Developer Discussion [Developers Only]] luciusfox:
With just the two repos, there really isn't the complexity needed to justify a local manifest yet.

What blobs are you using? Latest 7.1.1 from google?

---------- Post added at 02:13 PM ---------- Previous post was at 02:11 PM ----------

Yeah, AOSP camera then.

Who knows, maybe google camera will work?

But obviously RIL is the highest priority right now, probably followed by bluetooth.

EDIT: If you can get RIL working, then I can jump in. I'm working from home and don't have a backup phone, so I need to be able to do phone calls.
[Nexus 6 Developer Discussion [Developers Only]] J0SH1X:
disable sdfs and sdcard will be fixed we had exact same iusse on s6
[Nexus 6 Developer Discussion [Developers Only]] luciusfox:
Yeah, [MENTION=2658396]kkozma[/MENTION], common theme I'm seeing for everything to fix RIL;

https://github.com/TeamNexus/android_hardware_ril/commit/2ef9bae21f7078dec24d57287f1b135571da3808 (despite the repo name, this has *nothing* to do with any "Nexus" device)

https://github.com/SiXROM/platform_hardware_ril/commit/6a27b6a40e0ccec49b137d781b13c169c3e4d56f

Betcha that'll fix it.
[Nexus 6 Developer Discussion [Developers Only]] luciusfox:
Moved below the quagmire.
[Nexus 6 Developer Discussion [Developers Only]] wavedashdoc:
You are aware there is already a working 8.0 Oreo rom out there right?
[Nexus 6 Developer Discussion [Developers Only]] luciusfox:
You are talking about "sixrom", which is not even close to AOSP, and to top it off, is not reproducible.

In other words, its existence doesn't do anybody any good.
[Nexus 6 Developer Discussion [Developers Only]] wavedashdoc:
I could be wrong, but I believe the beta build out there now is AOSP since it has no extra features added. Looking at the git, that may change. I just don't want anyone to potentially waste their time if comments for already fixed things are available. Definitely appreciate the work as always!
[Nexus 6 Developer Discussion [Developers Only]] luciusfox:
They've changed hundreds of things throughout, look at their manifest.

But like I said, it is NOT REPRODUCIBLE.

So please stop burying useful posts in your quagmire.

---------- Post added at 11:17 PM ---------- Previous post was at 11:16 PM ----------

Moved to the bottom so as not to be buried in quagmire.

Unless somebody beats me to it, I'm currently uploading a test boot.img and system.img with the ril patch I mentioned above.

I'm *hoping* that ril "just works".

I don't expect bluetooth to work.

Wifi... who knows.

Else... who knows.

Note: no gapps. Please don't try installing gapps until you've done some testing on the base aosp build.

Suggestions for testing;

1) first BACKUP your boot, system, and userdata partitions, unless you happen to have a spare shamu that you don't need to actually be able to restore to its current state.

2) gunzip the images, and fastboot them as follows;

fastboot flash boot boot.img

fastboot flash system system.img

3) wipe userdata;

fastboot format userdata (or is it fastboot format data?).

4) reboot;

fastboot reboot

And see what happens.

If ril works, see if you can do a phone call with working audio.

Do a logcat and kmsg for bluetooth and wifi.

EDIT (links):

boot.img.gz:

https://drive.google.com/open?id=0B7...lNra2syMm8zY2c

system.img.gz:

https://drive.google.com/open?id=0B7...mtUZ2IzZDc0Rm8
[Nexus 6 Developer Discussion [Developers Only]] camcory:
Ive had a booting build for a while and just cleaned up my tree if anyone wants to take a peek. My only issues now are NFC and BT.
[Nexus 6 Developer Discussion [Developers Only]] luciusfox:
So correct me if I'm wrong, but I'm looking at yours, and it looks like the big thing is the ril commit, right?
[Nexus 6 Developer Discussion [Developers Only]] camcory:
Yeah the one ril commit is the only one needed for data. If you want to go the enforcing route you will need this for the sensors to work.
[Nexus 6 Developer Discussion [Developers Only]] kkozma:
Thanks!! I've got a build running now with your device and kernel. I suspect that maybe it was my kernel (modified franco) causing some issues as I applied all of those picks to the ril source and I still had no cellular. Also nuked my ccache just in case.

My machine takes about 2 hours to build, so I'll let you guys know how it goes when it's done.
[Nexus 6 Developer Discussion [Developers Only]] luciusfox:
Holy crap, 2 hours??!?!?! What is it, a laptop with a spinny magnet?
[Nexus 6 Developer Discussion [Developers Only]] kkozma:
LOL

It's an older machine, but it is/was pretty stout at the time when I built it. 6 core AMD 4ghz with 16GB ram. I used to be able to build lollipop and marshmallow in 45 minutes. I never really messed around with Nougat so I can't comment on how long that took. But it does seem awfully extreme to more than double in build time like that...
[Nexus 6 Developer Discussion [Developers Only]] Yasharkhan:
Bt is working?
[Nexus 6 Developer Discussion [Developers Only]] luciusfox:
Something must be funky with it.

My Vishara (8 core, 4 GHz) does the build in about 15 minutes.

---------- Post added at 04:18 PM ---------- Previous post was at 04:17 PM ----------

I'm not sure if he knows yet, he said it was in the process of building.
[Nexus 6 Developer Discussion [Developers Only]] kkozma:
Ok, so it booted. I still have no cellular, no wifi, no bluetooth, and no NFC. Interestingly enough BT does not crash repeatedly like it did before.
[Nexus 6 Developer Discussion [Developers Only]] camcory:
What vendor are you using. Link to your git?
[Nexus 6 Developer Discussion [Developers Only]] kkozma:
Using google's vendor. It's straight AOSP with no changes other than the RIL stuff.

---------- Post added at 12:48 PM ---------- Previous post was at 11:58 AM ----------

rebuilt with another set of vendors and I have cellular. :) Still no wifi, bt, or nfc.
[Nexus 6 Developer Discussion [Developers Only]] luciusfox:
What is the replacement vendor, and any idea what distinguishes it from AOSP? It would be nice to apply only the needed changes....

---------- Post added at 06:15 PM ---------- Previous post was at 05:59 PM ----------

Can you logcat these? Most especially the wifi and bt. Nfc is probably less important.
[Nexus 6 Developer Discussion [Developers Only]] sting5566:
First off it is AOSP and secondly the people running sure are getting a lot of good out of it.
[Nexus 6 Developer Discussion [Developers Only]] erk1725:
Running great for me:good:
[Nexus 6 Developer Discussion [Developers Only]] wrongway213:
Couple things.. SiX is absolutely an AOSP ROM first, and I am not sure what you mean by "not close to reproducible", given it has source up and all.

From the perspective of a Shamu ROM maintainer, I'm baffled by this post. The existence of this ROM has done me a lot of good in terms of preparing Oreo. This source has been frequently updated, and as I have been going through some personal issues, one being lack of WiFi or any connectivity beyond hotspot - truth be told, any question I've had has been answered.

I don't consider myself to be someone who needs his hand held - but given the personal and technical issues I've had lately, bringing up O was not the way it should have been for me. The existence of this source and the willingness of the one who created it to help me on a personal level has helped me tremendously with Shamu O. I'm very curious what makes you say its existence doesn't do anybody any good?
[Nexus 6 Developer Discussion [Developers Only]] luciusfox:
That is such nonsense that I can't even justify the time it takes to address how stupid it is.

---------- Post added at 07:07 PM ---------- Previous post was at 07:01 PM ----------

Go ahead and try building it.

Oh, it doesn't boot? Wow.
[Nexus 6 Developer Discussion [Developers Only]] wrongway213:
I can't say I've built it - if you read my post, a large part of my issues lately have been lack of internet access. That said - if it doesn't boot I don't know how those I know on the ROM are running it as DD?
[Nexus 6 Developer Discussion [Developers Only]] erk1725:
probably user error:confused:
[Nexus 6 Developer Discussion [Developers Only]] TrOjAnUK:
I am amazed you are all getting hot under the collar to someone that joined a week or so ago, you can clearly work out WHO that is.. :)

TrOjAn
[Nexus 6 Developer Discussion [Developers Only]] fkfmfz:
https://github.com/SiXROM
[Nexus 6 Developer Discussion [Developers Only]] wrongway213:
I don't come to XDA to fight or any of that, but to learn and teach, share, etc. I genuinely wanted to know why he thought the source was bad in some way, as this thread is meant to be informative. Others I know personally using the ROM have had a very different experience, so my intention is to ensure everyone is clear on the actual usefulness of the source in question. Setting technical aspects straight on a development forum should not produce adversarial results - correcting misinformation about development is the duty of any good XDA member, as I see it.
[Nexus 6 Developer Discussion [Developers Only]] kkozma:
FWIW: I'm now to the same point as SiXROM. Working cellular and Wifi, but no BT or NFC. NFC at least tries to turn on so I might be pretty close to that one...
[Nexus 6 Developer Discussion [Developers Only]] TrOjAnUK:
Nice one,

BT is a bit of a dog.. Im sure someone will get it at some point, we have tried a few fixes but no luck yet.. although, we got a few work round ideas..

Good luck with it... the race is on for BT lol

TrOjAn
[Nexus 6 Developer Discussion [Developers Only]] fkfmfz:
progress!!!
[Nexus 6 Developer Discussion [Developers Only]] Aerys:
Does anyone know what is causing the screen tearing?
[Nexus 6 Developer Discussion [Developers Only]] Yasharkhan:
Is It still happening with the latest Oreo build of Sixrom?
[Nexus 6 Developer Discussion [Developers Only]] camcory:
Maybe this probably should be this also not so sure this is needed. TARGET_USES_NEW_ION_API :=true
[Nexus 6 Developer Discussion [Developers Only]] camcory:
Wifi Hotspot

Fix hotspot
[Nexus 6 Developer Discussion [Developers Only]] fkfmfz:
Excellent!!! Thank you sir
[Nexus 6 Developer Discussion [Developers Only]] kkozma:
See that's how it's. done. Fix something and share.

Now, how'd you get NFC working?
[Nexus 6 Developer Discussion [Developers Only]] camcory:
I don't believe it is look at the beam entry states NFC is off.
[Nexus 6 Developer Discussion [Developers Only]] fkfmfz:
https://github.com/SiXROM/platform_device_moto_shamu/commits/oreo

check here the stuff from sep 04, still have a random fc but is getting there.
[Nexus 6 Developer Discussion [Developers Only]] kkozma:
Thank you! If I'm reading all of that correctly, does that mean you have everything working?

I think one of the things holding NFC back a bit is building this nfc_nci.shamu . Everything dealing with that looks to me like it's all for a different chipset than we have. When I removed it from my build, you can clearly see in the logcat that it starts up and runs. It eventually craps out with a seg fault trying to load the service.
[Nexus 6 Developer Discussion [Developers Only]] TotalChen:
Syncing the latest source, I fixed another 2 compiling problems : one caused by "Allow to doubletap or longpress power to toggle flashlight" commits，the other in SixSettings.java with logging.MetricsProto importing, and then I got it through to build an otapackge, finally.

Thanks for all your work! I'd like to dedicate my efforts to do maybe just a little help.
[Nexus 6 Developer Discussion [Developers Only]] fkfmfz:
that stuff was still being a worked on, sorry
[Nexus 6 Developer Discussion [Developers Only]] EA1DDO_SGS2:
I've installed last RC2 version first time, just for testing, and so far so good.

It is quite stable, no crashes at all.

Apart from BT, everything is working fine.

I would like to comment something for further checks, the WiFi behaviour is weir, mostly on 5Ghz band.

On 2.4MHz band seems to work as usual, but when I try to connect on 5GHz band, not always is getting the networks, and sometimes disconnects.

Perhaps, it is the radio module within RC2.

Big thank to Frankie.
[Nexus 6 Developer Discussion [Developers Only]] kkozma:
I synced back up with the sixrom device tree. Not sure what you guys have done and/or not pushed to git, but neither BT or NFC work for me with what you've pushed...

That being said, I did manage to get bluetooth working on my own, but NFC is still DOA. Same as before, it starts but then faults and dies.
[Nexus 6 Developer Discussion [Developers Only]] kkozma:
I think I got everything working, not sure. NFC is on, but for some reason you can't turn it off and I don't have any other devices to test it with.. The keyboard is a little wonky, but it works. Bluetooth works, cellular ,etc etc.

I can't figure out the sepolicy thing for bluetooth yet, so selinux is set to permissive. Give it a shot...

aosp_shamu-ota-eng.vwmofo.zip

md5: 9f3bc4b805e6b4ac7c1921f2bf97c814

Use these Gapps: https://androidfilehost.com/?fid=817550096634797336
[Nexus 6 Developer Discussion [Developers Only]] Aerys:
TWRP asks me for a password to decrypt Data after flashing your rom. Whats it? :)
[Nexus 6 Developer Discussion [Developers Only]] kkozma:
What? Seriously? What version of TWRP are you running?

Anyone else have that issue?
[Nexus 6 Developer Discussion [Developers Only]] GelucO_O:
Nop, the rom install and works fine
[Nexus 6 Developer Discussion [Developers Only]] camcory:
Have you tested? I have BT working with enforcing it plays while listening to web content ex. YouTube in browser but doesn't play with ex. Play music app with local device mp3,YouTube app, or amazon prime music.
[Nexus 6 Developer Discussion [Developers Only]] kkozma:
Are you talking about using BT? No, I haven't done much with it as I've never actually installed any apps to it. I can do that today.

Have you pushed the sepolicy change that fixed it to your git?
[Nexus 6 Developer Discussion [Developers Only]] camcory:
I'm working off my O-test branch.
[Nexus 6 Developer Discussion [Developers Only]] eocobby721:
Hey what version of TWRP are u on? Just to be sure.

Thanks
[Nexus 6 Developer Discussion [Developers Only]] GelucO_O:
The last one: 3.1.1

---------- Post added at 12:27 PM ---------- Previous post was at 12:24 PM ----------

BT works perfectly. I've been listening music for some time and i've not had any problem
[Nexus 6 Developer Discussion [Developers Only]] kkozma:
I'm using twrp 3.1.1.0 myself.

Bluetooth seems to work perfectly for me. Tested web based with youtube, play music, youtube app, etc etc. Now whether phone calls work, not sure. lol

Things I've tested so far that don't work...

NFC while the system reports that it's up and started, I can't make it actually do anything. lol

GPS works, but location services doesn't seem to work in apps, ie the "use my location" on a page. Used autozone.com to find a store and it said, sorry location was not shared.

AOSP Keyobard - pressing the numbers key causes it to crash. Install Gboard to fix
[Nexus 6 Developer Discussion [Developers Only]] kkozma:
I haven't noticed much lag, but I wouldn't be surprised..

Update on the location services. I think it's AutoZone that's broken. It worked just fine on walmart.com.
[Nexus 6 Developer Discussion [Developers Only]] camcory:
Fix for keyboard.

Also are you building with what is on your git or do you have other changes locally?
[Nexus 6 Developer Discussion [Developers Only]] kkozma:
Thanks!

I have a bunch of local changes... I'll clean them all up and git them pushed up in a bit.
[Nexus 6 Developer Discussion [Developers Only]] kkozma:
I was just coming here to update that I pushed everything. Sorry, when I rebuilt my build machine, I decided to give fedora a try and ended up hating it, so I reinstalled back to Ubuntu.

https://github.com/vwmofo/device_moto_shamu

Take a look at the oreo-wip branch. My device.mk is a mess because it's a giant cluster of things I got from you, sixrom, and moepda. Im certain there are some dupes in it, but with where I'm at everything works but NFC and I'm just too lazy to clean it up right now. lol

Speaking of, I compared everything that I have to your test branch and I'll be damned if I can find anything different anywhere that would allow BT to work for you in enforcing....
[Nexus 6 Developer Discussion [Developers Only]] luciusfox:
You didn't do something dumb, like let it install its default gnome 3, did you?