Database Info

[DEV] Porting over 2.6.29

Okay everyone. I am working on an optimized 2.6.27 until we can get .29 ported over. But I figure, since I am fairly new to the kernel world, how can we get started porting this bad boy over? I have been looking through the source code but am somewhat lost as to where to get started. I figure if we are able get this going we can make a github account and have the progress set up for everyone. All you devs wanna join in?

chuckhriczko said:
Okay everyone. I am working on an optimized 2.6.27 until we can get .29 ported over. But I figure, since I am fairly new to the kernel world, how can we get started porting this bad boy over? I have been looking through the source code but am somewhat lost as to where to get started. I figure if we are able get this going we can make a github account and have the progress set up for everyone. All you devs wanna join in?
Click to expand...
Click to collapse
Seems like I just read someones already got a github setup. Can we branch instead of running 2 accounts if this is the case?
I am also very new to the whole kernel. I think I have actually only compilied 3 succesful linux kernels in my short life. Attempted others, but I usually get lazy or run out of time.

Kcarpenter said:
Seems like I just read someones already got a github setup. Can we branch instead of running 2 accounts if this is the case?
I am also very new to the whole kernel. I think I have actually only compilied 3 succesful linux kernels in my short life. Attempted others, but I usually get lazy or run out of time.
Click to expand...
Click to collapse
If someone has made a github project please let me know. I havent made a 2.6.29 github project yet. I am currently doing one for 2.6.27.

I created a 2.6.27 repo this morning when the source was released. And I've checked out 2.6.29, just haven't set it up in github.

Really?
What's the difference between the android kernel and the regular linux kernel? It seems their version numbers are closely related. So why not go up to the newest stable (2.6.32.5)?

lazydev said:
What's the difference between the android kernel and the regular linux kernel? It seems their version numbers are closely related. So why not go up to the newest stable (2.6.32.5)?
Click to expand...
Click to collapse
It's not that simple. For starters we have to copy over the drivers for our phone and make sure they compile correctly. On top of that HTC modified quite a bit of the kernel. Porting it over will happen but it may take some time. Like I said before I am new to the linux kernel deal but I do know it is more difficult than it seems.

I'd say a completely functional port will take roughly 2 weeks time for a hobbyist. I'm not sure though as I'm still new to messing with linux kernels. I'm looking into a port of my own. Debating 2.6.29 or porting the android specific bits to a newer linux kernel. Chances are porting the hero specific stuff to the android 2.6.29 kernel source will be much simpler. It sucks I'm on my laptop at work and it isn't running linux so no compiling, diff patching or coding for me tonight. I wish I was a bit more profficient with C programming too. I guess now I have a good reason to do just that.

lazydev said:
What's the difference between the android kernel and the regular linux kernel? It seems their version numbers are closely related. So why not go up to the newest stable (2.6.32.5)?
Click to expand...
Click to collapse
edit: didnt release chuckriczko answered your question..

obelisk79 said:
It sucks I'm on my laptop at work and it isn't running linux so no compiling, diff patching or coding for me tonight.
Click to expand...
Click to collapse
Maybe it's time to start carrying around a LiveUSB distro of Linux on a flash drive

gu1dry said:
Maybe it's time to start carrying around a LiveUSB distro of Linux on a flash drive
Click to expand...
Click to collapse
no kidding... I wasn't expecting to wake up to a new release. Of course I could just run linux on my laptop and call it a day

Yeah, the reason it's better to start with .29 than jump to .32, because a lot of the work has already been done for us in .29. In fact, if you really investigate the kernel source they released, vs the kernel on our phones, you'll notice that HTC has already backported some of the .29 changes in the android-msm-2.6.29 branch into the source they released, which was *not* initially the case in the kernel that they shipped.
What we need to do to get .29 actually working, is the opposite: forward-port the HTC changes for hero/c into the .29 source.

FYI: got an initial codebase that compiles, but does not boot yet:
http://github.com/jhansche/kernel_msm/commit/19a2d673867a8e11b98cce399ed89c94811ebf77
Started from android-msm-2.6.29 branch, with a few modifications that HTC made in our code, ported over (not all of them, mind you). If anyone has any suggestions for debugging why the kernel doesn't boot, I'm glad to hear them If I had a serial debug cable, that would be useful, cause then it would work as a serial console. But for now all I have to go on is the fact that it dies *before* ram_console can be initialized (even with early-init enabled).
I've also disabled several pieces of hardware in the interest of just getting a clean compile -- namely headset, 3.5mm audiojack, EID mddi client (lcd panel) has not been copied over yet, and some other stuff.

