@RendyAK , @Nonta72 and @MSF Jarvis are requested to come here.
I have started to work on cm-13.0 device and vendor tree, any body please download latest cm-13.0 source.
we are going to discuss in comments.
Raised som cm-13.0 blobs, few blobs missing on stock 6.0? any file missing do a merge request. libMali.so was based on cm-12.1 so, if you have libmali based on stock 6.0 please handover or do a merge request.
Vendor: https://github.com/HostZero/android_vendor_d5110_infinix/tree/cm-13.0
Device: Work progress
- HostZero
HostZero said:
@RendyAK , @Nonta72 and @MSF Jarvis are requested to come here.
I have started to work on cm-13.0 device and vendor tree, any body please download latest cm-13.0 source.
we are going to discuss in comments.
- HostZero
Click to expand...
Click to collapse
Syncing sources up on my server now....
Sent from my Pixel V1 using XDA Labs
MSF Jarvis said:
Syncing sources up on my server now....
Sent from my Pixel V1 using XDA Labs
Click to expand...
Click to collapse
Roger That!
@HostZero, @Nonta72, @RendyAK Check out this : http://build-box.msfjarvis.me:8080/job/cm-13-seedmtk/lastBuild/console
Don't mind the job name, I had planned this for the other variant but now it's for infinix. My suggestion would be to create a GitHub organization and add in everybody to it rather than one person having it on his personal account. And also, gimme a local manifest for the d5110
Sent from my Pixel V1 using XDA Labs
MSF Jarvis said:
@HostZero, @Nonta72, @RendyAK Check out this : http://build-box.msfjarvis.me:8080/job/cm-13-seedmtk/lastBuild/console
Don't mind the job name, I had planned this for the other variant but now it's for infinix. My suggestion would be to create a GitHub organization and add in everybody to it rather than one person having it on his personal account. And also, gimme a local manifest for the d5110
Sent from my Pixel V1 using XDA Labs
Click to expand...
Click to collapse
Build Fail. ? Hmm I will submit device tree tommrow for infinix
HostZero said:
Build Fail. ? Hmm I will submit device tree tommrow for infinix
Click to expand...
Click to collapse
https://github.com/d5110-devs
Go there and accept the invitation, then go to your repository settings and select Transfer and transfer the vendor tree to this organization. @Nonta72, you have an invitation pending too. @RendyAK, I couldn't find you on GitHub so send any of us your GitHub username and we'll add you
About the fail, it doesn't matter, I have shell access to the server as well so I can debug it properly in case there's an issue.
Sent from my Pixel V1 using XDA Labs
MSF Jarvis said:
https://github.com/d5110-devs
Go there and accept the invitation, then go to your repository settings and select Transfer and transfer the vendor tree to this organization. @Nonta72, you have an invitation pending too. @RendyAK, I couldn't find you on GitHub so send any of us your GitHub username and we'll add you
About the fail, it doesn't matter, I have shell access to the server as well so I can debug it properly in case there's an issue.
Sent from my Pixel V1 using XDA Labs
Click to expand...
Click to collapse
Great!
MSF Jarvis said:
https://github.com/d5110-devs
Go there and accept the invitation, then go to your repository settings and select Transfer and transfer the vendor tree to this organization. @Nonta72, you have an invitation pending too. @RendyAK, I couldn't find you on GitHub so send any of us your GitHub username and we'll add you
About the fail, it doesn't matter, I have shell access to the server as well so I can debug it properly in case there's an issue.
Click to expand...
Click to collapse
I have an github account, here it is. https://github.com/Rendyindo/
Since i didnt have any ubuntu computer, so i only can help with some system files. Is it ok?
RendyAK said:
I have an github account, here it is. https://github.com/Rendyindo/
Since i didnt have any ubuntu computer, so i only can help with some system files. Is it ok?
Click to expand...
Click to collapse
It'd be nice if you can probably arrange to dual boot Ubuntu or something because all the files in vendor and device have file system permissions set and Windows tends to completely ruin those. Without Linux you can't even help with the system files
Sent from my Pixel V1 using XDA Labs
MSF Jarvis said:
https://github.com/d5110-devs
Go there and accept the invitation, then go to your repository settings and select Transfer and transfer the vendor tree to this organization. @Nonta72, you have an invitation pending too. @RendyAK, I couldn't find you on GitHub so send any of us your GitHub username and we'll add you
About the fail, it doesn't matter, I have shell access to the server as well so I can debug it properly in case there's an issue.
Sent from my Pixel V1 using XDA Labs
Click to expand...
Click to collapse
HostZero said:
@RendyAK , @Nonta72 and @MSF Jarvis are requested to come here.
I have started to work on cm-13.0 device and vendor tree, any body please download latest cm-13.0 source.
we are going to discuss in comments.
Raised som cm-13.0 blobs, few blobs missing on stock 6.0? any file missing do a merge request. libMali.so was based on cm-12.1 so, if you have libmali based on stock 6.0 please handover or do a merge request.
Vendor: https://github.com/HostZero/android_vendor_d5110_infinix/tree/cm-13.0
Device: Work progress
- HostZero
Click to expand...
Click to collapse
libMali.so is indeed missing. Unless the compiler compiles one; I'm not sure we can boot cm13 yet. cm12.1's one is probably not compatible (kind of).
And I'm really sorry. I've been very busy lately.
I pushed some updates on my github. Still have lot of work to do there.
Nonta72 said:
libMali.so is indeed missing. Unless the compiler compiles one; I'm not sure we can boot cm13 yet. cm12.1's one is probably not compatible (kind of).
And I'm really sorry. I've been very busy lately.
I pushed some updates on my github. Still have lot of work to do there.
Click to expand...
Click to collapse
Hmm anyways I have pushed the cm-13.0 device tree too I have upstremed as many files as possible.
https://github.com/d5110-devs
MSF Jarvis said:
It'd be nice if you can probably arrange to dual boot Ubuntu or something because all the files in vendor and device have file system permissions set and Windows tends to completely ruin those. Without Linux you can't even help with the system files
Click to expand...
Click to collapse
Hmm, okay.. Gonna dual boot it, or use virtualbox.
Or can i use bash in win10, and install git there, i know apt-get and everthing in ubuntu works there.
RendyAK said:
Hmm, okay.. Gonna dual boot it, or use virtualbox.
Or can i use bash in win10, and install git there, i know apt-get and everthing in ubuntu works there.
Click to expand...
Click to collapse
MSF Jarvis Seems to be compiling and i have ubuntu but.. my package is done! as tree and vendor are ready try to compile.
Here by OFFICIAL TWRP:
https://dl.twrp.me/d5110
RendyAK said:
Hmm, okay.. Gonna dual boot it, or use virtualbox.
Or can i use bash in win10, and install git there, i know apt-get and everthing in ubuntu works there.
Click to expand...
Click to collapse
git works, but filesystem permissions are an ext* FS thing, and Windows doesn't recognize ext3 and ext4 formatted partitions so permissions will still get borked. Only solution is a Linux distro.
Sent from my Pixel V1 using XDA Labs
MSF Jarvis said:
git works, but filesystem permissions are an ext* FS thing, and Windows doesn't recognize ext3 and ext4 formatted partitions so permissions will still get borked. Only solution is a Linux distro.
Click to expand...
Click to collapse
Okay then..
Edit:
We have 3.18 too, is it makes cm13 more stable?
RendyAK said:
Okay then..
Edit:
We have 3.18 too, is it makes cm13 more stable?
Click to expand...
Click to collapse
Kernel 3.18? Dunno what to do with it honestly, @HostZero has been handling the device tree till now. I'm just setting up builds at the moment.
Sent from my Pixel V1 using XDA Labs
MSF Jarvis said:
Kernel 3.18? Dunno what to do with it honestly, @HostZero has been handling the device tree till now. I'm just setting up builds at the moment.
Sent from my Pixel V1 using XDA Labs
Click to expand...
Click to collapse
OMG! You guys could provide 3.18, I have used the 3.10 which has come with STOCK 6.0 if you guys can provide MSF will update it!
- HostZero
I have not done any changes with tree I have upstreamed may files available to cm-13.0 from 12.1.
HostZero said:
I have not done any changes with tree I have upstreamed may files available to cm-13.0 from 12.1.
Click to expand...
Click to collapse
I've re-created the device repo with original files from @Nonta72's device tree. Please don't kill commit histories and steal credits. Nonta did the base work and deserves the respect for that. You can delete your local device repo, clone the device repo from d5110-devs and make your changes. And please, please, use meaningful commit messages. You don't have to make a commit for every file you change and you don't need to add a fake file every f***in' time. Please take out the time to learn how to use git before you continue work on the device tree since I can't be cleaning up the mess you make of the commit messages each time.
Sent from my Pixel V1 using XDA Labs
MSF Jarvis said:
I've re-created the device repo with original files from @Nonta72's device tree. Please don't kill commit histories and steal credits. Nonta did the base work and deserves the respect for that. You can delete your local device repo, clone the device repo from d5110-devs and make your changes. And please, please, use meaningful commit messages. You don't have to make a commit for every file you change and you don't need to add a fake file every f***in' time. Please take out the time to learn how to use git before you continue work on the device tree since I can't be cleaning up the mess you make of the commit messages each time.
Sent from my Pixel V1 using XDA Labs
Click to expand...
Click to collapse
WTF! I should do again. C'mon man... I ll do later mostly not now. I will send you tree.zip better you can push it. Because my push is failing.
Related
Hey guys,
I know the dev scene is pretty bleak here. I already had the android 4.3 jellybean source code synced on my laptop, since I was creating builds for my Nexus.
I tried for the SP, but then I realized that there is no device tree present. I found one by Krabappel but it was incomplete (or atleast I think so). It refers to 2 other extract-files.sh, but for the life of me I can't figure out which ones.
I know there are a few devs here, so can one of them help me out here? How to I get the blobs for the phone?
If I get that going, we can start with an AOSP build and then keep adding stuff to it.
Let me know. \
Cheers! :good:
sarkar1990 said:
Hey guys,
I know the dev scene is pretty bleak here. I already had the android 4.3 jellybean source code synced on my laptop, since I was creating builds for my Nexus.
I tried for the SP, but then I realized that there is no device tree present. I found one by Krabappel but it was incomplete (or atleast I think so). It refers to 2 other extract-files.sh, but for the life of me I can't figure out which ones.
I know there are a few devs here, so can one of them help me out here? How to I get the blobs for the phone?
If I get that going, we can start with an AOSP build and then keep adding stuff to it.
Let me know. \
Cheers! :good:
Click to expand...
Click to collapse
I tried building cm10.1 for the sp, but could not get past the kernel logo. Even the recovery didn't work.
If you want the blobs, I can upload them somewhere. I had extracted them from the current 4.1.2 implementation on the device.
the extract-files.sh are in the below repo
"repository": "android_device_sony_common",
"target_path": "device/sony/common"
I have tried to build the recoveryimage but I am getting problem in builting kernel.elf as normally it is in kernel.img
I have tried to both method building kernel and using zImage.
nil1511 said:
the extract-files.sh are in the below repo
"repository": "android_device_sony_common",
"target_path": "device/sony/common"
I have tried to build the recoveryimage but I am getting problem in builting kernel.elf as normally it is in kernel.img
I have tried to both method building kernel and using zImage.
Click to expand...
Click to collapse
Did you try to convert the zimage to elf using the build tools?
Here's the link that you may try http://forum.xda-developers.com/showpost.php?p=43356450&postcount=2
eeehaw said:
I tried building cm10.1 for the sp, but could not get past the kernel logo. Even the recovery didn't work.
If you want the blobs, I can upload them somewhere. I had extracted them from the current 4.1.2 implementation on the device.
Click to expand...
Click to collapse
Awesome. You can either upload them link me the git if its there
sarkar1990 said:
Did you try to convert the zimage to elf using the build tools?
Here's the link that you may try http://forum.xda-developers.com/showpost.php?p=43356450&postcount=2
Click to expand...
Click to collapse
I mean that i tried to make write device files from scratch
as given here
[link]http://wiki.cyanogenmod.org/w/Doc:_porting_intro[/link]
as on method 3 i tried using zImage as kernel as stated there.
but make recoveryimage fails
nil1511 said:
I mean that i tried to make write device files from scratch
as given here
[link]http://wiki.cyanogenmod.org/w/Doc:_porting_intro[/link]
as on method 3 i tried using zImage as kernel as stated there.
but make recoveryimage fails
Click to expand...
Click to collapse
If you want to learn. It would be best to clone the Doomlord git and then read the files and scripts that are present there. This will give you the knowledge you may need to proceed further.
the git for our processor msm8960t is already present on github. Also download the kernel sources and drivers provided by Sony themselves from their developerworld page
sarkar1990 said:
the git for our processor msm8960t is already present on github.
Click to expand...
Click to collapse
You mean the kernel sources or the cm / aosp sources ? Can you provide a link.
eeehaw said:
You mean the kernel sources or the cm / aosp sources ? Can you provide a link.
Click to expand...
Click to collapse
Here is the link
https://github.com/DooMLoRD/android_kernel_sony_msm8960t.git
eeehaw said:
I tried building cm10.1 for the sp, but could not get past the kernel logo. Even the recovery didn't work.
If you want the blobs, I can upload them somewhere. I had extracted them from the current 4.1.2 implementation on the device.
Click to expand...
Click to collapse
I am using the device tree: https://github.com/Krabappel2548/android_device_sony_huashan
I added CPU_TARGET_VARIANT according to JB 4.3 requirements. And loaded up the required gits.
But the thing is now I get an error:
Code:
Code:
make: *** No rule to make target `device/sony/huashan/zImage', needed by `out/target/product/huashan/kernel'. Stop.
Could you help me out a bit?
I recall CM10.1 needing a kernel build from scratch, along with building the ROM
"你看到了没? 爱让我流胆怯的泪..."
"Have you seen it? Love has made me cry cowardly tears..."
sarkar1990 said:
I am using the device tree: https://github.com/Krabappel2548/android_device_sony_huashan
I added CPU_TARGET_VARIANT according to JB 4.3 requirements. And loaded up the required gits.
But the thing is now I get an error:
Code:
Code:
make: *** No rule to make target `device/sony/huashan/zImage', needed by `out/target/product/huashan/kernel'. Stop.
Could you help me out a bit?
Click to expand...
Click to collapse
I did not use krabappel's device files. I had based my stuff on the Xperia T. I'll try this probably tonight.
eeehaw said:
I did not use krabappel's device files. I had based my stuff on the Xperia T. I'll try this probably tonight.
Click to expand...
Click to collapse
Can you push your device file on github
nil1511 said:
Can you push your device file on github
Click to expand...
Click to collapse
I'm behind a very nasty proxy which makes it super hard to push/pull files from github. Instead of pulling i just download the zip archives.
I'll check out ways to push files though.
eeehaw said:
I'm behind a very nasty proxy which makes it super hard to push/pull files from github. Instead of pulling i just download the zip archives.
I'll check out ways to push files though.
Click to expand...
Click to collapse
Man, I keep running into the error! Ahh.. I think we need a better device tree.
sarkar1990 said:
Man, I keep running into the error! Ahh.. I think we need a better device tree.
Click to expand...
Click to collapse
Try getting the yuga tree, and change yuga to huashan, and fusion3 to viskan wherever possible.
This should not be straightforward. You will have to make some tweaks also.
That *might* work.
CallMeVentus said:
I recall CM10.1 needing a kernel build from scratch, along with building the ROM
"你看到了没? 爱让我流胆怯的泪..."
"Have you seen it? Love has made me cry cowardly tears..."
Click to expand...
Click to collapse
You mean coping the kernel sources files to kernel/sony/huashan right ? I did the same thing.
eeehaw said:
Try getting the yuga tree, and change yuga to huashan, and fusion3 to viskan wherever possible.
This should not be straightforward. You will have to make some tweaks also.
That *might* work.
You mean coping the kernel sources files to kernel/sony/huashan right ? I did the same thing.
Click to expand...
Click to collapse
Hmm....and did you define the kernel building path in the boardconfig.mk?
"你看到了没? 爱让我流胆怯的泪..."
"Have you seen it? Love has made me cry cowardly tears..."
CallMeVentus said:
Hmm....and did you define the kernel building path in the boardconfig.mk?
"你看到了没? 爱让我流胆怯的泪..."
"Have you seen it? Love has made me cry cowardly tears..."
Click to expand...
Click to collapse
yes. The kernel was getting built. I was able to see a boot logo on the screen. FreeXperia/Sony logo in this case. And then it would hang. Once I got a bootloop. I was messing around with the ramdisk to see if any hacks get it working.
eeehaw said:
yes. The kernel was getting built. I was able to see a boot logo on the screen. FreeXperia/Sony logo in this case. And then it would hang. Once I got a bootloop. I was messing around with the ramdisk to see if any hacks get it working.
Click to expand...
Click to collapse
Did you implement the changes needed for a CM kernel from its stock sources? I'm not sure of the changes, though. Each kernel differs.
"你看到了没? 爱让我流胆怯的泪..."
"Have you seen it? Love has made me cry cowardly tears..."
CallMeVentus said:
Did you implement the changes needed for a CM kernel from its stock sources? I'm not sure of the changes, though. Each kernel differs.
"你看到了没? 爱让我流胆怯的泪..."
"Have you seen it? Love has made me cry cowardly tears..."
Click to expand...
Click to collapse
No. I knew there were changes but I never knew what they were ? I asked a few people in a few threads but was not able to decipher.
Do you have any idea what sort of changes are required. ?
Since this has been asked a few times
Multi windows support is not in by default
You need to cherry-pick this to include it in your build
https://gerrit.omnirom.org/#/c/53/
thank you,
I added it into my p5110 build, i'll let you know if it works well.
edit:: working well
I won't lie, I plan to build Omni today as my first-ever Android build. It may go hilariously badly, it may go wonderfully. Is it in the command line that I cherry-pick that piece of code? The rest I think I can figure out myself. Thanks in advance.
dibblebill said:
Is it in the command line that I cherry-pick that piece of code?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=37053013&postcount=7
chasmodo said:
http://forum.xda-developers.com/showpost.php?p=37053013&postcount=7
Click to expand...
Click to collapse
You probably will want to do a "repo start" first, otherwise your commit will be clobbered on sync.
e.g. from the root of the source tree:
Code:
repo start work frameworks/base
for more on repo - http://source.android.com/source/using-repo.html
Thank you both. Very helpful. It's wonderful receiving help from the developers, especially since this will be my first build
Sent from my Nexus 10
dibblebill said:
Thank you both. Very helpful. It's wonderful receiving help from the developers, especially since this will be my first build
Sent from my Nexus 10
Click to expand...
Click to collapse
For everybody there was a "first time"
chasmodo said:
http://forum.xda-developers.com/showpost.php?p=37053013&postcount=7
Click to expand...
Click to collapse
When I execute this using the linked cherry pick, all I get is "fatal: Not a git repository (or any of the parent directories): .git
dibblebill said:
When I execute this using the linked cherry pick, all I get is "fatal: Not a git repository (or any of the parent directories): .git
Click to expand...
Click to collapse
you tried this mate?
Code:
git fetch [url]https://gerrit.omnirom.org/android_frameworks_base[/url] refs/changes/53/53/19 && git cherry-pick FETCH_HEAD
before that u must be inside ~/android/omni/frameworks/base if i im rigth, u get there by
Code:
cd ~/android/omni/frameworks/base
someone correct me if im wrong pls.
makkeonmies said:
you tried this mate?
Code:
git fetch [url]https://gerrit.omnirom.org/android_frameworks_base[/url] refs/changes/53/53/19 && git cherry-pick FETCH_HEAD
before that u must be inside ~/android/omni/frameworks/base if i im rigth, u get there by
Code:
cd ~/android/omni/frameworks/base
someone correct me if im wrong pls.
Click to expand...
Click to collapse
[codegit fetch https://gerrit.omnirom.org/android_frameworks_base refs/changes/53/53/19 && git cherry-pick FETCH_HEAD[/code]
Exactly as copied and pated from the cherrypick itself, yep.
I was, however, in ~/android/omni/.repo/projects/frameworks/base, though. Now I got it fixed and inserted. thanks!
on my way to being a ROM hacker/compiler, then later developer
EDIT: Will the sources for this rescync automatically when I repo sync, or will I have to also re-cherry pickk this every few days?
dibblebill said:
[codegit fetch https://gerrit.omnirom.org/android_frameworks_base refs/changes/53/53/19 && git cherry-pick FETCH_HEAD[/code]
Exactly as copied and pated from the cherrypick itself, yep.
I was, however, in ~/android/omni/.repo/projects/frameworks/base, though. Now I got it fixed and inserted. thanks!
on my way to being a ROM hacker/compiler, then later developer
EDIT: Will the sources for this rescync automatically when I repo sync, or will I have to also re-cherry pickk this every few days?
Click to expand...
Click to collapse
If you do a "repo start" before cherry-picking, repo will try to automatically rebase when syncing. It will not sync newer patchsets though.
thanks, very useful.
just to know, why isn't it yet merged ?
BENETNATH said:
thanks, very useful.
just to know, why isn't it yet merged ?
Click to expand...
Click to collapse
Because it still has a lot of bugs that need to be worked out?
Unfortunately, since Omni went public, we've had a ton of device support stuff to work with people on, so the more difficult items have temporarily stalled.
Entropy512 said:
Because it still has a lot of bugs that need to be worked out?
Unfortunately, since Omni went public, we've had a ton of device support stuff to work with people on, so the more difficult items have temporarily stalled.
Click to expand...
Click to collapse
sadly i would say.
BBQ was a great timing but people went crazy on omni, which is a good and a bad thing ^^
i've built omni for my device, with the commit, and it's nice, but currently, it's nearly strictly an AOSP, which is a bit frustrating
keep the hard work, courage to all the omni dev !
BENETNATH said:
sadly i would say.
BBQ was a great timing but people went crazy on omni, which is a good and a bad thing ^^
i've built omni for my device, with the commit, and it's nice, but currently, it's nearly strictly an AOSP, which is a bit frustrating
keep the hard work, courage to all the omni dev !
Click to expand...
Click to collapse
Yeah, I would've liked to have polished things a bit more - but the BABBQ was an opportunity we didn't want to miss.
yep,
anyway, great work. what you guys need now is to keep that alive, and to limit the time spent on bringing devices, better enhance the rom.
Rom builders will join the effort for all the rom stuff, especially as it's really easy (i've bring my device in a dozen of minutes, from a CM branch. needs polishing but works)
Does anyone have the last patch set for multiwindow the 4.3 branch? It seems like the past two weeks worth of patches were lost after the Gerrit server hard drive failure, and I just got my first build done yesterday so I'm not sure what I can cherry pick to test out multiwindow. The last comment remaining seems to imply that the last patch set was broken.
https://gerrit.omnirom.org/#/c/1510/
chasmodo said:
https://gerrit.omnirom.org/#/c/1510/
Click to expand...
Click to collapse
That's the 4.4 branch. Time to cherry-pick!
sgt. meow said:
That's the 4.4 branch. Time to cherry-pick!
Click to expand...
Click to collapse
Are you cherry picking back to 4.3 or doing a 4.4 build? Let us know how it goes! I just set up a build this weekend for my N8013 but Gerrit was down so I couldn't get multiwindow, and when it came back the Gerrit ticket was missing two weeks worth of patches as I mentioned so I was feeling like it would be risky to try to apply it.
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/hydrogen-m-oss
Although the source tree name is hydrogen-m-oss, MI's staff Ivan says hydrogen and helium shares the same kernel source.
is this for real?? man I can't believe my eyes,this means real development, more ROMs...maybe I should stop dreaming and have some expert confirm,
@nijel8
@ajsmsg78
:good:
Hmm hope it's the real deal..
Sent from my MI MAX using XDA-Developers mobile app
laolang_cool said:
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/hydrogen-m-oss
But seems only hydrogen source is released
Click to expand...
Click to collapse
Yes its kernel source for hydrogen (android M kernel).
Now we can have better CM13 and roms based on it.
And we can compile android N also.
Confirmed with Santosh M sir (compiled android N for redmi note 3 first).
I am very much noob at compiling, lets hope developers come up with great things.:good:
Nice to hear it, if it is true...
I hope Helium will coming soon.
小米Max*全网通版*3GB/64GB*银色 - Resurrection Remix 5.7.4 build 6.10.28 by ajsmsg78
Yep it's out... Too bad I can't do anything for two more months...
Looking forward to AOSP or slim for max. too bad only hydrogen's source is out, mine is helium...
Hmmm, i will back ?
nijel8 said:
Yep it's out... Too bad I can't do anything for two more months...
Click to expand...
Click to collapse
how come?
please more roms for xiaomi max hydrogen KERNEL SOURCE IS OUT
I asked MI's staff who is also rom developer Ivan, he says hydrogen and helium shares a same kernel source.
laolang_cool said:
I asked MI's staff who is also rom developer Ivan, he says hydrogen and helium shares a same kernel source.
Click to expand...
Click to collapse
That's probably true looking at the config files... The max cpu's are set to 8.
BTW I managed to build it after fixing some compile errors but it doesn't boot... I guess .config needs tweaking but I am not a kernel expert ... Also /arch/arm64/boot/dts/qcom directory is missing and to get it to compile I had to borrow stuff from /arch/arm/boot/dts/qcom which probably is wrong... Anyway no success...
nijel8 said:
That's probably true looking at the config files... The max cpu's are set to 8.
BTW I managed to build it after fixing some compile errors but it doesn't boot... I guess .config needs tweaking but I am not a kernel expert ... Also /arch/arm64/boot/dts/qcom directory is missing and to get it to compile I had to borrow stuff from /arch/arm/boot/dts/qcom which probably is wrong... Anyway no success...
Click to expand...
Click to collapse
Ivan confirmed helium uses the same config file hydrogen_user_defconfig, and no file is missing... dts in arm64/ and arm/ linked to a same directory.
This is incredible news! Fingers crossed this will lead to some great new ROMs!
Let's hope this leads to some custom kernels
It quits with
Code:
drivers/video/msm/msm_dba/msm_dba.c:25:30: fatal error: msm_dba_internal.h: No such file or directory
for a weird reason here. The file is there, but it quits.
Edit: It works after changing #include <msm_dba_internal.h> to #include "msm_dba_internal.h" in msm_dba.c, but just like nijel8 stated it won't finish because of dts.
TEKME said:
It quits with
Code:
drivers/video/msm/msm_dba/msm_dba.c:25:30: fatal error: msm_dba_internal.h: No such file or directory
for a weird reason here. The file is there, but it quits.
Edit: It works after changing #include <msm_dba_internal.h> to #include "msm_dba_internal.h" in msm_dba.c, but just like nijel8 stated it won't finish because of dts.
Click to expand...
Click to collapse
Copy /arch/arm/boot/dts folder to /arch/arm64/boot/ and /include/dt-bindings to /arch/arm64/include keeping all already existing files(don't overwrite) and it will compile but without cpu_ctl.ko and wifi.ko modules.
nijel8 said:
Copy /arch/arm/boot/dts folder to /arch/arm64/boot/ keeping all already existing files(don't overwrite) and it will compile but without cpu_ctl.ko and wifi.ko modules.
Click to expand...
Click to collapse
From Ivan: cpu_ctl.ko is private. And wifi.ko doesn't exist in kernel/, it's in vendor/qcom/opensource/wlan/ , so MI doesn't release their module source(will not in the future I think...)
We need to get the wifi module source from qcom i.g. https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/, but not sure if max uses qcald-2.0 or not.
Is it possible to use Kenzo sources to fill in the gaps? I swapped my Kenzo for a Hydrogen and I'm loving this huge phone, although MIUI is still a bit clunky. The Nougat AOSP and CM ROMs for Kenzo are pretty much ready for daily use, with camera support and VoLTE being a bit buggy right now.
Both Kenzo and Hydrogen devices use msm8952 with fpc1020 fingerprint sensors, I'm not sure about the camera sensors though.
Introduction
Hello everyone, this is a thread to introduce both users and kernel developers to the concept of linux-stable as well as give developers some tips and a tree to either merge into their own, use as a base, or just as a reference. Feel free to ask questions and enjoy!
What is it?
linux-stable is, as the name implies, the stable branch of the Linux kernel, the base of Android. The phone could not run without the Linux kernel (at least not without reworking a lot of stuff). The Android kernels are based on the longterm stable trees:
Longterm
There are usually several "longterm maintenance" kernel releases provided for the purposes of backporting bugfixes for older kernel trees. Only important bugfixes are applied to such kernels and they don't usually see very frequent releases, especially for older trees.
Click to expand...
Click to collapse
Source: https://www.kernel.org/category/releases.html
All Linux development happens on the master branch, which is governed by Linus Torvalds. When issues are discovered there, the fixes are applied then backported to these various stable trees for consumption. It is not uncommon for a fix to need to go back a few years.
There is a LOT more information available in the notes repo in the android-linux-stable organization if you care to learn more in-depth: https://github.com/android-linux-stable/notes
What does this mean for me?
If you are a developer, this means you should be merging these changes into your own tree. These are vetted, stable fixes to real world problems and they are being handed out for free. It does not take long to get up to date (as you can just merge this tree directly into your own or do it yourself using the tree as a reference) and once you are up to date, there is usually a release once every two weeks, give or take. I provide a rebuttal to a lot of various complaints here. If you still feel like there is a good reason not to do this, please let me know, I'll be happy to try and debate on it!
If you are a user, it means that you should be looking for and using kernels that have these fixes, as it shows the developers care for your security and stability. The current version for this device is 3.18.100 and the current version upstream is 3.18.124 so all you need to do is go into Settings > About phone and look at the kernel version to know if you are up to date.
How do I use?
If you are a developer, the reference tree is located in the android-linux-stable organization: https://github.com/android-linux-stable/marlin
This can either be merged into your existing kernel tree if you have one or be used as a fresh base. You do not need my permission to use it nor do you need to give me credit (although it would be appreciated).
If you are a user, use a kernel that has the changes added in!
Getting notified about updates
There are a few ways to get notified of linux-stable updates:
The linux-kernel-announce mailing list: http://vger.kernel.org/vger-lists.html#linux-kernel-announce
The android-linux-stable Telegram channel: https://t.me/alsupdates
Subscribe to this thread
Follow me on Google+ or Twitter
Getting help
If you have any issues with getting these changes into your tree or want to ask a question, there are a few different ways to do it:
Post in this thread
Join the linux-stable support chat on Telegram: https://t.me/joinchat/C1UAJ1EMSX31PCFdwLnOSg
File an issue either in the android-linux-stable notes repo or the android-linux-stable repo for this device
When requesting help, please give some solid details as to what you are struggling with, as I am happy to provide assistant and clarity but not to do something for you (unless I screwed up).
3.18.88 has been merged in.
3.18.89 has been merged in.
3.18.90 has been merged in.
3.18.91 has been merged in (conflict notes).
Hi Nathan, thanks for the code - built the kernel and flashed (wasn't easy at first). All working well, will use it at a later stage when I build the ROM. BTW, I am running the factory image. Credit also to Anykernel for the zip file
GeyerA said:
Hi Nathan, thanks for the code - built the kernel and flashed (wasn't easy at first). All working well, will use it at a later stage when I build the ROM. BTW, I am running the factory image. Credit also to Anykernel for the zip file
Click to expand...
Click to collapse
Not a Dev, but totally would like to give this a try if you have a zip. On the factory image + twrp 3.2.1
Sent from my [device_name] using XDA-Developers Legacy app
Hi, No problem. There you go... Just flash in TWRP and feedback if all went ok
3.18.92 has been merged in.
Hi, thanks for the code, compiled it against linaro 6.4 (built the cross-compiler following your thread). Tested for one day. All smooth. Sharing the job for those who might be interested. BTW, flashed it directly from fastboot....
Code:
fastboot flash kernel Image.lz4-dtb
Hi, added WireGuard support.
@ nathanchance, sorry, do not mean to hijack your thread...
GeyerA said:
Hi, added WireGuard support.
@ nathanchance, sorry, do not mean to hijack your thread...
Click to expand...
Click to collapse
No worries lol, gives it some life :silly:
Sent from my Pixel 2 XL using XDA Labs
GeyerA said:
Hi, added WireGuard support.
@ nathanchance, sorry, do not mean to hijack your thread...
Click to expand...
Click to collapse
Running this now, so far so good! Thanks!
Definitely interested in wire guard, but currently use WindScribe and am not sure how to properly configure it.
Will try and Frankenstein a config file together tonight and report back [emoji106]
Thanks again
Sent from my [device_name] using XDA-Developers Legacy app
Hi, question. Added DSPManager to my ROM and see that it always gets killed. Can you support the idea to build the kernel with
Code:
CONFIG_SECURITY_SELINUX=n
. Will this get me the kernel permissive and any disadvantages with this? I also see that Viper4android needs a permissive kernel.
3.18.93 has been merged in.
Somebody willing to do a build of the update to flash with fastboot?
I would if I could (still learning how to build myself)
Thnx in advance.
Cheers
Sent from my Google Pixel using XDA Labs
Sgace said:
Somebody willing to do a build of the update to flash with fastboot?
I would if I could
Thnx in advance.
Cheers
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
Was just going to ask if someone could point me to a good resource on how to do so. Will post anything I manage to do [emoji106]
Sent from my [device_name] using XDA-Developers Legacy app
jimbub said:
Was just going to ask if someone could point me to a good resource on how to do so. Will post anything I manage to do [emoji106]
Click to expand...
Click to collapse
Hi,
I used this for the most part: https://forum.xda-developers.com/yureka/help/guide-compiling-64-bit-android-kernel-t3352728
And this:
https://forum.xda-developers.com/an...-how-to-compile-android-kernel-t3627297/page1
Was very helpful and am building right now
Credits to those guys offcourse.
Sent from my Google Pixel using XDA Labs
Sgace said:
Hi,
I used this for the most part: https://forum.xda-developers.com/yureka/help/guide-compiling-64-bit-android-kernel-t3352728
And this:
https://forum.xda-developers.com/an...-how-to-compile-android-kernel-t3627297/page1
Was very helpful and am building right now
Credits to those guys offcourse.
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
If it's ok, here is my personal first ever self built kernel from source. It's 3.18.93 and flashable in fastboot (unzip the zip and then: fastboot flash kernel Image.lz4-dtb)
Offcourse thnx to @nathanchance for the source and all the work!
Cheers
Sgace said:
If it's ok, here is my personal first ever self built kernel from source. It's 3.18.93 and flashable in fastboot (unzip the zip and then: fastboot flash kernel Image.lz4-dtb)
Offcourse thnx to @nathanchance for the source and all the work!
Cheers
Click to expand...
Click to collapse
Thanks for doing this, very much appreciate it! For some reason though, this prevented my phone from booting. Ended up restoring my boot partition and things are well now!
Hello, everyone.
I noticed, there are many custom roms, but not that many for the SM-T505. Is it because it's newly released, or are there other reasons?
Yes, this is a new device and many people are probably waiting for the Black Friday/Cyber Monday deals to grab one. I just grabbed one for $150 on Amazon, a steal compared to something like a Fire tablet IMO. This is a low-end tablet, so there won't be as much focus on it as say a flagship phone. But thankfully it's already been unlocked and rooted, so the next step will be to get TWRP on it, and then custom ROM development can start to pick up on it. Don't expect any updates before the end of the year for custom ROMs though, it will likely take time to have TWRP up and running on it, but I am hopeful that we will see good things on this tablet in 2021
Without kernel sources it won't happen. See https://opensource.samsung.com/uploadSearch?searchValue=sm-t505 and https://opensource.samsung.com/uploadSearch?searchValue=sm-t500.
You can request them on that page. I did it a few times but no response so far.
paziusss said:
Without kernel sources it won't happen. See https://opensource.samsung.com/uploadSearch?searchValue=sm-t505 and https://opensource.samsung.com/uploadSearch?searchValue=sm-t500.
You can request them on that page. I did it a few times but no response so far.
Click to expand...
Click to collapse
Interesting... is it just me or is there no button to start an inquiry?
EDIT: Found it... just posted an Inquiry.
Watching!! I just bought the T500.
jlang11 said:
Watching!! I just bought the T500.
Click to expand...
Click to collapse
Just got an answer from Samsung, but don't get to excited. It was just an automated answer, that they received my inquiry. So stay tuned...
https://opensource.samsung.com/uploadSearch?searchValue=t500 gives you a 514mb file with kernel and vencor files.
Maybe both 505 and 500 are similiar enough to get you started
Sources are available: https://opensource.samsung.com/uploadSearch?searchValue=sm-t500
They include a toolchain in kernel tree, broken KConfigs and a lot of junk. I will try to clean a bit a mess and update a lean kernel tree to github
paziusss said:
Sources are available: https://opensource.samsung.com/uploadSearch?searchValue=sm-t500
They include a toolchain in kernel tree, broken KConfigs and a lot of junk. I will try to clean a bit a mess and update a lean kernel tree to github
Click to expand...
Click to collapse
Will you also do a diff against the upstream version so we can see what they changed?
selemine said:
Will you also do a diff against the upstream version so we can see what they changed?
Click to expand...
Click to collapse
Sure, but I'm going to remove the toolchain from the kernel tree since the beginning. It takes About 1GB alone and I don't want to have it on git refs because it will still take a lot of space even if removed.
The rest of changes will be available on github.
paziusss said:
Sure, but I'm going to remove the toolchain from the kernel tree since the beginning. It takes About 1GB alone and I don't want to have it on git refs because it will still take a lot of space even if removed.
The rest of changes will be available on github.
Click to expand...
Click to collapse
It's been a long time, since i took up building custom roms and forgot about it for a while... if the kernel is cleansed from all the BS no one needs, that would be awesome.
There are a lot of small changes to comments and changes of 2 characters in a line. Wonder if they backported stuff there.
Kernel of the SM-T505 was just released...
If this is of any relevance, the download is 'just' 200MB... i wonder why.
The Platform Archive is mostly identical, just a few text files with notes and copyright were missing.
The Kernel Package as well, just small changes to netfilter and
a new defconfig file.
Defconfig for both devices also is more or less the same
gta4lwifi_eur_open_defconfig is missing one line compared to gta4l_eur_open_defconfig
CONFIG_SAMSUNG_FREECESS=y
Guess the difference comes from the toolchain mentioned above.
@paziusss
How far have you come?
Would be great if we had something clean to start a twrp and easier rooting
selemine said:
@paziusss
How far have you come?
Would be great if we had something clean to start a twrp and easier rooting
Click to expand...
Click to collapse
Sorry, I have a very bad internet connection (uplink it is ~50-100KiB/s)
I created the repo a month ago: https://github.com/pazos/android_kernel_samsung_gta4lwifi
,tried to push and failed. Never tried again until now, but it is still failing.
So, if somebody is nice enough to dump the contents of the SM-T500 kernel in a github repo, I can fork and submit the patches without having to upload the whole thing myself.
paziusss said:
Sorry, I have a very bad internet connection (uplink it is ~50-100KiB/s)
I created the repo a month ago: https://github.com/pazos/android_kernel_samsung_gta4lwifi
,tried to push and failed. Never tried again until now, but it is still failing.
So, if somebody is nice enough to dump the contents of the SM-T500 kernel in a github repo, I can fork and submit the patches without having to upload the whole thing myself.
Click to expand...
Click to collapse
Here you go
jayzarry84 said:
Here you go
Click to expand...
Click to collapse
Thank you! It helped.
I had to apply the patch manually, so everything is in a single commit, but should be easy for others to understand what each chunk of code does.
Here you go: https://github.com/pazos/android_kernel_samsung_gta4lwifi
paziusss said:
Thank you! It helped.
I had to apply the patch manually, so everything is in a single commit, but should be easy for others to understand what each chunk of code does.
Here you go: https://github.com/pazos/android_kernel_samsung_gta4lwifi
Click to expand...
Click to collapse
Just realized I didn't upload the Platform folder contents. It's uploading as we speak
jayzarry84 said:
Just realized I didn't upload the Platform folder contents. It's uploading as we speak
Click to expand...
Click to collapse
I really have to ask, can i use this to build a custom rom for the SM-T505 as well?