yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Android Development] mehmehmen:
:3 we are trying hard to get everything fixed up nicely. the issue with the encryption stuff is something we will look into, but for me i just go ahead and back up whatever i need from the sd card and then full wipe the device, install omni, then advanced wipe format data. I have no issues booting this way, the issue is the encryption which is performed by default AOSP. once a user sets any pin security in AOSP there is one workaround known that can ignore this issue, that involves basically deleting the credentials file created by the procedure, this method circumnavigates the encryption issue in a way but also means user cannot then set up new password or fingerprint credentials.

My overall advice to anyone looking to install omni for the 6P is to back up all your data and sd card files, perform a full data wipe, Install the omni rom, THEN do data partition format

once the rom has booted fully and you have configured the setup wizard (if you flashed a gapps) you should be able to reboot into recovery fine with no encryption issues
[Nexus 6P Android Development] mehmehmen:
you need to run wipe setting in twrp, hit advanced options and do full format on data partition.

We are looking into this issue to see if it is something we can fix in a later build, as it is surrounding encryption from previous rom installs it is something I am not hugely familiar with yet.

If you cannot live with format data partition route then i suggest waiting it out or trying to build omni and find a fix as we are :P
[Nexus 6P Android Development] Nekromantik:
If you read back a user said what the issue was that needed to be fixed for encryption. It's f2fs fstab.
[Nexus 6P Android Development] mehmehmen:
F2fs is not in omni fstab. So this is not the issue
[Nexus 6P Android Development] mehmehmen:
What needs to be understood here is that if a rom encrypts your data partition then to access the data partition under a new install u will HACE to format the whole data partition
[Nexus 6P Android Development] Nekromantik:
If thats the case then when I do a usual factory reset and flash any other ROM it works fine.

This is how I have been doing it. Current ROM encrypted with fingerprint, I disable the fingerprint unlock and then boot into recovery and do a factory reset and then system wipe.

I then Flash the new ROM zip plus GAPPS and reboot. It loads into Android and to setup wizard.

With Omni I do the same however on first boot it gets past boot animation and asks for password before letting me into setup wizard.

Something else is going on here as it only seems to effect this ROM. I have flashed various ASOP and CM13 ROMs all without issue.

I hope I dont sound annoying but Im trying to put across the issue as its only happening on Omni.
[Nexus 6P Android Development] Gandalf:
So many complaints and bug reports..

NOT ONE LOGCAT DMESG OR KMSG. Provide logs or don't post a bug report. It's that simple.
[Nexus 6P Android Development] Shawn5162:
Lol, a very valid point :)
[Nexus 6P Android Development] Jsilver73:
Sorry but I don't think anyone here is actually complaining, I think people are simply reporting what is happening.

According to omni ethos this is encouraged and commended as omni is supposed to be for all and omni devs wish to here from all whether brand new or old timers like yourself.

It's interesting that these issues only effect encrypted users flashing omni, I myself regularly backup my primary as in my signature (which is encrypted) do full wipes excluding internal, then flash whatever ROM/kernel and never have problems booting or setting up due to encryption.

Far be it from people complaining, I think people are just saying what is going on to try and help the people putting the rom together so they can find the solution - I really really don't think it is in the spirit of omni to discourage people reporting stuff so long as it is respectful, non demanding, and friendly - which I believe all of the posts here are.

