Develop Bugs

[LOLLIPOP] Xperia AOSP Project

hi all
we have included this device in open devices project
you can check news about project on
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
feel free to fork, build, fix and push back
Br
J
PS.
in case latest software does not appear just press "all Services"
flash latest software available and on top new loader

Custom ROM We Want! (Xperia T3 D5102)

jerpelea said:
hi all
we have included this device in open devices project
you can check news about project on
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
feel free to fork, build, fix and push back
Br
J
Click to expand...
Click to collapse
Good news for T3 devices!

All we need now is cwm/twrp recovery and the show may begin!!
great lollipot binaries... so android 5.0 will finally come to T3 ;p

updated guide and blobs for android Lollypop version 5.0.1
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/

How do we set up?

Berkant Ayhan Karabudak said:
How do we set up?
Click to expand...
Click to collapse
if you read the guide you will see

jerpelea said:
if you read the guide you will see
Click to expand...
Click to collapse
I am in turkey. My english is not so good.

Do you make installation guides?

AOSP 5.0.2 is published
http://developer.sonymobile.com/kno...ld-aosp-lollipop-for-unlocked-xperia-devices/

http://developer.sonymobile.com/kno...ld-aosp-lollipop-for-unlocked-xperia-devices/
- updated L build guide published
- new blob zip
- wifi is built into kernel
- media is built from source now
- NFC built from source
- audio built from source
- GPS built from source
enjoy
J

Error in sony.xml
<project path="device/sony/kernel" name="kernel" groups="device" remote="sony" revision="aosp/LNX.LA.3.5.2.2-03010-8x74.0 " />
Click to expand...
Click to collapse
You have a space after 8x74.0 and the "

jerpelea said:
hi all
we have included this device in open devices project
...
feel free to fork, build, fix and push back
Click to expand...
Click to collapse
It seems to be fine idea before (or instead?) official release will come.
How much unstable is it?
Ok. Checked.
Git fetched 32GB of data. The laptop wheezed ~9 h but finally it is done.
The system itself works fine. But.
It is completely nude. I've been trying to insert Google Play Services. Defeat.
So. There is no possibility to connect it with Google account and services.
I'm afraid aosp is going to be always to
experimental for regular use. As it is development version.

lalotche said:
It seems to be fine idea before (or instead?) official release will come.
How much unstable is it?
Ok. Checked.
Git fetched 32GB of data. The laptop wheezed ~9 h but finally it is done.
The system itself works fine. But.
It is completely nude. I've been trying to insert Google Play Services. Defeat.
So. There is no possibility to connect it with Google account and services.
I'm afraid aosp is going to be always to
experimental for regular use. As it is development version.
Click to expand...
Click to collapse
AOSP is intended to be a stable base for custom ROMs and developers
you can make your own ROM with all the apps you desire
br
J

build guide has been updated for easy reading
http://developer.sonymobile.com/kno...evices/how-to-build-and-flash-a-linux-kernel/
br
J

jerpelea said:
AOSP is intended to be a stable base for custom ROMs and developers
you can make your own ROM with all the apps you desire
br
J
Click to expand...
Click to collapse
That sounds better.
I have not enough time to make it seriously and full time but I've got a few ideas to try and of course - I'm going to check new aosps and new GServ. releases.
As Google services are essential for android functionality until I get it stable I won't try to build more complex set.
Sent from my D5103 using XDA Free mobile app hurray

