Hi everyone.
git repositories is the best modern way to work with Linux Kernel sources, designed by Linus himself in this purpose.
Today Samsung release sources as plain tarballs, often with a few missing files and it makes collaboration between developers difficult: instead of merging branches or patch in 2 commands, it creates a lot of headaches.
But also community fragmentation!
Sources are available now, source code will be shared here here as common reference point.
Also, benefit of this approach is free cleaned up upgrades when Samsung releases new sources for everyone.
Stay tuned, and contact me if you're an experienced developer that want to be involved in this source organization: https://github.com/GalaxySII
Galaxy S II Kernel sources
Galaxy S II Initramfs
Sample compile script template:
https://github.com/project-voodoo/scripts/blob/supercurio/galaxysii_build_kernel.sh
Sample flashing script:
https://github.com/project-voodoo/scripts/blob/supercurio/galaxysii_flash_kernel.sh
git remotes used:
origin git://github.com/GalaxySII/samsung-kernel-galaxysii.git (fetch)
origin [email protected]:GalaxySII/samsung-kernel-galaxysii.git (push)
android-common git://android.git.kernel.org/kernel/common.git (fetch)
android-common git://android.git.kernel.org/kernel/common.git (push)
linux-2.6-samsung http://git.kernel.org/pub/scm/linux/kernel/git/kki_ap/linux-2.6-samsung.git (fetch)
linux-2.6-samsung http://git.kernel.org/pub/scm/linux/kernel/git/kki_ap/linux-2.6-samsung.git (push)
longterm-linux-2.6.35.y git://git.kernel.org/pub/scm/linux/kernel/git/longterm/linux-2.6.35.y.git (fetch)
longterm-linux-2.6.35.y git://git.kernel.org/pub/scm/linux/kernel/git/longterm/linux-2.6.35.y.git (push)
stable-linux-2.6.35.y git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.35.y.git (fetch)
stable-linux-2.6.35.y git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.35.y.git (push)
So samsung will publish the source code on there or you will? Sorry I had trouble understanding - if samsung is that's great news!
good deal dude
jaju123 said:
So samsung will publish the source code on there or you will? Sorry I had trouble understanding - if samsung is that's great news!
Click to expand...
Click to collapse
Samsung will very probably release sources as a plain tarball.
But we are working to fully integrate the Galaxy S II sources they will release with Samsung mainline kernel repository on kernel.org.
http://git.kernel.org/?p=linux/kernel/git/kki_ap/linux-2.6-samsung.git;a=summary
In order to get the best quality source, easiest to upgrade etc.
Okay Galaxy SII sources are not available yet, but I messed with different source repo to make a clean starting point that will serve as base for the Samsung source drop.
Contains stuff from Linux 2.6 , Linux 2.6.35 stable (2.6.35.7) and linux-2.6-samsung.
Added initramfs !
https://github.com/GalaxySII/initramfs-galaxysii/tree/master/i9100-2.3.3-xwkdd
message to moderators: STOP RENAMING MY THREADS!
Especially with the most useless, unrelated and stupid name: "[KERNEL] coming soon..."
Thank you.
Sources are UP!
I somehow manually re-created commits from Samsung archive.
Before merging Samsung ED24 SHW-M250S sources, I created on a big merge branch named 2.6.35.7-samsung-android, containing
- 2.6.35
- Samsung mainline repository 2.6.35 (merged)
- 2.6.35.7 (merged)
- android 2.6.35.7 (merged)
Awesome!!! Wow! With developers like these we are sure in for a wonderful time ahead. Device got released in UK on May First and already we are seeing such development!! Thank you!
you actually took the time to split the commits by hand into categories
thats cool!
I just threw 5 euros your way for your work on Voodoo for the i9000, and also for the new work on the i9100. Seems fair since I used the kernel for the entire life of the i9000. My next step to pick up the i9100.
Merged manually M250K ED25 sources: https://github.com/GalaxySII/samsung-kernel-galaxysii/tree/shw-m250k-gingerbread
Merged manually M250L (WCDMA phone) ED27 sources: https://github.com/GalaxySII/samsung...0k-gingerbread
http://opensource.samsung.com/reception/reception_main.do?method=reception_search&searchValue=I9100
Galaxy S II source code
Rawat said:
http://opensource.samsung.com/reception/reception_main.do?method=reception_search&searchValue=I9100
Galaxy S II source code
Click to expand...
Click to collapse
Thanks! Just waking up.
Hold on with the tarball guys, you'll get it clean from the git repository very soon!
Galaxy S GT-I9000 source now all merged manually, with split categorized commit !
https://github.com/GalaxySII/
supercurio said:
Galaxy S GT-I9000 source now all merged manually, with split categorized commit !
https://github.com/GalaxySII/
Click to expand...
Click to collapse
Does this mean we have the whole thing? As in: full control of everything from hardware up to UI (drivers, kernel etc)? We "own" the hardware and can do as we please kind of thing?
OneTwoPi said:
Does this mean we have the whole thing? As in: full control of everything from hardware up to UI (drivers, kernel etc)? We "own" the hardware and can do as we please kind of thing?
Click to expand...
Click to collapse
Interested in knowing the same thing - how much control do "we" got over updates and sorts now? I heard this makes it really easy to update to the latest Linux kernel. Is that true?
OneTwoPi said:
Does this mean we have the whole thing? As in: full control of everything from hardware up to UI (drivers, kernel etc)? We "own" the hardware and can do as we please kind of thing?
Click to expand...
Click to collapse
kind of but not really. the consensus is that not everything is included in the source that samsung released. i'm just not clear on to what extent this is true.
i'm looking thru to try to find the audio files that could be easily edited to increase volume output, but i couldnt find it yet. maybe someone can shed some light.
RogerPodacter said:
kind of but not really. the consensus is that not everything is included in the source that samsung released. i'm just not clear on to what extent this is true.
i'm looking thru to try to find the audio files that could be easily edited to increase volume output, but i couldnt find it yet. maybe someone can shed some light.
Click to expand...
Click to collapse
There is no such consensus.
Galaxy S II kernel is 100% open source.
Some driver are partially Kernel partially user-space as usual, and we don't have source for those but speaking of the kernel we have everything. (already proven with custom kernels using arbitrary version numbers and no pre-compiled binary kernel module like mine)
Related
Hi!
I just want to vent my anger
Has anybody noticed that there are a minimum of four "parties" that work on an android kernel tree?
First there is the android open source project.
Then there is the CodeArora project.
There is also a kernel tree at Cyanogenmod.
And last but not least we have the "manufacturer" kernel tree.
AOSP has got a common tree and an individual tree for each architecture- just like Cyanogenmod.
CodeAurora has got multiple(!) trees for a single architecture.
The manufacturer seems to use some of CodeAurora's trees in the majority of cases.
Ah- I forgot the "original" linux kernel tree
This way we never get the most efficient and most stable kernel.
Just my two cents
you're right, but not only the kernel is used. LG takes code from codeaurora project - have seen this in code from the frameworks base tree^^
but on the other side: better they use community code as own code that didn't works perfect
WTF? LG really takes his sources from CodeAurora?!?!?
Well since code aurora is dedicated to qualcomm SoCs if i were a kernel developer i wud start with that tree..one question though does codeaurora contain gb kernel (.35) source for our msm7227 ??? u guys checked it out ???even if they theres a lot of other hardware that are going to need proprietary drivers i guess... THird world peripherals make porting tougher.. its just my take correct me if i m wrong
sarfaraz1989 said:
Well since code aurora is dedicated to qualcomm SoCs if i were a kernel developer i wud start with that tree..one question though does codeaurora contain gb kernel (.35) source for our msm7227 ??? u guys checked it out ???even if they theres a lot of other hardware that are going to need proprietary drivers i guess... THird world peripherals make porting tougher.. its just my take correct me if i m wrong
Click to expand...
Click to collapse
my kernel patches are taken from the codeaurora .35 source, but i can't adopt the complete kernel. there is a "must understand" and "must have many time" to do that
andy572 said:
my kernel patches are taken from the codeaurora .35 source, but i can't adopt the complete kernel. there is a "must understand" and "must have many time" to do that
Click to expand...
Click to collapse
That is exactly the problem!
I cannot really judge which patch from which tree is good- because I have not the time to read through Qualcomm's manuals (if they are public at all) and the kernel source.
If they would concentrate on one tree everything would be fine (ok- if you look at the "chaos commits" in the git repositories you become sick )
@caveman u working on a P500 kernel ??? how is porting so friggin easy for HTC devices..Do they have open source driver /generic hardware or what i mean a few of em even got a honeycomb partial port forget 2.3 ....
sarfaraz1989 said:
@caveman u working on a P500 kernel ??? how is porting so friggin easy for HTC devices..Do they have open source driver /generic hardware or what i mean a few of em even got a honeycomb partial port forget 2.3 ....
Click to expand...
Click to collapse
LG have some specific (old) hardware - they are using qualcomm hardware, but it's to old for newer kernel sources. the other problem is low cost hardware like the display - ms6000 is never used today, new devices are using samsung displays.
look at the wlan/smd chip - bcm4325 is never supported, bcm4329 is newer and is in kernel .38 too ... do you know, what i mean?
old hardware drivers are rare in kernels - never used drivers gets removed from tree, so there is no chance to bring it back.
ofcourse that's why it's called EVOLUTION
so it looks like u were right about getting a new phone
ciolnadu said:
ofcourse that's why it's called EVOLUTION
so it looks like u were right about getting a new phone
Click to expand...
Click to collapse
yes, it's marketing strategy and its ok - but why should i buy me a new device, when my is doing a good job?
andy572 said:
but why should i buy me a new device, when my is doing a good job?
Click to expand...
Click to collapse
+1 agreed 100% with andy.
andy572 said:
LG have some specific (old) hardware - they are using qualcomm hardware, but it's to old for newer kernel sources. the other problem is low cost hardware like the display - ms6000 is never used today, new devices are using samsung displays.
look at the wlan/smd chip - bcm4325 is never supported, bcm4329 is newer and is in kernel .38 too ... do you know, what i mean?
old hardware drivers are rare in kernels - never used drivers gets removed from tree, so there is no chance to bring it back.
Click to expand...
Click to collapse
Do you mean the drivers sources were in the old kernel and are removed in the new one? If so, I mean we have the old sources, why is it so difficult to port them to the new kernel sources? I am not a kernel developer so probably I am missing something
rivett said:
Do you mean the drivers sources were in the old kernel and are removed in the new one? If so, I mean we have the old sources, why is it so difficult to port them to the new kernel sources? I am not a kernel developer so probably I am missing something
Click to expand...
Click to collapse
code isn't moved but deleted.
Has anybody found out the CodeAurora git commit on which LG's V10r is based on?
I want to try and compile the oficial gb sources, mainly out of curiosity, but I would love having some clues on how to achieve it.
I'm a coder myself, but I don't know **** about android development. I guess I have to start by installing android sdk but then what? Any hints? A link to a begginer's guide or something would be great.
Sure I can find this info on google (starting the research right now) but maybe you guys can point me into the right direction.
Edit: I've found basic build instructions right inside the ZIP file containing the sources:
Code:
1. Android buid
- Download original android source code (gingerbread) from http://source.android.com
- Untar opensource packages of p500_gb_open_source.tar.gz into downloaded android source directory
- And, merge the source into the android source code(gingerbread)
- Run following scripts to build android
a) . build/envsetup.sh
b) make -j4
- When you compile the android source code, you have to add google original prebuilt source(toolchain)
into the android folder
( add prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin to PATH )
- After build, you can find output at out/target/product/generic
2. Kernel Build
- When you compile the kernel source code, you have to add google original prebuilt source(toolchain)
into the android folder.
( Add prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin to PATH
ex) export PATH=$PATH:$HOME/gb_original/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin )
- Untar using following command at the android folder
tar zxvf kernel.tar.gz
- cd Kernel
- make thunderg-perf_defconfig
- make zImage -j4
3. After Build, You Can find the build image at arch/arm/boot
4. Compile environment
- gcc 4.4.1
- Ubuntu 10.10
- Java 1.6.0_22
I'll continue researching and will post any finds and my progress here if there's anyone interested. Meanwhile you can contribute with anything you can and by the end we may have a good tutorial out of it.
Look at first post from Andy's Gingerbread, he describes what you need.
No need to install Android SDK.
I take sources from codeaurora, merge with LG-source.
drakull said:
I want to try and compile the oficial gb sources, mainly out of curiosity, but I would love having some clues on how to achieve it.
I'm a coder myself, but I don't know **** about android development. I guess I have to start by installing android sdk but then what? Any hints? A link to a begginer's guide or something would be great.
Sure I can find this info on google (starting the research right now) but maybe you guys can point me into the right direction.
Edit: I've found basic build instructions right inside the ZIP file containing the sources:
Code:
1. Android buid
- Download original android source code (gingerbread) from http://source.android.com
- Untar opensource packages of p500_gb_open_source.tar.gz into downloaded android source directory
- And, merge the source into the android source code(gingerbread)
- Run following scripts to build android
a) . build/envsetup.sh
b) make -j4
- When you compile the android source code, you have to add google original prebuilt source(toolchain)
into the android folder
( add prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin to PATH )
- After build, you can find output at out/target/product/generic
2. Kernel Build
- When you compile the kernel source code, you have to add google original prebuilt source(toolchain)
into the android folder.
( Add prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin to PATH
ex) export PATH=$PATH:$HOME/gb_original/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin )
- Untar using following command at the android folder
tar zxvf kernel.tar.gz
- cd Kernel
- make thunderg-perf_defconfig
- make zImage -j4
3. After Build, You Can find the build image at arch/arm/boot
4. Compile environment
- gcc 4.4.1
- Ubuntu 10.10
- Java 1.6.0_22
I'll continue researching and will post any finds and my progress here if there's anyone interested. Meanwhile you can contribute with anything you can and by the end we may have a good tutorial out of it.
Click to expand...
Click to collapse
Forget about this. LG did not released Android soures. There are kernel only.
Damn... are you sure, Mik?
Have you looked inside the zip? There's 2 tarballs, one for the Kernel and other reading 'p500_gb_open_source.tar.gz'. I tought it was the p500 gb android source files that needs to be merged with the main source code.
Well... that's a real shame.
drakull said:
Damn... are you sure, Mik?
Have you looked inside the zip? There's 2 tarballs, one for the Kernel and other reading 'p500_gb_open_source.tar.gz'. I tought it was the p500 gb android source files that needs to be merged with the main source code.
Well... that's a real shame.
Click to expand...
Click to collapse
it is on GB, and it was on FROYO - LG didnt release the complete source code,
only some modifications to the android sources - because not all parts of android
are GPLv1, they doesnt MUST release sources for this parts these arent of GPLv2 or GPLv3 in some cases ...
andy572 said:
it is on GB, and it was on FROYO - LG didnt release the complete source code,
only some modifications to the android sources - because not all parts of android
are GPLv1, they doesnt MUST release sources for this parts these arent of GPLv2 or GPLv3 in some cases ...
Click to expand...
Click to collapse
AFAIK Even with froyo LG didn't publish the WHOLE source,only pieces of it (AFAIK).
I'm still downloading sources from codeaurora, as soon as it's finished I'll merge the changes and we'll see what happens
_Arjen_ said:
I'm still downloading sources from codeaurora, as soon as it's finished I'll merge the changes and we'll see what happens
Click to expand...
Click to collapse
I can't even download sources,my internet connection freezes everytime I download something (only if speed goes above 350KB/s),so no Eclair build for meh . Gonna kill Telecom Italia soon
Viva l'Italia
_Arjen_ said:
Viva l'Italia
Click to expand...
Click to collapse
Ahaha lol I do love my country but internet services suck
_Arjen_ said:
I'm still downloading sources from codeaurora, as soon as it's finished I'll merge the changes and we'll see what happens
Click to expand...
Click to collapse
sounds like "i download as fast as i can the sources, do a "make gingerbread"
in the command line and release a build to megaupload.com...
i can say, there is a very small knowledge of how to build a android system from source - you need a lot of hours to get the system compiled so that most stuff
is working^^
andy572 said:
sounds like "i download as fast as i can the sources, do a "make gingerbread"
in the command line and release a build to megaupload.com...
i can say, there is a very small knowledge of how to build a android system from source - you need a lot of hours to get the system compiled so that most stuff
is working^^
Click to expand...
Click to collapse
I know that Andy
I'm not stupid
But you need to download sources and merge LG sourcecode before you can start anyway
So far the simple . build/envsetup.sh, lunch and make seem to work fine with 2.3.4 source, after compiling is complete we'll see if I got a working rom.
If al works fine I can start to modify and build again, so I've got hours and hours of mostly waiting
_Arjen_ said:
I know that Andy
I'm not stupid
But you need to download sources and merge LG sourcecode before you can start anyway
So far the simple . build/envsetup.sh, lunch and make seem to work fine with 2.3.4 source, after compiling is complete we'll see if I got a working rom.
If al works fine I can start to modify and build again, so I've got hours and hours of mostly waiting
Click to expand...
Click to collapse
Lol, look to my sources and compare it to lg's. Theren are nothing usefull except kernel.
After compiling you'll get default android that probably can start in emulator
mik_os said:
Lol, look to my sources and compare it to lg's. Theren are nothing usefull except kernel.
After compiling you'll get default android that probably can start in emulator
Click to expand...
Click to collapse
I love your sources because they gave me some really useful infos
mik_os said:
Lol, look to my sources and compare it to lg's. Theren are nothing usefull except kernel.
After compiling you'll get default android that probably can start in emulator
Click to expand...
Click to collapse
Nope, it runs on the phone,
did similar thing to build eclair (needed to change some things before I could build) and got it booting to our phone with froyo kernel, only a little hacking needed to get all working. Only gsm and bluetooth are not yet fully working on eclair, other things seem fine so far.
but will take a look at your sources, because you could be right there are better ways
Edit:
GB building is ready and working fine after flashing (using new baseband)
Just tried this because it was fun. Now I'm going back to get eclair fully working
The only GB-build I want to use is CM7, no-one needs just another GB while we have three good ones: Miks CM7, Andy's GB/CM7 and Noejns void #forever and with Franco's kernel these builds rock
Sorry Ciaox, forgot your coming GB-rom
Hello,
So far, I have:
A working Android build environment (Ubuntu 11.10 x64).
Managed to build, install and boot AOSP on my Nexus S. (I have downloaded but not attempted to build CM7 yet.)
Created a Github account.
Samsung's open source files for my target device, the Galaxy Gio GT-S5660M.
I've read some documentation and forum posts about Github, but I remain unsure as to what I should do to fork in a way that:
I'll be able to keep on syncing the remainder of the code.
My new device directories and modifications could be brought back (pulled?) to the main CM7 code base.
Will avoid needless frustrating re-downloads of the source code.
Thanks in advance,
Darkshado
After some further reading, I'm beginning to grasp some git basics...
I've forked two CM7 repos so far, added them as remotes in the appropriate installations. (Instead of forking and cloning, since I already had repo sync'ed the whole CM7 source. My commits show up on Github like they should, and I should be able to merge in commits to the origin remotes.)
I'm not going to do any pull requests until I've managed to build and boot.
By the way, yesterday I attempted to build AOSP with a bunch of files overwritten by the Samsung sources (that's how they tell you to do it!!) and this failed, as I expected.
Goodbye,
Darkshado
Update: I'm currently trying to port CM7 to the Gio 5660M. Still attempting a first successful build as I'm writing these lines.
My main issue so far has to do with the camera. I get the following error message:
make: *** No rule to make target « out/target/product/gio5660M/obj/lib/libcamera.so », needed by « out/target/product/gio5660M/obj/SHARED_LIBRARIES/libcameraservice_intermediates/LINKED/libcameraservice.so ». Stop.
After toggling off the camera by using the stub, I hit the same error further into the build with this:
make: *** No rule to make target « vendor/samsung/gio5660M/proprietary/wifi/ath6k/AR6003/hw2.0/athtcmd_ram.bin », needed by « out/target/product/gio5660M/system/wifi/ath6k/AR6003/hw2.0/athtcmd_ram.bin ». Stop.
I know this has to do with makefiles, but that's about it...
Thanks in advance for any help,
Darkshado
hi i'm interested too.
hi I found your github because I also interested poriting cyanogemod to galaxy gio korea(SHW-M290K). the device hardware is different from s5660. so I need some modification.
and your libcamera problem is that there is some reason that the make system can't find libcamera.so, so they cannot compile libcamera service. it should be in ./vendor/samsung/gio/proprietary according to your extract-files.sh .
have one cuorisity. I searched gio android device make file. and none of them are relreased source code. how did you make them?
I found this information. it may help you.
http://processors.wiki.ti.com/index.php/TI-Android-GingerBread-2.3.4-DevKit-2.1_PortingGuides
I'll have to update my Github, hadn't been in a rush due to lack of progress, but now my problem lies with libaudio instead.
I got the Samsung sources for the 5660M on their open source website, although I mostly worked with the CM7 ports for similar devices like Tass and Cooper as well as a Gio source provided by Phiexz but it didn't build either.
Thanks for the link, I'll check it out.
proprietary does not help
do you have any progress since last time?
well, I admit that proprietary files does not help.
does your s5660m hardware identical to s5660v?
becasuse galaxy gio in Korea(shw-m290k,shw-m290s) does different hardware.
well in this case, like me, you need to hack into not only android pdk, but also android kenel.
I have seen that phiexz has released kernel with latest cyanogenmod kenel in his github and I am modifing it to shw-m290k. there are some hardware differences i have to apply to.
I suggest you to compare phiexz's kernel and samsung original kernel from samsung opensource homepage.
My problem right now is that I don't have that much spare time to put into this, and that I'm very much learning as I go, so progress is not always that quick. Also, I'd like to get my Touchwiz based ROM updated and working properly before trying to build AOSP or CM again.
Another thing I want to try is building the kernel (probably based on Phiexz's) that will support ext4, and compare performance of the Touchwiz ROM on ext4 versus RFS.
As far as we can tell, GT-S5660 (Europe/Asia) GT-S5660M, L and V are identical except for the radio firmware. People with the 5660M initially encountered issues after flashing 5660 ROMs because they also contained the AMSS image.
my cyanogen kernel is based on samsung open source kernel
because cm-kernel on cyanogenmod github dont support our device, if we wnt use that kernel we must add some hardware pofile & board for galaxy gio
so alternative is make samsung's open source kernel compatible with cyanogenmod
Wouldn't it be much better from a code maintainability standpoint to make the CM kernel work on the Gio? (Also if you ever hope to get official CM team support, that's a given.)
The way I understand repo and git, you could create a github repo for your device and board configs and add those to your repo manifest so the whole CM7 source and your modifications all sync properly.
I've forked the CM7 manifest files off github, added my gio files and removed all those extra devices I didn't need, so my repo syncs are much faster too. (The idea comes from http://slightlymorethanworthless.blogspot.com/2011/05/remove-unwanted-devices-from.html)
hey a quick question...
just starting out here..
i'm on win7 32 bit, going to run ubuntu on virtualbox.
shud i choose ubuntu 32 bit or 64?
sorry for OT.
doesn't really matter
roofrider said:
hey a quick question...
just starting out here..
i'm on win7 32 bit, going to run ubuntu on virtualbox.
shud u choose ubuntu 32 bit or 64?
sorry for OT.
Click to expand...
Click to collapse
doesn't really matter. but compiling process needs much cpu power. so 64x would be better.
Well, im not a dev or a user of gt5660m, but good luck to you, hope u can finally port it
Sent from the GUN in my pants
darkshado, if you have same problem untill now.
http://strazzere.com/blog/?p=220
look this page. and check out koush's proprietary page. especially for samsung cooper(galaxy ace). because many of kernel procedure are same for gio.
https://github.com/coolya/android_device_samsung_cooper.git
https://github.com/koush/proprietary_vendor_samsung
i've upload galaxy gio source + proprietary files for galaxy gio
please see & help to fix some problem
github.com/phiexz
Darkshado said:
Hello,
So far, I have:
A working Android build environment (Ubuntu 11.10 x64).
Managed to build, install and boot AOSP on my Nexus S. (I have downloaded but not attempted to build CM7 yet.)
Created a Github account.
Samsung's open source files for my target device, the Galaxy Gio GT-S5660M.
I've read some documentation and forum posts about Github, but I remain unsure as to what I should do to fork in a way that:
I'll be able to keep on syncing the remainder of the code.
My new device directories and modifications could be brought back (pulled?) to the main CM7 code base.
Will avoid needless frustrating re-downloads of the source code.
Thanks in advance,
Darkshado
Click to expand...
Click to collapse
Really the best kernel for your phone is here:
http://forum.xda-developers.com/showthread.php?t=1991020
BLN enabled, optimized&stable kernel, jelly bean look
Whoa! Zombie thread!
Dude: the ROM you linked was published over a year after my original post in this thread. I'm pretty sure there was NO CM7 build available for the Gio back then. That's what I was trying to work on, but got beat to the punch by Maclaw and a couple others. (Hard-bricking my Gio and having a sluggish laptop to build on didn't help.)
Besides, I got rid of my Gio a long time ago. I enjoy my Note 2 and keep my Nexus S as backup.
Hi all,
i'm a noob to android, but i have nit of experience on other unix based systems.
I was wondering, why there is no custom roms for GT-S5690?
What's the problem?
Is bootloader locked some other way or is it somehow different from example Gio/GT-S5660?
There is a bunch of roms for gio..
I have one xcover, wich has no screen and covers, i thought i could use it for testing.
I think there are too less people who have a xcover, and I was actually pretty disappointed when I say there is a successor to the xcover available only in the US (Rugby Smart / Pro <-- with ICS!).
From the technical side, I don't know. Even the source code of the firmware is available at opensource.samsung.com. The Bootloader seems pretty much unlocked.
For me, the xcover is the best phone ever, it takes so much abuse. Maybe someday someone will port a newer ROM from the Ace/Gio/idk. It's a shame Samsung abandons their old phones :crying:
xkawer said:
I think there are too less people who have a xcover, and I was actually pretty disappointed when I say there is a successor to the xcover available only in the US (Rugby Smart / Pro <-- with ICS!).
From the technical side, I don't know. Even the source code of the firmware is available at opensource.samsung.com. The Bootloader seems pretty much unlocked.
For me, the xcover is the best phone ever, it takes so much abuse. Maybe someday someone will port a newer ROM from the Ace/Gio/idk. It's a shame Samsung abandons their old phones :crying:
Click to expand...
Click to collapse
I didn't were aware of successor models, now i'm very dissappointed.
I'm downloading these source codes at the moment, i'll check these out.
I'm not a developer, atleast YET..
AFAIK, hardware of s5690 is way different from any other samsung phones,
correct me if i'm wrong..
jonezy82 said:
AFAIK, hardware of s5690 is way different from any other samsung phones,
correct me if i'm wrong..
Click to expand...
Click to collapse
Seems like it's the only one with a Marvell MG2.
Let me know if you do anything interesting with the sources
Just flashed my xcover to XXLJ2 yesterday. At least it seems a bit faster now, but I have a weird bug when scrolling. If I give a list (for example settings) momentum, it doesn't stop when I put my finger on it again. But it does stop if I release the finger the second time.
jonezy82 said:
I'm downloading these source codes at the moment, i'll check these out.
Click to expand...
Click to collapse
Did the same. The GT-S5690_Platform.txt says:
Code:
How to build platform
1. Get android open source.
: version info - Android gingerbread 2.3.6
( Download site : http://source.android.com )
2. Remove external\webkit module in android open source which you got.
And then execute "clean build"
2. Copy files and modules to original Gingerbread source tree (overwrite)
3. build
- ./build.sh user
So wouldn't it be possible to download the JB sources, and compile them with the original kernel? Would be so cool.
Edit: It seems you need device specific binaries (drivers) since ICS. see: http://www.freeyourandroid.com/guide/compile-ics
Found a git https://github.com/manakeri/android_device_samsung_xcover, there is a
Code:
cyanogen_xcover.mk
file, this seems interesting. Apparently someone is trying to port it.
Edit2: In this git, there is also a "extract-files.sh"-file, which is neccessary to pull the proprietary files from the phone! With this I think we actually have everything we need to compile ICS/JB, like in the "freeyourandroid" tutorial.
I have never done this before, but someone must try it lol.
Oh look, there are more people who care about it!
http://www.droidevelopers.com/f338/14412-gt-s5690-opensource-kernel-available.html
Someone discovered my link and made a overclock kernel from the sources! This is so cool.
I hope we are going to see more :good:
xkawer said:
Oh look, there are more people who care about it!
http://www.droidevelopers.com/f338/14412-gt-s5690-opensource-kernel-available.html
Someone discovered my link and made a overclock kernel from the sources! This is so cool.
I hope we are going to see more :good:[/QUOTE
I own an xcover too a developer on another forum looked at some files i pulled using adb to try to port clockworkmod but no success. Told me the files i sent weren't standard android img but he would continue to look into it. Apparently the teamhacksungs goal is to port cyanogenmod for every Samsung device surely they can get it done. I've been waiting a long time to see some development for the awesome xcover
Click to expand...
Click to collapse
If its possible on the galaxy mini its got to be possible on xcover!. Ive tried to get involved and learn to port cyanogenmod but when it comes to git, repo, source tree, source code e.t.c e.t.c its a bit behond me for now.
Step in the right direction it seems. Fingers crossed
I have a LG P350 which development has stopped but i want to keep it updated, i have my computer ready for building, also i have kernel sources, Cyanogenmod 11 and 10.1 sources too, (I don't know exactly if 10.1 sources could help) and i know that i need to apply patches to work on Armv6 but i don't know how to apply them to the source code, also i don't know if i would just need the pure source code to build or i need to do more modifications to it and finally, i don't know if the rom would work with 2.36 kernel which it's the most stable one for this device, i'm very new in this but i know that i can keep update my little phone, thank you all in advance for help.
DiegoConD said:
I have a LG P350 which development has stopped but i want to keep it updated, i have my computer ready for building, also i have kernel sources, Cyanogenmod 11 and 10.1 sources too, (I don't know exactly if 10.1 sources could help) and i know that i need to apply patches to work on Armv6 but i don't know how to apply them to the source code, also i don't know if i would just need the pure source code to build or i need to do more modifications to it and finally, i don't know if the rom would work with 2.36 kernel which it's the most stable one for this device, i'm very new in this but i know that i can keep update my little phone, thank you all in advance for help.
Click to expand...
Click to collapse
Hello, looking at your situation here is what I can conclude. First off you will need to change things for building on ARMv6 architecture, check this out for example. But your biggest problem will be that Android 4.0+ uses Linux kernel version 3.0+, and with the 2.36 kernel you have a lot of things will be broken and need fixing. That being said if your up for the challenge for it cause that's what were all about .
shimp208 said:
Hello, looking at your situation here is what I can conclude. First off you will need to change things for building on ARMv6 architecture, check this out for example. But your biggest problem will be that Android 4.0+ uses Linux kernel version 3.0+, and with the 2.36 kernel you have a lot of things will be broken and need fixing. That being said if your up for the challenge for it cause that's what were all about .
Click to expand...
Click to collapse
Well, i got this http://forum.xda-developers.com/showthread.php?t=2144790 that is the most similar phone talking about hardware, it has 3.0 kernel working well so i thought i could port it, i found this http://stackoverflow.com/questions/15961306/porting-kernel-from-another-device so i think i would have less problems due hardware similarities (Look here http://www.gsmarena.com/compare.php3?idPhone1=3516&idPhone2=3735 ) so, if i have cm11 pure sources, i add this kernel sources and some patches i would have it booting? Sorry for this very dumb question but, i didn't get at all about the armv6 part, how to apply patches, which i would need and all that, i really want to learn about this so thank you for this answer and the next ones :good:
DiegoConD said:
Well, i got this http://forum.xda-developers.com/showthread.php?t=2144790 that is the most similar phone talking about hardware, it has 3.0 kernel working well so i thought i could port it, i found this http://stackoverflow.com/questions/15961306/porting-kernel-from-another-device so i think i would have less problems due hardware similarities (Look here http://www.gsmarena.com/compare.php3?idPhone1=3516&idPhone2=3735 ) so, if i have cm11 pure sources, i add this kernel sources and some patches i would have it booting? Sorry for this very dumb question but, i didn't get at all about the armv6 part, how to apply patches, which i would need and all that, i really want to learn about this so thank you for this answer and the next ones :good:
Click to expand...
Click to collapse
The best way to start is use the ARMv6 branch of Cyanogenmod 11, replace the CM 10.1 in the previous linked build guide with cm-11.0 ("repo init -u git://github.com/androidarmv6/android.git -b cm-11.0"), and then to direct the build to use your kernel take a look at this guide on integrated kernel building with Cyanogenmod.