UnityROM-2 v.2.5.0
*****Discontinued.... No way to test actively till I have a functional build.*****
HTC One M7 Sprint Edition ( m7spr )
Development Section...
Want to contribute to the project or become team member?
Contact Me by PM here or leave a post detailing what you can and are willing to do for the projects' advancement.
My Github: https://github.com/LiquidSmokeX64
All current project sources can be found there .
ALSO MY FOOL-PROOF BUILD GUIDE & SCRIPTS ARE THERE FOR THOSE TOO IMPATIENT TO WAIT FOR MY NEXT RELEASE .
**Sources current as of version 2.5.0**
**10/06/2014**
Direct link to guide:
https://github.com/LiquidSmokeX64/Guides-Scripts
Note: Noob Friendly. If you're new to building ROMs or have never done it at all. I will help for as long as you maintain civility and focus on the project goals.
Installation errors out. Here is a pastebin of log saved after error
http://pastebin.com/fz15gwwn
Edit: I was able to install after removing that set perm line from updater. I will let ya know how it goes.
gruesomewolf said:
Installation errors out. Here is a pastebin of log saved after error
http://pastebin.com/fz15gwwn
Edit: I was able to install after removing that set perm line from updater. I will let ya know how it goes.
Click to expand...
Click to collapse
Ok. I just removed it too. My bad adaptation from Evo LTE. Nothing too bad luckily.
Reuploading the fixed version now.
LiquidSmokeX64 said:
Ok. I just removed it too. My bad adaptation from Evo LTE. Nothing too bad luckily.
Reuploading the fixed version now.
Click to expand...
Click to collapse
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
gruesomewolf said:
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
Click to expand...
Click to collapse
So. You're a kernel dev... Got a question for you. How do I add more CFLAGS to the makefile without it not booting or whatever? I've tried adding -O3 to the 2 places I know to put CFLAGS. Same place I put the -w so it would work with GCC 4.8
gruesomewolf said:
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
Click to expand...
Click to collapse
Will you be releasing this kernel for the Evo 4G? [emoji14] Evo4gnoob here
LiquidSmokeX64 said:
So. You're a kernel dev... Got a question for you. How do I add more CFLAGS to the makefile without it not booting or whatever? I've tried adding -O3 to the 2 places I know to put CFLAGS. Same place I put the -w so it would work with GCC 4.8
Click to expand...
Click to collapse
I wouldn't say Im a kernel dev....more of a dabler...lol. I sent you a pm with my makefile so you can see adjustments I made for my kernels latest build (not yet publicly released)
Notorious said:
Will you be releasing this kernel for the Evo 4G? [emoji14] Evo4gnoob here
Click to expand...
Click to collapse
Umm....no I dont have any plans for that ATM
gruesomewolf said:
I wouldn't say Im a kernel dev....more of a dabler...lol. I sent you a pm with my makefile so you can see adjustments I made for my kernels latest build (not yet publicly released)
Umm....no I dont have any plans for that ATM
Click to expand...
Click to collapse
Was joking lol
Notorious said:
Was joking lol
Click to expand...
Click to collapse
So you're allowing the integration of it? Just to be clear.
So I'm not sure why but the kernel borked again. Maybe I need to go through one flag at a time? Or maybe forgot something....?
gruesomewolf said:
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
Click to expand...
Click to collapse
Hey. Im having nothing but issues building it in the ROM so I was curious if you could tell me what I need to do after copying the msm8960 folder to a new place and adding in the makefile changes? Ive never built a kernel independently before but would like it to be a boot.img like normal so I can just replace the one in the ROM zip with the new one. Im sure it's pretty easy, just figured I'd ask you rather than comb through 80 guides saying different stuff lol.
LiquidSmokeX64 said:
Hey. Im having nothing but issues building it in the ROM so I was curious if you could tell me what I need to do after copying the msm8960 folder to a new place and adding in the makefile changes? Ive never built a kernel independently before but would like it to be a boot.img like normal so I can just replace the one in the ROM zip with the new one. Im sure it's pretty easy, just figured I'd ask you rather than comb through 80 guides saying different stuff lol.
Click to expand...
Click to collapse
Could you pm me with more info. Exact process of building, errors during build, any changes made to source, etc.
I'm gonna download your source later, together we should be able to figure this out.
gruesomewolf said:
Could you pm me with more info. Exact process of building, errors during build, any changes made to source, etc.
I'm gonna download your source later, together we should be able to figure this out.
Click to expand...
Click to collapse
I'm not seeing errors. Hell I removed everything but the -O3 spots and it still refused to boot. I dont know what the deal is....
Anytim I do ANYTHING to the kernel its dead, no matter how stupid it is.
gruesomewolf said:
Could you pm me with more info. Exact process of building, errors during build, any changes made to source, etc.
I'm gonna download your source later, together we should be able to figure this out.
Click to expand...
Click to collapse
BTW. The makefile is borked. And was curious if you knew how to build AOSP for this device? CM was pretty easy, I'd figure AOSP isn't too different. Then I can try to get Android L running once I have a working Android K to cross-reference to and make the version specific changes in device, kernel, vendor, qcom-common, and s4-common
LiquidSmokeX64 said:
So. You're a kernel dev... Got a question for you. How do I add more CFLAGS to the makefile without it not booting or whatever? I've tried adding -O3 to the 2 places I know to put CFLAGS. Same place I put the -w so it would work with GCC 4.8
Click to expand...
Click to collapse
When certain flags or 03 is added it creates a larger zImage. In order to compensate the boot.img needs needs modified, either by kernel installer or if baked in the rom hex edited. To change the ramdiskaddr.
Sent from my HTCONE using Tapatalk
thicklizard said:
When certain flags or 03 is added it creates a larger zImage. In order to compensate the boot.img needs needs modified, either by kernel installer or if baked in the rom hex edited. To change the ramdiskaddr.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Absolutely correct. And to elaborate on this just a bit more. Since your source building here, you can actually adjust the ramdiskadd with the scripts, considering it uses mkbootimg commands to build the boot.img.
An additional line in your devices board config, to give it a new ramdiskaddr size. Then an additional line in the build folder factory_ramdisk.mk , to handle the command for a new ramdiskaddr size should do the trick.
As for your other question about building aosp. I'm afraid that would be beyond my area of expertise. You would have significantly modify aosp code to allow for caf. It would be much harder then building cm, cause cm already has all the adjustments needed for caf devices
thicklizard said:
When certain flags or 03 is added it creates a larger zImage. In order to compensate the boot.img needs needs modified, either by kernel installer or if baked in the rom hex edited. To change the ramdiskaddr.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
gruesomewolf said:
Absolutely correct. And to elaborate on this just a bit more. Since your source building here, you can actually adjust the ramdiskadd with the scripts, considering it uses mkbootimg commands to build the boot.img.
An additional line in your devices board config, to give it a new ramdiskaddr size. Then an additional line in the build folder factory_ramdisk.mk , to handle the command for a new ramdiskaddr size should do the trick.
As for your other question about building aosp. I'm afraid that would be beyond my area of expertise. You would have significantly modify aosp code to allow for caf. It would be much harder then building cm, cause cm already has all the adjustments needed for caf devices
Click to expand...
Click to collapse
I read this and my eyes glaze over. But you are in good hands with these two helping you. :highfive:
Yeah I'm working on it guys. Read the integrated kernel building guide and trying that. But if I could just get it to build me the boot.IMG and get my ramdisk sizes and whatever I'm looking at where to edit it in the device/BoardConfig changed the defconfig to a custom one I made based off the original one from the working boot.IMG but changed the I/O scheduler & CPU governed defaults. Gave it a local name (UnityKernel-x.x.x) and am fighting its last issues. So if nothing else help building it independently might be the most useful now. So if nothing else I can push a new boot.img
My bad. It just says the boot partition size so I think I might be almost there
Related
Hello:
I am looking to build the official Atrix-dev CM7 weekly/nightly, however, cannot find any instructions/guide to do so. Of course, I could simply pull everything from the Atrix-dev CM7 github and overlay on base CM7 source, but thought I'd ask before I do that.
Why build from source? I am not looking to build a CM7 based ROM or release anything, just change some minor things for my own consumption:
- Not have mmcblk1p2 mount as /sd-ext [currently set in a .mk file according to vanilla CM7 source for olympus]
- Since webtop doesnt work in CM7 (and I dont need it) expand /data(p16) to include the partition space of /osh(p13) [means mucking around with the partition table, and the init scripts to change mounts]
- have emmc mount on /sdcard and external sdcard mount on /sd-ext so that backups from other ROMs work
Cheers
acerbix said:
Hello:
I am looking to build the official Atrix-dev CM7 weekly/nightly, however, cannot find any instructions/guide to do so. Of course, I could simply pull everything from the Atrix-dev CM7 github and overlay on base CM7 source, but thought I'd ask before I do that.
Why build from source? I am not looking to build a CM7 based ROM or release anything, just change some minor things for my own consumption:
- Not have mmcblk1p2 mount as /sd-ext [currently set in a .mk file according to vanilla CM7 source for olympus]
- Since webtop doesnt work in CM7 (and I dont need it) expand /data(p16) to include the partition space of /osh(p13) [means mucking around with the partition table, and the init scripts to change mounts]
- have emmc mount on /sdcard and external sdcard mount on /sd-ext so that backups from other ROMs work
Cheers
Click to expand...
Click to collapse
Check here.
http://forum.xda-developers.com/showthread.php?t=915435
It's not for Atrix but you can just do it by modifying model name.
I just followed this method.
(Currently having java related problem though)
+1 it's a good one and is one of my references too.
AndroidON said:
Check here.
http://forum.xda-developers.com/showthread.php?t=915435
It's not for Atrix but you can just do it by modifying model name.
I just followed this method.
(Currently having java related problem though)
Click to expand...
Click to collapse
+1. Great recommendation. Just used it to complete my first build.
Sent from my MB860 using XDA App
AndroidON said:
Check here.
http://forum.xda-developers.com/showthread.php?t=915435
It's not for Atrix but you can just do it by modifying model name.
I just followed this method.
(Currently having java related problem though)
Click to expand...
Click to collapse
Thanks for the info - not quite what I was looking for though. If you follow these instructions you build the vanilla CM7. I wanted to get/build the Atrix customized bits (i.e fingerprint scanner for example) which are not in the vanilla sources. I am guessing that can be pulled down from Atrix-dev github. Original post was to see if there was an easy way to do that.
After looking at the atrix developer github, found a default.xml for the .repo that should work, and used it.
acerbix said:
Thanks for the info - not quite what I was looking for though. If you follow these instructions you build the vanilla CM7. I wanted to get/build the Atrix customized bits (i.e fingerprint scanner for example) which are not in the vanilla sources. I am guessing that can be pulled down from Atrix-dev github. Original post was to see if there was an easy way to do that.
After looking at the atrix developer github, found a default.xml for the .repo that should work, and used it.
Click to expand...
Click to collapse
The fingerprint scanner was working in my kang. The only thing I pulled from the atrix-dev-team's github were the proprietary vendor files. Other than that those instructions should get you an up to date nightly build.
Sent from my MB860 using XDA App
ghost_og said:
The fingerprint scanner was working in my kang. The only thing I pulled from the atrix-dev-team's github were the proprietary vendor files. Other than that those instructions should get you an up to date nightly build.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Thanks so much for the info - trying it now.
ghost_og said:
The fingerprint scanner was working in my kang. The only thing I pulled from the atrix-dev-team's github were the proprietary vendor files. Other than that those instructions should get you an up to date nightly build.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Hmm you have put that in the local_manifest.xml which line did you use? I'm trying to get it to work but somehow can't get the FP unlock option or the change of navigation with fp (navigation does work though).
acerbix said:
Thanks so much for the info - trying it now.
Click to expand...
Click to collapse
crnkoj said:
Hmm you have put that in the local_manifest.xml which line did you use? I'm trying to get it to work but somehow can't get the FP unlock option or the change of navigation with fp (navigation does work though).
Click to expand...
Click to collapse
Well I'm a big dummy. Looks like the only thing that was working was the trackpad navigation. I never use the scan/unlock feature so I just assumed it was working also. I should have checked before posting. I just caught up on my reading and saw your posts with t.s. eliot over in the Weeklys thread, crnkoj. Sorry for the misinformation acerbix.
Anyone else successfully built from source with full FP functionality?
ghost_og said:
Well I'm a big dummy. Looks like the only thing that was working was the trackpad navigation. I never use the scan/unlock feature so I just assumed it was working also. I should have checked before posting. I just caught up on my reading and saw your posts with t.s. eliot over in the Weeklys thread, crnkoj. Sorry for the misinformation acerbix.
Anyone else successfully built from source with full FP functionality?
Click to expand...
Click to collapse
Oh okay - I thought I must be doing something stupid so I PM'd you last night rather than post here. So we all can get trackpad working in the kang but not device setting/lock/unlock
crnkoj said:
Hmm you have put that in the local_manifest.xml which line did you use? I'm trying to get it to work but somehow can't get the FP unlock option or the change of navigation with fp (navigation does work though).
Click to expand...
Click to collapse
I tried replacing default.xml in .repo with the one in Atrix dev git repository, and then pulling down the code. That lead to multiple build failure, so I am assuming hte changes in the atrix dev github are not synced with the changes upstream coz vanilla cyanogenmod builds fine.
I am not even getting the "Device Settings" option that shows up in the weekly build, though the trackpad works fine. I'll try looking at the Settings.apk code to see if there is something I am missing.
cmkoj: Do you have a local_manifest.xml that works and gives you a good build? Open to sharing that?
ah ghost_og i see, i was like how could he get it to work np though anyhow i think one has to implement this: https://github.com/Atrix-Dev-Team/android_packages_apps_Settings into teh build aswell to get fp (read the latest commits there ). second to that probably one has to use https://github.com/Atrix-Dev-Team/android_device_motorola_olympus.git with the branch fingerprint int he local manifest to get it to work than (i have tried this like a few times still not working ...)
acerbix im not sure what you need? do you need a local manifest that makes fp work as it should ( i havent managed to get it to work yet) or just one that works for building? i can sure share the latter one
crnkoj said:
ah ghost_og i see, i was like how could he get it to work np though anyhow i think one has to implement this: https://github.com/Atrix-Dev-Team/android_packages_apps_Settings into teh build aswell to get fp (read the latest commits there ). second to that probably one has to use https://github.com/Atrix-Dev-Team/android_device_motorola_olympus.git with the branch fingerprint int he local manifest to get it to work than (i have tried this like a few times still not working ...)
acerbix im not sure what you need? do you need a local manifest that makes fp work as it should ( i havent managed to get it to work yet) or just one that works for building? i can sure share the latter one
Click to expand...
Click to collapse
Thanks! I feel like such an idiot now. When I changed the drop down list for the branch, I saw the source for the fingerprint unlock actions! (i.e chooselockfinger.java, confirmlockfinger.java).
Off to try a build now!
crnkoj said:
ah ghost_og i see, i was like how could he get it to work np though anyhow i think one has to implement this: https://github.com/Atrix-Dev-Team/android_packages_apps_Settings into teh build aswell to get fp (read the latest commits there ). second to that probably one has to use https://github.com/Atrix-Dev-Team/android_device_motorola_olympus.git with the branch fingerprint int he local manifest to get it to work than (i have tried this like a few times still not working ...)
acerbix im not sure what you need? do you need a local manifest that makes fp work as it should ( i havent managed to get it to work yet) or just one that works for building? i can sure share the latter one
Click to expand...
Click to collapse
Right now, I'd settle for one that works for building. I manually overlay files, so that will definitely be easier
t.s.eliot said:
Thanks! I feel like such an idiot now. When I changed the drop down list for the branch, I saw the source for the fingerprint unlock actions! (i.e chooselockfinger.java, confirmlockfinger.java).
Off to try a build now!
Click to expand...
Click to collapse
Lets know if you get it working I'm building too [clobber build just for the heck of it - will keep you posted]
Thanks a ton, cmkoj for all the help/pointers!
crnkoj said:
ah ghost_og i see, i was like how could he get it to work np though anyhow i think one has to implement this: https://github.com/Atrix-Dev-Team/android_packages_apps_Settings into teh build aswell to get fp (read the latest commits there ). second to that probably one has to use https://github.com/Atrix-Dev-Team/android_device_motorola_olympus.git with the branch fingerprint int he local manifest to get it to work than (i have tried this like a few times still not working ...)
acerbix im not sure what you need? do you need a local manifest that makes fp work as it should ( i havent managed to get it to work yet) or just one that works for building? i can sure share the latter one
Click to expand...
Click to collapse
Thank you for pointing out the Settings and Device branches. Was definitely using the old gingerbread branches before. I just replaced those two folders with the fingerprint branch and am building again. Will check back in once it's done.
*Update* Still no luck. I tried using the updated Device and Settings folders but only navigation works still. Dang.
ghost_og said:
Thank you for pointing out the Settings and Device branches. Was definitely using the old gingerbread branches before. I just replaced those two folders with the fingerprint branch and am building again. Will check back in once it's done.
*Update* Still no luck. I tried using the updated Device and Settings folders but only navigation works still. Dang.
Click to expand...
Click to collapse
Away from my Atrix so cant try this yet - do you think the kernel matters? Did you switch to the kernel included in the build?
acerbix said:
Away from my Atrix so cant try this yet - do you think the kernel matters? Did you switch to the kernel included in the build?
Click to expand...
Click to collapse
Hey guys, I also noticed that android_ frameworks_base has a fingerprint branch with updated commits from t0dbld. I've included this third replacement folder and will be trying another build. Might want to try including this with the 2 branches crnjok pointed out above. I'm keeping my fingers crossed for this one.
I have not replaced any kernels prior to building and use what comes with the stock build. That's a whole other issue for me. When I try to compile just the kernel my zImage ends up being 1mb bigger than faux's and the packaged boot.img I create will not boot. I'm guessing this is due to my being on a 32-bit machine, but I'm not positive.
ghost_og said:
Hey guys, I also noticed that android_ frameworks_base has a fingerprint branch with updated commits from t0dbld. I've included this third replacement folder and will be trying another build. Might want to try including this with the 2 branches crnjok pointed out above. I'm keeping my fingers crossed for this one.
I have not replaced any kernels prior to building and use what comes with the stock build. That's a whole other issue for me. When I try to compile just the kernel my zImage ends up being 1mb bigger than faux's and the packaged boot.img I create will not boot. I'm guessing this is due to my being on a 32-bit machine, but I'm not positive.
Click to expand...
Click to collapse
ye i forgot to mention that one lol, i thought its in the fingerprint build though. for my use i manually git cloned the vendor_motorola repo into /working_dir/vendor/ but havent had any luck. regarding the kernel afaik if you put the additional repos into your local_manifest.xml it should use the kernel from there (if one is available). but i dont really think the kernel is needed to be changed, since on my builds i had the authentec.truesuite (or whatever the process for fp is called) running, only the fp unlock/device option were missing (there is a Fingerprintsomething.apk in the vendor repo of atrix dev team that i have had pulled in and built with but it didnt work, so yes im slowly giving up (second to that i tried setting up a build env on a second pc that drastically faster than the other one an i cannot get repo sync to sync android_prebuilt - just deleted the whole thing and did init again...)
as for the local_manifest.xml it should look like this http://pastebin.com/ccvVi2k9 for building the gb (that is with nav functioning fp but no unlock) if you want to get unlock to work you need to probably put in the other ones aswell (just by copying the <project path="device/motorola/olympus"
name="Atrix-Dev-Team/android_device_motorola_olympus.git"
remote="gh"
revision="gingerbread"/>
part and changing the name to appropriate and teh revision in all to fingerprint)
thanks go to fattire from the nook color forums who thought me how to make and edit these local_manifest.xml files and i used his file as a template for mine aswell.
i have to admit it im slowly sick of not being able to build one with working fp =/
Guys, see here for what directories to be pulled from atrix-dev-team github vs what to be kept in original CM7:
https://github.com/Atrix-Dev-Team/android/blob/gingerbread/default.xml
crnkoj said:
(second to that i tried setting up a build env on a second pc that drastically faster than the other one an i cannot get repo sync to sync android_prebuilt - just deleted the whole thing and did init again...)
Click to expand...
Click to collapse
Try updating ~/android/system/.repo/manifests/default.xml. I used this to fix the problem with the prebuilt repo sync:
Another workaround is to add the following remote definition:
Code:
<remote name="github-https"
fetch="https://github.com/" />
Then change the project definition to:
Code:
<project path="prebuilt" name="CyanogenMod/android_prebuilt" remote="github-https"/>
Once things are back to normal, you can remove the additional remote, and restore the original manifest.
Click to expand...
Click to collapse
It was provided in the comments section here.
ghost_og said:
Try updating ~/android/system/.repo/manifests/default.xml. I used this to fix the problem with the prebuilt repo sync:
It was provided in the comments section here.
Click to expand...
Click to collapse
yes thanks, lol, i knew about the fix and had the first part of it done with changing to https, but forgot about the second part, idiot i...
anyhow i resynced and am building now on the other pc with this local manifest http://paste.pocoo.org/show/534837/
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. ?
General informations:
This thread's aim is only to represent a central meeting and discussion point for BCM21553 developers and, in particular, for the open Kernel/ROM sources development for the Samsung Galaxy Pocket GT-S5300 (codenamed Cori).
Information for common users:
As already described in the previous section, if you are not a developer, please restrict your posts to the general discussion thread so that developers can maintain good communication. Every post that is not strictly respecting these rules will be reported to the forum moderators. Thanks for your understanding.
For any other BCM21553 device related question or information, please, use this thread as a reference point, instead:
[DEVS ONLY][BCM21553 series] CyanogenMod 11 for BCM21553 Development Discussion
As someone already might know, I'm streambinder, from MoltenMotherBoard team.
I have already followed some projects for the GT-S5300, but especially kept in contact
with some of the events related to the porting of ROM and Kernel sources for BCM21553 chipset based devices.
In this precise moment, the sources in my possession allow you to be able to compile
a bugfree CWM 5.0.2.8 (based on CyanogenMod 7 code) with a kernel based on the Samsung stock one.
The only - fundamental - problem was due to the fact that unless I hadn't used the prebuilt INIT binary
token in the Samsung stock firmware boot.img, the phone would not work - or, better, boot up.
This means that until the situation - regarding this issue - doesn't change, our access to the porting of custom ROM
would be barred.
Recently, I decided to give Cori another chance and rework my sources, looking at the wonderful work brought
by the BroadcomCM team on CyanogenMod 9 (in particular, thanks to @bieltv.3 and @Alberto96) and @psyke83 on CyanogenMod 11.
They've not only been able to run these two ROMs in a more or less crude way, but this developer has been able to write
the necessary strings to make the INIT binary of some of these BCM21553 devices opensource.
Strong of this informations, I readjusted some of the sources of BroadcomCM's CyangenMod 9, which includes
all the progress carried out by both the team and psyke83, in order to make them work even on Cori,
and am now next to the first test of the CWM 6.X.X.X, based on IceCreamSandwich code.
At the same time, @akhbh is working on the KitKat code based CWM.
I hope I can give more information about any progress as soon as possible.
The General Discussion thread for non-development issues is here:
*.[DISCUSSION] CyanogenMod 11 For Galaxy Pocket GT-S5300 Discussion Thread
Made a first test of CWM based on CyanogenMod 9 code.
It seems it cannot flash it as it weighs so much compared to its partition configuration value: in fact, the maximum boot partition size is set up to 5.0MB, but the compiled boot.img weighs 5.3MB.
Will have to resize its weight in order to make it fill into the partition.
@akhbh, have you had any complication in these terms, with CyanogenMod 11 sources?
@psyke83, what do you suggest to do? Do you think an increasement of boot partition would be a better idea?
streambinder said:
Made a first test of CWM based on CyanogenMod 9 code.
It seems it cannot flash it as it weighs so much compared to its partition configuration value: in fact, the maximum boot partition size is set up to 5.0MB, but the compiled boot.img weighs 5.3MB.
Will have to resize its weight in order to make it fill into the partition.
@akhbh, have you had any complication in these terms, with CyanogenMod 11 sources?
@psyke83, what do you suggest to do? Do you think an increasement of boot partition would be a better idea?
Click to expand...
Click to collapse
No, I didn't faced those complications. My boot.img weighted around 4.5 MB in lzma compression mode. In gzip, it increased to more than 5 mb.
akhbh said:
No, I didn't faced those complications. My boot.img weighted around 4.5 MB in lzma compression mode. In gzip, it increased to more than 5 mb.
Click to expand...
Click to collapse
Perfect.
Which kernel have you based your build on?
streambinder said:
Perfect.
Which kernel have you based your build on?
Click to expand...
Click to collapse
Well, I took the GeTux kernel for cori, had to change the board name though and then compile it. CWM was booting even before changing the board name but there was no reaction from the phone on trying to boot cm9/cm11
And after changing board name, a black screen on trying to boot
Another info: When tried to merge cori source into the bcm21553 common one, it did compile but gave bootloop of GT-S5300 logo on trying to boot as well as when trying to go in CWM.
Bieltv.3 recommended to use cori source instead of the bcm21553 common one so we used cori sources
akhbh said:
Well, I took the GeTux kernel for cori, had to change the board name though and then compile it. CWM was booting even before changing the board name but there was no reaction from the phone on trying to boot cm9/cm11
And after changing board name, a black screen on trying to boot
Another info: When tried to merge cori source into the bcm21553 common one, it did compile but gave bootloop of GT-S5300 logo on trying to boot as well as when trying to go in CWM.
Bieltv.3 recommended to use cori source instead of the bcm21553 common one so we used cori sources
Click to expand...
Click to collapse
I suggest to use our Kernel sources for now, too: it will automatically bypass few errors/issues/bootloops that we cannot now fight with.
The most important thing is to make INIT working from sources (hope it will be working
on my CM9 sources, too) and check that every our configuration is correctly working and
making Cori boot into recovery.
Once we'll make it perfectly working without any kind of issue, will be the right time to try
to make Cori supported with the BC21553-common kernel.
streambinder said:
I suggest to use our Kernel sources for now, too: it will automatically bypass few errors/issues/bootloops that we cannot now fight with.
The most important thing is to make INIT working from sources (hope it will be working
on my CM9 sources, too) and check that every our configuration is correctly working and
making Cori boot into recovery.
Once we'll make it perfectly working without any kind of issue, will be the right time to try
to make Cori supported with the BC21553-common kernel.
Click to expand...
Click to collapse
Okay, I will use your kernel sources and try if something is changed once I reach home. For now, I neither have this device nor a PC, as I'm in another city.
Will be keenly watching your work. Will start after reaching home around the end of September
akhbh said:
Okay, I will use your kernel sources and try if something is changed once I reach home. For now, I neither have this device nor a PC, as I'm in another city.
Will be keenly watching your work. Will start after reaching home around the end of September
Click to expand...
Click to collapse
No problem, mate.
Here you have every source in my possession:
platform_kernel_samsung_cori
platform_device_samsung_cori
Keep in contact with me, as I will need some informations by you.
Anyway I'm now making another build, keeping some not so much important binaries excluded, so that I can make the compiled boot.img fill into our little Cori's boot partition. I know it's a dirty workaround, but if it works, I'll use it untill @psyke83 will suggest me a better way to do.
streambinder said:
No problem, mate.
Here you have every source in my possession:
platform_kernel_samsung_cori | github.com
platform_device_samsung_cori
Keep in contact with me, as I will need some informations by you.
Anyway I'm now making another build, keeping some not so much important binaries excluded, so that I can make the compiled boot.img fill into our little Cori's boot partition. I know it's a dirty workaround, but if it works, I'll use it untill @psyke83 will suggest me a better way to do.
Click to expand...
Click to collapse
have u tried to build cwm v6 from cm9 source ??
cleverior.ipul said:
have u tried to build cwm v6 from cm9 source ??
Click to expand...
Click to collapse
Of course, mate. I'm working on it, right now.
It doesn't seem to boot, strange if the same INIT binary sources are working for @akhbh.
#UPDATE
In order to troubleshoot, I'll give you some info.
For his build I used these sources:
platform_kernel_samsung_cori
platform_device_samsung_cori
android_device_samsung_bcm21553-common
Applied some lines on our bcm21553-bootimg.mk, too, in order to exclude parted and mke2fs and make the compiled boot.img weigh less.
@cleverior.ipul, can you link me your kernel sources, as akhbh said he used your ones for CM11.
@akhbh, which modifies have you applied in order to compile CWM based on CM11 code? Which device tree?
#UPDATE 2
Attached my compiled boot.img.
If anyone of you would extract it (you can easily use this tool: bootimgtools - read how to use it in the README) and make a diff with the CM11 one (just extract the ramdisk of both boot.imgs and - in the terminal - use this command: diff -urN /path/to/cm9/ramdisk /path/to/cm11/ramdisk > diff.patch), would make to me a huge favour.
Let me know.
streambinder said:
Of course, mate. I'm working on it, right now.
It doesn't seem to boot, strange if the same INIT binary sources are working for @akhbh.
#UPDATE
In order to troubleshoot, I'll give you some info.
For his build I used these sources:
platform_kernel_samsung_cori
platform_device_samsung_cori
android_device_samsung_bcm21553-common
Applied some lines on our bcm21553-bootimg.mk, too, in order to exclude parted and mke2fs and make the compiled boot.img weigh less.
@cleverior.ipul, can you link me your kernel sources, as akhbh said he used your ones for CM11.
@akhbh, which modifies have you applied in order to compile CWM based on CM11 code? Which device tree?
#UPDATE 2
Attached my compiled boot.img.
If anyone of you would extract it (you can easily use this tool: bootimgtools - read how to use it in the README) and make a diff with the CM11 one (just extract the ramdisk of both boot.imgs and - in the terminal - use this command: diff -urN /path/to/cm9/ramdisk /path/to/cm11/ramdisk > diff.patch), would make to me a huge favour.
Let me know.
Click to expand...
Click to collapse
I think we didn't had significant changes. Perhaps the same as totoro. But, that resulted in the internal_sd not mounting error in cwm.
Sadly, as said before, I am away from my home city and can't provide the files to you and can't do the boot.img diffs as well
Try to ask psyke83, he might have a solution for that
akhbh said:
I think we didn't had significant changes. Perhaps the same as totoro. But, that resulted in the internal_sd not mounting error in cwm.
Sadly, as said before, I am away from my home city and can't provide the files to you and can't do the boot.img diffs as well
Try to ask psyke83, he might have a solution for that
Click to expand...
Click to collapse
Then, if you didn't make any massive change upon the sources, then I'll only try using your kernel.
Can you give me your kernel sources, mate, please?
streambinder said:
Then, if you didn't make any massive change upon the sources, then I'll only try using your kernel.
Can you give me your kernel sources, mate, please?
Click to expand...
Click to collapse
Currently, I can provide you the boot.img only. For the sources, @cleverior.ipul can provide the kernel sources coz as said earlier, his kernel is used. Well, we were working together to bring cm11 but weren't successful
akhbh said:
Currently, I can provide you the boot.img only. For the sources, @cleverior.ipul can provide the kernel sources.
Click to expand...
Click to collapse
Ok, please send it to me, will compare it with my package.
streambinder said:
Ok, please send it to me, will compare it with my package.
Click to expand...
Click to collapse
Here it is:
http://www.4shared.com/zip/1nKFbOJ2ba/ccccGetux_CM11.html
streambinder said:
Of course, mate. I'm working on it, right now.
It doesn't seem to boot, strange if the same INIT binary sources are working for @akhbh.
#UPDATE
In order to troubleshoot, I'll give you some info.
For his build I used these sources:
platform_kernel_samsung_cori
platform_device_samsung_cori
android_device_samsung_bcm21553-common
Applied some lines on our bcm21553-bootimg.mk, too, in order to exclude parted and mke2fs and make the compiled boot.img weigh less.
@cleverior.ipul, can you link me your kernel sources, as akhbh said he used your ones for CM11.
@akhbh, which modifies have you applied in order to compile CWM based on CM11 code? Which device tree?
#UPDATE 2
Attached my compiled boot.img.
If anyone of you would extract it (you can easily use this tool: bootimgtools - read how to use it in the README) and make a diff with the CM11 one (just extract the ramdisk of both boot.imgs and - in the terminal - use this command: diff -urN /path/to/cm9/ramdisk /path/to/cm11/ramdisk > diff.patch), would make to me a huge favour.
Let me know.
Click to expand...
Click to collapse
here the link source https://github.com/cleverior/android_kernel_samsung_cori
i've changed the board name. If your device can not boot after using the zImage from this source, then rename init.bcm21553.rc to init.gt-s5300.rc.
@streambinder, what is grom? As bieltv.3 said that init built grom for cori is required to fix adb over cwm recovery. If adb gets working, then possibly the black screen while booting cm11 might get fixed
akhbh said:
@streambinder, what is grom? As bieltv.3 said that init built grom for cori is required to fix adb over cwm recovery. If adb gets working, then possibly the black screen while booting cm11 might get fixed
Click to expand...
Click to collapse
Sincerely don't what are you talking about.
Anyway, have to try to understand where's the problem with the not-booting CWM.
Will try with your sources and let you know.
Hi! I'm currently making a somewhat desperate attempt at porting cm12 to the d950. I know some basic things, I once tried to make a custom kernel. I have the device and vendor trees set up, with the cm12 source and the files from the flex source, and I've been making some changes. Can anyone help point me in some direction from here?
dongdong6968 said:
Hi! I'm currently making a somewhat desperate attempt at porting cm12 to the d950. I know some basic things, I once tried to make a custom kernel. I have the device and vendor trees set up, with the cm12 source and the files from the flex source, and I've been making some changes. Can anyone help point me in some direction from here?
Click to expand...
Click to collapse
Okay, so now I need to run extract-files.sh, only problem is it doesn't exist. and from my understanding, I have to already be running cm12 to do this, which obviously is not possible. Can anyone help me get the proprietary blobs?
You're better off looking at the g2 proprietary blobs as when I was trying I had the most success with them on CM11, its a good starting point
So should I take those, then make changes to suit the flex?
Yeah, its a good place to start, but it won't suddenly make it compile, it helped sort a couple of issues once we'd got it compiling in the first place....
Try msg playfulgod and see if he will point you in the right direction
Alright, I've got something that looks pretty good going, but I can't do anything without a working kernel. And as I don't know much about kernels, could Someone possibly try to make one for cm12? Also, I have the blobs from my boyfriend's g2, and I've made a lot of changes, but I might need a little more guidance. Any help is appreciated.
Do you have coding experience though thats the question.
Either Build a dummy kernel or modify the original kernel from cm11 roms that your device has and built it alongside the system images.
CyanogenMod doesnt allow Building of only the system.
Youll need to modify the following:
Kernel Source
Device Trees
Vendor Files
A good way to look at what is required for a cm12 bringup is to check other similar devices with the same architecture and compare the changes and the sources you have on your pc.
Regards
Sent from my Xperia SP using xda Forum
I took programming classes, and there were a few units on android.
So I just forked the blobs from playfulgods repo, and I've made a lot of changes to tbe devices folder, as well as 'POSSIBLY' do something good as for a kernel, but I doubt that will work. How does one build the kernel to test it? Using linux btw. I have all of the dependencies and everything, could someone explain breakfast/brunch/lunch?
HEY SO I THIN K I HAVE SOMETHING THAT MIGHT WORK AFTER HAVING SOME REALLY SMART PEOPLE HELP sorry for caps, but now I have something in the out folder for zee, what do i do with this, and how do i make it flashable? could someone do it for me? and also, kernels?
dongdong6968 said:
HEY SO I THIN K I HAVE SOMETHING THAT MIGHT WORK AFTER HAVING SOME REALLY SMART PEOPLE HELP sorry for caps, but now I have something in the out folder for zee, what do i do with this, and how do i make it flashable? could someone do it for me? and also, kernels?
Click to expand...
Click to collapse
I can write and add the meta-inf folders to make it flashable. But I don't do kernels
mattwheat said:
I can write and add the meta-inf folders to make it flashable. But I don't do kernels
Click to expand...
Click to collapse
I would really appreciate that! What means should I take of sending you the output?
dongdong6968 said:
I would really appreciate that! What means should I take of sending you the output?
Click to expand...
Click to collapse
I see 2 things with the Out Folder having problems.
1) What has the Build System Generate in the out folder?
2) CM12 will generate a pre configured Zip File if it doesn't, the build failed
Sent from my Huashan Device utilizing RR Milestone 1
Furrydaus said:
I see 2 things with the Out Folder having problems.
1) What has the Build System Generate in the out folder?
2) CM12 will generate a pre configured Zip File if it doesn't, the build failed
Sent from my Huashan Device utilizing RR Milestone 1
Click to expand...
Click to collapse
If anyone wants to take a look I zipped the out folder.
So you're going to tell us you zipped the folder but you're not going to tell us where it is? Lol
Sent from my Huashan Device utilizing RR Milestone 1
dongdong6968 said:
So I just forked the blobs from playfulgods repo, and I've made a lot of changes to tbe devices folder, as well as 'POSSIBLY' do something good as for a kernel, but I doubt that will work. How does one build the kernel to test it? Using linux btw. I have all of the dependencies and everything, could someone explain breakfast/brunch/lunch?
Click to expand...
Click to collapse
The device tree repos found in lg-devs github are the correct ones just change kernel source to our stock kernel and edit z.mk and verndor files can be extracted with the ./extract-fikes.sh script . But our kernel needs to be updated a little which i am working on mostly caf header need to be added to include/Linux for media and display. I trued using msm8974 kernel but our kernel has specific blobs we use which is easier to use stock kernel.
---------- Post added at 06:26 PM ---------- Previous post was at 06:16 PM ----------
dongdong6968 said:
HEY SO I THIN K I HAVE SOMETHING THAT MIGHT WORK AFTER HAVING SOME REALLY SMART PEOPLE HELP sorry for caps, but now I have something in the out folder for zee, what do i do with this, and how do i make it flashable? could someone do it for me? and also, kernels?
Click to expand...
Click to collapse
What you mean you got something lol. We just need to update our stock kernel which you can have a better understanding. Of what i mean visit lg-devs for z repos . we should stick to stock kernel doe.
dongdong6968 said:
I would really appreciate that! What means should I take of sending you the output?
Click to expand...
Click to collapse
Upload it to drive then message me with a link
mattwheat said:
Upload it to drive then message me with a link
Click to expand...
Click to collapse
https://www.dropbox.com/s/dx3sjp8bq720bkn/out.zip?dl=0
Furrydaus said:
So you're going to tell us you zipped the folder but you're not going to tell us where it is? Lol
Sent from my Huashan Device utilizing RR Milestone 1
Click to expand...
Click to collapse
Sorry, completely forgot. https://www.dropbox.com/s/dx3sjp8bq720bkn/out.zip?dl=0
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?