[Treble-Enabled Device Guides, News, & Discussion] tripLr:
Update News Flash Galaxy note 4 running Oreo 8.1

3-29-18

OMG. I said it here first. 32 bit processors CAN be ported to Oreo. Maybe not trebel yet. Smug emoticon

In just a few days , not even I thought it was possible.

Running Oreo via lineageOS 15.1 with root on my Samsung Galaxy Note 4.

The dev who devotes time to compiling builds [MENTION=6005084]ripee[/MENTION] has had his daily downloads of 14.1 for the note 4 has more than doubled. Currently running about 250 users testing builds. SMOKIN.....

Here is the OP

https://xdaforums.com/note-4/snapdragon-dev/oreo-8-1-0-unofficial-lineage-15-1-rom-t3760969/page92

Update 2-28-18

OpenGapps 8.1 is released for both arm and arm 64.

That means Oreo can be compiled it 32 bit.

Researching Oreo and Oreo go compiler instructions.

Mebbe I can compile AOSP for my older Note 4 .. So cool

https://xdaforums.com/android/apps-games/arm-unofficial-opengapps-builds-android-t3743495

Updated 1-20-18

Newest musings on top. Oreo Go is currently being modded into an older Sony phone. Awesome

So since I posted this OP...my musings have been correct in these posts.

This came out on XDA, check out the links in it.

https://www.xda-developers.com/android-go-old-android-8-1-oreo/

Android Oreo and android in general is getting closer to Linux . Mainly for the same reasons

I have been installing different distributions of Linux on an older laptop.

1. To learn installing hard to find drivers

2. Learning Linux architecture and commands

3. Learning to build Linux kernel for my device

http:// www.kernel.org

4. Learning to build lineageos14 in general

With these guides

https://xdaforums.com/note-4/general/guide-build-lineageos-14-1-trltexx-t3567885

Thanks [MENTION=6847876]_mone[/MENTION] and [MENTION=6005084]ripee[/MENTION]

https://xdaforums.com/chef-central/android/how-to-build-lineageos-14-1-t3551484

Thanks [MENTION=4315132]FSadino[/MENTION]

5. Actually compiling lineageOS-14 for my two devices I have access to

Galaxy note 4 Verizon thanks to [MENTION=6005084]ripee[/MENTION] for his contribution by building daily's at

https://xdaforums.com/note-4/snapdragon-dev/rom-lineageos-14-1-t3536401

And my galaxy tab S2 sm-t710

Thanks to [MENTION=3195328]Bonuzz[/MENTION] for getting the camera, mic GPS and Bluetooth working, and posting sources

https://xdaforums.com/tab-s2/development/t710-t715-lineage-14-1-t3713097

Thanks to [MENTION=494193]Ather[/MENTION] for getting Samsung to release their Kernel sources and building a android 7 rom

https://xdaforums.com/tab-s2/development/kernel-poseidonkernel-v1-0-permissive-t3588069

https://xdaforums.com/tab-s2/development/rom-poseidonrom-v1-0-deodexedrooted-t3590228

6. Thinking and musing about things

Symlinks, multi boot, and partitions. ( Treble )

In Linux, I have another partition with downloaded files on another drive

When the kernel boots, the directory tree just sees /data even though it's a separate drive

This is because of a symbolic link that mounts the partition as a folder. This prevents me, from deleting that data with permissions

So the Trebel rules tell the vendor to make a separate partition in the drive but the kernel gets a symbolic link to it, and the user (Google) cannot over write the partition with the critical info..when the ROM gets flashed? correct ?

The bootloader has boot path a, or boot path b.

The user files are in protected memory

So with Linux, when I updated my kernel,

The grub bootloader tells me I can use kernel 4.1.x or 4.2.x when I boot

The kernel loads the drivers

And then looks at the symbolic links to mount the drives.

This is somewhere in the /etc files or somewhere

So Trebel has to be a set of decision trees based on symbic links to hardware

Where all the hardware drivers are independent of the kernel

More musings later. Must build....

**************

Dec 2017 sometime

Thanks to all for viewing my first OP.

I'm just learning about building ROMs, and look forward to this thread to spitball ideas and see what sticks.

If I don't know something its because I am correcting my ignorance.

This won't be an actually development thread, just trying to understand hardware from 30 years of not being in the tech field.

Eventually I will tire or wear out of driving truck, and work with my passion again.

I am a follow the steps kind of mind, so I am learning how the world of Android / Linux works.

If I understand the Trebel development correctly...

https://www.xda-developers.com/goog...ze-android-so-oems-can-update-devices-faster/

IF we can modify the older device drivers to be Trebel compliant, then once they work, then they always should work. And any Trebel ROM can work on Any Trebel Device withOUT compiling over and over.

This should result in an explosion of custom ROMs .

So I am suggesting a repository of drivers per device that are compliant for older devices.

How do we do that?

So here is the Google announcement of Trebel

https://android-developers.googleblog.com/2017/05/here-comes-treble-modular-base-for.html?m=1

Here is the developer preview of ”O”

https://developer.android.com/preview/download.html

It details how to install it on your Trebel Device.