yashsingh1/xdaforums huggingface dataset:
[Nexus 9 Android Development] harryyoud:
Hi,

Sorry I've been not communicating too well recently; I've been really busy with college work (A-Levels are gonna finish me). I've submitted the changes needed for flounder_lte to be working (without modifications) to Gerrit. I've also submitted a change to add flounder to the nightly list. I'll add flounder_lte once my first change is merged.

I'm not entirely sure why flounder_lte is still having problems with mobile signal. I don't actually own one myself, so I'm limited by the amount of debugging I can do. Perhaps I'm missing flounder_lte specific vendor files? [MENTION=4804270]jackieku[/MENTION]: What made your build different?
[Nexus 9 Android Development] jackieku:
I found no LTE specific vendor files to build. Also we don't get any feedback from others with my build, it just works for me. There are, however, some differences between "user" and "userdebug" configurations, at least in SELinux policies.
[Nexus 9 Android Development] harryyoud:
I've made a completely unmodified flounder build (20161223). This will encrypt your device!

I'm returning to normal builds again tomorrow.

I've also had news back from adding flounder to the cm-14.1 nightlies. The change has been rejected as the device maintainers have to make the call to add it, so for now, we're stuck with unofficial builds. My changes for flounder_lte are still being reviewed.
[Nexus 9 Android Development] McFlypants:
This is working for me!!
[Nexus 9 Android Development] fleischbanane:
I did a clean flash with this build, but I can't change the root state in the developer settings. It's greyed out.

Will test it now and report of something else didn't work out if everything else is fine.

Edit: Gboard settings crash whenever I want to open it. I use the same gapps config as I use on my Nexus 5X.
[Nexus 9 Android Development] harryyoud:
Hi,

Hope you all had a great Christmas day.

You've probably all heard the bad news (https://www.xda-developers.com/the-death-of-cyangenmod-and-whats-in-store-for-the-future/). This means theres no chance of official nightlies in the near future. I'll continue to build these, and we'll see whether [MENTION=4973732]simonsickle[/MENTION] (the flounder(_lte) device maintainer) has anything to add, or wishes to do his own "official" builds.

H
[Nexus 9 Android Development] harryyoud:
Back again. Spoke to ciwrl (a member of CyanogenModLineageOS team), and I'm unofficially a device maintainer now for both flounder and flounder_lte (alongside razorloves, ciwrl and hashbang173). I'm going to now be posting completely stock LineageOS builds with NO modifications (encryption is back). This means exactly what you expected from the CM14.1 official nightlies. I'll continue these until LineageOS gets into gear and starts nightly builds.

First builds should be tonight.
[Nexus 9 Android Development] carlofabyss:
Thanks for the info man so with this whole lineage os thing, are they going to clean the slate or are cm mods going to remain in the development process?
[Nexus 9 Android Development] harryyoud:
At the moment, the codebase is basically just CyanogenMod. Lots of places where CyanogenMod is shown to the user is being replaced with LineageOS as we speak. I believe the plan is to keep things as close to CyanogenMod as possible to begin with until Android 8 is released. Almost all of the developers from CM are members of LineageOS.
[Nexus 9 Android Development] ElmTunes:
Hi,

I just want to install the CM14 onmy nexus 9. I use the cm-14.1-20161228-UNOFFICIAL-flounder.zip but I get an error by flasing this zip.

"Can´t install this package on top of incompatible date. Please try another package or run a factory reset"

Prozess Updater endete mit Fehler: 7

Fehler beim Installieren von ZIP '/sdcard/Neuer Ordner/cm-14.1-20161228-UNOFFICIAL-flounder.zip'

I also used the build from 20161223 with the same result.

Before I did this, I did a factory reset to 7.1.1 with the Nexus Root Tool which was succesfull and after that I flashed TWRP 3.0.2.1 which was also successfull.

