It's easy, it's free. And here's how you do it!
You will need to create two simple JavaScript files:
A file that describes your ROMs that you send to me.
A file that you host that lists your ROMs, so you can update your ROM Manager section.
First, your developer/ROM description file:
Code:
{
// This is what name you want your ROMs to show up under.
developer: "CyanogenMod",
// Your id. This should have no spaces or other funny characters.
// This would ideally be your Github id, so when you send me your manifest
// I can verify who you are. But it can be anything really.
id: "cyanogen",
// The display summary. Two lines max.
summary: "Mods and bacon for Dream, Sapphire, Droid, and Nexus One",
// The location of the developer's manifest.
manifest: "http://gh-pages.clockworkmod.com/ROMManagerManifest/cyanogenmod.js",
// The list of devices that this developer's ROMs support.
// If you don't support a device, just don't list it!
roms:
{
vibrant: true,
sholes: true
}
}
Send me that file! [email protected]
Link to developer sample: http://gh-pages.clockworkmod.com/ROMManagerManifest/samples/developer.js
And now, create your ROM list file:
Code:
{
// The version of the manifest, so ROM Manager knows how to load it
version: 1,
// The homepage for your ROM, if you have one.
homepage: "http://www.cyanogenmod.com/",
// The donate link for yuor ROM, if you have one.
donate: "https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=3283920",
// Your list of ROMs
roms:
[
{
// Display name of the rom
name: "CyanogenMod 5.0.5",
// Display summary of the rom
summary: "Stable",
// Device that this rom runs on
device: "sholes",
// This is the download URL of your ROM.
// These URLs should have unique filenames per version!
// Ie, don't use a zip with the same name
// as that of a previous version with a new version.
// Otherwise ROM Manager will continue using the
// old cached zip on the SD card.
// This must be a direct download,
// and not a Mediafire type link.
url: "http://www.droidaftermarket.com/koush/motorola/sholes/cyanogen_sholes-ota-eng.koush_5.0.5.zip"
},
// Antother, older ROM!
{
name: "CyanogenMod 5.0.4",
summary: "Stable",
device: "vibrant",
url: "http://www.droidaftermarket.com/koush/motorola/sholes/cyanogen_sholes-ota-eng.koush_5.0.4.zip"
}
]
}
Link to manifest sample: http://gh-pages.clockworkmod.com/ROMManagerManifest/samples/simplemanifest.js
And you're done!
If you're a pro dev, you can even create a ROM customizer. But I won't get into that here
Follow this link for more information: http://www.koushikdutta.com/2010/03/rom-manager-and-third-party-roms.html
Excellent thanks Koush!!
very nice, I love koush lol
Nice
Sent from my SGS Vibrant using tapatalk
Damn Kouch, you seem to be making all this pretty easy for everyone. I'm new to all this rooting stuff, and I've gotta say you've got me really excited about all this. I paid for your Clockwork app to show my support for your hard work, and time you've put into this. Can't wait to see what ROMs hit the Vibrant within the next few weeks!
Thanks!
This is the web address www .lg. com/global/support/opensource/opensource-detail.jsp
www .lg.c om/global/support/opensource/opensource.jsp
Ahjohnwon said:
This is the web address www .lg. com/global/support/opensource/opensource-detail.jsp
www .lg.c om/global/support/opensource/opensource.jsp
Click to expand...
Click to collapse
can you edit the proper adress ??
nyanyanyanyanyanyanyanyanyanyanyan
Ahjohnwon said:
This is the web address www .lg. com/global/support/opensource/opensource-detail.jsp
www .lg.c om/global/support/opensource/opensource.jsp
Click to expand...
Click to collapse
I don't get it.
Ahjohnwon said:
This is the web address www .lg. com/global/support/opensource/opensource-detail.jsp
www .lg.c om/global/support/opensource/opensource.jsp
Click to expand...
Click to collapse
That's nothing new....
"Welcome to the LG Electronics Open Source Distribution system.
LG Electronics, Inc. ("LGE") is pleased to make available source code relating to certain open source software on this website.
The copyright in the source code is owned by LGE and/or other third parties.
The source code is made available subject to the conditions of the licence terms specifically referred to in LGE's Open Source Software Notices.
The open source software and source code are provided to you on an "AS IS" basis and LGE, its affiliates and subsidiaries disclaim any and all warranties and representations with respect to such software and related source code, whether express, implied, statutory or otherwise, including without limitation, any implied warranties of title, non-infringement, merchantability, satisfactory quality, accuracy or fitness for a particular purpose.
LGE shall not be liable to make any corrections to the open source software or source code or to provide any support or assistance with respect to it.
LGE disclaims any and all liability arising out of or in connection with the use of this software and/or source code.
This statement does not impair or enhance any warranty or disclaimer which LGE provides in respect of any LGE product which incorporate our relevant open source software.
This site opened in August 2010. For information regarding products released prior to this date, please refer to the relevant product manuals."
If its good or if will help us , I don't know...
One downlodable "LGP880(X3)_Android_ICS_V10a.zip" have a "readme.txt" file that says:
"How to build
1. Android build
(1) Get the android base source code.
- Download the original android source code (Android 4.0.3 IceCreamSandwitch)(P880) from http://source.android.com
(2) Overwrite modules that you want to build.
- Untar opensource packages of LGP880_ICS_Platform.tar.gz into downloaded android source directory
- And, merge the source into the android source code.
(3) Merge the below code into android source file(bionic\libdl\Android.mk) at the last line.
##################################################################
# -begin
include $(CLEAR_VARS)
#LOCAL_LDFLAGS := -Wl,--exclude-libs=libgcc.a
LOCAL_SRC_FILES:= libdl.c
LOCAL_CFLAGS := -DLIBC_STATIC
LOCAL_MODULE:= libdl
ifeq ($(TARGET_ARCH),sh)
# for SuperH, additional code is necessary to handle .ctors section.
GEN_SOBEGIN := $(TARGET_OUT_STATIC_LIBRARIES)/sobegin.o
$(GEN_SOBEGIN): $(LOCAL_PATH)/arch-sh/sobegin.S
@mkdir -p $(dir [email protected])
$(TARGET_CC) -o [email protected] -c $<
GEN_SOEND := $(TARGET_OUT_STATIC_LIBRARIES)/soend.o
$(GEN_SOEND): $(LOCAL_PATH)/arch-sh/soend.S
@mkdir -p $(dir [email protected])
$(TARGET_CC) -o [email protected] -c $<
LOCAL_ADDITIONAL_DEPENDENCIES := $(GEN_SOBEGIN) $(GEN_SOEND)
endif
include $(BUILD_STATIC_LIBRARY)
# -end
#################################################################
(4) In other to compile the path (external\wfd_rtsp\librtsp) you have to separate and use NDK 6.0.
Please create the Android.mk file in the path (wfd_rtsp\librtsp\project\jni)
#####################################
LOCAL_PATH := $(call my-dir)
include $(CLEAR_VARS)
RTSP_SRC_PATH := $(LOCAL_PATH)/src
RTSP_INC_PATH := $(LOCAL_PATH)/include
LOCAL_SRC_FILES := \
$(subst $(LOCAL_PATH)/,,$(wildcard $(RTSP_SRC_PATH)/usageenvironment/*.c*)) \
$(subst $(LOCAL_PATH)/,,$(wildcard $(RTSP_SRC_PATH)/basicusageenvironment/*.c*)) \
$(subst $(LOCAL_PATH)/,,$(wildcard $(RTSP_SRC_PATH)/groupsock/*.c*)) \
$(subst $(LOCAL_PATH)/,,$(wildcard $(RTSP_SRC_PATH)/livemedia/*.c*))
LOCAL_C_INCLUDES := \
$(RTSP_INC_PATH)/usageenvironment \
$(RTSP_INC_PATH)/basicusageenvironment \
$(RTSP_INC_PATH)/groupsock \
$(RTSP_INC_PATH)/livemedia
LOCAL_CFLAGS := -DNULL=0 -DSOCKLEN_T=socklen_t -DNO_SSTREAM -DDEBUG
LOCAL_CPPFLAGS := -DBSD=1 -fexceptions
LOCAL_LDLIBS := -lm -llog -lz
LOCAL_MODULE := live_rtsp
include $(BUILD_SHARED_LIBRARY)
#############################################
(5) Run the build scripts.
- You have to add google original prebuilt source(toolchain) before running build scripts.
- Run the following scripts to build android
a) . build/envsetup.sh
b) make -j4
into the android folder
- If the android is built sucessfully, you will find the outputs in this directory,
"out/target/product/generic".
2. Kernel Build
- Untar using following command at the android folder:
tar xvfj LGP880_Kernel.tar.gz
- change directory to kernel root
cd kernel
- make kernel zImage:
make ARCH=arm CROSS_COMPILE=(absolute path of Android 4.0.3 IceCreamSandwitch)/prebuilt/linux-x86/toolcahin/arm-eabi-4.4.3/bin/arm-eabi- x3_defconfig zImage"
And contains two more files... "LGP880_Kernel.tar.gz" and "LGP880_ICS_Platform.tar.gz"
I found strange that they have two options, P880 (LGP880(X3)_Android_ICS_V10a) and P880G (LGP880G(X3)_Android_ICS_V10c).
What that means??? Cause to be the different firmware version, they should have more once that exists the V10d/e/f...
Didn't understood... thanks if someone can explain it :good:
Well V10E/F were just minimal updates to fix bug issues and such. The original firmwares are the V10A/C.
And this is old news already guys. There is already a thread about Open Source.
Hey all, what's up?
I got a problem, and I'm going crazy xD
I've successfully done a repo sync of AOSPA Legacy and successfully downloaded:
-Device Tree: https://github.com/CyanogenMod/android_device_lge_w7
-Kernel: https://github.com/CyanogenMod/android_kernel_lge_msm8226
-Vendor: https://github.com/Quarx2k/proprietary_vendor_lge
Now I'm following this guide: http://forum.xda-developers.com/showthread.php?t=1863547
In a step it tells me to extract "proprietary-files.sh" from my device folder.
Our "proprietary-files.sh" is called "setup-makefiles.sh"?
This is the first question.
The second question is that I must follow this tip.
"# Create /manifest/<device>.adds:
I'll give you two examples of .adds, to show the general extent of variation between devices:
For i9300:
Code:
Code:
[
{
"remote": "github",
"account": "CyanogenMod",
"repository": "android_frameworks_av",
"target_path": "frameworks/av",
"revision": "cm-10.1"
},
{
"remote": "github",
"account": "CyanogenMod",
"repository": "android_frameworks_native",
"target_path": "frameworks/native",
"revision": "cm-10.1"
Where I can find this kind of repos? D: I tried Googling but with no luck.
3rd question: Where I can find also this kind of things? >_<
"# Create /manifest/<device>.removes:
For i9300:
Code:
Code:
{
"name": "platform/frameworks/av",
"path": "frameworks/av"
},
{
"name": "ParanoidAndroid/android_frameworks_native",
"path": "frameworks/native"
},
{
"name": "platform/hardware/libhardware",
"path": "hardware/libhardware"
},
{
"name": "platform/hardware/libhardware_legacy",
"path": "hardware/libhardware_legacy"
},
{
"name": "device/common",
"path": "device/common"
},
{
"name": "ParanoidAndroid/android_frameworks_opt_telephony",
"path": "frameworks/opt/telephony"
}
]
Help me out
Last question: When I try to build..After 5 min the terminal gives me this.
Code:
"No private recovery resources for TARGET_DEVICE w7
make: *** Nessuna regola per generare l'obiettivo "external/chromium_org/v8/tools/gyp/generate_trig_table.host.linux-arm.mk". Arresto."
And also before this errors, there are other errors like:
Code:
"external/chromium_org/v8/tools/gyp/generate_trig_table.host.linux-arm.mk: File o directory non esistente
find: "phone/java": File o directory non esistente
find: "phone/java": File o directory non esistente
find: "dummy": File o directory non esistente"
If anyone can help me, please answer!
Thank you!!
You don't need to run that command, the proprietary_vendor_lge folder that you added to the manifest is what houses all of those files. Also, you will need to do quite a bit of file editing to get a cm device tree to build properly on AOSP. With that being said, there are much better/easier guides out there to set up your build environment. I'll find a couple and post them here for you to check out
CaptivateKing said:
You don't need to run that command, the proprietary_vendor_lge folder that you added to the manifest is what houses all of those files. Also, you will need to do quite a bit of file editing to get a cm device tree to build properly on AOSP. With that being said, there are much better/easier guides out there to set up your build environment. I'll find a couple and post them here for you to check out
Click to expand...
Click to collapse
I don't want to build a AOSP. I wanna build an AOSPA/Paranoid
Anyways thank you for your answer.
SlimShady's said:
I don't want to build a AOSP. I wanna build an AOSPA/Paranoid
Anyways thank you for your answer.
Click to expand...
Click to collapse
I meant to type AOSPA, but the same goes for building anything that isn't cm, or cm based. You will have to edit a few make files for it to compile correctly with a cm device tree
CaptivateKing said:
I meant to type AOSPA, but the same goes for building anything that isn't cm, or cm based. You will have to edit a few make files for it to compile correctly with a cm device tree
Click to expand...
Click to collapse
And how can I do it?
ANYKERNEL
espressowifi / espresso3g
Please respect the following 2 points
No feature requests!
Overclocked Kernel can be found here
NOTE:
This product is provided "as is" without any warranty. Use on your own risk.
I am not responsible for burned CPU or GPU.
Any kind of OC is really dangerous on Galaxy Tab2. While OMAP 4460 has a built-in temperature sensor, OMAP 4430 doesn't have one. Nothing stops it from overheating...
If you don't read and respect the OP, you accept to make a donation of 50$ to a charity of your choice!
[#WARRANTY]
It is difficult to update all Roms frequently, and it does not always makes sense to compile, download and flash a whole rom, if only some kernel changes are applied.
This kernel will include changes before i add them official to our kernel source (most of the time security bugfixes)!
Android 5.1 and Android 6.0
This Kernel works on all Android 5.1 and Android 6.0 Roms for espressowifi and espresso3g.
Android 4.4
On Android 4.4 we need a different kernel, 4.4 Kernel includes "KitKat" tag on zip name.
What else to say
Kernel compiled using GCC 4.8
Anykernel based on Anykernel2 by @osm0sis ( https://github.com/osm0sis/AnyKernel2 ) - it will dump your boot.img and replace the zImage and add proper kernel modules.
Roms with default libion
LineageOS (unofficial)
espresso3g
lineage-11-20180131-2053-UNOFFICIAL-espresso3g.zip and newer
lineage-13.0_espresso3g-6.0.1-20180130-2211.zip and newer
lineage-14.1_espresso3g-7.1.2-20180131-1859.zip and newer
espressowifi
lineage-11-20180131-2033-UNOFFICIAL-espressowifi.zip and newer
lineage-13.0_espressowifi-6.0.1-20180130-2146.zip and newer
lineage-14.1_espressowifi-7.1.2-20180131-1818.zip and newer
OmniRom (unofficial)
espresso3g
omni_espresso3g-4.4.4-20180127-2337.zip and newer
omni_espresso3g-6.0.1-20180128-0312.zip and newer
omni_espresso3g-7.1.2-20180128-1319.zip and newer
espressowifi
omni_espressowifi-4.4.4-20180127-2310.zip and newer
omni_espressowifi-6.0.1-20180128-0251.zip and newer
omni_espressowifi-7.1.2-20180128-1254.zip and newer
SlimRoms (unofficial)
espresso3g
Slim-espresso3g-4.4.4.build.9.15-UNOFFICIAL-20180128-0125.zip and newer
Slim_espresso3g-6.0.1-20180128-2332.zip and newer
Slim_espresso3g-7.1.2-20180131-1617.zip and newer
espressowifi
Slim-espressowifi-4.4.4.build.9.15-UNOFFICIAL-20180128-0028.zip and newer
Slim_espressowifi-6.0.1-20180128-2308.zip and newer
Slim_espressowifi-7.1.2-20180131-1555.zip and newer
Unlegacy-Android:
All official Unlegacy-Android builds starting on 15th feburary use the default libion
Roms with new DDK
Slim6 , Slim7, OmniROM4, OmniROM 6, OmniROM 7 and LineageOS 11, LineageOS 13 and LineageOS 14.1 compiled after 01.03.2019
[#DONATETOME]
XDA:DevDB Information
(unified) Anykernel, Kernel for the Samsung Galaxy Tab 2
Contributors
Android-Andi, Ziyan
Source Code: https://github.com/Unlegacy-Android/android_kernel_ti_omap4/commits/3.0/common
Kernel Special Features: Testing before applying on our source official, CVE fixes
Version Information
Status: Testing
Created 2016-10-21
Last Updated 2020-05-02
Reserved
As requested, here's my setup to compile espresso kernel.
01.05.2020
Follow https://github.com/andi34/android_build-bot/blob/manifest/README.md and https://github.com/andi34/android_build-bot/blob/kernelcompile/README.md
What do you need
Kernel Source (you can get our latest kernel source on SlimRoms, OmniRoms or CyanogenMods github, "espresso10 kernel")
GCC ( https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8 )
pvr source, added to omap4-common device repo and hardware_ti_omap4 repo (can be found on SlimRoms, OmniRoms or CyanogenMods github)
you can use my scripts put below (update some paths, marked red )
AnyKernel2 Source from osm0sis (see 1. post, update for your tab2 needed)
build-gcc4.8.env:
Code:
[COLOR="Red"]export CROSS_COMPILE='/android/kernelcompile/arm-eabi-4.8/bin/arm-eabi-'[/COLOR]
export LDFLAGS=''
export CFLAGS=''
export SUBARCH=arm
export ARCH=arm
[COLOR="Red"]export STRIP=/android/kernelcompile/arm-eabi-4.8/bin/arm-eabi-strip[/COLOR]
alias 'stm'='$STRIP --strip-unneeded *.ko'
compile-espresso.sh
Code:
#!/bin/bash
readonly red=$(tput setaf 1) # red
readonly grn=$(tput setaf 2) # green
readonly ylw=$(tput setaf 3) # yellow
readonly blu=$(tput setaf 4) # blue
readonly cya=$(tput setaf 6) # cyan
readonly txtbld=$(tput bold) # Bold
readonly bldred=$txtbld$red # red
readonly bldgrn=$txtbld$grn # green
readonly bldylw=$txtbld$ylw # yellow
readonly bldblu=$txtbld$blu # blue
readonly bldcya=$txtbld$cya # cyan
readonly txtrst=$(tput sgr0) # Reset
err() {
echo "$txtrst${red}$*$txtrst" >&2
}
warn() {
echo "$txtrst${ylw}$*$txtrst" >&2
}
info() {
echo "$txtrst${grn}$*$txtrst"
}
setbuildjobs() {
# Set build jobs
JOBS=$(expr 0 + $(grep -c ^processor /proc/cpuinfo))
info "Set build jobs to $JOBS"
}
info "Kernel source path: $KERNELSOURCE"
info "PVR Source path: $PVRSAUCE"
info "Working directory: $WORKINGDIR"
info "resulting zImage and modules stored at: $WORKINGOUTDIR"
setbuildjobs
info "Moving to kernel source"
cd $KERNELSOURCE
info "Import toolchain environment setup"
info "Toolchain: $TOOLCHAIN"
source $SAUCE/build-$TOOLCHAIN.env
info "Create a buid directory, known as KERNEL_OUT directory"
# then always use "O=$SAUCE/espresso" in kernel compilation
info "create working directory"
mkdir -p $WORKINGDIR
warn "Make sure the kernel source clean on first compilation"
make O=$WORKINGDIR mrproper
warn "Rebuild the kernel after a change, maybe we want to reset the compilation counter"
echo 0 > $WORKINGDIR/.version
if [ "$VARIANTDEFCONFIG" = "*p*" ]; then
info "Import kernel config file: $DEFCONFIGNAME"
info "Import variant config file: $VARIANTDEFCONFIGNAME"
make O=$WORKINGDIR VARIANT_DEFCONFIG=$VARIANTDEFCONFIG $DEFCONFIGNAME
info "Change kernel configuration if needed using:"
info " make O=$WORKINGDIR menuconfig "
VARIANTDEFCONFIG=
else
info "Import kernel config file: $DEFCONFIGNAME"
make O=$WORKINGDIR $DEFCONFIGNAME
info "Change kernel configuration if needed using:"
info " make O=$WORKINGDIR menuconfig "
fi
info "lets build the kernel"
make -j$JOBS O=$WORKINGDIR
if [ -f $WORKINGDIR/arch/arm/boot/zImage ]; then
info "Copying the resulting zImage and modules to: $WORKINGOUTDIR"
info "Creating directory..."
mkdir -p $WORKINGOUTDIR
mkdir -p $WORKINGOUTDIR/modules/system/lib/modules
cp $WORKINGDIR/arch/arm/boot/zImage $WORKINGOUTDIR/
find $WORKINGDIR/ -type f -name *.ko -exec cp {} $WORKINGOUTDIR/modules/system/lib/modules/ \;
info "Files moved!"
info "Pointing KERNELDIR to KERNEL_OUT directory"
export KERNELDIR=$WORKINGDIR
warn "Make sure the PVR source clean."
warn "Running 'make clean'..."
make clean -C $PVRSAUCE/build/linux2/omap4430_android
info "Building the PVR module..."
# we now use the default libion, our kernel was updated
make -j8 -C $PVRSAUCE/build/linux2/omap4430_android TARGET_PRODUCT="blaze_tablet" BOARD_USE_TI_LIBION=false BUILD=release TARGET_SGX=540 PLATFORM_VERSION=4.1
info "Copying the resulting PVR module to: $WORKINGOUTDIR"
cp -fr $PVRSAUCE/binary2_omap4430_android_release/target/pvrsrvkm.ko $WORKINGOUTDIR/modules/system/lib/modules/pvrsrvkm_sgx540_120.ko
mv $PVRSAUCE/binary2_omap4430_android_release/target/pvrsrvkm.ko $WORKINGOUTDIR/modules/system/lib/modules/
warn "Don't leave any module objects in PVR source!"
warn "Running 'make clean'..."
make clean -C $PVRSAUCE/build/linux2/omap4430_android
info "Properly stripping the kernel modules for smaller size (implified as stm command inside build.env)..."
cd $WORKINGOUTDIR/modules/system/lib/modules
stm
info "####################"
info "# Done! #"
info "####################"
else
warn "####################"
warn "# FAILED! #"
warn "####################"
fi
cd $SAUCE
espresso-m.sh
Code:
#!/bin/bash
[COLOR="Red"]SAUCE=~/android2/kernelcompile
PVRSAUCE=~/android2/official/omap4/stable/pvr-source/eurasiacon
KERNELSOURCE=~/android2/official/kernel/android_kernel_ti_omap4[/COLOR]
TOOLCHAIN="gcc4.8"
DEFCONFIGNAME=espresso_defconfig
WORKINGDIR=$SAUCE/out/$DEFCONFIGNAME
WORKINGOUTDIR=$SAUCE/$DEFCONFIGNAME-bin
. `dirname $0`/compile-espresso.sh
espresso-k.sh
Code:
#!/bin/bash
[COLOR="Red"]SAUCE=~/android2/kernelcompile
PVRSAUCE=~/android2/official/omap4/stable/pvr-source/eurasiacon
KERNELSOURCE=~/android2/official/kernel/android_kernel_ti_omap4[/COLOR]
TOOLCHAIN="gcc4.8"
DEFCONFIGNAME=espresso_kitkat_defconfig
WORKINGDIR=$SAUCE/espresso-kitkat
WORKINGOUTDIR=$WORKINGDIR-bin
. `dirname $0`/compile-espresso.sh
Reserved
DEVICE SPECIFIC ANYKERNEL
Edit 02.05.2020
Latest device specific AnyKernel-Zip can be found here:
https://forum.xda-developers.com/showpost.php?p=79259009&postcount=204
Please note: our kernel detects your Tab2 variant at boot and chooses the right driver and config for your device! In some cases (e.g. if the mainboard or the screen got replaced) your device variant isn't detected right and it will use wrong driver!
I am not sure how many user are affected, but in such case we can skip the intelligent board detection and hardcode the variant.
Attached device specific kernel should work on all unified espresso/espressowifi & espresso3g roms from Android 5 up to Android 7, for Android 4 Roms please use the "kitkat" version.
Feel free to buy me a coconut water if it helped you to keep your Tab still, after many years, almost up to date.
UPDATE AnyKernel-2016-10-21
- Update the ext-csd.rev check for eMMC5.1 (fixes emmc detection for some tab2)
- CVE-2016-5195
- CVE-2016-6828
- CVE-2016-7042
thanks andi.
working nice on my own builded aosp-6.0 10/16
Some more CVE fixes applied on top of previous kernel:
CVE-2014-8173
CVE-2014-7970
CVE-2014-5206
CVE-2016-0819
CVE-2015-8830
CVE-2014-9715
I added a CVE overview on 2nd post.
Edit:
Added a KitKat version
Hi Android-Andi.
Has this kernel the OPTION (or plan to enable) to overclock ?
Thanks.
galoneta said:
Hi Android-Andi.
Has this kernel the OPTION (or plan to enable) to overclock ?
Thanks.
Click to expand...
Click to collapse
No as mentioned in first post! Move out of this thread if you are not able to read first post.
~ All my work, news etc. on http://andi34.github.io ~
Guys, if you don't read the OP the thread will be closed and you can take care about a security patched kernel yourself.
Source is available on github, add everything you miss by your own and stop spamming this thread!
Edit: everyone not accepting the forum rules will be reported!
Edit2: Thanks @ Moderator for the post remove / thread clean
~ All my work, news etc. on http://andi34.github.io ~
SORRY!
I know its off topic but you should read this
http://www.xda-developers.com/9-yea...-dirty-cow-can-root-every-version-of-android/
Emo Darkemotion said:
SORRY!
I know its off topic but you should read this
http://www.xda-developers.com/9-yea...-dirty-cow-can-root-every-version-of-android/
Click to expand...
Click to collapse
OP states that its already patched
Android-Andi said:
"CVE-2016-5195" https://github.com/Unlegacy-Android/...b19311a9089b77
Click to expand...
Click to collapse
Emo Darkemotion said:
SORRY!
I know its off topic but you should read this
http://www.xda-developers.com/9-yea...-dirty-cow-can-root-every-version-of-android/
Click to expand...
Click to collapse
It is quite funny making noise about a bug which existed 9 years now.
1. It is fixed on my kernel as mentioned on 2nd post (wonder why i spend time doing it)
2. I don't see an issue on custom roms (can be fixed within 2 minutes), i would worry about android by your Manufacturer (on all devices).
On android we change the wheel: no central updates like on linux or windows - it is up to your manufacturer to update your device and there's a lot of security issues fixed by google on android every month (and sure, some kernel side too). How many stock updates you get? 1, maybe 2 within 1 year and support drops after that.
To be true: i am not sure if my next device is an android device:
On my g4 i am on stock rom and LG cares 0 about it (Security patch level 2016-07-01... I waited 6 or 7 month to get that update and it was already 1 month behind).
If manufacturer don't care about theire flagships, what else can we do? Flashing custom roms? Right works, but on my daylie driver i don't like to be a flashahollic... I am more thinking about using a different OS.
You should think about my words and don't care about a already fixed security issue
~ All my work, news etc. on http://andi34.github.io ~
Hi Andy,
First of all, many thanks for all your work! I´m using your ROMs and kernels since Slimkat and all are great!
I also do my best colaborating with the translating team of CyanogenMod and SlimRoms (Brazilian Portuguese).
But now I would like to compile a kernel bymyself, to patch the CVEs, changes I like, etc.
If you have time, can you post here the steps you do to compile the Anykernel?
Don´t need to waste time explaining the things, just post the step-by-step commands (git clone, makes, ADBs, etc) and I will do my research, ok?
Thanks in advance and greetings from Brazil!
AranhaEscarlate said:
Hi Andy,
First of all, many thanks for all your work! I´m using your ROMs and kernels since Slimkat and all are great!
I also do my best colaborating with the translating team of CyanogenMod and SlimRoms (Brazilian Portuguese).
But now I would like to compile a kernel bymyself, to patch the CVEs, changes I like, etc.
If you have time, can you post here the steps you do to compile the Anykernel?
Don´t need to waste time explaining the things, just post the step-by-step commands (git clone, makes, ADBs, etc) and I will do my research, ok?
Thanks in advance and greetings from Brazil!
Click to expand...
Click to collapse
Sure, i have nothing to hide i can upload my script next days. Busy on other stuff atm maybe send a small reminder if the script isn't added on 3rd post of this thread end of next week.
~ All my work, news etc. on http://andi34.github.io ~
Android-Andi said:
Sure, i have nothing to hide i can upload my script next days. Busy on other stuff atm maybe send a small reminder if the script isn't added on 3rd post of this thread end of next week.
~ All my work, news etc. on http://andi34.github.io ~
Click to expand...
Click to collapse
Oh and @Android-Andi just a small request , change the color of the text for ""CVE-XXXXXYYYY" DOES NOT AFFECT" because This colour is hard to read on the screen .
AranhaEscarlate said:
(...)
If you have time, can you post here the steps you do to compile the Anykernel?
Don´t need to waste time explaining the things, just post the step-by-step commands (git clone, makes, ADBs, etc) and I will do my research, ok?
(...)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=69241933&postcount=3
Must be enough, everything else you need to read / find out yourself
iamashwin said:
Oh and @Android-Andi just a small request , change the color of the text for ""CVE-XXXXXYYYY" DOES NOT AFFECT" because This colour is hard to read on the screen .
Click to expand...
Click to collapse
Done, should be better now.
Android-Andi said:
http://forum.xda-developers.com/showpost.php?p=69241933&postcount=3
Must be enough, everything else you need to read / find out yourself
Click to expand...
Click to collapse
Thank you very much, Andy!!!
It´s more than enough!
Everything else, I will read documentation at the Internet, but this is a great starting point for me.
What kind ANY KERNEL is important when you can not clocked CPU and graphics
Kutuzov666 said:
What kind ANY KERNEL is important when you can not clocked CPU and graphics
Click to expand...
Click to collapse
Dont use it if you dont want it!
It is for the kind of people who want a secure kernel ... more secure than the one given by samsung (I dont remember the last time they sent us a patched kernel update ...or did they !)
Nearly all the device I own are waaaay too insecure (be it my router (its also a linux system) , phone Landline TV ...) except for my 4 year old tab all thanks to Andi ! Respect it
Besides OP is doing all this as a hobby and not for your or my benefit.
Stop spaming this thread ! Please READ
Please respect the following 2 points
No feature requests!
Overclocking will never be added here!
If you don't read and respect the OP, you accept to make a donation of 50$ to a charity of your choice!
Click to expand...
Click to collapse
PSS If you are satisfied with the answer please delete the message and so will I .Lets keep this thread clean.