yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] followmsi:
I was even quicker as the pormised 30 minutes. :)

Pls delete the file you have .. and start a new download ..

AOSP_7.1.1_r28_N6F26U_flo-ota-eng.followmsi.zip

AOSP_7.1.1_r28_N6F26U_deb-ota-eng.followmsi.zip

The same files again .. same name - other files.

You will have no problems to install anymore :)

Cheers
[Nexus 7 (2013) Android Development] drewski_1:
anyone else having issues with Titanium Backup restoring apps? it just spins and spins and nothing seems to be happening.

i did grant it root when it launched. i thought it might be F2FS, but still doing the same thing after i converted back to Ext4
[Nexus 7 (2013) Android Development] mrbtree98:
https://www.xda-developers.com/psa-...broke-titanium-backup-substratum-heres-a-fix/
[Nexus 7 (2013) Android Development] TechnicsKuzya:
Hi, yesterday I installed this ROM and have a trouble with battery life... Doze don`t work? Why is "Miscellaneous"eating battery? Why is "Cellular network signal graph" in Wi-Fi tablet, usually if RED it eating battery too!!?
[Nexus 7 (2013) Android Development] followmsi:
Do you have more Android devices ?

Did you check the same value on the other devices ?

All my wifi tablets (3 Nexus devices on different ROM) show me red signal for mobile networks, no battery drain on all 3 devices.

On this ROM my "miscellaneous" is consuming 23% right now .. seems to be depending on the usage.

For me the battery life is quite good .. nothing to complain.
[Nexus 7 (2013) Android Development] fede01_8:
I downloaded Gapps from http://opengapps.org/ ARM, 7.1, Pico version. The install completes successfully however when I reboot none of the apps show up. Help!
[Nexus 7 (2013) Android Development] TechnicsKuzya:
I have Deb version with same ROM, if I enable Fly mode and then tap Wi-Fi switch (Wi-Fi on) - no any signal graph for mobile networks and Battery graph horisontal line!!! Now I install stock 6.0.1 at Deb and test it again, because IMHO I have a better battery life with it (6.0.1 stock). May be Wi-Fi lost cause eating battery, my timer switch off router at night!?

P.S. And now change the kernel at the Flo tablet (with your last ROM).
[Nexus 7 (2013) Android Development] followmsi:
When you install pico there will be only the play store available, nothing more.

(Text-to-speech as well)

Do you see the play store icon ?

Good luck !
[Nexus 7 (2013) Android Development] fede01_8:
Ok, I fixed it! Here's the solution in case anyone comes from google with the same problem: the custom TWRP on the OP doesn't install it even if the log says it did.

As opengapps.org says:

So, make sure you're using the official TWRP. :good:
[Nexus 7 (2013) Android Development] followmsi:
Sorry, you have this problem .. the TWRP here install gapps as expected.

Anyway .. fine that you have it running now.
[Nexus 7 (2013) Android Development] drewski_1:
Installs fine for me with OP TWRP
[Nexus 7 (2013) Android Development] TechnicsKuzya:
Now Install your last ROM with ElementalX-N7-6.05 at the Flo tablet and the stock 6.0.1 at the Deb one - test it this night and post results here.
[Nexus 7 (2013) Android Development] RazGame:
Can I flash it on my deb ?
[Nexus 7 (2013) Android Development] followmsi:
Yes ..

2.*Install*the Kernel Update.Zip*file*(the kernel works for flo and deb*devices)
[Nexus 7 (2013) Android Development] followmsi:
No .. not as I know.
[Nexus 7 (2013) Android Development] RazGame:
@ followmsi, So... Android O AOSP available now ?
[Nexus 7 (2013) Android Development] followmsi:
Yes the Oreo sources are available now.

Started with AOSP Oreo ROM for Pixel C .. to get some first impressions.

As it's a supported device the migration goes more or less quickly.

Still a few issues left.

The flo/deb versions will take longer .. too many changes under the hood.

- Starting with missing sdcardfs support inside flo kernels - except for glitch kernel.

- On first boot of Android Oreo your internal storage will be converted to sdcardfs format.

- Quota needs to be enabled too.

- Android binder seems to have changed as well.

- Causing boot-loops while booting into Android system.

- The "old" flo/deb sources need to be merged with 8.0 sources, if possible and applicable.

- Tons of build errors are expected :(

- And the 50 other problems I am not aware of - yet ;)

etc. ..

Takes plenty of time .. hope you have a better understanding now ..
[Nexus 7 (2013) Android Development] :
No need to rush, we are grateful for you even trying to bring 8.0 to flo :)
[Nexus 7 (2013) Android Development] whaevr:
Despite the name sdcardfs isn't a filesystem format, there will be no need to convert anything. You just need to mount them with the sdcardfs option instead of fuse.

Read more about it here and see examples on the differences between Oreo and Nougat
[Nexus 7 (2013) Android Development] followmsi:
Thanks for the update .. the internal storage will be mounted and not converted.

It's not a real file system like F2FS ..etc.

Nevertheless SDcardFS needs to be integrated into kernel .. and the work has to be done ;)

flo-kernel-aosp-20170825.zip

flo-kernel-aosp-20170825.zip.sha1

The kernel is working on flo and deb devices !

Changes:

- Ported "SDcardFS" from Glitch kernel into "stock" google msm kernel. ( Thx to [MENTION=3847629]Tk-Glitch[/MENTION] )

- Enabled Quota

- Change Android Binder configuration - to hopefully work with Android Oreo.

Installation:

1. Boot into TWRP

2. Install the Kernel Update.Zip file

3. Reboot into system .. no need for SuperSU / Magisk !

Tested on latest Android Nougat ROM.

Sources:

https://github.com/followmsi/android_kernel_google_msm/tree/followmsi-oreo_2017-08-25

Enjoy :p
[Nexus 7 (2013) Android Development] RazGame:
Maybe you can ask dev's of Oreo for Mi3/4 somethings
[Nexus 7 (2013) Android Development] followmsi:
Made the OpenGapps package for Android Oreo .. until the official version is ready.

Initially done for "arm64" version (Pixel C) .. but as you have to download all the sources for "arm" architecture as well.

Here is the arm verison for flo/deb devices ..

open_gapps-arm-8.0-stock-20170823-UNOFFICIAL.zip

Pls use the following config file as example ..

.gapps-config

Just the Oreo ROM itself is missing now :p
[Nexus 7 (2013) Android Development] followmsi:
Thanks for the info ..

Would like to see the device tree sources .. and their other customizations on GitHub .. or somewhere else - online.

The first BETA Oreo version is ready .. for flo device only.

I did not install/test this ROM until now .. maybe it's not booting at all.

Here you are ..

AOSP_8.0.0_r1_OPR6.170623.010_flo-ota-eng.followmsi_BETA-1.zip

The next time slot for "playing" with Android Oreo will be hopefully soon .. to get a BETA-2 version.

Again I did not test this ROM myself - not yet.

EDIT:

Quick technical update too ..

- F2FS support inside fstab.flo for /data partition has been removed.

- Used kernel from today - SDcardFS support .. etc.

- Selinux problems to be expected - as kernel is still "enforcing". (change manually to "permissive" for better testing -> setenforce 0)
[Nexus 7 (2013) Android Development] wavedashdoc:
[MENTION=5480152]followmsi[/MENTION] the Unofficial 8.0 GAPPS were too large for the system partition (error 70) fixed this by adding "gapps-config.txt" with NanoGApps inside the file to force it to shrink the install. Successfully flashed.

But... the beta Oreo build doesn't boot. Goes to google logo, then black for about 1 minute then to the bootloader. Tried again in TWRP and it failed to show the data partition as mounted. So unable to flash anything.

Used the old nexus root toolkit and restored factory 6.0. Will try again once I'm back up and running, with pico setting. Thanks for your hard work! Crazy to think that this device might see 8.0 before my nexus 6 lol.

EDIT: Wiped my storage partition. Make sure you save all your files before attempting this!

EDIT2: Second attempt failed as well. Won't get to the boot animation, and returns to bootloader. All storage is wiped.
[Nexus 7 (2013) Android Development] seansheng0412:
Can This version select language as "Chinese" ?

Can This version select language as "Chinese" ?

It's difficult to type on the phone.
[Nexus 7 (2013) Android Development] followmsi:
Thanks for your testing and report.

When you have flashed stock in between you use ext4 for /data partition.

If you still use F2FS you would get problems too.

/data should be formated to ext4 for testing the BETA.

If TWRP is not able to mount /data - SDcardFS is missing in TWRP kernel too ..same problem on Pixel C.

Had to use a new kernel for TWRP on Pixel C.

But you can still do installations via usb-otg at this point.

Will make a new TWRP version including the new kernel to support sdcardfs.

Made a kernel with disabled selinux for flo/deb .. in the same download folder - the permissive version.

Not sure if disabled selinux will fix booting .. I doubt.

Now we need to know what is blocking the boot process ..? ;)

Most probably the kernel.

You see .. because of all this issues you may get Oreo first on Nexus 6 ;)
[Nexus 7 (2013) Android Development] wavedashdoc:
You're welcome. Glad to assist!

I was using normal ext4, never bothered to go to F2FS.

Yeah I was thinking it was along the lines of an incompatibility, since each try resulted in the same case of losing the ability to see the data partition. I'm back up and running on your latest 7.1.2 with no issues.

Haha, it's always the same cycle when a new version of Android comes around. ??
[Nexus 7 (2013) Android Development] followmsi:
Thanks for the update .. strange issue indeed.

Made some more tests .. running Android 8.0 on Pixel C.

Tested TWRP using a Nougat kernel with SDcardFS support on Pixel C ... can't read my data partition anymore -> similar problem like on flo device.

If I just replace the kernel inside the recovery.img with Oreo kernel it works again - you can mount data without issues.

Compared Oreo and Nougat SDcardFS sources .. not much changes here - seems not to be the root cause of the problem.

It seems there are "more" kernel changes required to make Oreo working, more as just activating SDcardFS.

What is also very strange .. inside TWRP the sideload function does not work using the Oreo kernel.

The recovery.log is compaining about missing "libhwbinder.so" - never been part of the TWRP ramdisk.

They did kernel changes for the android binder .. maybe related.

Pixel C is using 3.18 kernel version and is still an official supported device .. You can easy build Oreo or Nougat kernels - as you have the sources available.

All Oreo supported devices are using verion 3.10 or above - but for sure no 3.4 kernel version like used for flo/deb. devices.

Maybe I will ask Glitch and other kernel guys for some help .. to make 3.4 kernel version ready for Oreo :)
[Nexus 7 (2013) Android Development] followmsi:
Default AOSP settings .. no changes are done.

But first we need to get it running at all :)
[Nexus 7 (2013) Android Development] poondog:
On bullhead there were some big changes to binder for oreo,

Including some defconfig changes.

Also the binder binaries might not be suited to our architecture

Just some things I've noticed diffing sources

Thanks for your work on this device
[Nexus 7 (2013) Android Development] followmsi:
Yes, quite some changes ..

Would love to checkout android-8.0.0_r0.2 and start compiling.

https://android.googlesource.com/kernel/msm/+/android-8.0.0_r0.2

And if you compare all the changes to "old" 3.4 flo binder implementation you will see even more differences.

Is it possible to port relevant 3.10 changes into flo/deb 3.4 kernel at all ?

If yes, who is able to port it ? .. not me - that's beyond my skills.

We need the kernel specialists here ;)
[Nexus 7 (2013) Android Development] mick3lson:
I've nexus 7 2013 with factory firmware image-razor-mob30 and TWRP_flo_3.1.1-0, is possible to install multirom to test your release AOSP_7.1.2_r28_N2G48C in other partition.
[Nexus 7 (2013) Android Development] followmsi:
Pls have a try .. did not test myself.

Pls let me know your results.
[Nexus 7 (2013) Android Development] defim:
Same experience ... lost internal storage data :-\ I should read before flash

TWRP was still there, so i used adb-sideload to install an aosp and los image. both asked for a "decrpytion password" .. i never used this feature :confused:

After some fails it showd me the option to factory reset but this did not help ^^
[Nexus 7 (2013) Android Development] followmsi:
Thanks for your update ... did not made any more tests for flo device.

But I have repacked TWRP with the same kernel we use in this Oreo ROM - to enable SDcardFS support in TWRP.

If you have time and want to test again ... pls use this TWRP version.

TWRP_flo_3.1.1-0_2017-08-26-Oreo.img

The discussion from above ..

If the kernel will need an updated binder version and other updates to work properly on Oreo we might have an bigger issue.

In this case the changed TWRP kernel will not help either.

Thanks
[Nexus 7 (2013) Android Development] RazGame:
Oreo for Nexus 5
[Nexus 7 (2013) Android Development] wavedashdoc:
Thanks [MENTION=5480152]followmsi[/MENTION]. A beta Nexus 6 Oreo build was released and successfully booted. Everything is working except Bluetooth. (and a little bit of screen tearing) Since Oreo is based off 5.0 and the stock driver is currently incompatible to run 5.0 Bluetooth. It's running a 3.10 kernel, so that maybe why they had success. I'll test flo tonight if I have time. Thanks for your continued support! ?
[Nexus 7 (2013) Android Development] followmsi:
I am typing on 3.18 Oreo kernel .. AOSP Pixel C.

3.10 is also "supported" .. Nexus 5X .. etc.

The Nexus 5 ROM above is more interesting.. it has 3.4 kernel. :)

Have already cherry picked all the Oreo changes into flo kernel.

Trying to fix build errors ..

If I will manage we can try BETA 2 .. and a new Oreo TWRP as well .. to be able to mount data.

Step by step ..
[Nexus 7 (2013) Android Development] followmsi:
Thanks for the link ..

I did merge all 50+ Oreo changes into flo/deb kernel.

Cherry picked all the changes and fixed a few build errors.

The new kernel has been compiled successfully now :)

Sources:

https://github.com/followmsi/android_kernel_google_msm/tree/followmsi-oreo_2017-08-29

Just started the build process for BETA 2 .. will post the new ROM later.

Cheers
[Nexus 7 (2013) Android Development] followmsi:
ccache is your friend .. :)

Now with the new "oreo" kernel .. pls have a try yourself.

AOSP_8.0.0_r1_OPR6.170623.010_flo-ota-eng.followmsi_BETA-2.zip

Maybe the ROM is still not booting .. but the implemented kernel changes are looking quite good.

We will see ..

If the kernel is working fine we can make a new TWRP version too.

Happy testing [emoji14]
[Nexus 7 (2013) Android Development] :
Still EXT4 only?
[Nexus 7 (2013) Android Development] followmsi:
Yes, for data is ext4 .. due to new quota function.

The kernel still support F2FS .. and the cache partition too.

If quota is working fine on F2FS I will add it for data too.
[Nexus 7 (2013) Android Development] dc239:
So i tried your beta 2 and it still doesn't boot. I don't know if it will help, but i included the last kernel message in this post
[Nexus 7 (2013) Android Development] followmsi:
Thanks for testing and logs ..

Data partition will not be mounted .. due to quota.

Will test without quota .. within the next flo/deb time slot.

And some services have problems too ..

Still a lot to do ..
[Nexus 7 (2013) Android Development] yattodettaman:
[MENTION=5480152]followmsi[/MENTION]:

here, another oreo rom for 3.4 kernel:

https://xdaforums.com/oneplus-one/orig-development/rom-aosp-oreo-oneplus-one-t3666741

Everything works !

A little question for you. Where if the file_context.bin in your rom ?!
[Nexus 7 (2013) Android Development] followmsi:
Thanks for the info .. will have a look.

The kernel is one thing .. but for Oreo you need to modify the flo/deb device config as well.

Plenty of changes.

Still not sure if the problems are kernel or ROM related .. or both.

file_context.bin seems to be splitted now ..

plat_file_contexts

nonplat_file_contexts

Anyway .. my time is limited and my knowledge too.
[Nexus 7 (2013) Android Development] ThanhNguyenn:
tks teammm...
[Nexus 7 (2013) Android Development] emmett.tsai:
[MENTION=5480152]followmsi[/MENTION]:

I have a test build on android oreo, base on android_8.0.0_r1

it can boot into android success, but still have a lot of issue.

here is the ota zip, boot.img, system.img, aosp recovery, and patch files

https://drive.google.com/open?id=0Bw-VQoPa51QWMXBNLUJ4RzBONFE

aosp_flo-ota-eng.emmett.zip

it can update by adb sildeload in recovery mode

sorry , i have no time to prepare a github repo for download yet, so just give patch here

flo-oreo-patch-20170907-064504.tar.bz2

./local_manifests

./NOTE

./patch

├── device

│** └── asus

│** └── flo

├── hardware

│** └── qcom

│** ├── audio

│** └── gps

├── kernel

│** └── msm

├── system

│** ├── bt

│** ├── core

│** └── sepolicy

└── vendor
[Nexus 7 (2013) Android Development] Aerys:
Good job! Whats working so far? :)
[Nexus 7 (2013) Android Development] followmsi:
Thanks a lot for your input .. and your ROM.

Well done !

Had a quick look .. your config is very similar .. used also the same repo as base for the Oreo changes.

https://github.com/AgentFabulous/android_oreo_bacon

Except for your selinux config .. which I did not really start yet.

Anyway you managed to get it booting .. again - well done.

Whatever I did change in the last days .. the bootanimation will not show up. :(

Would help a lot if you could upload the sources to Github.

Would love to have more time to proceed better here ..

Thanks

EDIT:
[MENTION=8199534]emmett.tsai[/MENTION] .. pls upload the device tree (only) to Github .. would help a lot - Thanks !
[Nexus 7 (2013) Android Development] .MoHaMaD:
edite updater-script

Successful installation

- Bluetooth WiFi USB Music : not work

show_progress(0.750000, 0);
block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat") ||
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
show_progress(0.200000, 10);
set_progress(1.000000);
[Nexus 7 (2013) Android Development] emmett.tsai:
[MENTION=4695277]Aerys[/MENTION]:

I'm not sure what's work now, just let it can boot into android success, have not do more test yet

[MENTION=5480152]followmsi[/MENTION]:

I found a miss patch in vendor folder, i forgot commit it before do format-patch.

https://drive.google.com/open?id=0Bw-VQoPa51QWckxoZVFzc3JHQlE

remove line : vendor/qcom/flo/proprietary/libsensor1.so:system/lib/libsensor1.so:qcom

in qcom/flo/device-partial.mk

load libsensor1.so fail will cause service died, just skip now for test

yes, i fork device tree, vendor, kernel source from [MENTION=4318865]DevSwift1[/MENTION] https://github.com/aosp-msm8960,

and reference/pick patch of device tree and kernel from

[MENTION=5834335]AgentFabulous[/MENTION](on bacon)、[MENTION=5501864]USBHost[/MENTION] (on Nexus9 ) and android-msm-marlin-3.18-oreo-r6

I will prepare github repo after off work today

[MENTION=4551527].MoHaMaD[/MENTION]:

thanks for test, maybe need implement HIDL, I'm not sure

I'll study andorid HIDL doc later after off work today
[Nexus 7 (2013) Android Development] emmett.tsai:
[MENTION=5480152]followmsi[/MENTION]

I setup github repo done, here the android oreo source for flo test:

https://github.com/EmmettTsai/manifest/tree/flo-oreo-test
[Nexus 7 (2013) Android Development] followmsi:
Cool .. thanks a lot !

I will have a look .. and build.

Hopefully on the weekend.
[Nexus 7 (2013) Android Development] followmsi:
Finally it's booting .. I did merge the new 8.0.0 branches into the existing 7.1.2 branches .. this was my problem.

"My" kernel was not working either.

Thanks to [MENTION=8199534]emmett.tsai[/MENTION] for the sources .. helped a lot - used your kernel sources now.

And some other stuff .. thanks again !

The flo lineageos maintainer is working on flo oreo kernel.

I guess/hope he will start working on flo device sources soon .. and other developers too.

The name "BETA" was quite optimistic at this point of time .. we should call it ALPHA ..

Netherless .. BETA-3 :)

AOSP_8.0.0_r1_OPR6.170623.010_flo-ota-eng.followmsi_BETA-3.zip

Tested the ROM .. same "level" like from [MENTION=8199534]emmett.tsai[/MENTION] - nothing works .. maybe audio a bit.

Have installed opengapps .. but the apps are not starting .. yet.

USB is not working .. especially adb is not working too - makes troubleshooting more time consuming.

Enabled F2FS again .. as we dont force quota in fstab - enabeld for both partitions - cache and data.

Next steps ..

Get USB (adb) working

Get WiFi working ..

etc.

It's just a matter of time until Oreo will run (smoothly) on flo/deb devices .. please be patient.

Happy testing :p
[Nexus 7 (2013) Android Development] jaucar:
Thanks for your work.

I installed the beta, I installed opengaps and the system boots.

It shows very unstable, the screen shakes, and the keyboard produces strange effects.

Many of the services do not work.

But work is on the right track

Thanks again
[Nexus 7 (2013) Android Development] dealpapa1:
https://source.android.com/security/bulletin/2017-09-01
[Nexus 7 (2013) Android Development] followmsi:
WiFi works now ..
[Nexus 7 (2013) Android Development] edgar096:
you think its time the oreo rom is ready to have a thread of itself?
[Nexus 7 (2013) Android Development] followmsi:
Starting to like your short comments .. no more words required :)

And here is my longer answer ...

I was hoping for a "proper" tagged September release from google .. actually the last 7.1.2 tagged release.

But they did include September pachtes already into first official ROMs for Oreo.

Only volantis got Septmeber release .. still based on 7.1.1 and not 7.1.2

In theory .. like a big company with much resources/developer will start to cherry-pick/merge all the relevant CVE changes/patches for september into their branches and make a new custom build . .for their customers.

As we know .. not all phone/tablet producer are releasing regular monthly updates like google .. another topic.

But as I am a "one-man-show" doing this stuff for fun I will not update Nougat branches this way .. :)

The same reason why for example purenexus has renamed/moved the nougat sources into "legacy" github.

Actually all the custom ROM developer are moving to Oreo .. clsing down the Nougat sources and starting over with Oreo.

Oreo has a lot of changes again .. they all need time to be implemented .. this takes time .. a lot of time !

Sounds hard .. but Nougat is legacy [emoji14]

EDIT:

Google released September updates today.

The reports were wrong including September patches in August already.

Anyway .. no 7.1.2 tags anymore .. just 7.1.1 and 8.0.0.
[Nexus 7 (2013) Android Development] followmsi:
Actually not :)

The plan is to move slightly into Oreo .. one thread is enough - at least for me.

As written above .. there will be no Nougat releases coming anymore.

To make it more visible I will rename the OP to AOSP OREO BETA .. later on.

The BETA4 is the next step forward .. not sure when I wil lfind time to work again on flo/deb device.

Sorry, but within this BETA period you have to "live" with the current status of the BETA or you move back to Nougat.