Can anybody help me?
[Nexus 9 Android Development] harryyoud:
In TWRP you need to wipe data, as the files there (from the stock ROM) aren't compatible with CyanogenMod:

Wipe -> Format Data (or something like that)

The reflash the ZIP

BE AWARE ALL YOUR DATA WILL GO (INCLUDING INTERNAL STORAGE) - AS IF YOUR TABLET WAS NEW FROM THE FACTORY. BACKUP ANYTHING IMPORTANT
[Nexus 9 Android Development] ElmTunes:
Oh yes, I have to wipe Data, too.

So I did this now, but I get another error...

Patching system image unconditionally...

E: unknown command [log]

E: unknown command [log]

deleted file system ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP

After finishing of flashing (GApps, too) the tablet hangs on the CyanogenMod logo and nothing happens...
[Nexus 9 Android Development] harryyoud:
Try flashing without Gapps. If it's still not working, try formatting all the partitions, and then reflash
[Nexus 9 Android Development] ElmTunes:
OK, I will check this.

And what GApps do you recommend?

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 9 Android Development] harryyoud:
Honestly, there's no choice atm. OpenGapps seems to be the only ones out there.
[Nexus 9 Android Development] ElmTunes:
So hereÂ´s an update.

After flashing only the CM 14.1 rom whitout GApps, CM starts.

After the first boot I switched to recovery and flash GApps (open_gapps-arm64-7.1-micro-20161220.zip) again. I hope that are the right one...

Now the CM logo hangs since many many minutes and nothing happens... :o(
[Nexus 9 Android Development] dictionary:
You have to flash gapps right after flashing the ROM. You can't boot without them or else you'll run into issues. Personally I always use pico.

Edit: yeah, apparently it's different now. No idea when that started. My bad
[Nexus 9 Android Development] ElmTunes:
but hazzer means:

So I did this and I have to update my last post again. After some minutes finally my nexus 9 boots in CM ;o)
[Nexus 9 Android Development] harryyoud:
That's not true. The Setup Wizard is borked for Gapps, so you have to do the ROM, boot, setup and then install Gapps. Otherwise you get stuck on "Restore apps from another device?" screen.
[Nexus 9 Android Development] dictionary:
Then it's changed a lot since the last time I used. Before you'd run into issues if you did it that way. Plus, I've only heard of people running into Gapps issues when running some of the other packages. Since I switched to Pico, I haven't had any. Good info to know. Thanks, and sorry to the other poster
[Nexus 9 Android Development] ElmTunes:
After that the rom runs, I have 2 questions...

1) I read that the ROM is without root, right? Do I only have to flash SuperSu.zip and root works?

2) whats about encryption? Is this enabled? How can I disable this, because I read that in a previous version, it was disabled and the performance was great...

Thanks

Elm...

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 9 Android Development] harryyoud:
1) The ROM has root as of 20161228. It is as if were an official nightly

2) Encryption is enabled (as it would be on a nightly). I would recommend this, but I'm not sure it's updated for Nougat ROMs yet. You could give it a try
[Nexus 9 Android Development] ElmTunes:
I just tested FED Patcher v8 for nexus 9 but with no success. Flash was successful, I had no errors, but encryption is still enabled after that...

And because of 1) titanium backup have no root access. Where can I see that the ROM is rooted?

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 9 Android Development] harryyoud:
1) Go to Settings > About tablet > Press Build number 7 times, until "You're a developer" message appears.

Go back to Settings > Developer Options > Root access > Apps and ADB

2) (Number 1 is required first)

Then in a command prompt on your PC with adb setup.

> adb shell

$ su

# sed -i s/forcefdeorfbe/encryptable /fstab.flounder

# exit

$ exit

> exit

And encryption will be off.
[Nexus 9 Android Development] harryyoud:
So I've taken a look at FED Patcher; it's not updated to work with Nougat FBE yet. I've made a patched version available on my website (under flashables). Hope this works for you.
[Nexus 9 Android Development] harryyoud:
The website is the same place you downloaded the build from. Check under the flashables page