First shot.
So. It was little trouble for google made geek.
After a few hours of hard fight (I mean hard googling) I've got rooted system and gaps working.
I decided to root it to easier play with system apps. I did not want to hack source tree as well.
Curious - make_ext4fs changes file privileges (I've needed to add some stuff into system.img).
I had to add some lines to init.rc to correct it.
There are some minor issues appearing in dmesg - could live with that.
And the one major problem - internal speaker is dumb.
Ear phones works right, but speaker is necessary - this is my only phone
l

custom rom for sony T3 D5102
please port custom rom for sony xperia T3 D5102:good::good::good::good:

So, considering I'm a new owner of a Xperia T3, we can say that 5.0.2 ROMs are working "ok" except from speaker and camera that are not working?
I'm considering install an AOSP ROM because I love pure android but I guess I'll give a try to Sony's one until this ROM is perfectly stable.
Have nice day!
Enviado desde mi XT1032 mediante Tapatalk

gbueno6 said:
So, considering I'm a new owner of a Xperia T3, we can say that 5.0.2 ROMs are working "ok" except from speaker and camera that are not working?
Click to expand...
Click to collapse
Yes. It looks, that everything else for D5103 is ok.
I checked headphones, microphone, gps and wi-fi.
I did not check bt, nfc and others (accelerator?) but nobody reported its faults.
For me speaker is necessary but if you like I've got even rooted 5.0.2 with gaps (git 2015-02-15).
l

[Sony] Xperia Open Devices Project

Sony Mobile is committed to supporting the open developer community, and one way to show this is by publishing parts of our code as well as selected tools developed by our internal developers.
For some of the Xperia™ devices, we provide Android™ Open Source Project (AOSP) device configurations on GitHub. This means that the software will be open for you as a developer to use and contribute to. This is a way for us to support the open Android community, and it is also a tool for us to facilitate and verify contributions to AOSP.
If you want to build AOSP for your unlocked Xperia device, you find all the resources you need in the sections below.
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
Unified 3.10 kernel sources
https://github.com/sonyxperiadev/kernel
Project git
https://github.com/sonyxperiadev/

jerpelea said:
Sony Mobile is committed to supporting the open developer community, and one way to show this is by publishing parts of our code as well as selected tools developed by our internal developers.
For some of the Xperia™ devices, we provide Android™ Open Source Project (AOSP) device configurations on GitHub. This means that the software will be open for you as a developer to use and contribute to. This is a way for us to support the open Android community, and it is also a tool for us to facilitate and verify contributions to AOSP.
If you want to build AOSP for your unlocked Xperia device, you find all the resources you need in the sections below.
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
Unified 3.10 kernel sources
https://github.com/sonyxperiadev/kernel
Project git
https://github.com/sonyxperiadev/
Click to expand...
Click to collapse
Will Open Devices recovery work with unlocked bootloader and Stock ROM? Or is it intended for Custom ROMs only? I ask because Stock ROMs are using recovery partition for FOTA and the only Stock that brings new partitioning scheme - the new Concept UI ROM - uses nasty security measures against changing either recovery or system partition...
Sent from my D6603 using Tapatalk

ondrejvaroscak said:
Will Open Devices recovery work with unlocked bootloader and Stock ROM? Or is it intended for Custom ROMs only? I ask because Stock ROMs are using recovery partition for FOTA and the only Stock that brings new partitioning scheme - the new Concept UI ROM - uses nasty security measures against changing either recovery or system partition...
Sent from my D6603 using Tapatalk
Click to expand...
Click to collapse
I think this link would indicate that it is meant for UB at this stage.
However I am building the AOSP android M preview, and will report back with my findings.

shoey63 said:
I think this link would indicate that it is meant for UB at this stage.
However I am building the AOSP android M preview, and will report back with my findings.
Click to expand...
Click to collapse
I meant combination UB+Stock. That UB alone is required is clear
Sent from my D6603 using Tapatalk

ondrejvaroscak said:
I meant combination UB+Stock. That UB alone is required is clear
Sent from my D6603 using Tapatalk
Click to expand...
Click to collapse
The link says to first install generic software on your device, so yes when released, UB+Stock will work.
But obviously, it will be different to the android concept scenario which (by my reckoning), is just a test by Sony on how to prevent people from rooting their phones on locked bootloader under the guise of providing a minimalistic Sony AOSP like experience. It is my opinion that they will implement it in their future devices.
Edit: I misread you post. Quite clear you were talking about UB

shoey63 said:
The link says to first install generic software on your device, so yes when released, UB+Stock will work.
But obviously, it will be different to the android concept scenario which (by my reckoning), is just a test by Sony on how to prevent people from rooting their phones on locked bootloader under the guise of providing a minimalistic Sony AOSP like experience. It is my opinion that they will implement it in their future devices.
Edit: I misread you post. Quite clear you were talking about UB [emoji14]
Click to expand...
Click to collapse
Anyway, if Sony would mean it seriously with security restrictions in Concept, then we have to go on at least with custom kernels. As soon as Z3 will be in Open devices, majority of problems like fish-eye camera problem may disappear. I think unified kernel sources for 3.10 are already online.
Sent from my D6603 using Tapatalk

Built it, flashed it, bootloops on kernel splash screen

shoey63 said:
Built it, flashed it, bootloops on kernel splash screen
Click to expand...
Click to collapse
With which fw you use it?
Sent from my D6603 using Tapatalk

Flashed back to pure stock. Version doesn't matter I think. Fastbooted the images and got stuck in an hypnotic bootloop. Kernel splash screen over and over...
Sent from my C6603 using XDA Free mobile app

ondrejvaroscak said:
Will Open Devices recovery work with unlocked bootloader and Stock ROM? Or is it intended for Custom ROMs only? I ask because Stock ROMs are using recovery partition for FOTA and the only Stock that brings new partitioning scheme - the new Concept UI ROM - uses nasty security measures against changing either recovery or system partition...
Sent from my D6603 using Tapatalk
Click to expand...
Click to collapse
recovery is intened for unlocked bootlaoder and custom roms only
br
J

shoey63 said:
I think this link would indicate that it is meant for UB at this stage.
However I am building the AOSP android M preview, and will report back with my findings.
Click to expand...
Click to collapse
i will update build guide for m-preview1 and publish new zip soon
the old blobs from m-preview are incompatible with new m-preview1!
br
J

I'm interested in building an AOSP (5.1.1) firmware for myself. However I lack the knowledge to do so. So bear with me as I ask a few stupid questions while I'm trying to learn something new.
First of all, if I were to follow the instructions on the link on the OP, does that mean that I'm able to build a perfectly working AOSP (5.1.1) firmware?
Secondly, I'm assuming that I need Ubuntu or Linux?
Thirdly, I don't quite understand how does one flash the firmware once it's built. I mean does it provide a kernel with a recovery or do I have to use the unified kernel?
Lastly, is root possible? (Not important)
Sent from my D6653 using Tapatalk

LeParkour012 said:
I'm interested in building an AOSP (5.1.1) firmware for myself. However I lack the knowledge to do so. So bear with me as I ask a few stupid questions while I'm trying to learn something new.
First of all, if I were to follow the instructions on the link on the OP, does that mean that I'm able to build a perfectly working AOSP (5.1.1) firmware?
Secondly, I'm assuming that I need Ubuntu or Linux?
Thirdly, I don't quite understand how does one flash the firmware once it's built. I mean does it provide a kernel with a recovery or do I have to use the unified kernel?
Lastly, is root possible? (Not important)
Sent from my D6653 using Tapatalk
Click to expand...
Click to collapse
For the second question.. You need any environment that supports git and compiling. The instructions are given for Ubuntu and I would stick with that. Ubuntu or compatible Debian based distro.
You get kernel, system and data images at the end. Those you flash in fastboot mode. See instructions. So far it doesn't provide recovery, but recovery may already be available for supported Open Devices. Once you flash recovery, it's kept in separate partition so you can boot it regardless of kernel.
As for rooting, you can do it with recovery or you can include su in your aosp system.
Sent from my D6603 using Tapatalk

jerpelea said:
recovery is intened for unlocked bootlaoder and custom roms only
br
J
Click to expand...
Click to collapse
Hi, I would paraphrase the Apollo 13 - "It is not important what it is intended for, but what it actually can do"

ondrejvaroscak said:
For the second question.. You need any environment that supports git and compiling. The instructions are given for Ubuntu and I would stick with that. Ubuntu or compatible Debian based distro.
You get kernel, system and data images at the end. Those you flash in fastboot mode. See instructions. So far it doesn't provide recovery, but recovery may already be available for supported Open Devices. Once you flash recovery, it's kept in separate partition so you can boot it regardless of kernel.
As for rooting, you can do it with recovery or you can include su in your aosp system.
Sent from my D6603 using Tapatalk
Click to expand...
Click to collapse
I tried following the instructions to setup Ubuntu. Used VMWare since for some reason I can't install it on a different partition on my Hard Drive (it gets stuck at login and black screen and loops). I get errors. I give up. Maybe I can use my other PC for Ubuntu.

LeParkour012 said:
I tried following the instructions to setup Ubuntu. Used VMWare since for some reason I can't install it on a different partition on my Hard Drive (it gets stuck at login and black screen and loops). I get errors. I give up. Maybe I can use my other PC for Ubuntu.
Click to expand...
Click to collapse
Nobody can help you or provide you with any guidance if you write just "I get errors" ... Compiling AOSP is not for newbies, it expects you to have profound knowledge of Linux kernel based systems, working with source code, compiling and cross-compiling and not least Linux administration. There is no such thing like a spoon feeding / cook book for compiling own system.

ondrejvaroscak said:
Nobody can help you or provide you with any guidance if you write just "I get errors" ... Compiling AOSP is not for newbies, it expects you to have profound knowledge of Linux kernel based systems, working with source code, compiling and cross-compiling and not least Linux administration. There is no such thing like a spoon feeding / cook book for compiling own system.
Click to expand...
Click to collapse
I think you misunderstood me here. I'm not asking for help. That's why I wasn't specific on the errors. I wanted to try on my other PC later on. To be honest I have no idea why I replied to you but I guess that's my mistake. Sorry
Sent from my D6653 using Tapatalk

LeParkour012 said:
I think you misunderstood me here. I'm not asking for help. That's why I wasn't specific on the errors. I wanted to try on my other PC later on. To be honest I have no idea why I replied to you but I guess that's my mistake. Sorry
Sent from my D6653 using Tapatalk
Click to expand...
Click to collapse
OK, I was bit referring to your first post, it seemed you expect step-by-step instructions to get "perfectly working" AOSP. Such thing doesn't exist.
When setting up building environment, be sure to provide generous space, not less than 200 GB.

ondrejvaroscak said:
OK, I was bit referring to your first post, it seemed you expect step-by-step instructions to get "perfectly working" AOSP. Such thing doesn't exist.
When setting up building environment, be sure to provide generous space, not less than 200 GB.
Click to expand...
Click to collapse
Ah I thought Sony released a fully functioning AOSP firmware. My bad.
200gb? That's huge. I guess using my other PC for Ubuntu is a good choice.
Sent from my D6653 using Tapatalk

LeParkour012 said:
Ah I thought Sony released a fully functioning AOSP firmware. My bad.
200gb? That's huge. I guess using my other PC for Ubuntu is a good choice.
Sent from my D6653 using Tapatalk
Click to expand...
Click to collapse
Sony releases support files for building AOSP, and yes, if you build from Sony sources, you will get pure Sony AOSP. However, the main intention of AOSP is customization, it is not intended as general purpose daiy use system.

Resurrection Remix and Oreo

Ive been enjoying Resurrection Remix [Unofficial] rom and was wondering if they or any other rom for the Xperia Z5 P will support Oreo?

There is no kernel so unfortunately no

tset351 said:
There is no kernel so unfortunately no
Click to expand...
Click to collapse
???

zacharias.maladroit said:
???
Click to expand...
Click to collapse
Well there are no kernel sources nor binaries, blobs etc. so I guess there will no custom rom be available anytime soon but please correct me if I'm wrong. I would be glad to have Oreo on my Z5P.

tset351 said:
Well there are no kernel sources nor binaries, blobs etc. so I guess there will no custom rom be available anytime soon but please correct me if I'm wrong. I would be glad to have Oreo on my Z5P.
Click to expand...
Click to collapse
The developer seems to be busy so allow me to answer (though I'm not that experienced). I'm pretty sure that Sony always releases it's phone's kernel sources. Phone hardware doesn't change from an update so when the sources are released they can be used to create a kernel for any android version (basically developers need access to unique hardware). Blobs are like closed-source kernel modules. They're provided with the kernel source but the manufacturer doesn't want them to be copyrighted or tampered with. So I'm sure that Oreo will be available on your device, just give the developers some time. And please don't answer questions if you don't know what you're talking about (at least write that you're inexperienced).

Nik0laTesla said:
The developer seems to be busy so allow me to answer (though I'm not that experienced). I'm pretty sure that Sony always releases it's phone's kernel sources. Phone hardware doesn't change from an update so when the sources are released they can be used to create a kernel for any android version (basically developers need access to unique hardware). Blobs are like closed-source kernel modules. They're provided with the kernel source but the manufacturer doesn't want them to be copyrighted or tampered with. So I'm sure that Oreo will be available on your device, just give the developers some time. And please don't answer questions if you don't know what you're talking about (at least write that you're inexperienced).
Click to expand...
Click to collapse
I am a very inexperienced person.
For MSM8994 platform there is only 3.10 kernel sources available, at least on sony's developer page. On open devices resource list, there are binaries for Z5 premium for 5.1, 6.0, 6.0.1, 7.0 and 7.1 but unfortunately no 8.0 or 8.1. And well, developers can take their time - as long as they want because I don't use that cell phone anymore and I won't expect any custom Rom changes anytime soon especially for a 2015 Device which had very less development going on since its launch.
But once again, I am very inexperienced.

Nik0laTesla said:
The developer seems to be busy so allow me to answer (though I'm not that experienced). I'm pretty sure that Sony always releases it's phone's kernel sources. Phone hardware doesn't change from an update so when the sources are released they can be used to create a kernel for any android version (basically developers need access to unique hardware). Blobs are like closed-source kernel modules. They're provided with the kernel source but the manufacturer doesn't want them to be copyrighted or tampered with. So I'm sure that Oreo will be available on your device, just give the developers some time.
Click to expand...
Click to collapse
Ok, sorry I got a bit mixed up in the devices :laugh:. Either way Snapdragon provides up to date documentation on their SOC's (which is the most important hardware component on the device) so developers should still be able to provide Oreo. And you are right the Z5 premium is an old device and support usually drops as soon as the developer gets rid of that device. But it's weird how much attention different devices get. For example I have a Oneplus X (SD801, I know it's ancient) (didn't even get Nougat) and there are multiple Oreo 8.1 ROMs available.

Is it possible to make a Touchwiz GSI rom?

Hi, i'm asking to devs if it's possible to port say Galaxy S9's rom to Treble enabled devices or even other manufacterer roms such as LG's or HTC? I thought S9 was released with Oreo, therefore it should have Treble support and could its stock rom can be used a GSI rom or am i wrong? Thanks in advance.

+1. Want to see Samsung Experience on my device too

I Wont Samsung Experience on my Device Too :crying:

Most capable man atm
@fxsheep

Jamie_oppo said:
Most capable man atm
@fxsheep
Click to expand...
Click to collapse
Wait for SE 10.0 Android P,

I can be possible. Yes!
But there are many Knox dependecies on TW kernel. Even if you did, stuff like storage wont work at all.

I'm doing a lot of research about GSIs and Project Treble recently; and that was the FIRST thing that came in my mind.
"What if my Xiaomi could run Samsung Experience?"
I absolutely love Stock Android; and Android Pie looks pretty close to Samsung Experience 9.0 based on Oreo.
But still; it'd be nice to have Galaxy Note's exclusive features on a bloody Xiaomi!
I think its going to be a headache for developers; but a bug-free, smooth running Samsung Experience GSI would be a bombshell for sure!

HighonBolo said:
Hi, i'm asking to devs if it's possible to port say Galaxy S9's rom to Treble enabled devices or even other manufacterer roms such as LG's or HTC? I thought S9 was released with Oreo, therefore it should have Treble support and could its stock rom can be used a GSI rom or am i wrong? Thanks in advance.
Click to expand...
Click to collapse
I'm not a Dev but I can tell you, No it'll never happen!
Here's some reasons why....
Project treble is just a way to separate proprietory vendor files and driver's from the base of ROM and giving them a standard to interface with new roms. It means the device is compliant with treble roms, not that their stock ROM is.
Treble roms are built from source code and that code is written to allow 1 GSI to be installed on multiple devices and work their hardware. Samsung has no source code for their roms.
Allot of Samsung's features are all tied in with their framework and also hardware dependent.
So the only way to remotely get a manufacturer ROM on another device is by porting. Which is a difficult process.

aaron74 said:
I'm not a Dev but I can tell you, No it'll never happen!
Here's some reasons why....
Project treble is just a way to separate proprietory vendor files and driver's from the base of ROM and giving them a standard to interface with new roms. It means the device is compliant with treble roms, not that their stock ROM is.
Treble roms are built from source code and that code is written to allow 1 GSI to be installed on multiple devices and work their hardware. Samsung has no source code for their roms.
Allot of Samsung's features are all tied in with their framework and also hardware dependent.
So the only way to remotely get a manufacturer ROM on another device is by porting. Which is a difficult process.
Click to expand...
Click to collapse
Thanks, but I wanna ask what will happen if I done these:
1. ADB pull everything from /system on a rooted Samsung phone
2. Repack it into system.img
3. Use erfangsi tool to convert it into a GSI
Not challenging you, just completely out of my curiosity.

[REFERENCE] Umbrella Kernel

WARNING:
This is not a post targeted to end users. It is a development reference. If you expect any installable download or even added features out of this thread, please close your browser. Thank you.
What is Umbrella?
Umbrella is a project that aims to make the kernel sources that HMD released for Nokia 8 Sirocco (A1N) compatible with the Nokia 8 (NB1). The idea behind this is to replace the outdated 8.0 kernel sources that HMD released for NB1 with more up to date ones that are used in the 9.0 builds for Nokia 8 Sirocco.
Why do this, you might ask. Well, the answer is simple: The devices are so similar that HMD / FIH already have their kernel sources in a shared source tree. You can validate that yourself, by downloading the kernel config from a stock NB1 kernel (under /proc/config.gz), unpacking it, and searching for the commended entry "CONFIG_FIH_A1N". What umbrella does is take the sources that were released for A1N, readd all device specific files for NB1 (they were pruned) from it's original kernel soure, and integrate the stock kernel config (also called defconf) from NB1.
Doing this also lead to some other small quality of life improvements that are not directly relevant to an end user.
Umbrella contains the latest changes from linux-stable (v4.4.179 at the time of writing, compared to the stock v4.4.153), and Qualcomms Codeaurora upstream
The WiFi driver from Qualcomm is compiled directly into the kernel, instead of being loaded as a module. This allows you to flash umbrella based kernels to every build version while keeping everything else working correctly. The stock kernels use signature enforcement, which means that the wifi module that is loaded from the system partition has to be signed against the kernel, which is not the case for every custom kernel or even the kernels that were built for a different security patch.
Unlike the officially released kernel sources, umbrella does not have stupid typos in it's device trees that cause the phone to display white bars on all of your screen etc.
Umbrella disables the block that FIH put in place to prevent users from rebooting into EDL mode from within android (using adb reboot edl).
Umbrella also includes a patch that causes the device to not reset it's entire memory when the kernel crashes, therefore retaining the last kernel output log, which can be used for debugging
You can compile the kernel with compilers newer than GCC 4.9 (not clang though), without having it immideately crash at boot.
It includes a tool that automatically sets up a crosscompiling environment for the kernel.
What Umbrella is not
Umbrella is not a project to add significant new features, or the ability to tweak things beyond what the stock kernel already offers (which is technically not that bad). It aims to be a reference kernel, a base for (potentially) other kernels that are based on it and add those features. I know that that is kind of a broad goal, considering I am the only one who seems to do actual development for this phone, but who knows. Having a lower entry level might help in case someone is curious and wants to get into kernel hacking. And I would certainly be happy if I wasn't the only one developing for this device.
If you want Umbrella to contain features like:
Overclocking
More governors / schedulers / whatever
Color / Sound / whatever control
Wakelock blocking
etc. etc. etc.
then please Alt-F4 your browser right now. Ok, don't do that but at least please don't request it because it will make you get ignored, nothing else.
Why the name Umbrella?
While I developed the initial prototype I watched through 3 Resident Evil movies, and this is kinda a zombie project, so I think the name fits quite well.
Why are you posting this?
I am posting this because I am hoping that it will be useful for anyone that would like to get into kernel development and tweaking without the hassle that comes with setting up the kernel sources that are released by HMD.
But, one disclaimer: I am not a kernel developer. I am a curious CS student suffering from a bad mix of too much time and stupid ideas that solve stupid problems. I am trying my best to produce something useful and be of help, but please don't expect wonders from me, thanks.
Links?
Source: https://github.com/resident-nokia/umbrella
Download: None, this is a development reference.

Looks promising
Sent from my NB1 using XDA Labs

Nice. this will likely be useful in the future

Updated the umbrella source to the latest 4.4.180 kernel, and May 07 CAF tag (LA.UM.7.4.r1-05100-8x98.0). Also readded some NB1 specific code where it was missing (discovered by doing a diff against the 5140 kernel source that Nokia recently released).
Just in case anyone actually cares about it

THMSP said:
Updated the umbrella source to the latest 4.4.180 kernel, and May 07 CAF tag (LA.UM.7.4.r1-05100-8x98.0). Also readded some NB1 specific code where it was missing (discovered by doing a diff against the 5140 kernel source that Nokia recently released).
Just in case anyone actually cares about it
Click to expand...
Click to collapse
I do. Who knows, in a year's time I might have enough knowledge to build a custom Rom for this phone

Kernel sources which is used on pie has been released officially. Finally, we have an "original" kernel and we've got closed one more step to custom roms.
https://www.nokia.com/phones/en_int/opensource/

techno_man000 said:
Kernel sources which is used on pie has been released officially. Finally, we have an "original" kernel and we've got closed one more step to custom roms.
https://www.nokia.com/phones/en_int/opensource/
Click to expand...
Click to collapse
@THMSP it would be interesting to let us know how different is your kernel mod from the newly released official pie kernel for Nokia 8

MDV106 said:
@THMSP it would be interesting to let us know how different is your kernel mod from the newly released official pie kernel for Nokia 8
Click to expand...
Click to collapse
As I described here: https://forum.xda-developers.com/nokia-8/development/official-source-code-releases-nokia-8-t3930324, they are identical. The only difference are the device tree files (which still contain typos that break the display), and of course all modifications I made to the sirocco kernel source that Umbrella is based on (wifi driver, EDL mode reactivation, upstreaming, etc.)

THMSP said:
As I described here: https://forum.xda-developers.com/nokia-8/development/official-source-code-releases-nokia-8-t3930324, they are identical. The only difference are the device tree files (which still contain typos that break the display), and of course all modifications I made to the sirocco kernel source that Umbrella is based on (wifi driver, EDL mode reactivation, upstreaming, etc.)
Click to expand...
Click to collapse
So, are these new codes broken like 4.84?

techno_man000 said:
So, are these new codes broken like 4.84?
Click to expand...
Click to collapse
I wouldn't call Nokia sources broken, but I would call them incomplete, outdated and impractical to work with. And that hasn't changed.

Iam currently building device tree for nokia 8..
Unable to figure out how to edit init folder specifically for nokia8

[email protected] said:
Iam currently building device tree for nokia 8..
Unable to figure out how to edit init folder specifically for nokia8
Click to expand...
Click to collapse
Please do so! We can't let this phone die so early!

which defconfig file should choose?

lk

[email protected] said:
which defconfig file should choose?
Click to expand...
Click to collapse
nb1_defconfig is for Nokia 8

Can somebody help me? I have built Lineage OS 16.0 for the Nokia 8 with the Umbrella Kernel. However I am facing issues with getting it into work. Firstly TWRP fails to flash it with error 7. I am including the recovery.log file in case anyone wants more detail. I then proceeded to extract the payload.bin file, and flashed boot.img and system.img seperately. However that didnt work either as my phone got stuck at the Bootloader unlocked warning screen. If anyone is interesteed I can upload the .zip outputed by the build
Device Tree: https://github.com/GPUCode/android_device_nokia_nb1
Recovery.log: https://hastebin.com/akohutiwed.sql
Thanks in advanced

emufan4568 said:
Can somebody help me? I have built Lineage OS 16.0 for the Nokia 8 with the Umbrella Kernel. However I am facing issues with getting it into work. Firstly TWRP fails to flash it with error 7. I am including the recovery.log file in case anyone wants more detail. I then proceeded to extract the payload.bin file, and flashed boot.img and system.img seperately. However that didnt work either as my phone got stuck at the Bootloader unlocked warning screen. If anyone is interesteed I can upload the .zip outputed by the build
Device Tree: https://github.com/GPUCode/android_device_nokia_nb1
Recovery.log: https://hastebin.com/akohutiwed.sql
Thanks in advanced
Click to expand...
Click to collapse
hey, did you wipe userdata before flashing this? I think you need to do that, like when switching to using GSIs.
also, have you checked this https://github.com/resident-nokia/twrp? Specifically the fstab file for NB1.

oaid said:
hey, did you wipe userdata before flashing this? I think you need to do that, like when switching to using GSIs.
Click to expand...
Click to collapse
Thanks for the suggestion. I have flashed GSIs before but never had any problems. Also I cannot find any userdata partition in TWRP. I asked in the Lineage OS discord and I was told that probably that TWRP image is broken. I am confused

emufan4568 said:
Thanks for the suggestion. I have flashed GSIs before but never had any problems. Also I cannot find any userdata partition in TWRP. I asked in the Lineage OS discord and I was told that probably that TWRP image is broken. I am confused
Click to expand...
Click to collapse
that's the data partition, if I'm not mistaken ?*
which twrp image are you using? Maybe try Dorian's latest?

oaid said:
that's the data partition, if I'm not mistaken ?*
which twrp image are you using? Maybe try Dorian's latest?
Click to expand...
Click to collapse
Yes I am using the latest TWRP. Before flashing I erased the data partition but still the error persisted