Nokia 8 kernel sources - Nokia 8 Guides, News, & Discussion

Here is the link to the Nokia 8 kernel sources (Nokia8 V4.84A OSS)
https://www.nokia.com/en_int/phones/opensource
Hope there are developers for this phone :fingers-crossed:

Hopefully this gets the Devs pumped up a bit! But without a Bootloader Unlock it's kind of a "Bake A Cake But You Can't Eat It" scenario

Actually its pointless to release kernel source without unlocking the bootloader. Or, please correct me if I am wrong.

Correct , pointless but we can hope I'm still hanging on to my Nokia 8 just on the of chance HMD do live up to their "we will unlock these pesky bootloaders"

I'm new to trying to understand Android phones sources, but to me it appears that this is insufficient. I can't find anything that resembles what I understand to be a device tree or the relevant make files. Also, it appears to be quite incomplete, certainly nowhere near the full android source tree. Does it even include all the copyleft source?

[/COLOR]
madb1lly said:
I'm new to trying to understand Android phones sources, but to me it appears that this is insufficient. I can't find anything that resembles what I understand to be a device tree or the relevant make files. Also, it appears to be quite incomplete, certainly nowhere near the full android source tree. Does it even include all the copyleft source?
Click to expand...
Click to collapse
Nokia released the *kernel*'s source code, not the full Android code..
Get you knowledge here: https://forum.xda-developers.com/an...erence-how-to-compile-android-kernel-t3627297

Related

BLU Finally got around to kernel source...