https://harryyoud.co.uk/cyanogenmod
[Nexus 9 Android Development] jolinnard:
I always flashed this zip to disable force encryption and dm-verity: forcencryption-off.zip (I'm not using it now, but I did when I run Google stock N)

This zip it's partially a kernel package but only the part that removes encryption (kernel will not be modified). So it should be safe to flash. Scripts will replace all the options in fstab files (like [MENTION=4598799]hazzer[/MENTION] said, but permanently).
[Nexus 9 Android Development] ElmTunes:
Sorry but the link on your website to "FED Patcher (Patched)" does not work, now...

Link:

https://harryyoud.co.uk/lineageos/downloads/fed_patcher_v8-harryyoud2.zip

Error:

Not Found

The requested URL /lineageos/downloads/fed_patcher_v8-harryyoud2.zip was not found on this server.
[Nexus 9 Android Development] dictionary:
Try again. I just downloaded it. Seems like he renamed it and dropped the 2

https://harryyoud.co.uk/lineageos/downloads/fed_patcher_v8-harryyoud.zip
[Nexus 9 Android Development] albsat:
Can i bypass encryption if during the rom installation, in twrp I install a kernel with encryption off?
[Nexus 9 Android Development] harryyoud:
Yes if you flash it after the ROM. Or flash the patched FED disabler on the Flashables page
[Nexus 9 Android Development] Elgsdyr:
I just installed lineage-14.1-20161231-UNOFFICIAL-flounder.zip, which seems to be running great in general. Only exception is Bluetooth. When I connect a keyboard or mouse the connection is lost almost immediately.
[Nexus 9 Android Development] harryyoud:
I'll look into that. Thanks for the feedback
[Nexus 9 Android Development] Elgsdyr:
I just did a reboot and tried again (the classic Windows fix), and now I can connect both mouse and keyboard. I had to remove the pairing of the keyboard and reconnect it but now it works at least.

No idea what went wrong yesterday but I'm sure it wasn't a user error. :rolleyes: I'll keep an eye on it and report back if it happens again.
[Nexus 9 Android Development] schickel:
JFYI

JFYI:

I've flashed the latest lineage-14.1-20170101-UNOFFICIAL-flounder on my Nexus 9 after a full wipe (previous CM13).

After flashing ROM I flashed the FED-Patcher, but on the first boot the encryption starts. For me this is not a big deal. All the other Apps doing their job very well and I didn't have any FC or reboot.

Thank you for the good job.
[Nexus 9 Android Development] Elgsdyr:
The problem just reappered. Had to disable and enable Bluetooth several times before I managed to get a connection to my keyboard. Seems very erratic.
[Nexus 9 Android Development] schickel:
My bluetooth keyboard works and my bluetooth headset works also without a problem.

Did you try the lineage-14.1-20170101 build?
[Nexus 9 Android Development] Elgsdyr:
No, but just installed it now. Unfortunately it's giving me the same headaches with BT. It doesn't automatically connect, when I turn on the keyboard, and trying to connect it manually opens up a load of annoying waiting while it unsuccessfully tries to connect.

A workaround that seems to work for now is to keep the keyboard off, go into the Bluetooth settings, wait for it to finish scanning and then turn on the keyboard. Then it seems to be detected correctly. Never had this issue with stock 7.1.1.

Edit: It appears that the workaround described isn't enough. Whenever I experience connection problems, I must go to BT settings, turn BT off and on, wait for it to finish scanning for available devices, and then turn on the keyboard. After that connecting works fine for a while. Dunno what causes it other than time. Maybe it's related to sleep mode?
[Nexus 9 Android Development] McFlypants:
I still have no working data connection on this build for LTE... It shows no connection and then comes a forced-close from android.phone and it says "no sim".

There were only two builds that worked. The first one (i guess from december 11th) and the one that someone built and posted here!

Any easy way to fix it by myself?
[Nexus 9 Android Development] Flounderist:
Hi all, I have some question before upgrading from FED decrypted cm13.0 .

1. Do I need to upgrade to stock 7.1.1 before flashing the new ROM, or I just need to flash last Vendor img?

2. Do I need to flash last TWRP (I'm on 3.0.2)?

3. SuperSu 2.79 will disable encryption or I need to perform the ADB shell script?

Thanks in advance for your co-operation :)

Please let me know!
[Nexus 9 Android Development] ipdev:
1....

At the very least you should make sure you are running the current bootloader and vendor.

(I also flash recovery.img and boot.img just to be safe.)

2....

Not sure if flashing twrp matters. (I leave stock recovery installed and fastboot boot 3.0.2-1 when needed.)

3....

SuperSU has left mine encrypted. (I do not remember when it became encrypted but, I personally do not have a reason to change it.)

Nexus 9 WiFi (volantis) - (I have and use.)

N4F26M (Jan 2017)

https://dl.google.com/dl/android/aosp/volantis-n4f26m-factory-c8b6741d.zip

bootloader-flounder-3.48.0.0141.img

vendor.img

Nexus 9 LTE (volantisg) - (I do not have but seems to be the most current.)

NMF26F (Dec 2016)

https://dl.google.com/dl/android/aosp/volantisg-nmf26f-factory-cb15d790.zip

bootloader-flounder_lte-3.48.0.0141.img

vendor.img

- Common (?)

twrp-3.0.2-1-flounder (volantis / volantisg? -Not sure if it is the same for WiFi and LTE)

https://dl.twrp.me/flounder/twrp-3.0.2-1-flounder.img.html

- General

Nexus factory images

https://developers.google.com/android/images

TWRP recovery

https://twrp.me/

OpenGApps

http://opengapps.org/
[Nexus 9 Android Development] Flounderist:
Hi, thank you for the info. :highfive:

I couldn't wait so yesterday I flashed bootloader, vendor and twrp. Then I reboot in recovery and flashed ROM+ Gapps. Once completed setup I flashed Sublime N9 kernel and SuperSU on top of it.

All went smooth and root checker ensured me root access also without SuperSU.

Unfortunately adaway 3.12 is not working and device is still encrypted. Any suggestion?

Cheers.
[Nexus 9 Android Development] ipdev:
Update AdAway. (Current is 3.2 and supports systemless su.)

https://xdaforums.com/showthread.php?t=2190753

- As far as flashing a custom kernel... I checked that one out and replied to your post in that thread.

:silly:
[Nexus 9 Android Development] Flounderist:
Installed 3.2 and it works flawlessly :svetius:
[Nexus 9 Android Development] game #1:
Installed latest unofficial release 14.1 and got fc with android.phone app

I choose close till next reboot and it's no issue till reboot. Lol.

Got nexus 9 LTE but sim card is not inserted. Always at flight mode with Wi-Fi on.

And it feels like heating a bit more than stock. And charging is slow.
[Nexus 9 Android Development] sheenswizner:
Install latest TWRP and full wipe included internal memory.

Flash Gapps stock only recommended.

I am using LTE latest version with no issues at all. Awesome ROM.
[Nexus 9 Android Development] game #1:
What about slow charging after installing cm14.1?

Maybe there is a kernel with possibility to take more amperes to charge the tablet?
[Nexus 9 Android Development] schickel:
Charging is really slow. 30% charged in 3 hours. Speed is something else..... I switched for short to PureNexus and get the same issue.
[Nexus 9 Android Development] game #1:
Official 7.1 was charging better . but got a lot of other issues.
[Nexus 9 Android Development] Bastlwastl2010:
[MENTION=4598799]hazzer[/MENTION]

Your server is down?
[Nexus 9 Android Development] harryyoud:
Yes. Fixed. Ran out of disk space
[Nexus 9 Android Development] Veritas06:
What carrier are you using? I'm using the latest version (Jan 10) & cannot get a data signal.

EDIT: Getting the com.android.phone crash & being told there's no SIM. Not able to open the APN settings to add Google Fi entry, because it just crashes along with com.android.phone =\
[Nexus 9 Android Development] Bastlwastl2010:
[MENTION=4598799]hazzer[/MENTION]

Do you revert the disable root by default change in your build or chnage your build setup to enable it?

https://review.lineageos.org/#/c/154019/

I dont understand this...to do this in a custom rom....
[Nexus 9 Android Development] harryyoud:
When I first starting doing builds (before Lineage rebrand, and before CM shutdown), I disabled root for personal reasons (passing SafetyNet by default). I achieved this by building the ROM as 'user' instead of 'userdebug', which disables and also doesn't install the su binary to /system.

When the project transitioned to Lineage (after the CM shutdown), I began to build as userdebug (this is the default) again, to be close to official nightlies as possible.

Members of the Lineage team decided to (by default) remove root from Lineage builds, so the ROM will pass SafetyNet by default. This means root is now disabled in my builds (as I haven't explicitly enabled root).

If you would like root in the ROM, (SuperSU) or (Magisk+phh) is the way to go
[Nexus 9 Android Development] harryyoud:
I stated at the start of this 'project', I am balancing this alongside school work. Unfortunately, it's just become too much to manage alongside time consuming A levels.

This means:

Builds will be less frequent (perhaps once or twice a week)

I'm not going to be available on XDA or IRC very often (if at all)

I apologise I haven't been the best at communicating or fixing issues, but I just didn't envisage having to invest the amount of time I have.

If anyone would like to take over, give me a shout. You can borrow my server for hosting and my blog article if you're willing to learn.

You might see me again sometime around July. Thanks everyone for helping me with an incredible learning process into the depths of Android.
[Nexus 9 Android Development] glockman4519:
I completely understand., It is going to suck not having the builds but you have a life to live too. If I was more familiar with building CM, I would take over for you but I am set up for PN and from what I remember there many changes to make to build CM as opposed AOSP..
[Nexus 9 Android Development] game #1:
16.01 release is much better, no android.phone errors.
[Nexus 9 Android Development] harryyoud:
LineageOS are almost ready for unofficial builds now (http://lineageos.org/Update-and-Build-Prep/), so my builds are stopping. To change over to the official weeklies, you need to first flash the EXPERIMENTAL build, then move to the officials.

Unfortunately, flounder(_lte) isn't on the weekly list for building. If it's not on by next week (I'm trying my hardest to push it there), then I'll start my builds again.
[Nexus 9 Android Development] Flounderist:
Did someone tried to flash Dolby Atmos on top of this ROM?

Yesterday I updated to 20170120 and flashed it on.

App had FC and then also audio in settings menu FC. I flashed (dirt) ROM again, but audio still FC.
[Nexus 9 Android Development] glockman4519:
Thank you. This is greatly appreciated by the whole Nexus 9 community.
[Nexus 9 Android Development] harryyoud:
I've spoken to the official maintainer of flounder, who says the two bugs that need to be sorted before weeklies are:

- problems with playing videos on the web (eg. YouTube in gello, the built-in browser), where the video will crackle, stall and jump

- volume control. Pressing the volume button from the home screen doesn't move the volume slider correctly.

I've yet to confirm these bugs exist, but I thought I'd let you all know.

Edit: chrome->gello
[Nexus 9 Android Development] Flounderist:
[MENTION=4598799]hazzer[/MENTION] do you know if audio in setting menu fc in last build? I already formatted system and reflashed but bug stand still. BTW audio output is fine. Did you ever noticed problems flashing Dolby Atmos?
[Nexus 9 Android Development] harryyoud:
The newest build I have on my flounder is 20161228, so I couldn't tell you. I haven't tried Dolby Atmos personally. If I have some time this weekend I'll give it a go
[Nexus 9 Android Development] firewave:
I'm running the last nightly (24th), with stock opengapps and SR3-supersu.

All runs smooth. AudioFX has 0 effect but I don't care. Good build, thanks!
[Nexus 9 Android Development] Flounderist:
Could you check if audio app in device settings menu works? I get fc all the times. Thank you!
[Nexus 9 Android Development] firewave:
It works here :o
[Nexus 9 Android Development] Flounderist:
Yep. Flashed 0124 and works back again. Thx anyway! :highfive:
[Nexus 9 Android Development] fleischbanane:
I hope that the official SU zip will work with your builds. Will do a clean flash this evening.
[Nexus 9 Android Development] sunng87:
Just dirty flashed 0124 from CM13. It works like a charm!
[Nexus 9 Android Development] ipdev:
Link to lineage su download. (add and remove.) Select Extras

https://download.lineageos.org

(Direct link - https://download.lineageos.org/extras )

Note :

Clean install took four and a half minutes on first boot.

(lineage-14.1-20170124-UNOFFICIAL-flounder and addonsu-arm64-signed.)
[Nexus 9 Android Development] McFlypants:
Still no LTE with build from 26th January.... I'm still on a december build.

I read about this issue at here.... I'm using o2 germany and i feel like having the same issue - the radio does not turn on.

It was working on some builds from you, why did this change?
[Nexus 9 Android Development] maelfilk:
Anyone else having no success trying to mount system and vendor as r/w? (to use viperfx for example). Everything is fine on aosp, but since marshmallow cm-based roms can't mount system and vendor as r/w using any root file manager.
[Nexus 9 Android Development] firewave:
Works here with 2.79-SR3 SuperSU
[Nexus 9 Android Development] adamsfan:
It seems LTE works on clean builds only for flounder_lte. I just did a build on an updated tree that had been used for a previous build. The build after "repo sync" had no working LTE. Another build after "make clean" had working LTE.
[Nexus 9 Android Development] McFlypants:
So can I fix it myself or is there any chance to get a lineageOS 14 Rom that is fixed?
[Nexus 9 Android Development] adamsfan:
Here is what I did last week. I looked up the wiki for lineageos.. There is a page for every device, sorry, I cannot post links yet, but I'm sure google will help.

Last week there also were instructions for flounder_lte but the page seems to have been removed, as it is not yet supported officially. Just take any device, like "deb". If you substitute the references in the instructions to "deb" with "flounder_lte" you should be able to create a build environment, the steps are the same.

I don't know about "fixing" the rom, but my observations were that LTE only works on clean builds for flounder_lte, as opposed to i9300 and oneplus2, where a clean build is not necessary every time.

Update: you can now find my nick on androidfilehost. I just uploaded today's build. LTE working, only thing not working is boot animation, no idea why, boot animation is working on other devices I built for. First boot after flash coming from lineageos should take less than 10 minutes.
[Nexus 9 Android Development] Avi8orCode:
Official?

Any news about becoming an official ROM? I mean no ETA, just probably yes or no. Thanks for your great effort so far!
[Nexus 9 Android Development] tamjan:
How difficult would it be to provide a lineage-13 rom for flounder_lte? Given that xposed doesn't exist for nougat yet, marshmallow is still very interesting. I haven't upgraded yet, and probably wont until xposed exists.
[Nexus 9 Android Development] compuguy1088:
I have a build server where I do nightlies for a bunch of devices. Since I own a nexus 9 LTE, I may add it to my morning (EST) builds. I also have a androidfilehost account (that I really need to update with new builds) as well.

Update, I configured a job for flounder_lte, it should run tomorrow morning, eastern standard time.
[Nexus 9 Android Development] McFlypants:
That would be great!! Hoping i get LTE working then