Related
Kernel Source for Google Nexus S Released
December 15, 2010 By: ElCondor
Android development for the Google Nexus S has now begun. The kernel source – originally made available upon the official phone release – has already been released by Brian Swetland, an Android kernel developer. This source code can be further investigated and explored by developers. Ultimately, this will lead to achieving development milestones much earlier than usual. One example is to root the phone just a few hours or days after it gets released.
Originally posted by supercurio
History for the Nexus S sources begins now.
Original source is here :
http://twitter.com/#!/dnaltews/status/14849739858116608
By Brian Swetland, Android kernel developer.
Thank you Brian !
XDA member supercurio created a thread in the Nexus S forums. Make sure to check it out to follow the discussion, or continue directly to the developer kernel site.
yeah.. it's out:
http://www.engadget.com/2010/12/17/android-2-3-gingerbreads-source-code-now-available/
i wonder why it takes to long to get a first build
Probably its just a matter of mili seconds before one pops up Cant wait >.<
d3sm0nd said:
yeah.. it's out:
http://www.engadget.com/2010/12/17/android-2-3-gingerbreads-source-code-now-available/
i wonder why it takes to long to get a first build
Click to expand...
Click to collapse
Long like more than half a day? Lol.
Don't you need the source for the rest of the OS as well to build a full system?
The source is available now.
tomhierl said:
The source is available now.
Click to expand...
Click to collapse
Here you can see whats going on with the CyanogenMod devs.
The question will soon become 'do I root and flash a custom Gingerbread rom... or wait to see if HTC release one...'
Lothaen said:
The question will soon become 'do I root and flash a custom Gingerbread rom... or wait to see if HTC release one...'
Click to expand...
Click to collapse
root anyway the custom roms are far superior
Theres a test build of Gingerbread in the oxygen thread
I'm unable to find it. Could you post a link?
Stretlow said:
root anyway the custom roms are far superior
Click to expand...
Click to collapse
Tempted, even if I just had a rooted stock and remove some of the junk that is in the rom's...
If you're happy with the stock ROM, don't bother. You'll end up flashing ROMs all the time, always trying the newest or different ones - which is fun for sure, but not really necessary and often quite frustrating.
Can't wait to boot 2.3 on my Desire!
schiznik said:
Theres a test build of Gingerbread in the oxygen thread
Click to expand...
Click to collapse
It's just a themed version I think.
I thought of developing a kernel so that i can use it with my CM11 that im going to port shortly. I thought I'll compile the stock kernel from source itself. I use android pre-built tool chain (arm-eabi-4.6)
I get a lot of compiler errors on stock kernel without any modifications itself...
Do i need to change my tool chain?
Sent from my One V using XDA Free mobile app
I never tried to build the stock kernel, but I think they did it with the android 4.0 toolchain.
To run CM, you need a CM-Kernel. You have to port things from the stock or a custom kernel (like Hellboy by maxwen) to the cm11 kernel.
Try to use rastomanchiks kernel sources (https://github.com/rastomanchik/android_kernel_htc_primou). This kernel is mostly working, stable and has a good battery life now.
I'd also like to build cm11, but my download speed is to slow to download the sources.
Exactly. Even my download speed is slow. And i have a cap also. After 8GB, my download speed drastically decreases. It takes ages to sync the sources...
Sent from my One V using XDA Free mobile app
How different is Cm kernel from stock? I mean what changes should i make?
Sent from my One V using XDA Free mobile app
Cm needs many features which aren't included in the stock kernel and also you should get ION memory allocator working.
Help
jonas2790 said:
Cm needs many features which aren't included in the stock kernel and also you should get ION memory allocator working.
Click to expand...
Click to collapse
Yeah. How do I port?
What happened to your CM12 project?
hehaichi said:
Yeah. How do I port?
What happened to your CM12 project?
Click to expand...
Click to collapse
I started working on cm12 again yesterday and finally have cm11 sources now, so expect a cm11 build in some days
I can't help you with porting, because all the porting work was done by rastomanchik and I chatted with him. You'd have to ask him about this, but he wasn't online the last weeks and can't speak english without google translator.
jonas2790 said:
I started working on cm12 again yesterday and finally have cm11 sources now, so expect a cm11 build in some days
I can't help you with porting, because all the porting work was done by rastomanchik and I chatted with him. You'd have to ask him about this, but he wasn't online the last weeks and can't speak english without google translator.
Click to expand...
Click to collapse
Actually I insist on porting myself so that I can learn building properly.
Actually these things are also interesting.. fixing bugs and all...
Have series of exams till May end. I cant build properly until then. I thought why not learn something..
Where did you learn about building and other stuff. Also I want to build the device tree on my own.
If you could specify some sources to learn, that would be grateful!
hehaichi said:
Actually I insist on porting myself so that I can learn building properly.
Actually these things are also interesting.. fixing bugs and all...
Have series of exams till May end. I cant build properly until then. I thought why not learn something..
Where did you learn about building and other stuff. Also I want to build the device tree on my own.
If you could specify some sources to learn, that would be grateful!
Click to expand...
Click to collapse
This is exactly the same point of view I had when I started some months ago
Sadly, there isn't much documentation about own device trees and own kernels out there.
There also is no reference device tree, so every dev does it in his own way. I'm always trying to have a clean, easy device tree and use the CM ones as a reference.
You can find some tutorials about building cm, but only with downloading a ready-to-use device config and kernel.
I just played around with it one or two weeks and learned the most.
If you have enough time, please at least try to get into this stuff, maybe we can get cm12 running.
You can reach me on irc in the channel #hov on freenode.
jonas2790 said:
This is exactly the same point of view I had when I started some months ago
Sadly, there isn't much documentation about own device trees and own kernels out there.
There also is no reference device tree, so every dev does it in his own way. I'm always trying to have a clean, easy device tree and use the CM ones as a reference.
You can find some tutorials about building cm, but only with downloading a ready-to-use device config and kernel.
I just played around with it one or two weeks and learned the most.
If you have enough time, please at least try to get into this stuff, maybe we can get cm12 running.
You can reach me on irc in the channel #hov on freenode.
Click to expand...
Click to collapse
I have sufficient time only after May. Till then I'll have to do some research and learn the basics.
I saw on the CM wiki page, it says you can run a prebuilt kernel also... So would it work if we could tweak the stock kernel a bit?
And how do I apply patches to the kernel?
hehaichi said:
I have sufficient time only after May. Till then I'll have to do some research and learn the basics.
I saw on the CM wiki page, it says you can run a prebuilt kernel also... So would it work if we could tweak the stock kernel a bit?
And how do I apply patches to the kernel?
Click to expand...
Click to collapse
Yes you can use a prebuilt kernel, but it will only work if the kernel supports you cm version.
You apply patches to a kernel by changing files or directories in the kernel. For example you can use another fs module (maybe with more functions) by copy and pasting the folder for the module from another kernel. The problem is, the new module may require some functions your kernel does not have so it won't compile.
Hey i had mailed rastomanchik and he said 3.4.x kernel is an impossibility for cm11? Why?
Sent from my One V
hehaichi said:
Hey i had mailed rastomanchik and he said 3.4.x kernel is an impossibility for cm11? Why?
Sent from my One V
Click to expand...
Click to collapse
1. It would be much, much, much work.
2. I think there are some device-specific drivers that only work with 3.0
I'm ready to do that work only if i knew how to...
Sent from my One V
hehaichi said:
I'm ready to do that work only if i knew how to...
Sent from my One V
Click to expand...
Click to collapse
Try to get into it yourself or talk with people who know about kernel developement, I'm also new to android developement.
Hi guys, I have been looking at / working on allowing the 32GB variant Mi5 to run at the full speeds (2.15/1.6/624) on the msm8996 SOC as its 64/128GB brothers.
I was able to patch the kernel frequency table to run my 64GB at the reduced frequency of the 32GB but cannot test this in reverse as I don't have a 32GB device
I am hoping a 32GB user can test a boot.img for me. Can fastboot boot/flash it, or flash via TWRP (install -> install image -> select img) and just backup your existing img.
I do suspect it will not boot or work (it does boot/otherwise work on my 64GB though, but there's a few more code differences I haven't changed), but it'd be nice to know
boot_rev1.img this revision does not work, yet
boot_rev2.img a few users report that this one works.
What I would like to know is overall stability for 32GB users, if they could test their phone in games etc as voltage tables may need more adjustment
Edit: please note this kernel is for CM13/AOSP based ROM. please don't flash it over MIUI8
Project moved to http://forum.xda-developers.com/mi-...d-32gb-mi5-t3482455/post69177557#post69177557
Source here: https://github.com/harrynowl/falconkernel-gemini
awesome. did you post in the miui forum?
rochee94 said:
awesome. did you post in the miui forum?
Click to expand...
Click to collapse
Not yet, hoping to find feedback here first
As you are using CM kernel as base, you must inform that this will only work on devices running MIUI 7.x firmware and a CM based ROM.
On top of that, don't forget to publish the link to the kernel source in order to follow XDA's GPL regulations. I know you have the source in Github.
Could you build a kernel to overclock the 64 &128GB versions too? That would be great.
Sorry out of topic but, does snapdragon 820 have mpdecision or not? (by default)
razibrizal said:
Sorry out of topic but, does snapdragon 820 have mpdecision or not? (by default)
Click to expand...
Click to collapse
No: https://source.codeaurora.org/quic/...init.qcom.post_boot.sh?h=LA.HB.1.3.1.c1#n1729.
GalaxyS4_Lollipop said:
Could you build a kernel to overclock the 64 &128GB versions too? That would be great.
Click to expand...
Click to collapse
First focus is on giving 32GB users the full power of the hardware they paid for
I've tried it and it fails to boot
It goes into the bootanimation but after like one second it freeze and reboot
And when it happen, it kinda overheat
Edit
Using AOKP and Cm13 same result
sys01 said:
I've tried it and it fails to boot
It goes into the bootanimation but after like one second it freeze and reboot
And when it happen, it kinda overheat
Click to expand...
Click to collapse
Thanks for info, I think I know why this is..
Harrynowl said:
First focus is on giving 32GB users the full power of the hardware they paid for
Click to expand...
Click to collapse
That's cool.
Anyway, if it is any method to power up the beast to the SnapDragon821 power, I wait for it. (on 64gb)
Good luck and thanks for your support.
4 days ago bought a 32gb Mi5 -> upgraded to latest MIUI 8.0.12
Unlocked bootloader -> Flashed Ressurection Remix's latest ROM via TWRP
Looking forward in testing this !
Alex4455 said:
4 days ago bought a 32gb Mi5 -> upgraded to latest MIUI 8.0.12
Unlocked bootloader -> Flashed Ressurection Remix's latest ROM via TWRP
Looking forward in testing this !
Click to expand...
Click to collapse
Well, please don't use the one I posted originally as it won't work. But I'm looking at a fix now :good:
Looking forward towards the fix.
Many people will be happy if this comes out with no issues !
Harrynowl said:
Well, please don't use the one I posted originally as it won't work. But I'm looking at a fix now :good:
Click to expand...
Click to collapse
thank u for the initiative will wait for the next build :good:
pls after making it work, build one for MIUI 8 if it's possible.
catalizgar said:
pls after making it work, build one for MIUI 8 if it's possible.
Click to expand...
Click to collapse
Miui8 firmware blobs are not currently compatible with the kernel sources we have.
A member got a kernel booting on miui8 but stability was a big problem.
First of all, thank you. I think all 32GB users will thank you for that.
Obviously when it's done, it will consume more power, and would have less SoT.
Can you make predictions of what it will take when optimized and fully working?
After changing my ROM to AOSP based I will use this. thanks for your hard working. really appreciated
I added a new boot.img to the OP with some updates to the source. Hopefully this one has more luck. Specifically changes to the voltage table(s).
Please test 32GB users
Hey, is anyone working on porting custom kernels that will allow the use of google camera at full 23 MP, well 20.5MP?
davidhozic said:
Hey, is anyone working on porting custom kernels that will allow the use of google camera at full 23 MP, well 20.5MP?
Click to expand...
Click to collapse
Not yet as far as we know
I have a xa2 ultra and I'm looking forward to building a unified custom kernel for the xa2(ultra), but there are no kernel sources yet for the latest 10.51 release. I've already asked jerpelea for them and he told me that they will come soon.
dani020110 said:
I have a xa2 ultra and I'm looking forward to building a unified custom kernel for the xa2(ultra), but there are no kernel sources yet for the latest 10.51 release. I've already asked jerpelea for them and he told me that they will come soon.
Click to expand...
Click to collapse
Any updates?
davidhozic said:
Any updates?
Click to expand...
Click to collapse
Nope, no kernel sources yet
If you want to know if the kernel sources are released straight from the Sony webpages, check here, in both look for the ones starting in 50 (that's the number for nile)
This one first, it's more important
https://developer.sony.com/develop/open-devices/downloads/open-source-archives/
https://github.com/sonyxperiadev/kernel-copyleft/branches
There are already some kernel sources for nile, but they are older ones, you should check for the newer ones that match our latest firmware releases
dani020110 said:
Nope, no kernel sources yet
If you want to know if the kernel sources are released straight from the Sony webpages, check here, in both look for the ones starting in 50 (that's the number for nile)
This one first, it's more important
https://developer.sony.com/develop/open-devices/downloads/open-source-archives/
https://github.com/sonyxperiadev/kernel-copyleft/branches
There are already some kernel sources for nile, but they are older ones, you should check for the newer ones that match our latest firmware releases
Click to expand...
Click to collapse
Do you need the latest sources to updste the kernel when you make it for example? Like does it become incompatible?
davidhozic said:
Hey, is anyone working on porting custom kernels that will allow the use of google camera at full 23 MP, well 20.5MP?
Click to expand...
Click to collapse
23MP works with HedgeCam 2 on LineageOS.
davidhozic said:
Do you need the latest sources to updste the kernel when you make it for example? Like does it become incompatible?
Click to expand...
Click to collapse
Well, while it might even boot, it's definitely better to use the latest one, because incompatibility issues might arise and it wouldn't pretty much make sense to run different versions
Finally, it will make it harder to update or add the security patches due to its age, when a kernel from a newer release likely have them.
schmatzler said:
23MP works with HedgeCam 2 on LineageOS.
Click to expand...
Click to collapse
Yeah i know but i'm like looking for sth that could utilize google's hdr cam without 95% of quality loss like on AOSP
dani020110 said:
Nope, no kernel sources yet
If you want to know if the kernel sources are released straight from the Sony webpages, check here, in both look for the ones starting in 50 (that's the number for nile)
This one first, it's more important
https://developer.sony.com/develop/open-devices/downloads/open-source-archives/
https://github.com/sonyxperiadev/kernel-copyleft/branches
There are already some kernel sources for nile, but they are older ones, you should check for the newer ones that match our latest firmware releases
Click to expand...
Click to collapse
Hey would this work? It's for xa2 plus but it is new i guess.
https://developer.sony.com/file/download/open-source-archive-for-50-1-a-11-40/
davidhozic said:
Hey would this work? It's for xa2 plus but it is new i guess.
https://developer.sony.com/file/download/open-source-archive-for-50-1-a-11-40/
Click to expand...
Click to collapse
This one may work
I'll take a look at it
(Dear Valued RedMagic Customer,
Thank you for your patience,
Please check the source code at https://github.com/ztemt. If you cannot access the connection, please refresh the interface and try again the next day. Thank you for your understanding.)
Edit :
It's already released.
Now I hope the developers start creating fantastic roms for this beast phone
salahomer said:
(Dear Valued RedMagic Customer,
Thank you for your patience,
Please check the source code at https://github.com/ztemt. If you cannot access the connection, please refresh the interface and try again the next day. Thank you for your understanding.)
Click to expand...
Click to collapse
Isn't our device NX729J? I don't see kernel source released for this... Sounds like they giving you the run around. They would sell a lot more phones if they did release. I almost didn't buy one due to this.. Hopefully they will release it soon.
Edit: Cool! It's finally released!
JWnSC said:
Isn't our device NX729J? I don't see kernel source released for this... Sounds like they giving you the run around. They would sell a lot more phones if they did release. I almost didn't buy one due to this.. Hopefully they will release it soon.
Click to expand...
Click to collapse
Very soon, not now...so let us wait a few more days or weeks
JWnSC said:
Isn't our device NX729J? I don't see kernel source released for this... Sounds like they giving you the run around. They would sell a lot more phones if they did release. I almost didn't buy one due to this.. Hopefully they will release it soon.
Click to expand...
Click to collapse
I see there are 7S and 6S kernels, but I don't see any custom ROMs for them, so idk if we will see any for this phone too.
The repo is now available, however, it's empty by the time of me posting this now. It took them two weeks just to create the repo, that's insane. Well, at least it finally happened. Waiting for sources to be uploaded, they probably have to use slow vpn or something to do that, so it might take quite a bit of time.
What can we do with the kernel source?
So it is here.
JWnSC said:
Isn't our device NX729J? I don't see kernel source released for this... Sounds like they giving you the run around. They would sell a lot more phones if they did release. I almost didn't buy one due to this.. Hopefully they will release it soon.
Click to expand...
Click to collapse
Edit :
It's already released, check again.
Now I hope the developers start creating a new fantastic roms for this beast phone
Well, apparently we'll have to write drivers for our device:
Code:
# nubia driver
drivers/nubia
arch/arm64/configs/vendor/nubia
arch/arm64/configs/vendor/NX729J_diff.config
arch/arm64/configs/vendor/NX729J-perf_diff.config
arch/arm64/configs/vendor/NX729J_driveronly.config
This is from .gitignore, so we can't build this kernel and run it i.e. on stock rom.
aaa.bbb111222 said:
Well, apparently we'll have to write drivers for our device:
Code:
# nubia driver
drivers/nubia
arch/arm64/configs/vendor/nubia
arch/arm64/configs/vendor/NX729J_diff.config
arch/arm64/configs/vendor/NX729J-perf_diff.config
arch/arm64/configs/vendor/NX729J_driveronly.config
This is from .gitignore, so we can't build this kernel and run it i.e. on stock rom.
Click to expand...
Click to collapse
So... What does that mean for new custom roms
gwenmillett said:
So... What does that mean for new custom roms
Click to expand...
Click to collapse
We're not gonna see them until someone writes these drivers or zte publishes them. Both are very unlikely, so...
Seems like they uploaded it again, on zips. I checked and it seems to contain several things inside the /drivers/nubia folder so we probably have now a full workable kernel source