maejrep said:
FYI: got an initial codebase that compiles, but does not boot yet:
http://github.com/jhansche/kernel_msm/commit/19a2d673867a8e11b98cce399ed89c94811ebf77
Started from android-msm-2.6.29 branch, with a few modifications that HTC made in our code, ported over (not all of them, mind you). If anyone has any suggestions for debugging why the kernel doesn't boot, I'm glad to hear them If I had a serial debug cable, that would be useful, cause then it would work as a serial console. But for now all I have to go on is the fact that it dies *before* ram_console can be initialized (even with early-init enabled).
I've also disabled several pieces of hardware in the interest of just getting a clean compile -- namely headset, 3.5mm audiojack, EID mddi client (lcd panel) has not been copied over yet, and some other stuff.
Click to expand...
Click to collapse
Great work! As I said before I am new to this linux kernel stuff and don't think I can help but I am cloning the repo so I can take a look anyway.

Any progress with getting it to boot?

Any update on this project?

I have also been curious about this for a couple of days, just didn't want to sound pushy to the devs... hope theyre seeing progress.

theoottesen said:
I have also been curious about this for a couple of days, just didn't want to sound pushy to the devs... hope theyre seeing progress.
Click to expand...
Click to collapse
I checked the githup out. still doesn't boot

Yeah, I've been hitting a brick wall trying to get some kind of indication that something is happening... On .27 I lucked out by somehow getting it to go past the ram console, then reboot, so I could see the panic messages on /proc/last_kmsg. But in .29, I can't even write directly to the ram console memory space in a pure_init section. The problem is that there's no way to know how far it's getting in the boot process. So we're really just booting blindly.
On top of that, the android-msm-2.6.29-nexusone branch has non-QSD8k bugs (that is, if you select that it's an MSM device, not a QSD device, it won't compile without fixing stuff in their acpu code for arm11, MDP22 code paths, etc. it's like the nexusone branch was only ever tested with scorpion, not arm11 (even though it has the board files for sapphire, so you would expect it to compile for sapphire)

maejrep said:
Yeah, I've been hitting a brick wall trying to get some kind of indication that something is happening... On .27 I lucked out by somehow getting it to go past the ram console, then reboot, so I could see the panic messages on /proc/last_kmsg. But in .29, I can't even write directly to the ram console memory space in a pure_init section. The problem is that there's no way to know how far it's getting in the boot process. So we're really just booting blindly.
On top of that, the android-msm-2.6.29-nexusone branch has non-QSD8k bugs (that is, if you select that it's an MSM device, not a QSD device, it won't compile without fixing stuff in their acpu code for arm11, MDP22 code paths, etc. it's like the nexusone branch was only ever tested with scorpion, not arm11 (even though it has the board files for sapphire, so you would expect it to compile for sapphire)
Click to expand...
Click to collapse
So if I understand correctly, the devs that worked on the kernel for the Nexus One got lazy and never tried to see if it compiled on the Sapphire?

If they were developing the kernel for the nexus id hardly call them lazy for not taking the time to check it on other devices.

What can we do to help get Aries!?!?!?

Not really a technical question but I was wondering what we "noobs" and devs that aren't working on the 3.0.8 kernel can do to speed up or help in the development (we're all in this together right!?) Donations may help but are there any builds we can test with alogcats or just repetitive labor that manpower can aid in? If so feel free to put it here. One tip, guides to non intuitive stuff would help because like I said there are a quite a few noobs lurking (me included). Hopefully this is in the right thread I was contemplating putting it on the general but I wasn't sure.

I'm sure if they needed our help they would ask as they know many of us want to help. Best thing to do is just be patient and not bug them.
I guess you can help by flashing the build posted in the cm9 thread and reporting any bugs that haven't already been reported.
Sent from my SGH-T959V using xda app-developers app

This is a terrible way to get on the good book. Just fork bhundvens github repo. Make changes that work or look good, then push a pull request, then you'll be good.
Also, its called Aries not aires
Sent from my SGH-T959V using xda premium

Sit tight, let Bryan do his thing, and enjoy it when it gets here.
Sent from my SGH-T959V using xda premium

gregcapps said:
Sit tight, let Bryan do his thing, and enjoy it when it gets here.
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
A passive approach works too

Educate me what is Aries?

Bitcloud30 said:
Educate me what is Aries?
Click to expand...
Click to collapse
It is the proper Kernel for ICS which is more stable and offers better battery life. More specifically it is the machine type of the phone. Currently all builds are herring.

it's not a "Proper Kernel" per se.
Just the team hacksung people created a generic kernel to work with for all the Galaxy S 1 devices. Well, there are alot more devs over there and that's what's officially supported by CM. So now we are trying to merge into the official Galaxy S CM kernel.

Correct me if I'm wrong but Aries is the processor that our phone runs on it is hardware not software meaning it is a physical component that can't be changed by flashing any files
Sent from my SGH-T959V using xda app-developers app

anoymonos said:
Correct me if I'm wrong but Aries is the processor that our phone runs on it is hardware not software meaning it is a physical component that can't be changed by flashing any files
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
nope, the processor is hummingbird. too many codenames. :silly:

also known as Exynos which is what anoymonos was getting confused with.

One of the big reasons to get on a kernel based on the Aries source is that it makes it a lot easier to move forward with AOSP releases. Right now, "our" kernel is a bit of AOSP, a bit of Samsung stock, a bit of TeamAcid work, a bit of TeamHacksung, a bit of..., so every time something comes up, it is a "custom job" to add it. I won't say that getting closer to mainline code will make JB a slam dunk, but without it, it would likely be lipstick on the pig.

Aries and Herring are Board Names (think motherboard).
Exynos and s5pc110 are Processor Names (both are SoC with the RAM in a PoP configuration).
Herring is the board name used for the nexus one and nexus s in Google's AOSP Samsung source.
The main board definition file for herring is: mach-herring.c
When Samsung worked with t-mobile, at&t, verizon, etc... to make Galaxy S phones, they basically reused the AOSP Samsung kernel for multiple devices. For instance, if you look at our UVKJ6 kernel drop, you will notice ifdefs in there for VIBRANTPLUS (Galaxy S 4G), KEPLER (Captivate), DEMPSEY (Infuse 4G), and a few others.
Aries is the main board definition file for the stock kernel is: mach-aries.c
Even though the board name is still herring. Ger.
They basically copied mach-herring.c to mach-aries.c and made their changes in mach-aries.c.
The Aries kernel, like jeffsf mentioned, is a kernel made by teamhacksung to be a combined kernel for galaxy s devices, and they use mach-aries.c and the aries board name.
If you get the stock kernel drop for any of these other devices in the same kernel drop from their respective drop, there will be subtle differences between each kernel drop. (crazy huh?)
And every file that samsung touches gains tens of lines of ifdefs, sometimes conflicting, as well as code that was '#if 0'ed out because they didn't code it right and left some other variable definitions without also '#if 0'ing them as well leaving nasty build warnings.
If you don't know anything about embedded devices, linux kernel development, or kernel debugging, just lay back and chill. We're getting close, just some nasty rough edges to clean up.
If you do have one or more of those skills, join us in #teamacid.
As it stands right now, most of the problems are GPIO issues. I am having a rough go at figuring out our GPIO configuration for this phone. Everytime I think I figure out something I find that I am wrong.
Also, to make things harder and more confusing, unlike the stock kernels, the aries kernel puts the GPIO pin configuration right in mach-aries.c, where as stock kernels put them in include/mach/gpio-settings-<devicename>.h... :sigh:
Hopefully m4xm4n and jeffsf can give me a hand with this stuff.
It would be nice if some teamhacksung members could give a hand and some guidance.

bhundven said:
Aries and Herring are Board Names (think motherboard).
Exynos and s5pc110 are Processor Names (both are SoC with the RAM in a PoP configuration).
Herring is the board name used for the nexus one and nexus s in Google's AOSP Samsung source.
The main board definition file for herring is: mach-herring.c
When Samsung worked with t-mobile, at&t, verizon, etc... to make Galaxy S phones, they basically reused the AOSP Samsung kernel for multiple devices. For instance, if you look at our UVKJ6 kernel drop, you will notice ifdefs in there for VIBRANTPLUS (Galaxy S 4G), KEPLER (Captivate), DEMPSEY (Infuse 4G), and a few others.
Aries is the main board definition file for the stock kernel is: mach-aries.c
Even though the board name is still herring. Ger.
They basically copied mach-herring.c to mach-aries.c and made their changes in mach-aries.c.
The Aries kernel, like jeffsf mentioned, is a kernel made by teamhacksung to be a combined kernel for galaxy s devices, and they use mach-aries.c and the aries board name.
If you get the stock kernel drop for any of these other devices in the same kernel drop from their respective drop, there will be subtle differences between each kernel drop. (crazy huh?)
And every file that samsung touches gains tens of lines of ifdefs, sometimes conflicting, as well as code that was '#if 0'ed out because they didn't code it right and left some other variable definitions without also '#if 0'ing them as well leaving nasty build warnings.
If you don't know anything about embedded devices, linux kernel development, or kernel debugging, just lay back and chill. We're getting close, just some nasty rough edges to clean up.
If you do have one or more of those skills, join us in #teamacid.
As it stands right now, most of the problems are GPIO issues. I am having a rough go at figuring out our GPIO configuration for this phone. Everytime I think I figure out something I find that I am wrong.
Also, to make things harder and more confusing, unlike the stock kernels, the aries kernel puts the GPIO pin configuration right in mach-aries.c, where as stock kernels put them in include/mach/gpio-settings-<devicename>.h... :sigh:
Hopefully m4xm4n and jeffsf can give me a hand with this stuff.
It would be nice if some teamhacksung members could give a hand and some guidance.
Click to expand...
Click to collapse
Hopefully you get the help you need. Hey here's a dumb question, could you not call the manufacturers of the phone and ask them what the gpio config is?

IIRC the gpio functions are part of a proprietary code source. So no Samsung will not tell you.

eollie said:
IIRC the gpio functions are part of a proprietary code source. So no Samsung will not tell you.
Click to expand...
Click to collapse
The GPIO pins are signal pins on the SoC that allow you to connect external devices to the main cpu.
It is actually specific to the board because each phone have different connected devices (such as lcd panel, wifi, touch screen, etc...).
The GPIO pins and interrupt signals are all documented in the S5PC110 User Manual, but the pin layout in that manual is specific to the reference board it is describing. Each phone/device has its own GPIO layout and it is specific to the schematic.
Sure wish we had a vibrantplus schematic.

airfluip1 said:
it's not a "Proper Kernel" per se.
Just the team hacksung people created a generic kernel to work with for all the Galaxy S 1 devices. Well, there are alot more devs over there and that's what's officially supported by CM. So now we are trying to merge into the official Galaxy S CM kernel.
Click to expand...
Click to collapse
OK...maybe not a "proper" kernel technically , but certainly a whole lot closer to what to we need to have a better experience with the newer versions of android os.
Sent from my SGH-T959V using xda premium

you aren't wrong. I just explained it a bit.
@othern00bs
Here is a simple way to put it for the others who are confused
CyanogenMod Team made kernel = aries = more polished = newer kernel version = we can get regular kernel/version updates because the team acid members won't have to manually port them = potentially Jellybean in the long run (as soon as ICS is polished)
TeamAcidMTD kernel = herring = older version ported to work with ICS = needed to port again for JB = buggier = degraded bat life = manually having to port each change and CM version

bhundven said:
Sure wish we had a vibrantplus schematic.
Click to expand...
Click to collapse
What, the 2426 pages of S5PC110 manual aren't enough bedtime reading for you?
(No, the page count is not a joke.)

Well, I agree that getting Some Hacksung member on IRC should help you.

Kernel Source Acquired

After a month of back and forth with Barnes and Noble support and numerous references to the GPL, I think I've managed to acquire a copy of the kernel source for this tablet. It's published as a ZIP on Barnes and Noble's website. I haven't spend a whole lot of time with it, as I currently do not have the resources to build it, but from a cursory glance it seems to be reasonable, if in a weird format. I've also mirrored the source on GitLab (unfortunately, GitHub doesn't work with files over 100 MB nicely) for you guys to play with in case the Barnes and Noble link goes down or you'd like a faster download. If you see anything crucial missing, let me know and I'll try to get it fixed by pestering them to give it to me!