Of course logs are really helpful, as soon as I get home (I'm in Spain with family atm, I live in the UK) I will be happy to provide what I can if the solution has not already been found.

I hope I'm not coming across badly, I'm really grateful for the work of the devs working on this, and I really believe in the ethos of omni being open to all and most of all friendly, please do take the time to read the 'about omni' documentation on the official omni website if you haven't already ;)
[Nexus 6P Android Development] Nekromantik:
Well said.

If people were going around saying "It dont work fix it now" or something like that then fair enough be harsh but thats not been the case.

I need my phone until weekend so cant flash it until then to provide logs.
[Nexus 6P Android Development] SwimDrewid:
Yes. To [MENTION=5528810]Jimsilver73[/MENTION]'s point, the ROM wouldn't load to a point where adb would connect
[Nexus 6P Android Development] DontPushButtons:
Looking through system/bin I noticed there's a make_f2fs file and an fsck.f2fs. I'm no expert by any means, but wouldn't that imply some sort of overall preparation for f2fs? If those being present aren't an* issue, I suppose we're back to square one.. Just figured it may be worth mentioning.
[Nexus 6P Android Development] Gandalf:
allow it to fail to boot, reboot directly to TWRP, mount /system, do this:

adb pull /sys/fs/pstore/console_ramoops

since the system isn't even starting, a logcat is quite clearly NOT what we want, or can even obtain right now. a dmesg would be useless as well since, well, the system hasn't started. this failure to boot is caused by a kernel panic, but we don't know WHY there is a kernel panic. so providing these logs will tell us what is causing the kernel panic and therefore causing the failure to boot.

so yes, my point is extremely relevant and completely valid, since a reported problem would ideally be accompanied with the appropriate logs and steps to reproduce.

It is common practice to include logs when reporting issues. This is similar to calling your auto mechanic and saying "my car is broken, FIX IT NAO!" without providing any other information.

http://xdaforums.com/showthread.php?t=1520508

However, since this device uses the 3.10 kernel, we must realize the "last_kmsg" has been moved to pstore, and lives at the path above.
[Nexus 6P Android Development] DontPushButtons:
Experimented a bit, removed the make_f2fs and changed fsck.f2fs to fsck.ext4fs, flashed with gapps and su and booted just fine. Running without issue as of yet, still encrypted and all.

Thanks for the adventure [emoji14]

Ah, and for those of you that cant get it to boot past the google logo, you might need to fashtboot the newest vendor image. If youve only used the flashable to update vendor, the img usually sorts you out.

Spoke too soon, likely due to my hackjob getting it to boot, i get no audio in call. Ill wait for a build I didnt modify for a real report.
[Nexus 6P Android Development] Nekromantik:
My issue is not that it wont boot.

It boots but asks for a password before going into android.

So we have two different issues it looks like.
[Nexus 6P Android Development] Jsilver73:
Here is my pstore https://www.androidfilehost.com/?fid=24345424848487977

Hope it helps.

FYI I did originally fastboot flash the latest vendor for mmb29m
[Nexus 6P Android Development] gigoo25:
Looks like the angler is surfacing on the official Omnirom git.

https://github.com/omnirom/android_kernel_huawei_angler
[Nexus 6P Android Development] mehmehmen:
Yes indeed i asked if they would put up our work so far and to help make this all a bit easier for any one looking to get involved with the current development work or go along on their own and develop themselves.

As a heads up a omni dev looked into some of these encryption issues and he made a build that now recognises the old password details for the previous encryption so it allows us to use the current password to get in as normal. Once we hav another build that includes all the other changes for the latest omni updstes and i will have a new rom linked for everyone. The latest development has fixed lots of the issues and has some nice new bits and bobs in it too. :)
[Nexus 6P Android Development] gigoo25:
Yeah i've been building from the official tree for a couple days now but seems to be have a couple of issues like no sim recognition and stuff
[Nexus 6P Android Development] mehmehmen:
Thats odd. It should function on all the basic features of the phone side. I will check in the irc when our quassel server reboots in a bit and have a chat with some peeps. It should definitely function fully so it may be an issue on ur build end.
[Nexus 6P Android Development] gigoo25:
That's what I thought too... I'm going to repo sync and try another build see if everything functions properly..
[Nexus 6P Android Development] gigoo25:
Just completed a build again and radio still states that it is an Unknown band... Everything else works flawless though
[Nexus 6P Android Development] mehmehmen:
what network is the device? is it locked and is it verizon?
[Nexus 6P Android Development] gigoo25:
I am on T-Mobile
[Nexus 6P Android Development] Gandalf:
You're missing vendor
[Nexus 6P Android Development] Shawn5162:
But assuming you were missing vendor, the fingerprint scanner shouldn't have been working either. Was it (on your build)?
[Nexus 6P Android Development] klo_lol:
This is awesome already.

I had some weird behavior of crackling with the System sounds (ringer, sms, low on battery), but tuned the volume down and it's pretty much normal again.

I suppose this is due the DSP Manager not working as of now, but already kind of integrated (when looking through the commits on github).

