Related
(I would post this in the developer forum, but I don't have 10 posts)
I'm working on building Gingerbread from AOSP for Droid. I was hoping to gather information here on how to do this should someone want to build a rom in the future.
So far, I've followed the steps at http://source.android.com/source/download.html to fetch android-2.3.3_r1 (FWIW, I'm running OS X). For the droid, I also needed to clone these git repositories (mostly CM7 fixes) into the associated folder:
https://github.com/koush/proprietary_vendor_motorola - into vendor/motorola. When running git clone, be sure to add "-b gingerbread" to get the latest version. These are the binary blobs that one would normally get by running extract-files.sh.
https://github.com/CyanogenMod/android_device_motorola_sholes - into device/motorola/sholes. This is Droid-specific device information.
https://github.com/CyanogenMod/android_system_wlan_ti - into system/wlan/ti. This is the wifi driver.
https://github.com/CyanogenMod/android_hardware_ti_omap3 - into hardware/ti/omap3. These are other hardware drivers.
https://github.com/CyanogenMod/android_hardware_libhardware_legacy - into hardware/libhardware_legacy. More hardware libraries.
Additional fixes needed to complete build:
In device/motorola/sholes/overlay/frameworks/base/core/res/res/values/config.xml, comment out the line containing "config_flashlight_affects_lightsensor". This is part of CM7 code which disables the light sensor when the flashlight is on; an alternative fix would be to port this code into your tree.
Perform the two fixes at the bottom of the OP in http://forum.xda-developers.com/showthread.php?t=899674 - RGB_565 and Camera. Camera is definitely necessary for building - I believe the RGB_565 fix is necessary for Live Wallpapers.
Take the changes from https://github.com/CyanogenMod/andr...mmit/29f40ea86fe96f66b5a22c7a2bb84055c73e99be - this will prevent Launcher from crashing on boot. Thanks to PeterAlfonso for this fix!
Once the source tree is set up as described, you can run:
Code:
source build/envsetup.sh
lunch (select generic_sholes-userdebug)
make -j 4 otapackage
to start building Android, which will take a while depending on the speed of your machine.
This will create a file named out/target/product/sholes/generic_sholes-ota-eng.*username*.zip - this can be applied as an update.zip in the usual fashion. However, it contains the stock recovery files, which will overwrite the recovery partition you have. So, using any program which can modify zip files, delete the recovery/ folder.
At this point, you should have a flashable, Gingerbread, AOSP rom for droid!
Peter Alfonso (author of a great stock rooted Gingerbread rom for Droid) pointed out a fix for the launcher issues I was having, and I've updated the OP to reflect this. Compiling the changes now - hopefully the rom will boot, and this will represent a full set of instructions for compiling a vanilla gingerbread Droid rom!
I'm trying to compile it, but I'm getting this error:
Code:
Nathan-Camposs-MacBook-Pro:AOSP Nathan$ lunch generic_sholes-userdebug
sed: illegal option -- r
usage: sed script [-Ealn] [-i extension] [file ...]
sed [-Ealn] [-i extension] [-e script] ... [-f script_file] ... [file ...]
build/core/product_config.mk:194: *** _nic.PRODUCTS.[[device/motorola/sholes/sholes.mk]]: "build/target/product/small_base.mk" does not exist. Stop.
** Don't have a product spec for: 'generic_sholes'
** Do you have the right repo manifest?
Nathan-Camposs-MacBook-Pro:AOSP Nathan$
Could you help me?
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
FEEL FREE TO DONATE US FOR ALL WE'RE DOING FOR YOU!
For general discussions, bug reports and FAQ, write HERE!
Credits:
alfsamsung
P880-dev
csk1jw
MoltenMotherBoard!
Downloads:
MoltenMotherBoard mirror | AndroidFileHost
Full sources:
MoltenMotherBoard sources: MoltenMotherBoard | Github
Device: platform_device_lge_p880 | Github
Kernel: lge-kernel-p880 | Github
Changelog:
20151122:
AOSP 5.1.1_r29 branch up to 2015/11/21
20151121:
p880: kernel: various upstream changes from android-6.0.0_r0.4/5 branch (thanks to @csk1jw)
p880: ril: cleaner and lighter patches (thanks to @csk1jw)
p880: gps: cleaner and lighter patches (thanks to @csk1jw)
AOSP 5.1.1_r13 branch up to 2015/11/20
20150826:
p880: kernel: enable cleancache, remove cpu boost driver
p880: kernel: mm: frontswap: core frontswap functionality
AOSP 5.1.1_r13 branch up to 2015/08/26
20150824:
frameworks/base: fix wakelock issues
p880: set zRAM values with LZ4 and 256MB of RAM
p880: kernel: enable SWAP and LZ4
AOSP 5.1.1_r13 branch up to 2015/08/24
20150714:
frameworks/base: fix GPS for old GPS HALs along with @csk1jw patches
AOSP 5.1.1_r8 branch up to 2015/07/14
20150625:
p880: cm-12.1 kernel branch rebase
AOSP 5.1.1_r1 branch up to 2015/06/25
20150423:
AOSP 5.1.1_r1 branch up to 2015/04/23
20150406:
p880: restore old 'Recent Apps' behavior
AOSP 5.1.0_r3 branch up to 2015/04/01
20150327:
AOSP 5.1.0_r3 branch up to 2015/03/27
20150318:
p880: android-5.1.0_r1 bringup
AOSP 5.1.0_r1 branch up to 2015/03/17
20150123:
p880: revert any update from 2015/01/18
p880: update spn overrides (v3)
P880-dev cm-12.0 branch up to 2015/01/18
AOSP 5.0.2_r1 branch up to 2015/01/23
20150122:
p880: update spn overrides (v3)
P880-dev cm-12.0 branch up to 2015/01/22
AOSP 5.0.2_r1 branch up to 2015/01/22
20150121:
@alfsamsung: p880: prop: reduce ro.ril.wake_lock_timeout and misc cleanup
@alfsamsung: p880: SE policies: allow init to start lgsecclk and set radio props
@alfsamsung: p880: ril: cleanup
frameworks/opt/telephony: implement UICC TLV Data decoding
p880-dev cm-12.0 branch up to 2015/01/21
AOSP 5.0.2_r1 branch up to 2015/01/21
20150120:
frameworks/opt/telephony: Revert: implement UICC TLV Data decoding
p880: add spn overrides
P880-dev cm-12.0 branch up to 2015/01/20
AOSP 5.0.2_r1 branch up to 2015/01/20
20150118:
build: prevent recovery partition to get replaced
frameworks/opt/telephony: implement UICC TLV Data decoding
P880-dev cm-12.0 branch up to 2015/01/18
AOSP 5.0.2_r1 branch up to 2015/01/18
20150117:
p880: update patches method
@P880-dev: p880: audio_effects adjustements
@P880-dev: p880: fix NFC
build: ota: remove cruft
frameworks/native: compatibility work around for bad graphics driver dependency
hax: Add back the SURFACE_SKIP_FIRST_DEQUEUE legacy EGL workaround
p880: fix RIL typo
@P880-dev: p880: add missing cam include
@P880-dev: p880: add 48000 a2dp sampling rate
@P880-dev: p880: update AudioWrapper to fix video recording
@P880-dev: p880: update SE policies
surfaceflinger: squashed fixes for additional hwrotation
libgui: squashed commits for MR0 devices
frameworks/base: fix GPS for old GPS HALs
P880-dev cm-12.0 branch up to 2015/01/17
AOSP 5.0.2_r1 branch up to 2015/01/17
20150111:
binder: add legacy MemoryDealer constructor for Nvidia OMX adaptor
p880: enable ffmpeg decoders
p880: revert audio primary outputs updates
libgui: add pre-MR2-compatible symbol for setPosition and setOrientation
libutils: refbase: jellybean mr1 compat
p880: temporary revert few overlays
frameworks/base: reintroduce button-backlight (and respective inactivity timeout)
@alfsamsung: p880: SE policies updates
@alfsamsung: p880: GPS fixes
@P880-dev: p880: update RIL for 5.0
@P880-dev: p880: GPS fix and config cleanup
P880-dev cm-12.0 branch up to 2015/01/10
AOSP 5.0.2_r1 branch up to 2015/01/10
20150107:
build: use an updated apns-conf.xml version
p880: include MMB vendor
build: bring back Camera2 into the package
libutils: put back the unused virtuals in Vector<>
telephony: SignalStrength: hotfix GSM and TD-SCDMA
init: add a mechanism to extend the property service in device configs
telephony: RIL: squashed support for old RIL
bionic: linker: enable support for non-PIE executables
libbt: add support for board-specific configuration
p880: patches: correct frameworks/opt/telephony repo path name
telephony: RIL: make RIL subclassable
telephony: allow a device to include its own RIL subclass
build: exclude Home launcher
frameworks/av: stagefright: add legacy MediaBuffer::acquireBuffer symbol
build: include Launcher3 and Camera2 modules by default
p880: temporary revert few overlays
camera.tegra: fix camera_common.h include
frameworks/av: libstagefright: extended media support via FFMPEG
bionic: linker: avoid logcat warning with pre KK/LP blobs
build: prevent zip to replace recovery partition
build: do not report an error if building with Sun JDK
build: include kernel inline build
build: make OUT_DIR an absolute path
p880: add patches support
P880-dev cm-12.0 branch up to 2015/01/03
AOSP 5.0.2_r1 branch up to 2015/01/06
Issues:
-----
Do you want to report an issue? Do it here!
In order to do it, create a new issue, choosing correct labels corrisponding to: Device/OS which you're using, ROM/project you're on, kind of issue.
Also, please, be sure you're running the ROM/project in the exact way we've provided it to you (do not create issues if you're using different
kernel, mod, plugins and dependencies we didn't tell to use).
General Questions: MoltenMotherBoard Projects | General Questions and Info
XDA:DevDB Information
AOSP Lollipop, ROM for the LG Optimus 4X HD
Contributors
MoltenMotherBoard, streambinder
Source Code: https://github.com/MoltenMotherBoard/platform_local
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.1.x
Based On: AOSP
Version Information
Status: Stable
Created 2015-01-07
Last Updated 2015-08-26
Hey. I'm the project mantainer. Again.
Just to ping it:
streambinder said:
First of all, it's my first thread here: then, I don't want to be overbearing in offering my work, never.
If I would ever result like that, please tell me.
About the project: my team has always followed AOSP projects, even with ARMv6.
This time I decided to work on it, for this phone, as I need bugfree sources even for it, as for all the others custom ROMs.
The build shared is only the result of the first compilation, quickly tested by me.
I would like to ask you to test and report any bug you experience, so that we can reach as soon as possible a bugfree release.
Click to expand...
Click to collapse
This time, I've something else to tell you.
The build is now uploading is pretty stable and the only issues that are affecting it are the ones listed above (as NFC continously crashes, I excluded it from the build).
Updates will come, do not worry, but tomorrow gonna have an exam, and on Monday another one, so... please, be patient.
For testers, have fun with this build!
And... for @fritzcola, this is for you: http://pastebin.com/qUZ9pmKx
Cheers!
Here's a little hands-on clip, made by @EsromG5:
isn't our kernel based on 3.1.x, not 3.0.x?
good job :good:
Flying_Bear said:
isn't our kernel based on 3.1.x, not 3.0.x?
good job :good:
Click to expand...
Click to collapse
Sorry, my mistake.
Anyway, build is up!
Just flashed rom. Feels smooth. Mobile data work without issue for now:good:
Issues:
-can't make outgoing calls (major)
-camera(already known)
-no root acces(you can fix that flashing this ---> http://download.chainfire.eu/641/SuperSU/UPDATE-SuperSU-v2.40.zip)
-lack of options (it's early stage, so :good
Install take a little longer just like start(at boot animation) be patient
I still cant place a call like on euphoria rom :/
streambinder said:
Sorry, my mistake.
Anyway, build is up!
Click to expand...
Click to collapse
There are problems with flashing, don't flash it yet guys.It gives an error; I'll edit and add the lines soon
After rebooting into recovery, it was fixed (as far as I can remember the error was about sys/.../tegra3/app mount failed)
It was probably because I mounted sdcard as flash storage via TWRP before I flashed
xperia u20i said:
Just flashed rom. Feels smooth. Mobile data work without issue for now:good:
Issues:
-can't make outgoing calls (major)
-camera(already known)
-no root acces(you can fix that flashing this ---> http://download.chainfire.eu/641/SuperSU/UPDATE-SuperSU-v2.40.zip)
-lack of options (it's early stage, so :good
Install take a little longer just like start(at boot animation) be patient
Click to expand...
Click to collapse
Thanks for your report:
- can you pull a log? I test every RIL function and everything is working properly on my side, calls too.
- already known.
- not a prio: as you said, you only need to flash a patch.
- can confirm: that's exactly why I love AOSP.
ex0rt said:
I still cant place a call like on euphoria rom :/
Click to expand...
Click to collapse
Can you pull a log? I don't have any problem.
ottomanhero said:
There are problems with flashing, don't flash it yet guys.It gives an error; I'll edit and add the lines soon
Click to expand...
Click to collapse
Did not have any issue while flashing, it only takes a little bit more.
Which error do you have?
streambinder said:
Thanks for your report:
- can you pull a log? I test every RIL function and everything is working properly on my side, calls too.
- already known.
- not a prio: as you said, you only need to flash a patch.
- can confirm: that's exactly why I love AOSP.
Can you pull a log? I don't have any problem.
Did not have any issue while flashing, it only takes a little bit more.
Which error do you have?
Click to expand...
Click to collapse
I can confirm that there is no flashing error.
Log is here...
edit
https://www.dropbox.com/s/clpj7ntf9k5h4x4/2015-01-07_12.34.zip?dl=0
xperia u20i said:
I can confirm that there is no flashing error.
Log is here...
edit
https://www.dropbox.com/s/clpj7ntf9k5h4x4/2015-01-07_12.34.zip?dl=0
Click to expand...
Click to collapse
Have you wiped /system, /data and /cache partitions before flashing AOSP?
And if you have, I saw you restored few backups with Titanium - and/or maybe something else -, have you checked if making calls worked out-of-box.
I suggest you to wipe everything and test it as the first thing you do once ROM boots up.
streambinder said:
Have you wiped /system, /data and /cache partitions before flashing AOSP?
Click to expand...
Click to collapse
yes, i made full wipe. everything except internal sd card
I edited my post, while this is my usual procedure when flashing ROMs (first mount as USB storage, then copy over and flash) it was seemingly fixed by rebooting to recovery and attempting to flash again.
xperia u20i said:
yes, i made full wipe. everything except internal sd card
Click to expand...
Click to collapse
Have you edited anything before testing calls?
ottomanhero said:
I edited my post, while this is my usual procedure when flashing ROMs (first mount as USB storage, then copy over and flash) it was seemingly fixed by rebooting to recovery and attempting to flash again.
Click to expand...
Click to collapse
No problem, dude.
Glad to see it's working for you, too.
@streambinder Feels pretty smooth after a few minutes!!
streambinder said:
Have you edited anything before testing calls?
Click to expand...
Click to collapse
No, installed rom and gapps (pa gapps) enter email, and flash super su, but maybe i flashed after that tried to make a call i can't remember exactly-
Nothing of that should messed out things, i think.
fritzcola said:
@streambinder Feels pretty smooth after a few minutes!!
Click to expand...
Click to collapse
Yup, I totally agree with you!
xperia u20i said:
No, installed rom and gapps (pa gapps) enter email, and flash super su, but maybe i flashed after that tried to make a call i can't remember exactly-
Nothing of that should messed out things, i think.
Click to expand...
Click to collapse
Maybe, or maybe not.
I suggest you to try: just flash only the AOSP package - do not with the other you mentioned - and check at first calls.
As I do not have your issues, we'll just try to narrow the possibilities field.
streambinder said:
Yup, I totally agree with you!
Maybe, or maybe not.
I suggest you to try: just flash only the AOSP package - do not with the other you mentioned - and check at first calls.
As I do not have your issues, we'll just try to narrow the possibilities field.
Click to expand...
Click to collapse
ok..my battery is empty now (don't know how ) i'll try to make a test again just with flashed rom, today, if not, tomorrow morning.
I got error while flashing and system doesn't boot here's my error
mount: failed to mount /dev/block/platform/sdhci-tegra.3/by-name/APP at /system: Device or resource busy
streambinder said:
Can you pull a log? I don't have any problem.
Click to expand...
Click to collapse
I didn't flashed gapps when I tried it, must say it was really smooth, but I need to call people . Can you recommend me an app for logs and I will try to get it asap.
xperia u20i said:
ok..my battery is empty now (don't know how ) i'll try to make a test again just with flashed rom, today, if not, tomorrow morning.
Click to expand...
Click to collapse
Ok, waiting for your updates.
CrazyWinner said:
I got error while flashing and system doesn't boot here's my error
mount: failed to mount /dev/block/platform/sdhci-tegra.3/by-name/APP at /system: Device or resource busy
Click to expand...
Click to collapse
Have you formatted /system before flashing the ROM?
{
"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"
}
SlimRom is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and Gerrit.
Code:
/* #include <std_disclaimer.h>
*
* Your tablet's warranty is now void.
* This is a custom ROM developed by p3dboard.
* You are flashing this on your Samsung Galaxy Tab 7.7 at your own peril.
* I am not responsible for hard bricks, damages to SD Cards, thermonuclear war,
* or you getting fired because the alarm app failed.
* I would definitely help you out if you are stuck somewhere, provided that you give
* me clear details of the mishap.
* Don't ask for ETA's cause there is a thing called "LIFE" outside XDA.
*/
SlimLP is currently in beta stage, some settings are already in place, much is still missing and would come with time. Stay tuned!
I am also new to development, so not as experienced as Daniel, and I also don't have a lot of extra time, so I'll do what I can, and fix what I can as I learn over time. But I wanted to contribute something new, and from Daniels survey, Slim was the second most popular rom after Carbon.
WHAT'S INCLUDED: (This is just a standard blurb, some of these SLIM extra's are not in their Beta yet)
Android Lollipop
Slim Center
Slim Launcher
Slim File Manager
Slim Heads Up
The Real Dark Slim User Interface
SlimPIE (inspired by ParanoidAndroid's PIE with a light touch of Slim)
Smart Card Service
Adaptive Backlight
Adaptive Brightness
Smart Lock
Privacy Guard
Sounds Tweaks(Audio FX and Music FX)
Status Bar Tweaks
Battery Saver Mode
Removed Bloatwares
Notification Reminder/Snoozer
Drawer Shortcuts
Lockscreen Shortcuts
Custom Quick Settings Tiles
Improved Performance
Camera - True View
Camera - Smart Capture
and Much More!
WHAT'S WORKING:
Camera
Video Recording
Wi-Fi
Bluetooth
ADB
Proximity Sensor
External SD Card
Internal SD Card
Video Playback
Speaker
Airplane Mode
RIL(Mobile and Data Network)
Compass - Can require calibration before being reasonably accurate (moving tablet around in a figure 8 a few times) - Might be a way to recalibrate this?
Automatic Brightness Sensor
GPS
POSSIBLY WORKING - TESTING REQUIRED:
Mobile Hotspot (can someone with a p6800 tell me if it works for them?)
BUGS/NOT WORKING:
Wifi Driver Bug that can reboot (ES Explorer Direct Send between two devices)
QS Torch Tile (Quick Settings Torch)
Touch Keyboard at initial boot - you need to either not flash GAPPS immediately or cancel the Setup with GAPPS flashed, then go into SETTINGS -> LANGUAGE&INPUT -> Current Keyboard and then turn on Hardware Input - After that the AOSP keyboard works - need to figure out how to fix this.
HOW TO INSTALL:
1. Download the ROM and the GApps and place them on your SD Card/Internal Storage.
2. Reboot tablet into TWRP recovery.
3. Wipe data, cache(factory reset), dalvik/art cache and system.
4. Flash the ROM and the GApps.
5. Reboot System. (First boot takes 5-6 minutes. Be patient.)
UPGRADING: If you are upgrading from a previous SlimLP build (not Kit kat Slim rom's, as you will get some issues)
1. Download the ROM, place it on your SD Card/Internal Storage.
2. Reboot tablet into TWRP recovery.
3. Flash the ROM
4. Reboot System.
SOURCES:
Daniel_HK's GitHub
SlimRoms Website
Google+
My code change notes - Download "Slimlp Changes to compile.txt" - How to compile after you have read and understood Daniels Instructions on compiling Rom's - read - read - read - something I didn't and don't always seem to do
CREDITS:
SlimROMs Team
@daniel_hk
and others I may have forgotten.
DOWNLOADS AND CHANGELOG IN THE SECOND POST
XDA: DevDB Information
SlimLP 5.1.1 by SlimRoms, ROM for the Samsung Galaxy Tab 7.7
Contributors
@p3dboard
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
ROM Firmware Required: Galaxy Tab 7.7 (p6800,p6810)
Based On: AOSP
Version Information
Status: Build #1.8
Latest Build Release Date: 2016-04-06
Created 2015-09-15
Last Updated 2015-10-28
Change Log and Downloads
Slim Gerrit - Slim Rom's change log
4 April 2016
SlimLP Beta 0.15 - Build #1.8 - Build Date 20160406 - Download ROM from this URL
- Updated Source Code to Beta 0.15 (Patch Level is up to February 2016 in Security - Possibly this is the last update Slim might make for Android 5.1.1, CM 12.1 sources have been updated to April 2014, but not Slim so far)
- P6800 & P6810 builds completed (just the NoZram version)
- Added Daniel's Performance Control app, but it errors out when going to the Battery tab, I'll leave it in their incase anyone wants to use the CPU / Governor controls - but if you want to tweak memory, use another app like Trickster Mod from the play store.
- Returned Davlik Memory settings back to stock in this build, as if you don't have too many apps installed that run background services, you can open apps that use larger Ram values.
I decided to recompile a newer build as I wanted a Rom with a more recent security patch level that also had Google Play Movies working, Android 6.0 currently has issues the the L3 DRM blobs. It's still got the same old issues as mentioned in the first post with workarounds as above - Touch keyboard, and the QS Flashlight not working, along with the reboot bug if you try to transfer data over Wifi using Es Explorer. But apart from that its pretty stable.
28 Oct 2015
SlimLP Beta 0.10 - Build #1.7 - Build Date 20151028 - Download ROM from this URL
- Updated Source Code to Beta 0.10
- Making two version of the build, one with zRam and one without - you can choose which one you feel performs better
- Updated RIL libraries for p6800 from Daniels latest CM 12.1 build (October 2015 build)
- p6800 rom's uploading now for Build 1.7, zRam and no-zRam version
- The no zRam version still supports zRam but its not turned on by default. If you have the app Trickster Mod from the playstore, (there's probably others) you can turn the zRam off any time you want to while running the rom. If you turn it off and then back on in Trickster Mod however, the new zRam partition is only 10% of the memory, which is smaller then the 256mb zRam I am turning on at boot.
- P6810 Zram build uploaded, uploading non-zram p6810 rom version now, compiling p6800 rom.
- P6810 beta 0.10 compile completed (no zRam version), uploading, compiling p6810 zram build. Once this finishes building, i'll start the p6800 build
- Synced SlimLP Beta 0.10 source code, starting compile of P6810 rom
- I'll make two builds of each for the next rom, one with Zram turned on and one without.
- I still haven't had time to look at the Keyboard issue or the QS torch icon, got to many things on at the moment - so just doing source code updates
14 Oct 2015
SlimLP Beta 0.9 - Build #1.6.2 - Build Date 20151014 - Download ROM from this URL
- Added missing blob libsec-ril.so file for p6800
- Added a 256mb zram swap partition (cm12.1 i9100 nightly just implemented this as they said it can help with low memory situations, so I've added it to see if it helps us at all - give me feedback, we can always turn it off).
@4:05pm - p6800 build is uploaded.
@3:35pm - p6800 build complete, checked that libsec-ril.so was in the /system/lib folder. Uploading now (about 30min it should be there)
@8:44am - build 1.6.2 for p6810 with 256mb zram uploading now. I am building the p6800 rom now.
@8:25am - I just discovered I missed adding /system/lib/libsec-ril.so to the p6800 build (builds 1.6 and 1.6.1) - so stick with 1.5.1 until I fix this on the p6800, so Mobile services won't be available. I'll recompile the rom for the p6800 today.
13 Oct 2015
SlimLP Beta 0.9 - Build #1.6.1 - Build Date 20151013 - Download ROM from this URL
- New Stagefright security patch and October 1st Android Security patches (see Slim Gerrit changes for today for the latest list of changes)
- Bug in this build: P6800 rom missing RIL blob - mobile / data won't work
@6:43pm - p6810 build completed, uploading now.
@4:55pm - p6800 build 1.6.1 compiled, uploading now. Compiling the p6810 build now.
@4:00pm - i just noticed that the slimlp source just received the new stagefright security fix, i've synced the new source code updates and am compiling build 1.6.1, it also has the other Google security updates for October. Building p6800 rom now.
SlimLP Beta 0.9 - Build #1.6 - Build Date 20151012/13 - Download ROM from this URL
- Sources updated to SlimLP Beta 0.9
- Bluetooth built using Daniels new Bluetooth packages that allow Bluedroid and Bluez to co-exist
- Daniels USB-OTG update (from his sources)
- Bug in this build: P6800 rom missing RIL blob - mobile / data won't work
@3:08pm - p6800 build is up.
@2:20pm - p6800 build 1.6 compile completed. Uploading now (should be about 30min)
@8:23am - p6810 build 1.6 is uploaded
@8:20am - I'm uploading the p6810 build at the moment, then I'll start compiling the p6800 build
12 Oct 2015
- I've just downloaded SlimLP Beta 0.9 source code and sync'd Daniels latest device tries, starting on compile for the p6810 (Android 5.1.1_r20)
- I'm also going to test adding persist.sys.debug.multi_window=true to /system/build.prop - which might only be a Marshmallow (Android 6.0) setting, but I'll see if it works in 5.1.1_r20 of SlimLP Beta 0.9 source code
- I'm also going to test building Daniel's updated Bluetooth Package from his Github that allows it to co-exist with Bluedroid Bluetooth, rather then removing it.
- I haven't had any time to look at the Torch QS tile or the keyboard fault in the last two weeks, eventually I'll get onto those.
1 Oct 2015
SlimLP Beta 0.8 - Build #1.5.1 - Build Date 20151001 - Download ROM from this URL
- Modified /system/build.prop Davlik values again based on some more testing. dalvik.vm.heapgrowthlimit=64m. Previous build 1.5 tends to be laggy when launching multiple apps. You can test Build 1.5 and 1.5.1 and decide which settings give better performance if you like. If you know how to modify build.prop with root access, you don't need to reflash the rom, just set the Build.prop values.
@11:00am - p6810 build also uploaded.
@10:20am - p6800 build uploaded. p6810 build uploading now.
@9:17am - p6800 build compiled. Uploading. Compiling p6810 build now.
@8:00am - I think the new Davlik values are a bit excessive. I think increasing to dalvik.vm.heapgrowthlimit=64m, instead of dalvik.vm.heapgrowthlimit=100m, provides better responsiveness, but still enough for background apps like facebook (which uses around 60m of ram). For example, with the 64m value, opening a hyperlink from Gmail in Chrome works nicely, but at 100m, it's very laggy. My previous builds had this value set at 48m.
I think these values are better - I'll put a build 1.5.1 up soon, for those who want to try the different values (or you can manually set it yourself in Build.prop if your comfortable).
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=320m
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=2m
30 Sept 2015
SlimLP Beta 0.8 - Build #1.5 - Build Date 20150930 - Download ROM from this URL
- Updated Device Tree's from Daniel, Mobile Hotspot should be fixed for p6800 users
- GPS fixed
- Modified /system/build.prop Davlik values based on Article about Ram and Davlik settings, seems to be giving better performance, Games like Asphalt 8 seem to be smoother, more Ram seems to be generally available.
@7:14pm - p6800 rom uploaded
@6:34pm - p6800 build completed, uploading now, should be there in 30min
@6:15pm - P6810 Build #1.5 is uploaded. P6800 build still compiling..
@6:10pm - playing with Facebook installed in the background, dalvik.vm.heapsize=256m is more friendly for Facebook (dalvik.vm.heapgrowthlimit=100m is what helps Facebook to run more smoothly as a background process) in that games like Asphalt 8 are still playable with the 256m value, rather than dalvik.vm.heapsize=320m. But dalvik.vm.heapsize=320m / 384m is better for Real Racing 3 on High detail level, medium and low detail are fine with 256m.
@5:30pm - finished p6810 compile, uploading p6810 rom. Compiling p6800 rom now.
@3:35pm - doing a recompile of the p6800/p6810 with the adjusted Davlik VM settings, after which I will upload the rom's
@3:30pm - I finished my Davlik memory testing, I'm going with these values for my Build 1.5, a bit larger for the dalvik.vm.heapsize, as games like Real Racing 3 benefit from the larger value, and probably the Chrome Web browser does as well. The article recommended dalvik.vm.heapsize=174m, which is probably better if you have lots of smaller apps, but I'll optimize for some bigger apps using dalvik.vm.heapsize=320m. The dalvik.vm.heapgrowthlimit=100m seems to have given back more base memory, I can get over 460m of free Ram at times now.
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=100m
dalvik.vm.heapsize=320m
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=8m
@8:35am - Test Build 1.5 - GPS works - so Non-Pie blob support is working again! Just testing the new Davlik memory settings now.
@8:00am - p6810 build 1.5 test build completed, if it's working ok I'll upload it as Build 1.5, otherwise I'll have to investigate why the Non-Pie support is not working.
29 Sept 2015
- 7:50pm - Starting build 1.5 for p6810 - will test to make sure GPS is working before doing p6800 build.
-I've manually updated the Bionic libraries with the Non-Pie support, as the Bionic libraries in SlimLP Beta 0.8 had more changes to them then just the non-pie support additions from the previous library which Daniel had given me, which was basically the same Bionic Library as SlimLP Beta 0.7 with the Non-Pie additions.
- Found interesting article on Davlik Heap values and ART https://01.org/android-ia/user-guides/android-memory-tuning-android-5.0-and-5.1 - I am going to test build my next one with their recommended settings to see the difference in performance (they say this benefits facebook as well due to the way it uses memory).
28 Sept 2015
- Looks like Daniel pushed another change to danielhk/proprietary_vendor_samsung_smdk4210 for the Hotspot after I did the Build 1.4 yesterday - https://github.com/danielhk?tab=activity - so I think that when I compile Build 1.5, this will hopefully fix the hostpot as well. I
- Build's 1.3 and 1.4 have issues with GPS again. I will have to do a recompile, it seems like the non-pie support was not enabled for GPS in those builds. Builds 1.1 and 1.2 the GPS works fine.
27 Sept 2015
SlimLP Beta 0.8 - Build #1.4 - Build Date 20150927 - Download ROM from this URL
- Updated Device Tree's from Daniel, Ambient Sensor should be fixed
- Mobile Hotspot doesn't seem to be fixed
- GPS has broken (non-pie support) - It has on my p6810 - will have to do a recompile for Non-Pie support that got missed some how
@10:15pm - The compile with CONFIG_KEYBOARD_SEC_DOCK=m or CONFIG_KEYBOARD_SEC_DOCK=n failed due to the fact that this causes other issues with the Kernel code. The code would need some adjustments to make this work for us. Anyway, I'll keep on investigating trying to turn the initial value to on for the Hardware switch in the Language and Input settings error. I checked Daniels omnirom build, and he's not turning on the hardware switch, so he must be specifically enabling the Touch Keyboard in the code even if a hardware keyboard is listed as present (I have seen some old code examples of people doing this, but some of the variables are not present in the SlimLP code - so I can't just copy their examples without finding the rest of the additional code needed).
@10:00pm - I got a reply from a Galaxy Tab 2 developer, he told me how they overcame this same issue, they got the commit included into Cyanogenmod to make the Keyboard Dock driver a module, so for anyone who needs it, the module can be started as an init.d module. I am doing a compile now to see if this fixes the keyboard driver, if so I'll make it build # 1.5...
http://review.cyanogenmod.org/#/c/83499/
espresso10: build KEYBOARD_SEC_DOCK as module Our sec_keyboard driver does not properly unregister the input device when no dock is detected, which makes the system believe that a physical keyboard is present at all times, which prevents the software keyboard from being shown. Some user own a Keyboard-Dock and meight miss the ability to use the dock if it gets disabled completely. Building it as module gives the user the ability to add a simple init.d script to start the module at boot if they need it.
/kernel/samsung/smdk4210/arch/arm/configs/cyanogenmod_p6800_defconfig
Code change CONFIG_KEYBOARD_SEC_DOCK=y -> CONFIG_KEYBOARD_SEC_DOCK=m
/kernel/samsung/smdk4210/arch/arm/configs/cyanogenmod_p6810_defconfig
Code change CONFIG_KEYBOARD_SEC_DOCK=y -> CONFIG_KEYBOARD_SEC_DOCK=m
@9:41pm - p6800 build compiled, uploading now.
@7:47pm - p6810 build compiled and uploading, building p6800
SlimLP Beta 0.8 - Build #1.3 - Build Date 20150926 - Download ROM from this URL
- SlimLP Source code updated to Beta 0.8
- GPS has broken (non-pie support) - It has on my p6810 - will have to do a recompile for Non-Pie support that got missed some how
@3:04pm - p6800 build 1.3 uploaded. P6810 build 1.4 commenced.
@2:35pm - resetting Code base and Resyncing Daniels Device Library changes for Build 1.4 (Hotspot fix and Ambient Display fix)
@2:30pm - P6800 SlimLP Beta 0.8 build finished, uploading now (build 1.3)
@ 8:00am - P6810 SlimLP Beta 0.8 build finished and uploaded. Building P6800 rom. (My Rom build # 1.3)
- I've just looked at Daniels new Omnirom Change Log for 20150926 build and his new sources (which came out just after I started this new build) fixes the Wifi Hotspot and the Ambient Display issues. Once the first build of Beta 0.8 is compiled, I'll resync my Sources to get his updates and then build 1.4, which will include these fixes.
26 Sept 2015
5:30pm - I've just updated my SlimLP code base to Beta 0.8, and am recompiling my p6810 build. I'll leave it compile tonight and compile a p6800 build after that.
Next week I'll keep on tracking down this Soft Keyboard bug, where it's not initially enabled (I'm only going to try set the initial Toggle value to on - not try and resolve the false positive on the driver believing that there's a keyboard docked).
5:00pm - My testing has confirmed that this code only removes the hardware option (set to false and the hardware option re-appears), it doesn't set the hardware toggle to on. But I might be able to use this bit of code to help me start to find the option. I just need to find where the Default Value of this toggle switch is set, and then adjust the default to be turned on, instead of off.
2:30pm - I just had a chance to test the build, the value of config_forceDisableHardwareKeyboard = true, completely hid the Hardware option from the Input and Settings area, preventing the value from being changed. I am just trying a test build with the value of False, but I don't think this is going to turn on the value.... I'll have to try see if I can find where the Hardware Setting is kept (probably in the same part of the code) and work on some sort of fix.
8:30am - I've made a p6810 test build to see if it fixes the keyboard. I'll test it later today as I have to go out now.
I've set the config_forceDisableHardwareKeyboard to true via an overlay file (which overrides the default value of false - which I believe turns off the fix and makes things behave as if the extra code was not included). From what I understand from my reading, the keyboard issue is present because the default driver is wrongly reporting that a Keyboard dock is present. Which if you plug in a keyboard via usb, you see that it behaves like one is, the softkeyboard just gives you word predictions on screen, but no keyboard. So I think that is right. Changing that Hardware option in input corrects this wrong assumption and then the soft keyboard appears.
25 Sept 2015
10:43pm @ I think i might have found some code to fix the soft keyboard not working at startup issue at https://gerrit.omnirom.org/#/c/903/2
Edit: Looking over Cyanogenmod code, they have already implemented this fix, but SlimLP hasn't added it to their code base, so I have added it to the source code and am doing a compile now. The only thing I think I need to work out is if I need a true / false value for the config_forceDisableHardwareKeyboard parameter, but once I have that worked out, hopefully this should fix it.
24 Sept 2015
SlimLP Beta 0.7 - Build #1.2 - Build Date 20150924 - Download ROM from this URL
- Media DRM fixed for Google Play Movies / Youtube DRM based content (libraries from p3100)
- increased dalvik.vm.heapsize=320m - Hopefully should provide a bit more memory for Facebook / Facebook Messenger
@9:30pm - p6800 build is uploaded
@8:43pm (10:43am GMT)- Compile finished for p6800, uploading now
@7:00pm - Build #1.2 - Compiled p6810 build and am uploading. Compiling p6800 build
@10am - I fixed the Play Movies streaming issue. Using libdrmdecrypt.so from p3100 (https://github.com/TheMuppets/proprietary_vendor_samsung/tree/cm-12.1/p31xx/common/system/lib) - goes in the /system/lib, also the three libwv*.so files from (https://github.com/TheMuppets/proprietary_vendor_samsung/tree/cm-12.1/p31xx/common/system/vendor/lib) in the /system/lib folder, the libdrmwv...so file from (https://github.com/TheMuppets/propr...ee/cm-12.1/p31xx/common/system/vendor/lib/drm) in the /system/lib/drm folder and finally, in /vendor/lib/mediadrm (the vendor folder should really be a link to /system/vendor, not a seperate folder as it currently is in our builds), the libwvdrmengine.so from (https://github.com/TheMuppets/propr...-12.1/p31xx/common/system/vendor/lib/mediadrm).
- Next build if I will try incorporate this fix
23 Sept 2015
- I was having a bit of a play last night with Google Play Movies, as to why it doesn't stream. It seems that Lollipop (as compared to kitkat) requires /vendor/lib/mediadrm/libwvdrmengine.so and possibly a few other components. I have gotten a copy of this file from the exynos 4412 smdk files, but there are a few more components missing (this might not even be compatible with our exynos 4210 but its worth a try). But with this file in place, it no longer gives the device is unsupported message, it tries to start streaming and errors out. I had a quick look in the log and I think it also wanted another crypto .so driver file, so I'll see if I can find that driver as well. There's a large collection of samsung blobs at https://github.com/TheMuppets/proprietary_vendor_samsung
20 Sept 2015
- 1:25pm - 3:25am GMT - I tested GPS on my P6810 (wifi model) and it now works!
- 7:51am - 9:51pm GMT - p6800 build is uploaded.
Daniel has given me some feedback on the i815 and some other things I was wondering about, so I'll go read over his instructions and my code some time next week and see if I can work this out. Once I have it compiling i'll make an update. Thanks @daniel_hk
- 7:24am - 9:24pm GMT - uploading p6800 build. It should be there in the next 20 minutes.
19 Sept 2015 - 11:18pm - I've uploaded the P6810 build of the rom, I'm waiting on the p6800 build to finish compiling - going to sleep now, so that will probably be in the morning. I've had a report from a tester that the Package Installer was crashing on the p6800 build when trying to manually install an APK package. I haven't had this happen on my P6810 build, so if someone can test the new build and let me know if this is an issue still that would be great.
SlimLP Beta 0.7 - Build #1.1 - Build Date 20150919 - Download ROM from this URL
- Rebuilt rom with Bionic Library supplied by Daniel that has Non-Pie Blob / Driver support
- GPS working
- Manually copied RIL Libraries into /system/lib folder from Daniels latest Omnirom Build - Hopefully for the p6800 this should enable RIL / Sim Card support - Files copied from Omnirom build are as follows:
/system/lib/libreference-ril.so
/system/lib/libril.so
/system/lib/librilutils.so
/system/lib/libsecril-client.so
/system/lib/libsecril-client-sap.so
/system/bin/rild
19 Sept 2015 @ 7:14am - Checked my PC this morning and it failed with the same compile error again for the i815. I'll have to keep on looking.
18 Sept 2015 @7:55pm - 9:55am GMT - Clearing out my build folders to try a fresh compile of the i815 code in case some of the p6800/p6810 build code is causing issues. I'll probably post an update tomorrow on how this went. Once I can compile the i815 code properly, I'll start looking at the other issues.
Update: 10:48pm - it may have gotten past the error below now, during the build I noticed the following in the output... still a number of hours to go before the i815 compile finishes.
Code:
build/core/Makefile:46: warning: overriding recipe for target '/home/peter/android/slimlp/out/target/product/i815/system/lib/hw/sensors.exynos4.so'
build/core/base_rules.mk:550: warning: ignoring old recipe for target '/home/peter/android/slimlp/out/target/product/i815/system/lib/hw/sensors.exynos4.so'
15 sept 2015 @10:42pm - 12:42am GMT - My compile of the i815 code hit an error, I'll have to track it down tomorrow if I get a chance
Code:
make: *** No rule to make target '/home/peter/android/slimlp/out/target/product/i815/obj/SHARED_LIBRARIES/libinvensense_hal_intermediates/export_includes', needed by '/home/peter/android/slimlp/out/target/product/i815/obj/SHARED_LIBRARIES/sensors.exynos4_intermediates/import_includes'. Stop.
make: *** Waiting for unfinished jobs....
15 sept 2015 @5:38pm - 7 :38am GMT - p6800 rom uploaded
Around 7hr 15 min for my old e5400 CPU to compile the 21gb of output per device specific folder to build the p6800 rom (there's a common output, and then device specific output). I'm just about to start the i815 build... just moving my cm12.1 code folder off the drive to an external disk so I have enough room to build the i815 rom.
15 Sept 2015 @ 10:52am - 12:52am GMT - I've uploaded the p6810 rom, I'm currently compiling the p6800 rom and when that's done I'll compile an i815 rom
SlimLP Beta 0.7 - Build #1.0 - Build Date 20150915 - Download ROM from this URL
- Built from SlimLP Beta 0.7 Sources
- Bluetooth Fixed
- OpenGL ES values set to 2.0 values in /system/etc/build.prop
- Davlik VM settings adjusted to possible better values
- Compiled from Daniel's Github sources - check the local_manifest.xml to see which sources where used
- GPS and ASOP keyboard bugs still present, QS tile for torch not working.
- Google Play Movies only work if you download locally first then play, not streamed - I have tested this on other Android 5.1.1 roms on my p6810 and it's the same on all of them at the moment.
- GPS.exynos4.so (GPS driver) from Galaxy S2 i9100 / CM 12.1 rom in this build (it may or may not work with our Exynos 4 processor, but it's a PIE build of the GPS blob for Exynos 4, which means that I didn't need to modify the BIONIC libraries for Non-Pie support). I've uploaded the GPS exynos 4 blob to my Androidhost.com folder for Slim as well - Next build I try for my p6810, I'll use Daniel's older GPS blob's and enable non-pie. However with this PIE based GPS blob, I don't get any GPS Client communication errors / socket not open errors. So I might simply need a different gps config file for this to work
GApps:
Official SlimRoms GApps
Questions and Answers
Testing- Just a note at the moment, I only have a p6810 (wifi only model) so my testing is limited to this. I am compiling p6800 and i815 rom's based on @daniel_hk's github source tree's, doing the modifications that I do for my p6810 to compile. So if you want to test and let me know about p6800 and i815 issues that would be great
i815 - Hopefully in a week or two I'll have time to make a build once I sort out a compile error. Daniel's given me some feedback, I just need to find some time to look over it.
QS Torch - I'll try work out the code for this QS torch tile setting soon
Memory Settings - Interesting article on Davlik Heap values and ART on android 5.0 and 5.1 https://01.org/android-ia/user-guide...id-5.0-and-5.1. Give me some feedback on performance as i still think we can tweak ram a bit more.
No time frames on anything, I'll just do what I can when I can.
Sim card not detected
I tried the new rom on p6800 with no sim card error.
Thanks for reporting back, at least I know that it boots on the p6800. Next build I do for the p6800/p6810 I'll be enabling the Non-PIE blob support which should help with some of the older driver libraries for things like GPS and possibly the RIL library which might fix this error for you as well.
hot spot not working on p6800
dear sir,
I just flash the new 1.1 rom on p6800. Every thing was fine except the hotspot.
My phone can detect the hot spot by p6800, but cannot get connected.
Thank you so much for such a great works.
Wait so is beta 0.7 the newest or alpha 1.1
On beta0.7 now and very smooth
philipnzw said:
Wait so is beta 0.7 the newest or alpha 1.1
On beta0.7 now and very smooth
Click to expand...
Click to collapse
Beta 0.7 is the slim ROM teams designation of their ROM build status. Alpha 1.1 is just my own designation to say it's my test builds, that being my second build, once I have the bugs sorted I will call it stable.
p3dboard said:
Beta 0.7 is the slim ROM teams designation of their ROM build status. Alpha 1.1 is just my own designation to say it's my test builds, that being my second build, once I have the bugs sorted I will call it stable.
Click to expand...
Click to collapse
Aha
It's quite stable already
philipnzw said:
Aha
It's quite stable already
Click to expand...
Click to collapse
I've changed my personal Labelling to Build #, instead of Alpha, that way its less confusing
p3dboard said:
Questions and Answers
QS Torch - I'll try work out the code for this QS torch tile setting soon
Click to expand...
Click to collapse
i think this could be an issue with slimroms in general.
it wasnt working on slimbean last time i tried it and its currently not working on slimkat either. (im on daniels slimkat)
p3dboard said:
Automatic Brightness Sensor - Have to do some more testing - Turning off Automatic Brightness, allows for a greater range of brightness
Click to expand...
Click to collapse
this issue is also present on daniels CarbonLP for me. either its related or somethings wrong with my p6800 thats duplicated on your p6810.
even tho its stable according to some, i think ill wait for a gps update before trying this out.
its times like these i wish we could have the dual/multi boot functionality.
way better and easier for the community to help test out the new/experimental builds.
especially for people like me whos using the p6xx as a daily driver.
good luck to you sir.
HM i will try it and lett you know how it go on my P6800,the lollipop 5.1.1 from daniel,i dont know what is wrong,when the wi-fi is turned on,i cann not tell you how much the difference in performance is,when i turn it on,it become laggy unbearably,so i will check with this................
Still holding up well after installing some xposed modules
Turning on awesome player seemed to help with YouTube crashing randomly
Also, uploading a picture with fb messenger app crashes everything (need to hold down power button)
Think Daniel's roms didn't have this issue.
I might need to increase the maximum memory amount for apps in the Build.prop,i set it to 256m, the default is 384m, but i dropped that lower as when some apps got to that size the rom's can become sluggish. I have had another app (real racing 3) lock up while trying to upload a game profile. I will play with the values some more. These are set in the build.prop file under /system/etc i have posted about them before in one of the other rom threads. If you are comfortable playing with the settings you could put them back to stock values and see if that fixes things for you and you can let me know. Thanks, Peter
Lag
p3dboard said:
I might need to increase the maximum memory amount for apps in the Build.prop,i set it to 256m, the default is 384m, but i dropped that lower as when some apps got to that size the rom's can become sluggish. I have had another app (real racing 3) lock up while trying to upload a game profile. I will play with the values some more. These are set in the build.prop file under /system/etc i have posted about them before in one of the other rom threads. If you are comfortable playing with the settings you could put them back to stock values and see if that fixes things for you and you can let me know. Thanks, Peter
Click to expand...
Click to collapse
Something to REPORT,i dont know it this just on my tab or not,but,it doesn't matter do i use CyanogenMod 12 or Carbon,or this SlimLP,yesterday wehn i instaled Carbon,after 30min when i installed all my apps,the last one that i installed was Facebook,and when i set it,then it become unbelievably Lagg,and i then installed SlimLP,and didnt installed other apps just Facebook,and this Lagged to,just now it just restarted alone.......................is this just because of FB or what is it,i just cann not take it any more,when i see it,the best android was 4.0.1
Definitely Lollipop rom's are more memory hungry than Kitkat Rom's. I am enquiring with one or two other rom maintainers who say they have implemented some optimizations for devices with 1 Gb Ram, to see what changes they are adding to improve performance. So far the best performing Rom i find is still Slimkat 8.2, Android 4.4.4, but it maybe possible to tweak lollipop for better performance. I have read on the Galaxy s2 forum that Facebook is an app with issues on the s2 CyanogenMod 12.1 rom as well. I will do a bit of testing and hopefully with some input from some others we might be able to fix this, we really need a lollipop rom with low memory overheads. Have you tried Facebook on Daniel's omnirom builds? They are the closest to stock Android, and may work better
Edit: i just installed Facebook on my s2 phone with CyanogenMod 12.1 (Android 5.1.1) and it seems to be ok, just wanted to test it on another 1gb ram device. The s2 has about 20mb more usable ram than our galaxy tab 7.7 due to lower screen resolution. Anyway, we will see what we can do to try improve things, a bit of trial and error,playing around
p3dboard said:
Definitely Lollipop rom's are more memory hungry than Kitkat Rom's. I am enquiring with one or two other rom maintainers who say they have implemented some optimizations for devices with 1 Gb Ram, to see what changes they are adding to improve performance. So far the best performing Rom i find is still Slimkat 8.2, Android 4.4.4, but it maybe possible to tweak lollipop for better performance. I have read on the Galaxy s2 forum that Facebook is an app with issues on the s2 CyanogenMod 12.1 rom as well. I will do a bit of testing and hopefully with some input from some others we might be able to fix this, we really need a lollipop rom with low memory overheads. Have you tried Facebook on Daniel's omnirom builds? They are the closest to stock Android, and may work better
Click to expand...
Click to collapse
no,i didnt try omnirom,i just used Daniel's Cyanogenom and Carbon,and this Slim,but when i charge my p6800 i will instal omni and try it.
LeonardoD93 said:
no,i didnt try omnirom,i just used Daniel's Cyanogenom and Carbon,and this Slim,but when i charge my p6800 i will instal omni and try it.
Click to expand...
Click to collapse
Might wanna try fb lite
Always avoided the main app on lollipop roms,after fb the whole system just lags like mad
Fb lite is like a smaller version of the main app,the user interface is absolutely horrible,but hey it works~
Just letting you all know that I have a fix for the Google Play movies not streaming DRM based content. I've posted about it in my Change Log.
philipnzw said:
Still holding up well after installing some xposed modules
Turning on awesome player seemed to help with YouTube crashing randomly
Also, uploading a picture with fb messenger app crashes everything (need to hold down power button)
Think Daniel's roms didn't have this issue.
Click to expand...
Click to collapse
I just tested Facebook Messenger with the davlik memory value set at 320m, and it uploaded a photo fine in my test, no crash. So it may be a memory limitation. SlimLP seems to be lighter on Ram, it may even be ok with 384m, but 320m seems to working ok for me. Next build, I'll increase the /system/build.prop Ram value to at least 320m, possibly 384m.
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.