saagarjha said:
After a month of back and forth with Barnes and Noble support and numerous references to the GPL, I think I've managed to acquire a copy of the kernel source for this tablet. It's published as a ZIP on Barnes and Noble's website. I haven't spend a whole lot of time with it, as I currently do not have the resources to build it, but from a cursory glance it seems to be reasonable, if in a weird format. I've also mirrored the source on GitLab (unfortunately, GitHub doesn't work with files over 100 MB nicely) for you guys to play with in case the Barnes and Noble link goes down or you'd like a faster download. If you see anything crucial missing, let me know and I'll try to get it fixed by pestering them to give it to me!
Click to expand...
Click to collapse
What resources do you need. I picked up the new bn 7 tablet the other day. It's the 650 model. I have Ubuntu and superr kitchen
Edit: screen smashed...will donate the board to someone for Dev...

I have no idea what to do with it, actually. How can I do something useful with this?

saagarjha said:
I have no idea what to do with it, actually. How can I do something useful with this?
Click to expand...
Click to collapse
If we had a build of twrp, we could probably start building custom roms with this kernel I bet. I'm gonna ask B&N about getting the source for BNTV460 since that is the one I have.

A big issue that i'm having with this source is I can't figure out which defconfig to use for this device

I have recently built LineageOS 15.1 for the Nook Tablet 7" (Only st18c7bnn/bntv460) and have looked over the kernel source and found that this source code is essentially useless because it is missing the lcm code, which controls screen and touchscreen. I do not see them releasing full kernel source for this device or for the oreo model in the future as every time I've called I have had no luck getting anything from them. If anyone else is willing to try to ask for kernel source from them, please do since it is not only their legal obligation to give it with all of their modifications, but also a huge help for development. The st16c7bnn & st18c7bnn both use the same LCM, although for some reason, st16c7bnn(the marshmallow device) is 64bit while st18c7bnn(oreo) is 32bit only.