Also, thanks!
[Nexus 6P Android Development] Gandalf:
That has should have nothing to do with dspmanager, but I've seen stranger
[Nexus 6P Android Development] Danish2980:
For how long should I be looking at the google splashscreen?

I wiped everything including data and then flashed the following:

Latest build

OpenGapps

SuperSU 2.52

Try again without Gapps, but got the same result..
[Nexus 6P Android Development] Gandalf:
You must use systemless root
[Nexus 6P Android Development] DigitalDementia:
Is anyone else having issues with Google Camera? I can take videos but not pictures. However I can take pictures just fine with Camera2.
[Nexus 6P Android Development] 21cdb:
I have the same problem on Beanstalk. Is it a CM issue?
[Nexus 6P Android Development] Danish2980:
Tried the newest version.. Still to no avail?
[Nexus 6P Android Development] Gandalf:
You need to fully wipe system data cache and clean install

*facepalm* GET A LOG PLEASE
[Nexus 6P Android Development] Danish2980:
I always clean flash...
[Nexus 6P Android Development] DigitalDementia:
Here's the logcat. Hope this helps. Sorry for not posting it earlier, just wanted to see if it was common or I was an anomaly.
[Nexus 6P Android Development] mehmehmen:
Hey guys sorry to of been radio silent for a while but been busy with christmas and UNI work. we have fixed many issues internally on omni with regards to things like camera apps working and any encryption issues that we were facing previously

as it stands we are slowly working towards a new twrp build for angler, along with getting the latest updates and ui tweaks merged into angler omni. once the large portion of work is done i will release a new test build but BE WARNED it is going to be a test build, there may be issues and we will only know once we get the next stablish build to boot and so on.

Will update in a few days or sometime at the weekend

happy new year.
[Nexus 6P Android Development] Danish2980:
Can't wait.. Really want to try Omni, but couldn't get the previous versions to either get past Google screen nor Omni bootanimation..
[Nexus 6P Android Development] mehmehmen:
Ok so quick update on progress right now, we have a new build working, i have flashed it and tested everything i physically can (do not have the requirements to test usb OTG and so on) only issue so far apps wise is DSP mnager force closing without fail

Aside from that this build is fully functional but there is a new issue that we may have found which is actually directly in the source code for marshmallow for angler from googles own source and it seems the cpus are being incorrectly identified and we are investigating if our hunches are correct.

I am happy to share the test build privately to people who do not mind these things but i will not update the download url until we have overcome some of these hurdles.

If you want access to the test version feel free to ping me a message and i will share (disclaimer anything that goes wrong when testing a test build id your own responsibility, i advise against it but it is personal choice)
[Nexus 6P Android Development] DigitalDementia:
I'll give it a whirl!
[Nexus 6P Android Development] Danish2980:
Any news regarding the new build?
[Nexus 6P Android Development] DigitalDementia:
Is this no longer in development?
[Nexus 6P Android Development] mehmehmen:
It is in development. The issue has been manpower and time. I am knee deep in my assignments for uni as well as about to go to a funeral for a close relative who died in the Christmas period. I have been radio silent on so many fronts lately but the underbelly is still digesting things quietly. We have a test build up which was built on the 12th of this month I have not put it publicly as I don't want users having issues without knowing exactly what they are doing as I am not around currently to offer decent support. If you message me I will share the current link.

This is in the proviso you understand there could be issues we don't know about yet and anything you do with your device with the build is your responsibility. I'm so busy other people's issues just cannot be addressed by me regularly enough for me to be happy to post the link in thread.

Regards NinjahMeh aka mehmehmen
[Nexus 6P Android Development] DigitalDementia:
I apologize for the way I worded my question, and am sincerely sorry for your loss.