In theory this should be quite useful, no?
Just putting this up here for those who may have lost hope, but on a whim I checked their source repository today and it would seem they've at least uploaded Kernel source!
ftp://Kernel_End_User:[email protected]/
Directory: Pure XL P0010UU (it's a bit of a mess, you may wish to CNTRL+F this)
I haven't checked their software repo yet for ROM source, but it was not uploaded when I initially found this information about a month and a half ago.
The kernel is only VANILLA STOCK source, I haven't compiled it or anything, I'm only linking their servers because I imagine that this isn't getting checked on a regular basis (not much to expect would happen). But, something has happened, so I figured I'd draw some attention to it.
Many thanks to those ROM and kernel devs who have been working to bring us some solid software. It's honestly my only major gripe with the phone.
We (me, acheron, root-expert) tried to compile this several times with CyanogenMod repos with no luck. It's from 7th December 2015 so nothing changed.
bemolx said:
We (me, acheron, root-expert) tried to compile this several times with CyanogenMod repos with no luck. It's from 7th December 2015 so nothing changed.
Click to expand...
Click to collapse
Darn. If only they were more willing to facilitate development.... the software is my only real issue with the phone. Thanks for your work, however.
Same thing here... I would love to have the latest CyanogenMod
Only for updating this post:
Kernel source, mostly ready for Marshmallow ROMs, you can find here on 'cm-13.0' branch.
Linux upstream 3.10.103
Still trying to boot it up.
Gonna update CyanogenMod thread soon.
Cheers
bemolx said:
Only for updating this post:
Kernel source, mostly ready for Marshmallow ROMs, you can find here on 'cm-13.0' branch.
Linux upstream 3.10.103
Still trying to boot it up.
Gonna update CyanogenMod thread soon.
Cheers
Click to expand...
Click to collapse
Great news @bemolx
TheLastCanadian said:
Darn. If only they were more willing to facilitate development.... the software is my only real issue with the phone. Thanks for your work, however.
Click to expand...
Click to collapse
Out of curiosity, how have other manufacturers "facilitated" this sort of development for their products?
vicks1008 said:
Out of curiosity, how have other manufacturers "facilitated" this sort of development for their products?
Click to expand...
Click to collapse
Some lend active support to the venture, LG has a dedicated team for liason, better documentation, etc.
I think it's probably pretty telling that it's only now the BLU source has worked - and it took them 5 months to even release it.
BLU releases kernel source codes upon request instead of proactively providing them. If they're asked for on launch, then the kernel source is released shortly after. So I don't believe the claim that it took 5 months to release.
Can you show me proof of other manufacturers lending support to show BLU?
NVMD.
TheLastCanadian said:
Your belief is irrelevant. They have had many requests, and always it is a referral to the FTP site they host. This site did not populate with the kernel/rom source for quite a few months after I bought the phone, and I was already behind the curve by about 2. I purchased mine on the 30th of December, 2015. I made this post the day after I noticed they had Kernel/Rom. If the URL was still working, I could verify for you the time limit. With that said, it was approximately 5 months.
As for other manufacturers lending support.... ZTE for instance is collaborating with Cyanogenmod, LG proactively provides source and has actually tried to make the process quite simple for most of their phones, and ultimately, contacting BLU about the matter is functionally worthless, as BLU is a reseller and at the whim of Gionee. BLU can't help because they don't do R&D or software as I can tell for the phone.
I'm particularly pissed about the fact I asked before I bought the phone if source was available and it was GPL compliant and I was told yes. 5 months is just a little outside of Amazon's return policy. The Pure XL is a good phone, but the software is quite lacklustre. CM would really be the bees' knees.
Click to expand...
Click to collapse
Well I'm obviously not going to bother contacting my connections at BLU with that attitude. Good luck guys!
vicks1008 said:
Well I'm obviously not going to bother contacting my connections at BLU with that attitude. Good luck guys!
Click to expand...
Click to collapse
I should correct myself slightly. Supposing my e-mail record is correct, they released it 4 months after the phone. I say your belief isn't relevant because a fact is a fact.... as of April 5th, I was still getting apologies from them about Kernel source not being available, specifically, "No ETA on source at this time". Ergo, it could have been longer.
As for BLU, I'm just being honest. They don't develop, they're a reseller.
bemolx said:
Only for updating this post:
Kernel source, mostly ready for Marshmallow ROMs, you can find here on 'cm-13.0' branch.
Linux upstream 3.10.103
Still trying to boot it up.
Gonna update CyanogenMod thread soon.
Cheers
Click to expand...
Click to collapse
Just a small update;
Linux kernel upstream: 3.10.104
Regenerated defconfig as well, the same branch.
I'll try it with full build today.

Project treble on android 8.0

Will Huawei mate 9 support which android oreo's feature project treble?
Sent from my MHA-L29 using Tapatalk
Don't count on it. They already removed the stock ROM images from the official downloads page. Seems Huawei is moving towards more closed source, and I don't think they care about updates.
arminbih said:
Don't count on it. They already removed the stock ROM images from the official downloads page. Seems Huawei is moving towards more closed source, and I don't think they care about updates.
Click to expand...
Click to collapse
thats horrible bs on huaweis part. huawei is legally obligated to release all sources since they use android. google should really enforce the gpl on all oems. project treble would fix huaweis **** software problem.
sadly it seems that everyone who owns a huawei device is either brainwashed or a shill because they seem to be okay with using old outdated software without the possibility of having an update.
i hope huawei does grow here in the US. it might lead to some kind of legal action against them for not releasing sources. if anything it could result in some kind of small payday for not complying.
btw, doesnt anyone care about longevity? many phones are being released with 6GBs of RAM and very fast processors nowadays. these can last years with proper software updates. why upgrade hardware when all that is needed is newer software?
droidbot1337 said:
thats horrible bs on huaweis part. huawei is legally obligated to release all sources since they use android. google should really enforce the gpl on all oems. project treble would fix huaweis **** software problem.
sadly it seems that everyone who owns a huawei device is either brainwashed or a shill because they seem to be okay with using old outdated software without the possibility of having an update.
i hope huawei does grow here in the US. it might lead to some kind of legal action against them for not releasing sources. if anything it could result in some kind of small payday for not complying.
btw, doesnt anyone care about longevity? many phones are being released with 6GBs of RAM and very fast processors nowadays. these can last years with proper software updates. why upgrade hardware when all that is needed is newer software?
Click to expand...
Click to collapse
Not all. They just need to release the kernel source. Which they have (though it breaks the stock camera app...).
The firmware/updates are up to them.
And for your question, I'm just speculating here, but they'd not make any money at all if they release one phone then keep updating it for a few years.
Custom roms is the reason many old devices are still being used. That and some people are cheap and don't care about security. Or they just can't afford a new phone every year.
They've publicly made a commitment to prompt OS and monthly security updates going forward within the last month. They've pledged Oreo in December.
They have made a commitment to be one of the first manufacturers to adopt Project treble. Project Treble is confirmed, and they have promised it for all devices going forward.
I realize this is an old thread now, but this still I suppose could be of use for someone so I'll leave it up.
Project Treble
bunt1691 said:
They've publicly made a commitment to prompt OS and monthly security updates going forward within the last month. They've pledged Oreo in December.
They have made a commitment to be one of the first manufacturers to adopt Project treble. Project Treble is confirmed, and they have promised it for all devices going forward.
I realize this is an old thread now, but this still I suppose could be of use for someone so I'll leave it up.
Click to expand...
Click to collapse
Project Treble is mandatory from Android 8 on according to Google (for devices shipping with Oreo), and from the manifest.xml in the Huawei Oreo update it is fully enabled in the upcoming Oreo releases. This is going to make updates and custom roms a lot easier as long as they don't rely on custom kernels and low level libraries. Treble will insulate the Android framework from the low level stuff. They have already built booting AOSP Android from Google ASOP sources (using the Huawei Oreo kernel). According to Google, implementing treble will enable phone manufacturers to update Android without having to update kernels and low level SoC stuff it will be a while before there are any AOSP based custom ROMs, but with project treble it sure will be a bunch easier
Sources
droidbot1337 said:
thats horrible bs on huaweis part. huawei is legally obligated to release all sources since they use android. google should really enforce the gpl on all oems. project treble would fix huaweis **** software problem.
sadly it seems that everyone who owns a huawei device is either brainwashed or a shill because they seem to be okay with using old outdated software without the possibility of having an update.
i hope huawei does grow here in the US. it might lead to some kind of legal action against them for not releasing sources. if anything it could result in some kind of small payday for not complying.
btw, doesnt anyone care about longevity? many phones are being released with 6GBs of RAM and very fast processors nowadays. these can last years with proper software updates. why upgrade hardware when all that is needed is newer software?
Click to expand...
Click to collapse
First off, the only source that Huawei is "legally" obligated to provide is there source for Android itself, which is and always has been freely available, they are not obligated to release source for any of their libraries or drivers. Anything having to do with the hardware is closed source and will probably remain that way. Old outdated software? On a phone that has only been out a year you must be kidding, there are phones or there that are still shipping with Android 6 (KitKat). At least Huawei will be one of the quicker phone manufacturers at rolling out Oreo to their devices, even on some of their older devices, I've had the other major manufacturers phones and they are not any better at updates than Huawei, worse on major updates actually as their updates have to get bounced back and forth between carrier and manufacturer before finally getting pushed to the user. If you're so unhappy with your device and it's **** software as you put it, sell the damn thing and buy a Samsung or LG.
https://www.xda-developers.com/stock-android-oreo-huawei-mate-9-project-treble/

[PETITION]Kernel source

https://www.change.org/p/people-xio...are_petition&utm_term=share_for_starters_page
Sign the petition guys....
nothing gonna happen by going to that site.. pretty much useless..
But a petition like this gave success to moto g4 plus for getting official oreo
If Xiaomi decides to put out kernel source, they will do it regardless of the petition or community begging. If they don't want to do it, they won't do it. Simple as that.
matcho13579 said:
If Xiaomi decides to put out kernel source, they will do it regardless of the petition or community begging. If they don't want to do it, they won't do it. Simple as that.
Click to expand...
Click to collapse
They will surely, but it might take months to release it.
Guys, let's be patient, if they released source for pretty much all their other recent devices running QCOM there is no real reason to doubt they will for this device as well, just wait, we already have stock android, so need to suffer the horrors of MIUI while we wait
matcho13579 said:
If Xiaomi decides to put out kernel source, they will do it regardless of the petition or community begging. If they don't want to do it, they won't do it. Simple as that.
Click to expand...
Click to collapse
That is not an option this time. As it is a Google device they open themselves up for a lawsuit if they don't.
Was wondering if this was gonna happen.
Also remember that the source only has to be provided upon request. Most post-it to github.com just to cut down on having to fill the request. Has anyone asked them about it?
It seems they are planning to release the kernel source within the next three months, according to this post.

Upgrade sm-j700t to 8.1.0

Hello
Recently, being tired of being restricted to Nougat for my phone, I have done everything I can short of successfully compiling a new android system to get a better experience. That being said, I want 8.1, and there are no ROMs for the sm-J700T so, I have decided I will compile my own version. However, I seem to have a bit of a problem. I cannot find a device tree for my device, but I have found ones for similar devices (sm-j700f) yet as far as I am aware, these devices have different proprietary binaries. So, how can I modify one of these device trees for my device? I have the files from Samsung, from Samsung's Open source Resource Center, and I asked them for advice on how to sue their files and they basically told me "We know how to use them with AOSP, but because our ROMs are better because they're optimized for your device, we wont tell you. Go look it up on google." When I have searched the depths of the internet for the past few days, before I asked. Needless to say I left a very dissatisfied review with them.
Anyways, in short, how do I modify a device tree from github for use with AOSP, and am I supposed to use Samsung's OSRC files?
Here is a device tree I could use is on github but frankly I cannot post a link so that's fun.
The SM-j700T is very similar to the j700F variant, but as I said, they are supposedly different.
Update now
SomeDevPerson said:
Hello
Recently, being tired of being restricted to Nougat for my phone, I have done everything I can short of successfully compiling a new android system to get a better experience. That being said, I want 8.1, and there are no ROMs for the sm-J700T so, I have decided I will compile my own version. However, I seem to have a bit of a problem. I cannot find a device tree for my device, but I have found ones for similar devices (sm-j700f) yet as far as I am aware, these devices have different proprietary binaries. So, how can I modify one of these device trees for my device? I have the files from Samsung, from Samsung's Open source Resource Center, and I asked them for advice on how to sue their files and they basically told me "We know how to use them with AOSP, but because our ROMs are better because they're optimized for your device, we wont tell you. Go look it up on google." When I have searched the depths of the internet for the past few days, before I asked. Needless to say I left a very dissatisfied review with them.
Anyways, in short, how do I modify a device tree from github for use with AOSP, and am I supposed to use Samsung's OSRC files?
Here is a device tree I could use is on github but frankly I cannot post a link so that's fun.
The SM-j700T is very similar to the j700F variant, but as I said, they are supposedly different.
Click to expand...
Click to collapse
could you create the rom bro?

Petition : LineageOS support for Nokia 8

Hello fellow TA-1004/TA-1012 users.
Nokia 8 has been a bittersweet experience for most of us. The insane price drop killing it's resale value. Stock but buggy and sub par software. It's a flagship that has ticked as many wrong boxes as it did right.
But the software experience leaves a lot to be desired.
http://chng.it/5X8ncWT6XB
Let's go ahead and sign this petition in numbers to get LineageOS official support for this device.
Please spread the word.
Eh? The issue is not at LineageOS, they would support it if there only was something to work with.
The issue is HMD Global unwilling to provide sufficient sources or provide any help for the community around their devices.
LineageOS can't just throw developers into puzzling proprietary blobs. They will just be shooting in the dark and will have a real hard time maintaining anything. You need a proper source code or clear device specifications to make anything usable..
Modding and puzzling around vendors firmware is totally another thing than actually maintain code.
Signed!

Categories

Resources