Hi, I'm working on my build environment in order to cook ROMs for our beloved P990 myself. However, there are some questions I couldn't answer yet. Maybe our developers can help me...
manifest repo
So I've found 2 manifest repos, but none of them has a cm-11.0 branch, yet:
https://github.com/djnoxd-p990/android
https://github.com/p990-dev/android.git
TonyP has a device specific repo (no manifest repo) for cm-11.0, but no matching manifest repo. So... @DJNoXD/tonyp/hjunii: please upload your latest manifest repo.
linaro toolchain
TonyP wrote that he was using the default gcc toolchain (gcc 4.6 and gcc 4.7 for cm-10.1 and cm-10.2). Has anyone tried the linaro toolchain, yet? From what I found out so far gcc completely disables the fpu by building code that uses the cpu for floating point operations, which results in a performance decrease of 5%-40% in average. Linaro is not doing such things, so I'm hoping for a big performance increase when using it...
kernel 3.10
There's a new kernel release from nVidia for our tegra device: kernel 3.10 (https://android.googlesource.com/kernel/tegra/). Anyone tried that one, yet?
Like this?
https://github.com/tonyp/android_vendor_cm/tree/cm-11.0-tonyp
https://github.com/p990-slimrom/android_device_lge_p990/tree/kk4.4_new
Good luck
As far as I know - no. These are "normal" repositories. But in order to build a complete ROM I need the "manifest repo", which is some kind of enveloping repository. It is tiny (look at https://github.com/CyanogenMod/android for example), but contains a file called default.xml, which references all "normal" repositories that are needed.
I hope I got that right. Please tell me if I write total bull****.
https://github.com/p990-slimrom/platform_manifest/tree/kk4.4
But I think you don't need it. I'm building CyanogenMod for O4x with unofficial sources with local manifest added to CyanogenMod sources
My manifest (you have to change repos):
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/lge/p880" name="P880-dev/android_device_lge_p880" groups="device" />
<project path="kernel/lge/x3" name="P880-dev/android_kernel_lge_x3" />
<project path="vendor/lge" name="P880-dev/proprietary_vendor_lge" />
</manifest>
EDIT: the kernel, which you're pointing is not for tegra 2 (Nvidia ended support) and porting that to newer tegras is so much difficult, so developers usually don't do it.
Yay, that's what I was looking for!
Alright, so now let's start building a ROM.
Good Luck!
Gesendet von meinem SM-T210R mit Tapatalk
thorstenhirsch said:
As far as I know - no. These are "normal" repositories. But in order to build a complete ROM I need the "manifest repo", which is some kind of enveloping repository. It is tiny (look at https://github.com/CyanogenMod/android for example), but contains a file called default.xml, which references all "normal" repositories that are needed.
I hope I got that right. Please tell me if I write total bull****.
Click to expand...
Click to collapse
I have included the device specific stuff into the default repo, This make the work easier for me.
Related
Hi Folks
I thought I throw this one up for good measure.
Archos Kernel 3.0.21
I've made a couple of changes which are outline in the README2 file in the repo, but a quick summary.
Patched arch/arm/mach-omap4/omap4-reboot-reason.c to enable bootmode system property setting from the kernel command line which is required by CWM-SDE
I also back-ported the arch/arm/mm/proc-v7.S from the android-omap-3.4 kernel which means the kernel can be built using the standard android aosp toolchains Although It's probably still better to use Linaro Optimized!!
github.com/trevd/android_kernel_ti_archos.git
README2
Code:
android linux kernel 3.0.21 based on original archos sources found at
http://gitorious.org/archos/archos-gpl-gen9-kernel-ics branch: linux-ics-3.0.21
Android boot mode awareness:
----------------------------
changes made to arch/arm/mach-omap2/omap4-reboot-reason.c to enable correct setting
of android system property ro.bootmode.
designed to be used in conjunction with roms created using device files locating in
https://github.com/trevd/android_device_ti_archos.git
Proc-v7.S changes
-----------------
I've backported arch/arm/mm/Proc-v7.S from the android-omap-3 kernel 3.4 branch, this
was done to allow the kernel to be built using the standard android toolchain.
Building
--------
Clone the android aosp toolchain
git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6
Using the Bourne Again Shell ( bash ) export an alias to make cross compiling easy
alias make-arm='<toolchain path>/arm-eabi-4.6/bin/:$PATH ARCH=arm SUBARCH=arm CROSS_COMPILE=arm-eabi- LOCALVERSION_AUTO=n make'
make-arm distclean && make-arm mrproper
make-arm ti_archos_defconfig
make-arm -j$(grep -c processor /proc/cpuinfo)
Out of tree drivers
-------------------
PowerVR Kernel Modules are not included in this release, they are available from omapzoom android aosp
repo located at git://git.omapzoom.org/device/ti/proprietary-open.git. this repo also contains the matching
userland binary blobs, versions of which exist for Gingerbread, ICS and JellyBean. See device tree documentation
for further details ( https://github.com/trevd/android_device_ti_archos.git )
Hi Trevd !
Thank you very much for your great work ! :good:
....how much I wish I could be useful ( I am currently with hands tied :laugh: - I have not my tablet ....but I'll be back as soon as I will receive my tablet from reparation centre ! )
Good luck & keep up your awesome work ! :good::good::good:
Wifi Drivers info and resources.
Hi Folks.
Along with building the PowerVR Drivers out of tree, It should be also possible to use the latest drivers for the wireless chip
This Page [ linuxwireless.org ] provides some nice documentation with the links to the repo's contain the lastest code along with what looks like some useful android related utilities
Hello,
In this thread I will be compiling a list of tricks and techniques that I use to build roms for our phone.
I am not a developer, so some of the fixes in this may be bandaid-y and I may not be able to help will all errors, but I will post fixes for those that I have encountered.
This thread is a WIP and will be updated as I receive questions and encounter problems myself. This hopefully will be a good source of knowledge for those who are interested in compiling other roms for our phone, and from this hopefully we will see some more roms developed.
Building
First of all, the device trees. Thanks to codewerx, who has generously created a device tree we can use for our phone.
I would like to link you to the following guide, which instructs you on how to build AOSPA (formerly Paranoid Android).
http://forum.xda-developers.com/showthread.php?t=1863547
You can follow this guide verbatim, as it is mostly laid out for i9300, however we must add this to the Manifest.xml rather than what he has provided.
Code:
<remote name="gh"
fetch="https://github.com/" />
<project name="teamhacksung/android_device_samsung_i9305" path="device/samsung/i9305" remote="gh" revision="cm-10.1" />
<project name="CyanogenMod/android_device_samsung_smdk4412-common" path="device/samsung/smdk4412-common" remote="gh" revision="cm-10.1" />
<project name="CyanogenMod/android_kernel_samsung_smdk4412" path="kernel/samsung/smdk4412" remote="gh" revision="cm-10.1" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="gh" revision="cm-10.1" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="gh" revision="cm-10.1" />
<project name="teamhacksung/proprietary_vendor_samsung_i9305" path="vendor/samsung/i9305" remote="gh" revision="cm-10.1" />
Check to see if any of these are already in your manifest, and remove them if they are.
To make sure that the correct RIL for phone support is included,
1. Navigate to your frameworks/opt/telephony folder.
2. Open a shell session in this folder.
3. Apply this change by codewerx http://review.cyanogenmod.org/#/c/31703/ by
4. Typing the following into terminal
Code:
git fetch http://review.cyanogenmod.org/CyanogenMod/android_frameworks_opt_telephony refs/changes/03/31703/1 && git cherry-pick FETCH_HEAD/[code]
[B]Fixes[/B]
If you encounter the following error:
[code]make: *** No rule to make target `/home/sam/RootBox/out/target/product/i9305/obj/SHARED_LIBRARIES/libTVOut_intermediates/export_includes', needed by `/home/sam/RootBox/out/target/product/i9305/obj/EXECUTABLES/mediaserver_intermediates/import_includes'. Stop.
Navigate to vendor/samsung/smdk4412-common/proprietary, and open Android.mk
The reason we get this error is because the propietary files are not copied over properly, so we must edit the line in Android.mk which resembles
Code:
ifneq ($(filter i9300 n7100 n8000 n8013,$(TARGET_DEVICE)),)
to
Code:
ifneq ($(filter i9300 [b]i9305[/b] n7100 n8000 n8013,$(TARGET_DEVICE)),)
- Reserved -
Link missing
Could you please add the link to the howto you mentioned?
perchrh said:
Could you please add the link to the howto you mentioned?
Click to expand...
Click to collapse
Oh wow i'm so sorry about that haha I was sure i embedded it
I'll fix it now
Thanks!
I was also able to build CyanogenMod 10.1 using your xml-excerpt.
The "Fixes" section turned out to be unnecessary, as they were already applied for CM.
The RIL-step is still necessary, though.
hey there...
nice work... but can you say me, how i can get the flac support back to my i9305 on aosp?!
perchrh said:
Thanks!
I was also able to build CyanogenMod 10.1 using your xml-excerpt.
The "Fixes" section turned out to be unnecessary, as they were already applied for CM.
The RIL-step is still necessary, though.
Click to expand...
Click to collapse
I wrote a similar guide for CM, see http://forum.xda-developers.com/showthread.php?t=2164954
Programmers can:
Rebuild the BCM21553 Android 4.0 graphics stack from source
Develop fully open drivers for other VideoCore devices, including the Raspberry Pi’s BCM2835 and the BCM21654 (a low-cost 3G integrated baseband for emerging markets).
Gain insight into the internal operation of VideoCore for performance tuning purposes
Write general-purpose code leveraging the GPU compute capability on VideoCore devices
take a look at this post and download em
finally :victory: after 2 years.
Gah, to my God! They are really BCM21553 GPU drivers (basicly VideoCore IV source). Now, we need good developer to start working on it (i believe in bieltv3 + spacecaker), because compiling sources with .mk files always makes my problems. This source is for OpenGLES 1.1 and 2.0.
I think its best if we wait for bieltv.3 to look at these.
finallyyyyyy ics...
Envy-X said:
I think its best if we wait for bieltv.3 to look at these.
Click to expand...
Click to collapse
PM'd @bieltv.3 .
Oh yeahh!! Broadcom! At least you heard our prayers
Wow great news...!!! Finally...
Can't wait to see developement with the new drivers
Gesendet von meinem Nexus 5 mit Tapatalk
Awesome!
With the release of source drivers, this thread should be up and running,..victory!
README.txt
This package contains the Broadcom Android ICS Graphics stack for arm v5
==================================================================
Package contents:
a new folder that contains the Graphics stack source codes:
-----------------------------------------------------------------
brcm_usrlib/dag
Required file changes in existing AOSP repos to build this Graphics stack
-----------------------------------------------------------------
AOSP repo name: repo_aosp/platform/bionic
libc/private/bionic_tls.h
AOSP repo name: repo_aosp/platform/build
core/legacy_prebuilts.mk
target/board/generic/device.mk
AOSP repo name: repo_aosp/platform/external/webrtc
src/common_audio/resampler/main/source/Android.mk
src/common_audio/signal_processing_library/main/source/Android.mk
src/common_audio/vad/main/source/Android.mk
src/modules/audio_processing/aec/main/source/Android.mk
src/modules/audio_processing/aecm/main/source/Android.mk
src/modules/audio_processing/agc/main/source/Android.mk
src/modules/audio_processing/main/source/Android.mk
src/modules/audio_processing/main/test/process_test/Android.mk
src/modules/audio_processing/main/test/process_test/process_test.cc
src/modules/audio_processing/main/test/unit_test/Android.mk
src/modules/audio_processing/ns/main/source/Android.mk
src/modules/audio_processing/utility/Android.mk
src/system_wrappers/source/Android.mk
AOSP repo name: repo_aosp/platform/frameworks/base
opengl/include/EGL/eglext.h
opengl/libagl/egl.cpp
opengl/libs/EGL/egl.cpp
opengl/libs/EGL/eglApi.cpp
opengl/libs/EGL/egl_entries.in
opengl/libs/EGL/getProcAddress.cpp
opengl/libs/GLES2/gl2.cpp
opengl/libs/GLES_CM/gl.cpp
services/input/InputReader.cpp
services/surfaceflinger/Android.mk
services/surfaceflinger/DisplayHardware/DisplayHardware.cpp
AOSP repo name: repo_aosp/platform/hardware/libhardware
Gralloc changes:
include/hardware/fb.h
modules/gralloc/Android.mk
modules/gralloc/framebuffer.cpp
modules/gralloc/gr.h
modules/gralloc/gralloc.cpp
modules/gralloc/gralloc_priv.h
modules/gralloc/mapper.cpp
Hwcomposer changes:
modules/gralloc/Android.mk
modules/hwcomposer/Android.mk
modules/hwcomposer/hwcomposer.cpp
AOSP repo name: repo_aosp/platform/system/core
include/system/graphics.h
==================================================================
Instructions to build this Graphics stack on Android ICS project:
1. Check out a Android ICS (example: android-4.0.1_r1.1) workspace with the following sequence of commands:
repo init -u https://android.googlesource.com/platform/manifest -b android-4.0.1_r1.1
repo sync -j8
2. Extract the content of this package (excludes this README.txt) in the root directory of the Android ICS workspace:
3. Build the Android source tree with the following sequence of commands:
source build/envsetup.sh
lunch full-eng
make -j8 TARGET_DEVICE=generic_armv5
This package contains the Broadcom Android ICS Graphics stack for arm v5
==================================================================
Package contents:
a new folder that contains the Graphics stack source codes:
-----------------------------------------------------------------
brcm_usrlib/dag
Required file changes in existing AOSP repos to build this Graphics stack
-----------------------------------------------------------------
AOSP repo name: repo_aosp/platform/bionic
libc/private/bionic_tls.h
AOSP repo name: repo_aosp/platform/build
core/legacy_prebuilts.mk
target/board/generic/device.mk
AOSP repo name: repo_aosp/platform/external/webrtc
src/common_audio/resampler/main/source/Android.mk
src/common_audio/signal_processing_library/main/source/Android.mk
src/common_audio/vad/main/source/Android.mk
src/modules/audio_processing/aec/main/source/Android.mk
src/modules/audio_processing/aecm/main/source/Android.mk
src/modules/audio_processing/agc/main/source/Android.mk
src/modules/audio_processing/main/source/Android.mk
src/modules/audio_processing/main/test/process_test/Android.mk
src/modules/audio_processing/main/test/process_test/process_test.cc
src/modules/audio_processing/main/test/unit_test/Android.mk
src/modules/audio_processing/ns/main/source/Android.mk
src/modules/audio_processing/utility/Android.mk
src/system_wrappers/source/Android.mk
AOSP repo name: repo_aosp/platform/frameworks/base
opengl/include/EGL/eglext.h
opengl/libagl/egl.cpp
opengl/libs/EGL/egl.cpp
opengl/libs/EGL/eglApi.cpp
opengl/libs/EGL/egl_entries.in
opengl/libs/EGL/getProcAddress.cpp
opengl/libs/GLES2/gl2.cpp
opengl/libs/GLES_CM/gl.cpp
services/input/InputReader.cpp
services/surfaceflinger/Android.mk
services/surfaceflinger/DisplayHardware/DisplayHardware.cpp
AOSP repo name: repo_aosp/platform/hardware/libhardware
Gralloc changes:
include/hardware/fb.h
modules/gralloc/Android.mk
modules/gralloc/framebuffer.cpp
modules/gralloc/gr.h
modules/gralloc/gralloc.cpp
modules/gralloc/gralloc_priv.h
modules/gralloc/mapper.cpp
Hwcomposer changes:
modules/gralloc/Android.mk
modules/hwcomposer/Android.mk
modules/hwcomposer/hwcomposer.cpp
AOSP repo name: repo_aosp/platform/system/core
include/system/graphics.h
==================================================================
Instructions to build this Graphics stack on Android ICS project:
1. Check out a Android ICS (example: android-4.0.1_r1.1) workspace with the following sequence of commands:
repo init -u https://android.googlesource.com/platform/manifest -b android-4.0.1_r1.1
repo sync -j8
2. Extract the content of this package (excludes this README.txt) in the root directory of the Android ICS workspace:
3. Build the Android source tree with the following sequence of commands:
source build/envsetup.sh
lunch full-eng
make -j8 TARGET_DEVICE=generic_armv5
Oh yeaahh, I mean the sources is present for my birthday that will be tomorow. :thumbup:
Send From My Ace i Using Tapatalk
Cant wait for biel and robin when they will see this..
Sent from my GT-S5830i using Tapatalk 2
Yay finally!! (Good for you as I'm already on KK, sold my cooperve )
Sent from me using my tablet using an app.
we did it guys!!!!
my congrats to all bcm21553 users!!
bcm21553-one love<3
Finally!!! Please accept my congratulations!!!
i think broadcom released all gpu sources of our devices.so now we dont have any complain towards them!!!
finally after thousands of people signing the petition, abusing broadcom for a long time and the raspberry pi challenging to port the sources for its platform! broadcom gives the sources for the hope we dont need to struggle any further for the drivers @Biel.tv3 here you go!
2year before we write in our signatures: Kill Broadcom
Now we love they
Отправлено с моего GT-S5830i через Tapatalk
OMG!OMFG!!! :laugh:
Thats Reallly A Great News !:laugh:
:fingers-crossed:
Madre de dios! Господе Боже! Mother of God!! This is awesome! But do we have developer for creating the rom?
Biel, SpaceCaker, Lopicl
Отправлено с моего GT-S5830i через Tapatalk
** HOW-TO COMPILE BEANSTALK YOURSELF **
{
"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"
}
NOTE: Pre-compiled nightly builds in the second post
or
Official Builds are found here
While BeanStalk is offically supported for our device, I noticed that there hasn't been a new build for a little while and loving the ROM as much as I do, I'm addicted to having the latest features. Here is a basic tutorial for building this yourself. If I'm stepping on anyones toes by posting this, please let me know. I am in no way affiliated with the development of this ROM or with scott.hart.bti the creator of it.
I compiled on a Debian Wheezy system, 64bit (squeeze should be the same). A 64-bit computer is required to compile KitKat (ICS and above for that matter), so don’t attempt this on anything less. If you are unfamiliar with installing Debian, you can use LMDE, it's a live Debian system that you can install with minimal linux knowledge and works pretty nice. However the installation process is pretty easy for vanilla Debian and a good learning process, so give it a shot if you have the time.
Do this all as root
Download dependencies:
Code:
apt-get install git-core gnupg flex bison gperf build-essential zip curl libc6-dev libncurses5-dev x11proto-core-dev libx11-dev libreadline6-dev g++-multilib mingw32 openjdk-6-jdk tofrodos python-markdown libxml2 libxml2-utils schedtool pngcrush xsltproc zlib1g-dev lib32stdc++6 lib32ncurses5 ncurses-libs.i686 libstdc++.i686 libgcc.i686 lib32readline-gplv2-dev lib32z1-dev
Link files:
Code:
ln -s /lib32/libncurses.so.5 /lib32/libncurses.so
or for Ubuntu 10.10:
Code:
sudo ln -s /usr/lib32/mesa/libGL.so.1 /usr/lib32/mesa/libGL.so
Install Google’s repo script:
Code:
mkdir ~/bin
PATH=~/bin:$PATH
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod 755 ~/bin/repo
Make your working Directory and start syncing with BeanStalk
Code:
mkdir ~/beanstalk; cd ~/beanstalk
repo init -u git://github.com/scotthartbti/android.git -b kk44
repo sync
Setup the build environment for our device (jflte)
Code:
. build/envsetup.sh
lunch 56 ## or type lunch and find "jflte_userdebug" in the menu
Add the device source code and Proprietary Vendor files by adding the following line to ~/beanstalk/.repo/local_manifests/roomservice.xml
So it should look like this afterwards:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_jflte" path="device/samsung/jflte" remote="github" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" />
<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" />
<project name="CyanogenMod/android_device_samsung_msm8960-common" path="device/samsung/msm8960-common" remote="github" />
<project name="CyanogenMod/android_kernel_samsung_jf" path="kernel/samsung/jf" remote="github" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_external_libtar" path="external/libtar" remote="github" revision="cm-11.0" />
</manifest>
Sync the repo again:
Code:
repo sync
Get your prebuilt terminal emulator:
Code:
cd ~/beanstalk/vendor/cm && ./get-prebuilts
Now there is a bug that will cause our builds to fail, so we need to apply the following for our unified devices:
Edit ~/beanstalk/device/samsung/jflte/system.prop
Add these two lines to the end:
Code:
ro.product.device=jflte
ro.product.model=Samsung JFLTE
That should be it, now we can build!
Code:
cd ~/beanstalk
. build/envsetup.sh
lunch 56 ## or type lunch and find "jflte_userdebug" in the menu
time mka bacon
when finished, it’ll be located in ~/beanstalk/out/target/product/jflte/
TIP:
Install the github app and follow scott.hart.bti to see when new updates get added to the sourcecode
Also, if you are into building, checkout my acompile script in my signature, it'll email you when your build is complete using Gmail's snmp and will include the time it took and the last few lines of the output. I find it very useful for knowing when my build is done (especially since they take me about 3+ hours apiece)
Also, I am using the latest NAE Firmware with no problems, however the stock MJA worked fine as well. Here is a link if you care to upgrade your modem drivers.
SOURCES:
This page helped a lot with a great tutorial on building ROMS
This forum is filled with great people who others with the building of ROMS. A great source when you run into errors you don’t understand.
BeanStalk Github for Scott.Hart.bti
jflte kernel source
I hope this helps someone,
-Mike
BUILDS:
If you would just like a compiled version, here are mine (they are stock, except for reverting this commit because I like the transparent Vol panel personally)
These builds are using the SlimRom's JFLTE Kernel which is kernel 3.4.82 vs the standard 3.4.0 from Cyanogenmod that is used stock with BeanStalk Offical builds.
NOTE: These are unified builds, meaning they can be flashed all all the S4 variants that were previously known as: jflteatt, jfltecan, jfltecri, jfltecsp, jfltespr, jfltetmo, jflteusc, jfltevzw, jfltexx
JFLTE BeanStalk 10/30/14 Nightly
Unofficial BlissStalk 10/29/14 Nightly
Unoffical BlissStalk 10/20/14 Nightly
Unofficial BlissStalk 10/17/14 Nightly
JFLTE BeanStalk 4.4.4010 Nightly 8/1/14
JFLTE Beanstalk 4.4.4010 Nightly 7/18/14
JFLTE Beanstalk 4.4.4007 Nightly 7/11/14
JFLTE Beanstalk 4.4.4001 Nightly 6/25/14
JFLTE BeanStalk 4.4.285 Nightly 4-21-14
JFLTE BeanStalk 4.4.278 Nightly 4-14-14 ## NOTE: If you have issues with receiving calls and/or texts, make sure to clean flash this build, that will fix it.
JFLTE Beanstalk Nightly Build 3-29-14 ## NOTE: No new features over the 3-24-14 build but uses SlimRoms kernel source instead (3.4.82 vs 3.4.0)
JFLTE Beanstalk Nightly Build 3-24-14
JFLTE Beanstalk Nightly Build 3-18-14
JFLTE Beanstalk Nightly Build 3-17-14
JFLTE Beanstalk Nightly Build 3-11-14
JFLTE BeanStalk Nightly Build 3-7-14
JFLTE BeanStalk Nightly Build 2-28-14
Slim Beta 4.4 Gapps Toggleable
PA GAPPS
Photosphere Addon ( Google Camera is in the PlayStore now, this is just for the 4.4 camera )
Sound Packs (System Sound Themes for switching on the fly)
ISSUES:
- Some people are having issues with the compass not always pointing north.
Enjoy,
-Mike
Changelog:
Again, I only compile, the code changes are done by the ROM Dev's
Code:
10/20/14
-New Version Number (001) to reflect being out of beta now.
-New Boot Animation
-ViperFX add and CM DSP removed
-SuperSU added to Downloads Section
-Netflix Fix added to Downloads Section
-Mem and CPU info removed from About Phone section
-More Bliss Stalk logos and names added.
-Torch Changes from CM11
-JFLTE Humidity Sensor permissions fixed
10/17/14
-Switched to BlissROM sources for a BeanStalk fork that is more current with changes and commits.
-Menus Updated
-Omni Switch Added
-Settings Menu Updated
-Xposed moved to the "Bliss Downloads" section for latest version.
-Bluetooth code updated by CM11
-Camera driver updated.
8/1/14
- No code changes in the beanstalk source since last build
- Enabled transparent lockscreen status bar
7/18/14
- Ad blocker
- EOS Weather
- Navigation Bar swipe left to open in Window
- App Circle SideBar
- Floating windows fixes
- Update to 4.4.4_r2 / Beanstalk 4.4.4010
7/11/14
- Hover added
- Driving mode
- Update Roboto fonts to Android L versions
- Use Android L navbar icons
- Reset battery stats
- Reworked non-intrusive incall ui
6/25/14
-Updated dialer
-Shake settings
-Glowpad transparency in dialer
-Doubletap custom tile
-Updated terminal
-Adjusted Auto-Brightness curve
-Android 4.4.4
4/21/14
- Update to BeanStalk 4.4.285
- CM Fixes for unifyed devices (JFLTE)
- Faster Framework animations
- Fixes the sometimes missing first task in AOSP and SlimRecents
- Shake to lock? (still trying to find this in settings)
- Smart Phone Call in Dialer (type number and hold to you ear to dial)
- CM11 Fixes
4/14/14
- Update to BeanStalk 4.4.278
- Fixes to the LTE tile
- Option for Screen Color in Settings (hue, contrast, etc)
- Theme support added to Ringtones
- Voice+ integrated into Settings
- Latest CM11 commit merges
- Toggle Flashlight when shaking
- Add On-The-Go mode (use camera as display overlay, for walking)
-Add Fast Charge QS Tile
- SlimRecents: Make expanded layout pretty
- Implement SIM card management
3/29/14
- Fixes to the LTE tile
- Option for Screen Color in Settings (hue, contrast, etc)
- Theme support added to Ringtones
- Voice+ integrated into Settings
- Latest CM11 commit merges
Cool Ty , looking forward to giving it a try
Sent from my SPH-L720 using Tapatalk
Nice! Will you continue to build Beanstalk for our device? I just left it for PAC since it hadn't been updated in ages.
Sent from my SPH-L720 using Tapatalk
themisterwilson said:
Nice! Will you continue to build Beanstalk for our device? I just left it for PAC since it hadn't been updated in ages.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Well our device has official support from BeanStalk already here, it seems that the builds for our devices stopped though when Cyanogenmod moved our device source into a unified code (combining jfltespr, jflteatt, jfltevzw, etc in one source "jflte"). Trying to build this ROM straight will fail because of this unification (see above in the tutorial for the fix), so I'm guessing that's why we haven't seen an official build in a while. I'll be more than happy to keep uploading nighties as I build them until the official builds start back up though, as long as I'm not stepping on the current maintainer's toes.
Cheers,
Mike
You keep on keeping on :thumbup::beer:
Sent from my SPH-L720 using xda app-developers app
Man thanks for the nightly it's amaze balls.....so grateful to be back on the stalk!!!!!
Sent from my SPH-L720 using XDA Premium 4 mobile app
Thanks so much been waiting for a version of stalk I could run on USC!
Sent from my SCH-R970 using Tapatalk
btoddweber said:
Man thanks for the nightly it's amaze balls.....so grateful to be back on the stalk!!!!!
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
My sentiments exactly! Thank you! Been amazing all day
Sent from my SPH-L720 using Tapatalk
Is the back to kill app option here? Looked everywhere and can't seem to find it. Also can't get a GPS lock!
Sent from my SCH-R970 using Tapatalk
Came across this on Google. Thank you so much for the tutorial and compiles. Please continue to share your builds as I will be using this on a T-Mobile S4.
bignick1215 said:
Is the back to kill app option here? Looked everywhere and can't seem to find it. Also can't get a GPS lock!
Sent from my SCH-R970 using Tapatalk
Click to expand...
Click to collapse
At one time I believe it was in the developer options at the bottom, can you use pie (with custom app) or hw buttons?
Sent from my SPH-L720 using Tapatalk
Not in developer options and the hw buttons Dont have a kill option! I guess I could use xposed but I just Dont care for it. Its really minor I just tap the greenify widget before I lock the screen and has the same affect. The GPS not locking on the other hand I've yet to get me a work around for that one.
Sent from my SCH-R970 using Tapatalk
bignick1215 said:
Not in developer options and the hw buttons Dont have a kill option! I guess I could use xposed but I just Dont care for it. Its really minor I just tap the greenify widget before I lock the screen and has the same affect. The GPS not locking on the other hand I've yet to get me a work around for that one.
Sent from my SCH-R970 using Tapatalk
Click to expand...
Click to collapse
There is not an option for mapping long-press actions to the back button currently, you could the BeanPie or LMT for that however (that's what I do). As for GPS, I get a lock just fine, what firmware are you using? I 've only tested with MJA and NAE (both located here). Anyone else having GPS issues?
Cheers,
-Mike
That explains the GPS lock! I'm on mja baseband but older firmware
Sent from my SCH-R970 using Tapatalk
Rebooted for the 3rd time and got instant GPS lock!
Once I toggle off and back on its a no go again! Turned it on then rebooted and it works again.
Sent from my SCH-R970 using Tapatalk
bignick1215 said:
Rebooted for the 3rd time and got instant GPS lock!
Once I toggle off and back on its a no go again! Turned it on then rebooted and it works again.
Sent from my SCH-R970 using Tapatalk
Click to expand...
Click to collapse
Haven't noticed any problems with GPS, but I'll try to re-create tomorrow and get back to you.
Cheers,
Mike
No problems at ALL on my end. Great job!!!! And many thanks again!!! Very glad to have stalk again
Sent from my SPH-L720 using XDA Premium 4 mobile app
mikshepard said:
Haven't noticed any problems with GPS, but I'll try to re-create tomorrow and get back to you.
Cheers,
Mike
Click to expand...
Click to collapse
Much appreciated! And thanks for the great work.
Sent from my SCH-R970 using Tapatalk
btoddweber said:
No problems at ALL on my end. Great job!!!! And many thanks again!!! Very glad to have stalk again
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
+1 many thanks!
Sent from my SPH-L720 using Tapatalk
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.