I just wasn't sure if you were working in it anymore as I realize people get busy with real life and I didn't see any mention of it in the recent rounds of release news but did see the 5X. Thanks for the update, take as long as you need I know development isn't the easiest task especially with limited manpower.
[Nexus 6P Android Development] MikeRL100:
I just helped Simon Sickle get pre-nightly builds ready for the Nexus 9 and debugged the builds and logged them. I'll be getting a Nexus 6P tomorrow in the mail, and I will flash Omni on it shortly after. I can test the private builds as long as you're willing to give me basic instructions on any logs needed. I don't mind the crashing - we had DSP Manager FCs on flounder and fixed them rather quickly. Be seeing more of things here soon. I have time and don't mind helping where I can when I can. Just as long as a schedule can be worked out so I don't get in your way. I can promise I will have better manners than many of the posts I just read above - some of these are jumping from A to Z and are drawing illogical conclusions, or come off as whiny. People need to remember to have manners. I hope some of these people were raised right as kids. Who the heck acts annoyed and inconvenienced when someone is going from funerals to a constant flow of course work? People need to show some respect, or maybe some of us will start showing disrespect to people who don't know what respect is for some stupid reason.

The above info and accompanying rant is not targeted to any one person - but society and XDA as a whole. LEARN FREAKING RESPECT, OR ELSE!
[Nexus 6P Android Development] DontPushButtons:
I don't think being disrespectful in return for perceived whining or disrespect is going to garner the results you're looking for. Its XDA, you're going to have a lot of poorly phrased or misunderstood comments, best just to kill them with kindness or ignore them.

Rant aside, I'm sure a dedicated tester/troubleshooter will be helpful for future development. I'm also willing to guinea pig some builds as time allows, since I don't seem to stay in one place for more than a few days.

That all said, enjoy your new angler.
[Nexus 6P Android Development] mehmehmen:
Lol thanks for the support, I must ay i havent perceived a great deal of the posts as whining, I made a big noise when we got up and running, then life came along and was like *flips the bird at me* and i carry on. There are currently a few things going on right now which are massively taking my time up so deving android spare time is low low down my list. I am working on a top secret new project as part of my uni project module and this is something im really hyped for android wise, more news may follow once progress starts to be made on the concept.

I think as the guy below said though, forums make nerdy types like us sound more whiny than we are, people just want in on a good rom for a dev friendly device, i dont blame em, thats why i got my 6P :P

Indeed, once i get some time i will look into possibly putting the most recent build up as a really test build with lots of HUGE DISCLAIMERS AND OMINOUS CAPS TO WARN AWAY THE YOUNGUNS and what not. Main reason i havent done much is i dont want someone bricking a 600 pound phone for the sake of a pretty stock rom on a stock android flagship lol
[Nexus 6P Android Development] DontPushButtons:
Well no rush, it goes without saying that users will be here to flash builds at your convenience. Best to have your feet firmly planted before you start moving along again. Risk comes with the territory, but we certainly appreciate your precautions ;).
[Nexus 6P Android Development] MikeRL100:
Regardless, I'll be sure to grab the logcat and upload it here or link to it once I get the device in my hands. That will at least be something to look at - I actually like DSP Manager a lot, and the people who develop Omni in general likely wouldn't mind helping you if needed.
[Nexus 6P Android Development] dlads:
Just call it an alpha build mate until it's had the kinks ironed out.

First and foremost, get yourself sorted in real life. :thumbup:
[Nexus 6P Android Development] MikeRL100:
Well, I talked with Simon Sickle who maintains flounder, and I helped him get it running. He has offered to help with this device, but he wants a list of the device specific bugs. How many are there? He and I may be able to help. At least get some progress going around here when your free time is short and spread out. He doesn't have the device, but mine will arrive tomorrow.

Edit: Kind of too late to ask. Work has already started on GitHub. Prepare for the fun to start.
[Nexus 6P Android Development] mehmehmen:
So far off the top of my head, DSP manager FCs, CPU frequency for main cpu caps at 1.55 GHz (seems as though it looks at the low powered proc as main which is top speed 1.55, main cpu is 1.96 and benches show this speed cannot be attained currently) google camera ap camera doesnt function correctly (video works and stock camera works fine) erm other than that cant think of the rest but those are the glaring few I remember sticking out
[Nexus 6P Android Development] MikeRL100:
We tried building it, but I'm the only one out of the two of us with the device. I get a decryption error when trying to boot up after a fresh wipe. Is there some way to fix this or at least log it since ADB logcat hasn't and cannot be granted from that stage?
[Nexus 6P Android Development] klo_lol:
did you try to "TWRP > advanced > wipe data" + select format button & reflash the ROM? (ATTENTION: you will lose all data on the device)
[Nexus 6P Android Development] MikeRL100:
I actually did the same as what you suggested but with fastboot to get around the warning. Still, that is a bug specific to the device on an early blind build. I was hoping the maintainer had any insight on getting around the issue. I can format stuff, but you shouldn't have to mess around with formatting when flashing OmniROM after stock and wiping. But the problem isn't so much of me knowing how to get around it as it is fixing the bug so nobody else has to deal with it. And that may take time as I just got sick pretty badly and the maintainer is busy until next week. I actually tried formatting userdata on the first day I tried the build, but I encountered SIM errors past that and said screw it and went back to stock until there's time to really look into this.
[Nexus 6P Android Development] klo_lol:
Allright, it was just what i was doing in the dec build to get it working, as it was suggested.

