[SOURCE] Gingerbread sources released by Samsung
https://opensource.samsung.com/reception/reception_main.do?method=reception_search&searchValue=9100
good news !!!
keijames said:
[SOURCE] Gingerbread sources released by Samsung
https://opensource.samsung.com/reception/reception_main.do?method=reception_search&searchValue=9100
Click to expand...
Click to collapse
Does it for 2.3.4?
wanam said:
Does it for 2.3.4?
Click to expand...
Click to collapse
Mobile Phone GT-I9100_CHN_CHN I9100ZCKG4 GT-I9100_CHN_CHN.zip
zckg4 is 2.3.4 offical rom in CHINA~maybe this is 2.3.4 sources
~
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hopefully this is the 2.3.4 sources so devs can finally start adding real tweaks!
sorry guys but this is not 2.3.4
Open up the Platform file, then read the README file. It should say 2.3.4_r1 instead of 2.3.3_r1.
readme file
Code:
How to build platform
1. Get android open source.
: version info - Android gingerbread 2.3.3(r1)
( Download site : http://source.android.com )
2. Overwrite modules that you want to build.
- \external\webkit : Delete this source tree at Android gingerbread and then copy & execute "clean build".
3. Copy the files to original Gingerbread source tree (overwrite) and then make
4. Add the following lines at the end of build/target/board/generic/BoardConfig.mk
BOARD_USES_ALSA_AUDIO := true
BOARD_HAVE_BLUETOOTH := true
BOARD_HAVE_BLUETOOTH_BCM := true
BT_ALT_STACK := true
BRCM_BT_USE_BTL_IF := true
BRCM_BTL_INCLUDE_A2DP := true
BOARD_USES_ALSA_AUDIO := true
5. make -j16 PRODUCT-generic-user
Does this works for gbread 2.3.5?
Sent from my GT-I9100 using XDA App
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sources: MiniCM
I accept patches via github, pm, or any way available.
Nightlies have NO support whatsoever. Use them at your own risk -- For a stable MiniCM9 check: here
Requirements:
Latest 2.1.1.C.0.0 SE firmware / Baseband: M76XX-TSNCJOLYM-53404015
Unlocked bootloader
Latest version of the ICS nAa kernel
Download:
MiniCM9 nightlies (robyn)
gapps
Useful links:
http://wiki.cyanogenmod.com/wiki/Barebones clean your rom to make space
CHANGELOG What's new in this version :
http://changelog.bbqdroid.org/#/cm9/undefined
http://review.cyanogenmod.com/#/q/status:merged+branch:ics,n,z
If you'd like to donate, click:
Disclaimer:
We can't be held responsible if this ROM bricks your device or makes it explode in your hands! Use it at your own risk!
Preface
Building android from source is not as hard as it sounds. I urge all enthusiasts to try to build their personal ROM on their own. Why copy a prebuilt binary when android gives you the chance to build it from sources?
Step1: Setup a build machine
Setup a real or VM machine using the info from here.
Step2: Checkout the code
Code:
repo init -u git://github.com/MiniCM/android.git -b ics
repo sync -j16
Step3: Build MiniCM
Code:
. build/envsetup.sh
lunch cm_robyn-eng
brunch cm_robyn-eng
Step4: Ready to flash!
Pickup the build from out/target/product/robyn/MiniCM9-xxx.zip
Step5: Contribute!
You got an idea on how to improve this rom? Try to implement it by looking at the code and seeing how similar things are already done.
Android is based on open-source spirit: You got it working? Share the patches for everyone to enjoy!
So Nightly means that the latest repo sync was today?
Sent from my E10i using xda app-developers app
Such foremost reason for this post is to ask for help and would like to compile my own kernel from my xperia M2 D2306 but I find a little inconvenience is only to find a file identification from my xperia I explain what this is.
This is the tutorial I'm following:
[ULTIMATE GUIDE] [Noob Friendly] Compile your own kernel from source android
As well I follow this tutorial sony:
How to rebuild kernels for flagship Xperia devices [tutorial]
And drop tools that tell me there is a problem but tell me this:
Code:
Replace Device Name with the configuration file found at:
Source / arch / arm / configs
It's written in This Way something_DeviceCodename_user_defconfig
and I went to the specified path but can not find any file of this type
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
information from the filename of the Xperia M2:
Code:
Xperia M2
aosp_yukon_eagle_defconfig
How could set the name of my device before entering the kernel configuration script
would be helpful thanks
You are barking at the wrong tree.
The reason there is no defconfig for M2 (yukon) is that they have not uploaded the defconfig in their Github repo.
From this site it is clear that
http://xperiafirmware.com/8-firmware/53-sony-xperia-m2-d2303/
M2's firmware is 18.x.x.x
If you check the branches on Github ,there is no branch with 18.x.x.x
Moral
That source won't work.
Instead use kernel source from the Open source center.
http://developer.sonymobile.com/downloads/opensource/
This one should work fine for all the M2 devices .
http://developer.sonymobile.com/dow...-18-3-1-a-1-7-18-3-1-b-1-8-and-18-3-1-c-1-13/
Lenovo K900 custom kernelAndroid 4.3 (linux 3.4.43)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
>>> Please welcome - world`s first custom kernel for Lenovo K900 <<<
Disclaimer:
custom kernel based on Lenovo`s Open Source Code. Kernel is fully working. Adding new features.
How to flash:
unlock bootloader, flash any custom recovery, flash the the attached files.
Source code:
https://github.com/lenovo-k900/android_kernel_lenovo_redhookbay
Changelog:
build 001 : first release;
build 002 : added NTFS support, WI-FI Direct.
Download:
build 001 :: https://drive.google.com/file/d/0Bz3X7ZuowQimc2cxc1FYb2l4eXM/view?usp=sharing
build 002 :: https://drive.google.com/file/d/0Bz3X7ZuowQimSG5Oc0tNeEl4Nnc/view?usp=sharing
Credits:
pavluha2004
AirShark
XXX-Man
Nice work, works a treat!
How easy is it to build? I've been desperately wanting a kernel with kvm virtualization builtin (CONFIG_KVM, CONFIG_KVM_INTEL, CONFIG_VHOST_NET, CONFIG_VIRTIO_NET, CONFIG_KVM_DEVICE_ASSIGNMENT etc not as modules but builtin) - I don't suppose you've got time to do a rebuild?
rwt33 said:
Nice work, works a treat!
How easy is it to build? I've been desperately wanting a kernel with kvm virtualization builtin (CONFIG_KVM, CONFIG_KVM_INTEL, CONFIG_VHOST_NET, CONFIG_VIRTIO_NET, CONFIG_KVM_DEVICE_ASSIGNMENT etc not as modules but builtin) - I don't suppose you've got time to do a rebuild?
Click to expand...
Click to collapse
U can rebuild it by yourself, it`s pretty easy. Sources are full, go ahead.
is this work for 4.2.1?
Hello guys i am trying to build new lineageos for our l9 devices but i always get error, when i use lunch it terminates with this error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm new to ROM development can anyone guide me to compile this ROM successfully.
Or can anyone suggest me a good Guide for ROM development.
Thanks in advance : )
Image don't load
http://www.lineageosrom.com/2017/01/how-to-build-lineageos-rom-for-any.html
Use this guide and try again
I hope you succede
:good:
Thank you i will try to build it soon when i get time.
optimus l9 said:
Thank you i will try to build it soon when i get time.
Click to expand...
Click to collapse
Keep us informed! It's something new to L9, new and interesting)
Yeah! Really keep us informed about it!!! It would be very nice to have it for LG L9 =) It is always a good phone!
Thanksss anyway!!!
You can't just build lineage os for optimus l9 without modifying anything, mainly because our device p760 isn't officially supported by lineageos . CM official support for p760 ended with cm-10.2 . Hence the official CM p760 device repository doesn't contain the branch cm-14.1 . So the brunch command complains about it.
What you have to do is,
-fork the p760 device repo containing the branch same as the cm / lineage version you are trying to build.
-If there is no such repo, you have to create a p760 device repo with the branch same as the CM version
-Modify the device configuration files properly to work with the CM version.
-Add this device repo to your local manifest.
-repo sync
-build.
is this still ongoing? im crying
I don't know if it has been posted before or if anyone is aware, but apparently the kernel source for the Lenovo Yoga Book (X5-Z8550) is available here: https://pcsupport.lenovo.com/dk/en/products/TABLETS/YOGA-SERIES/YOGA-BOOK/downloads/DS118515
If the site loads the Windows drivers site, simple under 'Operating Systems' select 'Android' and the kernel source code .zip is available for download (Open Source Code - Lenovo YB1-X90F/L).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Palm Trees said:
I don't know if it has been posted before or if anyone is aware, but apparently the kernel source for the Lenovo Yoga Book (X5-Z8550) is available here: https://pcsupport.lenovo.com/dk/en/products/TABLETS/YOGA-SERIES/YOGA-BOOK/downloads/DS118515
If the site loads the Windows drivers site, simple under 'Operating Systems' select 'Android' and the kernel source code .zip is available for download (Open Source Code - Lenovo YB1-X90F/L).
Click to expand...
Click to collapse
Thanks for the heads up. It'll be interesting to see if any devs on here can make use of this.
It's there since 05 Sep 2016... what a deep dive discovery...
And pretty sure Marshmallow...
jamespmi said:
It's there since 05 Sep 2016... what a deep dive discovery...
And pretty sure Marshmallow...
Click to expand...
Click to collapse
Like your energy....
Already contacted Lenovo to ask if they're going to release the kernel source for Android N.....
Sorry about that....
Have a nice day....
The link has been updated to show sources from march 2018