turtleletortue said:
I have recently built LineageOS 15.1 for the Nook Tablet 7" (Only st18c7bnn/bntv460) and have looked over the kernel source and found that this source code is essentially useless because it is missing the lcm code
Click to expand...
Click to collapse
So, if I'm understanding correctly you have a non-functional LineageOS? Or is it that the st18c7bnn is the only one that needs the LCM code, and it already works on st18c7bnn (if so, would you mind sharing the build)?
I'd be happy to contact them again (maybe they'll see my old ticket and redirect it to the person who handled that issue), but I would have to know exactly what to ask for because otherwise they are really slow and ask a bunch of questions.

saagarjha said:
So, if I'm understanding correctly you have a non-functional LineageOS? Or is it that the st18c7bnn is the only one that needs the LCM code, and it already works on st18c7bnn (if so, would you mind sharing the build)?
I'd be happy to contact them again (maybe they'll see my old ticket and redirect it to the person who handled that issue), but I would have to know exactly what to ask for because otherwise they are really slow and ask a bunch of questions.
Click to expand...
Click to collapse
Sorry for the long delay in response. Basically, I have an almost perfectly functioning build of LineageOS for st18c7bnn (Nook Tablet 7" 2018 Android Go Edition only), but I wanted the kernel source so I could rebuild the kernel and attempt to merge in security fixes for it. If you have the 2018 model of the device, I'll gladly send the TWRP zip of the rom to you. Seems to work fine, and imo is better than using a gsi. I still have to do more testing, but I'm currently busy with another device. I just want to have the full kernel source (which would include necessary dtb and lcm drivers) for the st18c7bnn and st18c10bnn (Nook Tablet 10.1) like the license the kernel is under should force B&N to do. Since the devices have been discontinued, I figure it's now or never for that, since the longer we wait, the more likely that Emdoor deleted the kernel source off of their machines. But any help is appreciated. Thanks

X86 Atom Android tablet BLISS ROM. Kernel source & HALS, is tha enough to get going?

X86 Atom Android tablet BLISS ROM. Kernel source & HALS, is tha enough to get going?
I have a TX201LA tablet runs Android 4.2. Its a dual device 2 systems in 1. The tablet half is what i am focusing on. NOT the dock as I have windows 10 running fine on that half. The tablet is nearly useless as it is on android 4.2. I've been exploring a few options for getting an android update. My tablet runs an atom x86 cpu with 2GB of ram and is quad core cloevertrail CPU x2560. Plenty of power to run a newer android or even chromeOS, cloudready, or remixOS. I've explored those options but Bliss is the most straight forward as there are already x86 builds of Bliss. I think support should be relatively easy to add for my device.
There are a few caveats however I know ways to overcome them if I can get a rom to load.
1. I dont have a unlocked bootloader but I maybe able to unlock using zenfone 5 unlock method. Still no custom rom has ever been made for my tablet, only for similar devices like zenfone 5, galaxy tab 3 10.1, & dell venue 7.
2. Once I get it unlocked, I can load CWM or use flashfire. My tablet boots with Droidboot, which I can replace with CWN via again a zenfone 5 exploit that I have confirmed works with my tablet.
3. Would bliss load things like my LCD driver, touch screen etc? That is possibly the biggest issue. I have the kernel code here, UPDATED: http://support.asus.com.cn/Download....1LAF&p=3&s=587 OR here original: http://support.asus.com.cn/Download....01LA&p=3&s=587
3A. If the kernel code has all the HALS isnt it possible to build a Bliss rom that would be loaded via CWM/Flashfire and then boot-able?
3B. Could the Bliss team build a rom with the kernel code listed above, that I could then test? Or would the bliss team need to the device (I would think not, i hope). If a rom could be created I would GLADLY donate to BLISS.
Love to find out if this is possible. THANKS

madhits45 said:
I have a TX201LA tablet runs Android 4.2. Its a dual device 2 systems in 1. The tablet half is what i am focusing on. NOT the dock as I have windows 10 running fine on that half. The tablet is nearly useless as it is on android 4.2. I've been exploring a few options for getting an android update. My tablet runs an atom x86 cpu with 2GB of ram and is quad core cloevertrail CPU x2560. Plenty of power to run a newer android or even chromeOS, cloudready, or remixOS. I've explored those options but Bliss is the most straight forward as there are already x86 builds of Bliss. I think support should be relatively easy to add for my device.
There are a few caveats however I know ways to overcome them if I can get a rom to load.
1. I dont have a unlocked bootloader but I maybe able to unlock using zenfone 5 unlock method. Still no custom rom has ever been made for my tablet, only for similar devices like zenfone 5, galaxy tab 3 10.1, & dell venue 7.
2. Once I get it unlocked, I can load CWM or use flashfire. My tablet boots with Droidboot, which I can replace with CWN via again a zenfone 5 exploit that I have confirmed works with my tablet.
3. Would bliss load things like my LCD driver, touch screen etc? That is possibly the biggest issue. I have the kernel code here, UPDATED: http://support.asus.com.cn/Download....1LAF&p=3&s=587 OR here original: http://support.asus.com.cn/Download....01LA&p=3&s=587
3A. If the kernel code has all the HALS isnt it possible to build a Bliss rom that would be loaded via CWM/Flashfire and then boot-able?
3B. Could the Bliss team build a rom with the kernel code listed above, that I could then test? Or would the bliss team need to the device (I would think not, i hope). If a rom could be created I would GLADLY donate to BLISS.
Love to find out if this is possible. THANKS
Click to expand...
Click to collapse
For one, you should ask Bliss OS (x86) related questions in the Bliss OS thread: https://forum.xda-developers.com/bliss-roms/bliss-roms-development/x86-bliss-x86-pc-s-t3534657
Second, I tend to only use source dumps that maintain proper commit attribution. This is our way of giving credit where it is due (the original developers) Most of the source dumps I come across are a bunch of source code, with one commit at best titled, "initial commit" or "dump", and this to me says that there is something not trustworthy about it. I would like to see all the individual commits and changes made throughout the commit history, as this allows us to easily target changes that were made for that specific device.
If others want to go through the trouble of picking out those differences and creating a pull request with the proper attribution attached, we have no issues merging into our releases after testing.

electrikjesus said:
For one, you should ask Bliss OS (x86) related questions in the Bliss OS thread: https://forum.xda-developers.com/bliss-roms/bliss-roms-development/x86-bliss-x86-pc-s-t3534657
Second, I tend to only use source dumps that maintain proper commit attribution. This is our way of giving credit where it is due (the original developers) Most of the source dumps I come across are a bunch of source code, with one commit at best titled, "initial commit" or "dump", and this to me says that there is something not trustworthy about it. I would like to see all the individual commits and changes made throughout the commit history, as this allows us to easily target changes that were made for that specific device.
If others want to go through the trouble of picking out those differences and creating a pull request with the proper attribution attached, we have no issues merging into our releases after testing.
Click to expand...
Click to collapse
Did you look at my source to see if this is a problem? I'm not exactly sure how it needs to look but is this something you have found to be the case with other asus sources in the past? I'd be surprised if it was. I'd love to get a bliss rom for my tablet but I figured this would not be so easy even with x86 support being its base.

madhits45 said:
Did you look at my source to see if this is a problem? I'm not exactly sure how it needs to look but is this something you have found to be the case with other asus sources in the past? I'd be surprised if it was. I'd love to get a bliss rom for my tablet but I figured this would not be so easy even with x86 support being its base.
Click to expand...
Click to collapse
By the time I read your post, the links didn't work. And of the Asus source dumps I've seen in the past, they haven't included any git history

electrikjesus said:
By the time I read your post, the links didn't work. And of the Asus source dumps I've seen in the past, they haven't included any git history
Click to expand...
Click to collapse
Hey Electrik jesus, Here is the new link: https://www.asus.com/2-in-1-PCs/ASUS_Transformer_Book_Trio_TX201LA/HelpDesk_Download/
I'm from Michigan to.. So hopefully you can help another Michigander lol with a bliss build. Asus recently changed up there whole support site and the source code used to only be available on the international site now it seems its also on there US site. The Tx201LA was sold more overseas then in the US. It so similar to about 50 other devices (same Soc) asus made but mostly a lot of them are phones.

madhits45 said:
Hey Electrik jesus, Here is the new link: https://www.asus.com/2-in-1-PCs/ASUS_Transformer_Book_Trio_TX201LA/HelpDesk_Download/
I'm from Michigan to.. So hopefully you can help another Michigander lol with a bliss build. Asus recently changed up there whole support site and the source code used to only be available on the international site now it seems its also on there US site. The Tx201LA was sold more overseas then in the US. It so similar to about 50 other devices (same Soc) asus made but mostly a lot of them are phones.
Click to expand...
Click to collapse
I checked it out, and it is just as I was expecting. no .git folder or anything to show what commits were made on top of the standard kernel source. I guess the only thing we can do about it though is set an example of how to do it...
Example of how a kernel commit history could look: https://github.com/BlissRoms-x86/platform_kernel_common/commits/k4.15.10-ipts

electrikjesus said:
I checked it out, and it is just as I was expecting. no .git folder or anything to show what commits were made on top of the standard kernel source. I guess the only thing we can do about it though is set an example of how to do it...
Example of how a kernel commit history could look: https://github.com/BlissRoms-x86/platform_kernel_common/commits/k4.15.10-ipts
Click to expand...
Click to collapse
So if I understand you correctly the source code needs to be gone through to be pick out the comments etc and then it can be pulled into the bliss x86 source for merging? I think this is above my skill set, what can I do if I dont have the skills to do this?

madhits45 said:
So if I understand you correctly the source code needs to be gone through to be pick out the comments etc and then it can be pulled into the bliss x86 source for merging? I think this is above my skill set, what can I do if I dont have the skills to do this?
Click to expand...
Click to collapse
It's more of a prevention on our end from not giving attribution to the original author. Let's say that someone who worked on a linux project, got the GPU to finally work right with the chipsets in your ASUS. I would like to see that one guy's additions, but even moreso, I would like to see ASUS show that they used his work. Because for all we know, there are hundreds of commits in there that were added, and some of that could be work that someone else deserves to be reimbursed for. The fact that they removed the .git folder shows that they have something to hide. Calling it "trade secrets" shouldn't be allowed when it comes to kernel code.

electrikjesus said:
It's more of a prevention on our end from not giving attribution to the original author. Let's say that someone who worked on a linux project, got the GPU to finally work right with the chipsets in your ASUS. I would like to see that one guy's additions, but even moreso, I would like to see ASUS show that they used his work. Because for all we know, there are hundreds of commits in there that were added, and some of that could be work that someone else deserves to be reimbursed for. The fact that they removed the .git folder shows that they have something to hide. Calling it "trade secrets" shouldn't be allowed when it comes to kernel code.
Click to expand...
Click to collapse
So its about credit and royalties? I understand being upset at asus because they did not or have not credited someone but what can i do about that? Am I stuck at not being able to have my device supported because asus is a bad actor? Is there any way I can get support?

madhits45 said:
So its about credit and royalties? I understand being upset at asus because they did not or have not credited someone but what can i do about that? Am I stuck at not being able to have my device supported because asus is a bad actor? Is there any way I can get support?
Click to expand...
Click to collapse
There is, you could take the route Jakeday has for the Surface line. Since we don't know the author, he created patches to add the support needed to the kernel. It's far from the easy road, but this is what helps developers far more than any source dump
https://github.com/jakeday/linux-surface

electrikjesus said:
There is, you could take the route Jakeday has for the Surface line. Since we don't know the author, he created patches to add the support needed to the kernel. It's far from the easy road, but this is what helps developers far more than any source dump
https://github.com/jakeday/linux-surface
Click to expand...
Click to collapse
What I am confused about is this.
1. Is it a protocol thing? IE asus did not give credit and thus bliss refuses to add support unless they do.
OR
2. Is it an actual road block? IE we cant use the source code as is because it needs more information or reformatting?
Or is it both with more weight on #2?
If its #1 then can we make an exception? and if it is #2 why isnt there some sort of code AI that can redo the code to make it conform to the needed edits, seems like that should be possible. I would hope that if it is #1 only that you would admit that is all it is and help more people instead of forcing people to work around the bureaucracy brought onto them by bad actors like asus.

madhits45 said:
What I am confused about is this.
1. Is it a protocol thing? IE asus did not give credit and thus bliss refuses to add support unless they do.
OR
2. Is it an actual road block? IE we cant use the source code as is because it needs more information or reformatting?
Or is it both with more weight on #2?
If its #1 then can we make an exception? and if it is #2 why isnt there some sort of code AI that can redo the code to make it conform to the needed edits, seems like that should be possible. I would hope that if it is #1 only that you would admit that is all it is and help more people instead of forcing people to work around the bureaucracy brought onto them by bad actors like asus.
Click to expand...
Click to collapse
It's the third option, I'm too busy to do the work for something that is more important to you than it is to me.

electrikjesus said:
It's the third option, I'm too busy to do the work for something that is more important to you than it is to me.
Click to expand...
Click to collapse
LOL.. Pretty PLEASE, with big traverse city cherrys on top.
I have also emailed asus to see if they will look at the source code again to properly format it, not likely but worth a shot.

Does this help: https://proandroiddev.com/ooga-chaka-git-hooks-to-enforce-code-quality-11ce8d0d23cb
Is the process of going through the code very time consuming? So even if using git hooks it will take time? Im still trying to understand why there is no AI that can go through it.

electrikjesus said:
It's the third option, I'm too busy to do the work for something that is more important to you than it is to me.
Click to expand...
Click to collapse
It is important for several people. I hope at some point you have enough time to be able to help us. please help.

I am revisiting this conversation after a few months, and for starters, I would like to say I'm sorry for being rude. Secondly, I would like to use this conversation to start change where we need it. Innovation is the key point here. and if any of us are to build off of one another, we must work together to make it all possible. The lack of commit attribution by OEMs is a blatant disregard for GPL and Open Source licensing. As a ROM team, I would love to work with any OEM to help them through the process of adding a proper commit history. As Bliss, we are open to taking on any new device work, and we have in the past with Udoo-x86 & PINE64, but one of our requirements is that we can release full source, commit history, etc. Everything anyone could need to build off our work.
Too many OEM's are using patents as a way to stab eachother in the back, or use it as a "competitive" road block to stop the sale other devices that may have a similar method or feature. We don't agree with this practice and believe it is driven by greed and the wants of a few, not the needs of the majority. We as Bliss will continue to do what we can to act as an example of what should be done to best facilitate the rapid development of mobile technology and software for all parties involved.

New official source code releases for Nokia 8

Hi everyone,
I bugged HMD about not releasing more recent source code for the Nokia 8 and a few days ago they updated their site with links to code for the Android 9 builds. Note they still haven't published the latest build (5.150) nor and 4.88 builds nor any Android 7.1x builds.
I checked the archives and they are different from the previous 4.84 release, but I've no idea if they are buildable. They still look like they might be missing some useful bits, from my limited knowledge. Those of you who know what to do with this can test it and see if it's useful to you.
Let me know if you would like me to keep bugging them about the 4.88 build's code, or even any earlier 3.x builds.
Have fun!
Cheers

Thanks for bugging them!
Sadly it still contains the same device tree typos that the previous NB1 and even A1N sources contained, so without fixing them those trees do build but won't work correctly as the display won't be accessed correctly (half the screen will be white IIRC).
To be clear, this is what I mean: https://github.com/resident-nokia/u...f68ad2f#diff-6ea71fa79b281dd80cbab0bea96d9472
Also, as a funfact: A quick diff I did showed that the 5140 source is identical to the 4120 kernel source from Nokia 8 Sirocco that was released around December if I am not mistaken (minus the device tree files and some places where device names were hardcoded). That would mean that our kernel hasn't seen an update since December (actually even September, since thats the first CAF tag (Qualcomm upstream) that has changes you can find in those sources). Customer service I guess ¯\_(ツ)_/¯

Hi @THMSP!
Thanks for checking it out, shame it's still got errors in it. That's very interesting about the comparison with the Sirocco and the last change being in September. I suppose a new build doesn't automatically mean a new kernel though.
Since both the Android 8 and 9 source contain errors my only wonder is if the Android 7 source would also have errors, or if it might actually work?! I will ask them for it.
Cheers
EDIT: So the device tree is there after all? I had obviously misunderstood some of the other conversations I'd read, I had always thought it was missing. So it seems the device tree is there, but broken? Or only partially there, and what is there is broken?

The device tree files are all there, but they contain four serious typos that cause them to not actually work when you boot your compiled kernel. The rest of the source code does work. Correcting those typos is not much of a deal, but it is annoying (and personally I wonder how on earth they even maintain these sources).
The other annyoing issue is that for any custom or mismatching kernel the wifi driver won't load (because of signature enforcement for kernel modules), so if you want to make a kernel that doesn't break wifi, you need to add the Qualcomm wifi driver yourself (which then requires additional patches to actually work as well).
When you do those two things, the kernel will work just like the one that Nokia is shipping. For example, my TWRP builds for NB1 actually use the kernel source code for Sirocco, but with the (corrected) device tree files from NB1, and a patched version of the qualcomm wifi driver compiled into the kernel directly.
I am not sure if the nougat sources would help that much to be honest. It's not like those sources are broken because HMD / FIH don't know how to fix them, I bet they break them on purpose (or they get broken by the tool they use to package them). So any further release by them will probably contain the same stupid errors.

Wow! That's a lot to do to make them usable. I agree that I have many questions about QC and QA in the software for these phones, not only because of the source code releases.
You did very well making the device tree for the NB1 then and getting TWRP running, well done! And thanks
Like many I'm interested in the possibility of running other OSes on the NB1, particularly /e/ and any that run on Halium. I presume it will still take a lot of work to get another OS running on the NB1, but is it doable? I think in all cases these projects start from a LOS base.
Cheers

madb1lly said:
Wow! That's a lot to do to make them usable. I agree that I have many questions about QC and QA in the software for these phones, not only because of the source code releases.
You did very well making the device tree for the NB1 then and getting TWRP running, well done! And thanks
Like many I'm interested in the possibility of running other OSes on the NB1, particularly /e/ and any that run on Halium. I presume it will still take a lot of work to get another OS running on the NB1, but is it doable? I think in all cases these projects start from a LOS base.
Cheers
Click to expand...
Click to collapse
Most of the work regarding TWRP and the kernel was actually done by @dg28gadhavi - I just tried to update everything a bit and adapt it to all the new bootloader bugs features that were introduced over time. He deserves all the credit, otherwise I would've had nothing to learn all this stuff from.
Regarding custom ROMs: Sure it is possible. But it is a huge amount of work, that requires you to risk your device (Snapdragon chips are unbrickable, but you couldn't use it as a daily driver), with potentially very few people actually caring (or even donating etc.). When you reached the point where you are able to port a ROM, you have the knowledge to make the changes that you need yourself with Magisk as well. So the only real reason to port a ROM is to give something to the community. And the Nokia 8 community simply isn't big enough that anyone would do that, imo.

Well thanks for @dg28gadhavi as well then!
Yes, I have read that Magisk can do most of what a custom Android ROM might have done. I have some reservations about Magisk, since it's not open source I don't know if I fully trust it, but that could also be the case for most of the software I use! Personally I'm interested most in /e/, which is currently built of a LOS base, but I don't know if all the customisations they've done (mainly to remove any communication with Google services) can be done with Magisk.
As for Halium-relate OSes (Ubuntu Touch, Plasma Mobile, Sailfish OS, LuneOS... some others too), Magisk can't recreate those as they're basically completely different from Android, they just run off the Android kernel and use libhybris to interface with the Bionic library drivers; the rest of Android is not used.
Anyway, this is all beyond my available time at present, so I will just have to carry on with stock Android maybe with some Magisk customisations until my phone breaks!
Cheers

madb1lly said:
I have some reservations about Magisk, since it's not open source I don't know if I fully trust it
Click to expand...
Click to collapse
Magisk is completely opensource, it has always been: https://github.com/topjohnwu/Magisk
You might be thinking about SuperSU which was / is indeed closed source