I'm just really thankfull for anyone involved in developing here, Omni is my favourite ROM. Using it since the first days. I'd like to be able to contribute something myself, but my limit is at building, testing & cherry-picking existing stuff if needed. (Also i've tried to port it over to angler myself, and even succeeded, but NinjaMeh's approach was more professional than mine)

By the way - i've built from Simon's github sources and also got the simcard problem. I thought something simply went wrong on my end tough. Like i said, i'd wish i could contribute more.

That being said, i hope you're all feeling better soon. Don't misunderstand me as being pushy to get the builds rolling - sure, i can't deny my "greed" - but i really mean it. And again, thanks!
[Nexus 6P Android Development] OmegaBlaze:
Anything new?
[Nexus 6P Android Development] klo_lol:
Here's an up2date build as of today (30th March 2016) for anyone not knowing how/wanting to set up a build environment.

You need to flash the latest vendor.img from the Factory image, else the SIM card will not be detected.

I don't know if the latest bootloader and radio need to be flashed. Anyways, all of these files are in the latest MHC19L factory image zip.

https://drive.google.com/file/d/0B1swN4DCfhVwUFEtR1BXU2Y2RWs/view?usp=sharing
[Nexus 6P Android Development] klo_lol:
I'd like to point out that the Omni staff is still looking for an active maintainer for the Nexus 6P - the main thing preventing official builds.

I wanna give a shoutout to Jake Whatley aka jakew02. He did an amazing job at supporting me through some serious stuff for this build.

-merged in the latest AOSP changes

-fixed the distorted first sound after booting up (fix taken from CM)

-added Project Fi stuff (i can't test this as it is unavailable here, so please report back if everything is working)

-ofc, latest Omni changes in general

As always flash the latest vendor.img (MHC19Q)

Download: https://drive.google.com/file/d/0B1swN4DCfhVwZTlTOFRtdnlwNkU/view?usp=sharing
[Nexus 6P Android Development] Nekromantik:
Used to love this on old HTC days. Shame they still not got anyone for our device.
[Nexus 6P Android Development] OmegaBlaze:
Could someone post the updated version of installation for this ROM?
[Nexus 6P Android Development] klo_lol:
Same procedure as before.
[Nexus 6P Android Development] klo_lol:
Here's a new build.

This is the last build i can provide for about the next three months, as i will have no access to my computer for that time.

https://drive.google.com/file/d/0B1swN4DCfhVwTTZuVlVzeV9RNkU/view?usp=docslist_api

Hope someone has been found as a maintainer, or at least someone who keeps our device up to date, by the time i come back. If you're interested please hop on to omni's irc.
[Nexus 6P Android Development] Gandalf:
No news on a maintainer still.
[Nexus 6P Android Development] resynx:
Wish I knew how to be a maintainer.. Hope you guys find someone soon!
[Nexus 6P Android Development] ryukiri:
I'm highly considering being the maintainer. Seeing how I haven't been active recently due to time constraints, the only thing holding me back is that I'm not sure if I have enough time to dedicate...
[Nexus 6P Android Development] indian84:
That will be great. I miss omni from my Bacon days. Get in touch with [MENTION=4683552]maxwen[/MENTION] when you decide to be maintainer.
[Nexus 6P Android Development] Gandalf:
The main thing for Nexus devices is that they need to be updated once per month with the security releases, other than that, it's Nexus, it basically builds itself and everything works