Related
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.0 (ICS), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
First time flashing CyanogenMod 9 to the Nexus S, or coming from another ROM?
Root the device and install ClockworkMod Recovery. Instructions are available here.
Perform a NANDroid backup of your current ROM.
Format the system, data & cache partitions of your device.
Perform a factory reset.
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Upgrading from earlier version of CyanogenMod 9?
Perform a NANDroid backup of your current ROM.
Flash CyanogenMod (your Google Apps will be backed up & restored automatically).
Issues?
Experience issues? Please provide the following info:
If the device was hard reboot, please provide the file "/proc/last_kmsg".
If the device was soft reboot or is "bootlooping", please run a logcat and provide the full output.
Please use Pastebin when possible.
Download Links:
CyanogenMod:
Latest version: V7 patch 0 (from v6.x to v7.x should be no need to make a clean install)
Download: link
Download: link Mirror
Download: No torrent already ( )
Download: link mirror ( by korumera Thanks )
MD5sum: bb2dc9139a90d5096afcb0aeefc9b48f
Night Builds can be found here: http://get.cm/?device=crespo ChangeLog: http://cm-nightlies.appspot.com/?device=crespo
Click to expand...
Click to collapse
Old Version: V6 patch 0
Download: link
REMEMBER TO INSTALL GAPPS ALWAYS AFTER INSTALL AND UPDATED ROM.
For those who want to install faceunlock read this: https://plus.google.com/u/0/111722836277981844223/posts/2LthtkGD8aY
TO MAKE A CLEAN INSTALL. LOOK HERE
REPORT ISSUES ONLY IF:
You made a clean intall
You use the default kernel
You have not installed new framework
You have confirmed the issue is there with default CPU speed
Take a look for those willing to restore bootanimation. That is the new bottanimation posted here ( sorry one of the users posted but not remember the nick "message me" ) and I added to recover for those who have selected no boot animation on previous versions: http://goo-inside.me/devs/kalimochoaz/Others/CM_Animation.zip flash it from recovery
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
CHANGELOG
For those who preffer to continue on alfa 13, here is an update ( alfa 14 ) Alfa 14 can be installed over alfa 13 without clean
ROM: http://bit.ly/CM9Alfa14
GAPPS: http://download.clockworkmod.com/test/gapps-ics-20111128.zip
Those files are not compatible with Alfa 15 and up
Click to expand...
Click to collapse
NEW on alfa 14:
Notification LED issue solved.
Updated code
Updated T9
Voodoo color changes to v1
NEW ON ALFA 15:
Kernel 3.0.8
LED notification is on
T9 in call patched from alfa 13
LED Keys not turning ON when screen is off and you touch the screen
NEW ON ALFA 16:
Added voodoo color control
Updated code for some issues
NEW ON ALFA 17:
Added voodoo sound control
Added MusicFx
Updated code for some issues
Superuser corrected, now works without issues
[...]
NEW ON ALFA 18:
Overclock kernel ( use setcpu )
Removed MusicFX since there is DSPManager
System updated. Advanced users can now use compcache
[...]
NEW ON ALFA 20:
Overclock kernel up to 1400 ( use setcpu )
Removed software egl for now until we find a reason on why is here.
Added DeepIDLE ( Thanks to Ezekeel ) also some other kernel changes.
Added Touch to focus on camera. Now if you touch the screen it will make a previous focus.
[...]
NEW ON ALFA 20.p1:
Readded Trebuchet
NEW ON v1:
Code updated to CM
Review kernel code to make stable
Upgraded kernel to 3.0.17
No more flickering on turn on/off
Added all sound options to DSPManager. ( voodoo app is not compatible, use the options in device settings to control colors and options in dsp manager under wm8994 to control sound )
Added zram option.
Optimized for battery life and speed.
NEW ON v1.1:
Default RGB gamma set to 0 ( choose the best gamma you want at device settings )
NEW ON v2.0:
More kernel upgrades
code updated
Added some overclock patches for stability
New music app
Added New settings
Added new governor lulzactive. I suggest you to use this one for depending the use of your phone.
New Settings icons
No more flickering on turn on/off the screen
Modified kernel for kms
lulzactive as default governor with some tweaks.
Added setting to control kms ( settings/ performance / memory ) You will win memory on your devices
Default values for ksm set to reduce cpu usage
more system updates
New option to control lulzactive governor. Look on Settings/advanced
Reapaired error at multiplier colors
Cleaned the code at device options
Added Torch working app
Voodoo wm8994 DSP corrected into DSPManager to avoid sporadic FCs
NEW ON v3.0:
Added Torch, now with widget ( widget for the screens, not for the drawer app )
Added option to camera to take photos by pressing power button
Updated Code to 20.02.2012
Added code to display %battery
Removed Lulzactive
Solved the caller app issue ( after some calls you received and FC on number pressing on old releases )
Updated kernel 3.0.21 & new kernel speeds
Changed various settings
NEW ON v3.3:
Added new bootanimation
Added turn on with volume
Solved some DSP 8994 issues settings
Updated kernel 3.0.22
Changed various settings
NEW ON v3.4:
Corrected bootanimation size
NEW ON v4.0:
New kernel 3.0.25
Updated code to 22.03.2012
NEW ON v5.0:
New kernel 3.0.27
Updated code to 05.04.2012
Kernel and code based on 4.0.4
NEW ON v6.0:
Deep idle is now stable, at least on our tests.
Gamma hack is new, a new idea with great colors Check the CM preset button on gamma hack and on multipliers.
More battery time.
Code updated
...
NEW ON v7.0:
Deep idle is now tested and stable.
Ne preset screen with gama/multipliers combinations (thanks to ale.landra91 cpaixao and malycomix.
More battery time.
Freq issues solved on deepidle
Better 1.2GHz OC stability reached
...
Q/A Post
Q/A:
I have an extrange green color at boot and when I have automatic brightness setted, what can I do:
Go to crespo setting and change in gamma the values: ( by default values on google are 0,0,0 but I suggest you to explore the best you like) for me is:
RED: 50
GREEN: 46
BLUE: 46
How can I do to make a clean install?
Read that post http://forum.xda-developers.com/showpost.php?p=20485148&postcount=146
I have 2 times gallery app repeated and is buggy:
Install again gapps. This happens because you updated and no installed gapps after installing.
I need to go root with adb, but it doesn't work:
adb root
After you can type "adb remount" or simply "adb shell" and you are root.
How can I do to enable KSM?:
Settings -> performance -> Memory Management -> Kernel Samepage merging ( KSM )
Changelog
ALPHA 15:
Kernel 3.0.8
LED notification is on
T9 in call patched from ALPHA 13
LED Keys not turning ON when screen is off and you touch the screen
4G working - 4g power widget included
MMS receive working
ALPHA 16:
Kernel - Voodoo Color Control
SuperUser - Updated for ICS
Questions
Please do a complete wipe/clean prior to installation, even if currently running an ICS ROM. Many changes between builds prior to 4.0.3 and this build.
Cleaning
Wipe Data/Factory Reset
Wipe Cache Partition
Mounts and Storage -> Format /system
Mounts and Storage -> Format /boot
Advanced -> Wipe Dalvik Cache
Launcher is Laggy
From home screen -> Preferences
Drawer -> Uncheck "Join with Apps"
Thanks...; p
Inviato dal mio Nexus S usando Tapatalk
Thanks a lot! Will try!
Thanks, been waiting foe this all weekend
Sent from my Nexus S using xda premium
At last..along waited..lol
Sent from my Nexus S
Thank you!!!!!
Hot diggity!
Edit: Higher speed mirror:
Alpha 15
ROM: Links removed. Deprecated.
Gapps: Links removed. Deprecated.
Gapps v2: Links removed. Deprecated.
Another Mirror on page three. Enjoy.
downloading now!
Sent from my Nexus S 4G using XDA App
Thank you very much sir. Downloading now
[oICSv36] - [3.0.8GLaDOS-CFS-v2.0]
i assume the rom is fully rooted?
renna1992 said:
i assume the rom is fully rooted?
Click to expand...
Click to collapse
Of course.
Sweet..downloading also ya boyeee
Sent from my Nexus S 4G using xda premium
Thanks for your work!
Sent from my Nexus S 4G using xda premium
If anyone can't access multiupload or would like a high-speed mirror, let me know.
will you add this to rom manager?
Sent from my Nexus S
sixstringsg said:
If anyone can't access multiupload or would like a high-speed mirror, let me know.
Click to expand...
Click to collapse
Please ..................
{
"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"
}
arter97's Linaro-built CyanogenMod 10.1.3 based ROM V4 for Galaxy S3 [Android 4.2.2]
* Tux is a penguin character and the official mascot of the Linux kernel.
* Above character is a redesigned Tux by @irendah07
● "What is this?"
'this' is a custom ROM built for Galaxy S3 based on CyanogenMod 10.1.3 code.
The main differences are 'Optimizations' and 'Features'.
I'm a huge fan of stock AOSP and I developed this without screwing up stock CyanogenMod's feeling.
You won't find any major UI differences.
I know that this article is very long. Please take your time on reading this.
You should at least know what this ROM offers you. Right?
● Features
Performance improvements & optimizations
- Built with latest Linaro stable toolchain with lots of optimizations flags
- Built with latest Java Development Kit(JDK) - (7u45)
- All *.jar, *.apk files within the ROM are uncompressed, zipaligned for maximum read speeds
- Optimized all images within the ROM by image_optim
- fstrim, remount all partitions with discard option on boot
- FSTRIM is performed while installing
- Optimize all /system, /cache, /data partitions with journal_data_writeback while installing
- Use Exynos optimized memcpy, memset
- Light build.prop optimizations
New features
- ListView animation by team ThinkingBridge (ignore others credit. This was originally designed and coded by ThinkingBridge)
- Camera Shutter Sound control
- Status-bar Quick Peek with Timeout control
- Status-bar transparency control with seperate Lock-screen transparency from Carbon
- 0% transparency on notification icons (icons on the status-bar are basically clearer)
- HALO from ParanoidAndroid (not 2.0)
- Screenshot Quick Trash
- Improved download/upload animation (just go to market and download anything)
- Vertical Electron-beam animation
- Animation scale in Development settings now has additional 0.6x ~ 0.9x (for those who thinks 0.5x is too fast and 1.0x is too slow)
- f2fs supported installation (for those who uses f2fs file-system on /system like me)
- Multitasking UI is now fullscreen
- LED notification behavior is same as CyanogenMod 10.1.0 (turn off the screen, the LED will go off)
- bootanimation is from http://forum.xda-developers.com/showthread.php?t=2429613
- Removed CMstats, CMupdater
- Full, proper exFAT, NTFS support
- No kernel is included in this build since kernels doesn't support gcc 4.8 out-of-the-box.
- Gesture based lockscreen security
- Pinch to enable expanded desktop added to Trebuchet (go to Settings->Launcher->General)
- AOKP custom system animations (go to Settings->System->AOKP Custom System Animations)
- added ADB over network QuickSettings Tile
- back-to-kill timeout control by neighbors28 from DokDo ROM
- DMB functionality for SHV-E210S, SHV-E210K (needs kernel-side support)
● What you need to know
- Even with all of those changes above, you still won't find any major UI differences.
- Linaro toolchain offers many optimizations than the stock Google's toolchain.
Also, the latest gcc 4.8 is used. Basically, this ROM has gcc 4.8 + Linaro optimizations.
Optimization flags includes : -w -s -pipe -O3 -marm -munaligned-access -mcpu=cortex-a9 -mtune=cortex-a9 -march=armv7-a -mfloat-abi=softfp -mfpu=neon -fno-unsafe-math-optimizations -mvectorize-with-neon-quad -fgcse-lm -fgcse-sm -fsched-spec-load -fforce-addr -fno-tree-vectorize -fno-tree-slp-vectorize -fno-defer-pop -fmerge-constants -fmerge-all-constants -fgcse-after-reload -fno-unsafe-loop-optimizations -fomit-frame-pointer -finline-functions -funswitch-loops -fpredictive-commoning -fivopts
-ffast-math has been explicitly disabled due to causing major and minor problems here and there across the entire ROM.
- Java Development Kit(JDK) 7 offers more stable, secure and optimized result than previous versions.
The latest 7u45 has been used.
- image_optim(https://github.com/toy/image_optim) is an image optimizer.
It can reduce image's size up to 95%. It will make the image load faster.
image_optim has, literally, took 26 hours to optimize the entire ROM.
- Uncompressed *.jar, *.apk will result in faster read speeds and reduce CPU loads by skipping decompression unlike any other ROMs out there.
It, of course, will use more space than stock CyanogenMod ROMs.
This ROM + optimized gapps will use about 680 MB in size.
- FSTRIM is a trim-like functionality on SSDs.
http://www.xda-developers.com/android/yet-another-reason-to-update-to-android-4-3-trim-support
- No kernel is included in this build since kernels doesn't support gcc 4.8 out-of-the-box.
Please use other 3rd-party kernel or stock CyanogenMod 10.1's boot.img.
- journal_data_writeback is an option to EXT4 partitions.
It will write datas to RAM first and flush it later. It will increase write speed dramatically.
- ListView is originally designed and coded by the team ThinkingBridge and can be controlled from Settings -> System.
Other ROM devs mostly has their credit written wrong. Please give proper credit to the original author!
- Camera Shutter Sound can be controlled from Settings -> Sound.
Please note that disabling the Camera Shutter Sound can be illegal in some areas.
- Status-bar transparency is cherry-picked from Carbon ROM and can be controlled from Settings -> Status Bar.
Lock-screen transparency has its separate control.
- HALO is cherry-picked from neighbors28's Github who ported HALO to DokDo ROM from ParanoidAndroid.
Credit goes to neighbors28 and other DokDo ROM developers and ParanoidAndroid ROM developers.
(Unfortunately, HALO included in this ROM is not 2.0 yet. Maybe not forever.)
- Light build.prop optimizations only has :
browser.tioptimization=true
dalvik.vm.execution-mode=int:jit
dalvik.vm.verify-bytecode=false
debug.performance.tuning=1
persist.sys.purgeable_assets=1
ril.category.delay=0
ro.config.nocheckin=1
ro.gpu.driver=1
ro.HOME_APP_ADJ=1
ro.HorizontalBUA=true
ro.HorizontalVVM=true
ro.kernel.android.checkjni=0
ro.kernel.checkjni=0
ro.media.enc.jpeg.quality=100
ro.product.gpu.driver=1
ro.ril.spender.bending=1
video.accelerate.hw=1
wifi.supplicant_scan_interval=180
windowsmgr.max_events_per_sec=90
● FAQ (Frequently Asked Questions)
Q : What is Linaro and why should I care about them?
A : Linaro is a not-for-profit engineering organization consolidating and optimizing open source Linux software and tools for the ARM architecture. It's widely known to provide the best optimized toolchain sets for arm-eabi and Android. Not only can it bring more faster binary, it can also bring stable, more bug-fixed binary as well. I care compiler optimizations more than the Android source code itself. Since compiler optimizations can speed up the same source code up to 5x, I hunted a lot for the best optimization flags available for Android. As a result, this ROM is speedier, more reliable than other ROMs that uses stock Google's toolchain.
Q : What about Linaro 4.9?
A : Linaro toolchain is built on the official GNU's code. Since GNU hasn't even finished on gcc 4.9 yet, Linaro 4.9 can be considered unstable. I'll work on it when GNU officially releases gcc 4.9.
Q : Can you teach me how to build ROM using Linaro toolchain?
A : There are tutorials of how to build ROM using Linaro toolchain on XDA already. Google is your friend.
Q : Is this ROM open source?
A : For selective parts, yes. Framework and Settings are available on http://bitbucket.org/arter97 . Don't repo init towards my repository. It doesn't have all repositories for full ROM build.
Q : No plans for CyanogenMod 10.2?
A : Yes, I do have plans on rebasing on CyanogenMod 10.2. I'm waiting for CyanogenMod 10.2's source code becoming bit more stabilized.
Q : Can I install your ROM on top of CyanogenMod 10.2 without factory reset?
A : No. Upper versions of Android's data are not compatible with older versions. You have to do a full data wipe in order to install my ROM on top of CyanogenMod 10.2.
Q : I got stuck on Galaxy SIII logo HELP!!!
A : Let me say it again, this ROM DOES NOT includes any kernel. Since kernel built with gcc 4.8 doesn't boot at all, I decided to remove kernel out of this ROM. Please use other kernel.
Q : What is F2FS?
A : F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk at Samsung for the Linux operating system kernel. I use a custom-kernel that has F2FS support and I use my /system, /cache, /data with F2FS. F2FS support on this ROM is mainly for me Please don't ask me how to use F2FS.
Q : Some app crashes!
A : I won't get any sort of bug reports on app crashing on my ROM. My ROM uses Linaro and it can break some compatibility between userspace applications. Popular example, Handcent SMS. And it will not be fixed.
● Supported devices
- GT-I9300
- SHW-M440S (Korean 3G variant)
- SHV-E210S (Korean SK-LTE variant) (Fully applies telephony patches)
- SHV-E210K (Korean KT-LTE variant) (Fully applies telephony patches)
● Installation
- Download ROM from http://d-h.st/users/arter97/?fld_id=25066
or Downloads tab on the top
(Supported device All-In-One zip installation file)
- Download gapps from http://d-h.st/VtQ
(Checkout http://forum.xda-developers.com/showthread.php?p=45406214 for more information on my gapps. It's also uncompressed and optimized. I highly recommend to use my gapps with my ROM.)
- Download kernel
- Use Clockworkmod or TWRP
- Flash ROM, gapps, kernel in order.
- Enjoy!
● To do
- Korean translation
- Increase volume steps
● Disclaimer
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
- No mirrors are allowed. Please ask me if you need any mirrors.
- Do not use files within my ROM and redistribute or edit.
- Redistribution or modifications are not allowed.
● Thanks to
- @irendah07 for the stylish drawing
- CyanogenMod (https://github.com/CyanogenMod)
- ParanoidAndroid (https://github.com/ParanoidAndroid)
- DokDo(neighbors28) (https://github.com/DokDo-Project)
- lion0738 (https://github.com/lion0738)
- Linaro (http://www.linaro.org)
- ThinkingBridge (https://github.com/ThinkingBridge)
- Carbon (https://github.com/CarbonDev)
- Der-Schubi (https://github.com/Der-Schubi)
- gal3 (갤3)
Comments are always welcomed!
Please hit "Thanks"!
XDA:DevDB Information
arter97's Linaro-built CyanogenMod, a ROM for the Samsung Galaxy S III I9300
Contributors
arter97
ROM OS Version: 4.2.x Jelly Bean
Based On: CyanogenMod
Version Information
Status: Stable
Current Stable Version: V4
Stable Release Date: 2013-11-07
Created 2013-09-19
Last Updated 2013-11-07
Changelog
● Changelog
- V4 : compiler option -funroll-loops has been removed; it was causing weird issues such as suddenly-fast-playing bootanimation.
built using Linaro toolchain 2013.10
built using JDK 7u45
host has been upgraded from Ubuntu 12.04 to Ubuntu 13.10 with gcc 4.8.2
dalvikvm, libdvm has been compiled with -ffast-math option for faster java runtime
--- This will be most likely the end of CyanogenMod 10.1 release. Since CyanogenMod 10.2 has a stabler M source tree, arter97 ROM will be getting rebased for Android 4.3 ---
- V3 : compiler option -fno-fast-math added to completely disable -ffast-math, -fmodulo-sched option removed; this will drastically improve system stability. (+ fixes video recording, WebKit parsing errors)
added -funroll-loops -fivopts compiler options to gain performance
built using JDK 7u40
used blobs from TheMuppets
added AOKP custom system animations (go to Settings->System->AOKP Custom System Animations)
fixed SHV-E210 variant's Airplane mode switch issues
Gallery2: reduce the latency between cam&camcorder switch
partial KO translations by lion0738
fade recents thumbnail to transparent earlier
show Expanded desktop toggle at the lock screen as well
play lock screen sound sooner
added ADB over network QuickSettings Tile
added back-to-kill timeout control by neighbors28 from DokDo ROM
- V2 : rebased on CyanogenMod 10.1.3 stable (adds CMAccount)
Revert Vold changes from Android 4.3; it may cause external SDcard mounting errors resulting in com.android.media force closes.
Added 01fstrim to init.d to replace Vold functionality of fstrim (remounts partitions with discard option, fstrim /system, /data, /cache; checkout adb logcat | grep arter97)
Focal has been removed; please download it from Google Play
Superuser deamon has been removed to provide more free resource to the system
added "Gesture based lockscreen security"
apns-conf.xml updated for SHV-E210
disabled additional MMS patch for SHV-E210 since it was causing SMS sending errors
back-to-kill timeout adjusted to 0.75s
misc Trebuchet changes to improve responsiveness
Pinch to enable expanded desktop added to Trebuchet (go to Settings->Launcher->General)
- V1 : initial release
Known issues
● Known issues
- As of V2, CMAccount has been added and it can cause FC loop on initial setup for some users.
After clicking like crazy, OK button on the FC message, you will be able to bypass the FC.
Sorrt for the inconvenience! But it looks like a source-code issues up from CyanogenMod
reserved
reserved #3
1 question : is navbar included with removal of 3-dot menu overflow button ?
if not, then please add it, and fix bug that 3-dot menu overflow button doesn't go off when nav bar is enabled.
this bug in all cm10.1 roms.
RohanAJoshi said:
1 question : is navbar included with removal of 3-dot menu overflow button ?
if not, then please add it, and fix bug that 3-dot menu overflow button doesn't go off when nav bar is enabled.
this bug in all cm10.1 roms.
Click to expand...
Click to collapse
Navbar is not included at all. (And I don't have it planned)
If you want to enable it, you have to do a build.prop trick.
Can you give me a open-source ROM address that has that 3-dot fixed?
Thank you for this ROM! Can you tell me if the ROM has a good camera (like no FC etc bugs etc) and also if there are any graphic glitches etc like some other CM roms?
Thanks again for your work!
zadusimple said:
Thank you for this ROM! Can you tell me if the ROM has a good camera (like no FC etc bugs etc) and also if there are any graphic glitches etc like some other CM roms?
Thanks again for your work!
Click to expand...
Click to collapse
What you've asked is identical to official CyanogenMod 10.1.3.
As of a personal experience, I haven't had any issues with the stock Camera app.
Graphic glitches are barely noticeable.
(Not like early CM-10.2 stage)
Sent from my SHV-E210S using xda app-developers app
A dumb question. Why based on 10.1? CM ditched 10.1 alltogether? Why not move to 10.2, it's stable now, and the glitches are gone? I'd love to try your rom, the feature list is amazing (I really want to try F2FS) as soon as you move to 10.2 CM base.
granets said:
A dumb question. Why based on 10.1? CM ditched 10.1 alltogether? Why not move to 10.2, it's stable now, and the glitches are gone? I'd love to try your rom, the feature list is amazing (I really want to try F2FS) as soon as you move to 10.2 CM base.
Click to expand...
Click to collapse
Because I want "stability".
If CyanogenMod 10.2 is stable, they would already put a "M", "RC", or "stable" tag.
They didn't.
I consider it unstable at the moment.
It's a quite big pain in the a** to build a ROM that's based on nightly since I'm not good on maintaining Git.
But, I do understand you.
If I have more free time, I'll try to
About F2FS, it's a serious journey both to you and the device.
Of course you need a FULL device wipe and you need an appropriate kernel, ROM and recovery.
What this means is you are stuck using one kernel, one ROM, one recovery.
(version may vary)
I make all three of them so I am free to use F2FS on my device.
But you, sometimes, may want to try other? Then you are in big trouble.
If you want your life to be more easier to live, I recommend not to try so
com.andriod.media force close
adilrenzu said:
com.andriod.media force close
Click to expand...
Click to collapse
Which ROM were you using before?
Sent from my SHV-E210S using xda app-developers app
arter97 said:
which rom were you using before?
Sent from my shv-e210s using xda app-developers app
Click to expand...
Click to collapse
cm 10.1.3 rc2
adilrenzu said:
cm 10.1.3 rc2
Click to expand...
Click to collapse
Can you tell me
Kernel/gapps/other mods you've flashed
Sent from my SHV-E210S using xda app-developers app
arter97 said:
Navbar is not included at all. (And I don't have it planned)
If you want to enable it, you have to do a build.prop trick.
Can you give me a open-source ROM address that has that 3-dot fixed?
Click to expand...
Click to collapse
latest rootbox (10.1) builds have 3 dots fix, and temasek's builds based on 10.2.
.
plz plan for nav bar.
arter97 said:
can you tell me
kernel/gapps/other mods you've flashed
sent from my shv-e210s using xda app-developers app
Click to expand...
Click to collapse
no mods or gapps but i flashed googy max kernel, may b that's the problem, cant you make it compatible with this kernel please
adilrenzu said:
no mods or gapps but i flashed googy max kernel, may b that's the problem, cant you make it compatible with this kernel please
Click to expand...
Click to collapse
i just flashed temasek kernel and not start just w8 on the bootanimation :S
FINEEEEE said:
i just flashed temasek kernel and not start just w8 on the bootanimation :S
Click to expand...
Click to collapse
I think this rom is compatible with only the kernel which support F2FS.
Sent from my GT-I9300 using XDA Premium 4 mobile app
adilrenzu said:
I think this rom is compatible with only the kernel which support F2FS.
Sent from my GT-I9300 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
uhmm thx then what kernel are compatible with F2FS?..
FINEEEEE said:
uhmm thx then what kernel are compatible with F2FS?..
Click to expand...
Click to collapse
I dnt know. I hv seen this word first time.
Sent from my GT-I9300 using XDA Premium 4 mobile app
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.
Disclaimer: Flash at your own risk! Backup your data before flashing! I am not responsible for bricked devices, World War III or your exploding cats!
Warning: The SGP611 images are not tested, but just built by me, as I do not own the device. But as the two devices are the same except for the 4G Modem, it should work. If not, please let me know.
About:
As my beloved SGP621 was just collecting dust, I decided to try porting Android 7.1 AOSP onto it. That worked well, so I moved on to CM 14.1 and now LineageOS
And voila, with a few tweaks here and there, it works (for the most part). But this is still considered BETA, so be warned and flash at your own risk. This will most likely replace the CM14.1 from the thread here, so the Changelog will also be continued on here.
What works:
- Display
- Sound
- WiFi
- 4G Data
- Bluetooth
- Camera (Taking Pictures and Video works, but focus does not work)
- NFC (somewhat flakey)
- LED
- Magnetic Cover Sleep/Wake
- Double-Tap to wake
- LiveDisplay
- SELinux enforced
- FM Radio (only minor glitches remain)
- AptX and AptXHD BT support
What doesn't work:
- Audio Volume has some issues (Loudest in the middle of the slider, than does not change after.)
- QuickCharge (Implementation to high a risk [Overheating], will leave it out for now.)
- You tell me
If your battery depletes rapidly, please disable NFC and check if it betters things. Then comment here, so I can look into it.
Flashing from CM14.1 (This should no longer be needed, as everyone should be updated by now):
If you have CM14.1 from the other thread installed, and want to upgrade, you need to take special care and follow the instructions here or you could end up with a bootlooping device. Anyways, as always, before you try to upgrade, make a backup. I repeat, MAKE A BACKUP! LineageOS is now enforcing SELinux, which leads to all kinds of complications, but makes the device more secure in the end and is well worth the extra effort needed. So lets get to it then.
First you need to have twrp recovery, as cm recovery is, for some reason we have not been able to figure out yet, not capable of installing GApps to the device. After that, flash the update.zip any way you want (via SD or sideload) and DIRECTLY after flash GApps (if you use them. If not you should be good to go). If you forget to flash GApps you will end up in a bootloop. But do not panic, it can be fixed by (you may have guessed) rebooting back into recovery and flashing GApps.
Flashing:
If you installed the recovery to the FOTAKernel partition then, while booting, get your device into recovery mode, by hitting VolUp multiple times once the LED flashes purple. Do so until it turns orange. (If you already have another recovery installed, boot into it.)
Now select install from adb sideload and from your computer issue:
Code:
adb sideload lineage-14.1-(DATE)-UNOFFICIAL-Lowtraxx-scorpion(_windy).zip
gapps:
Lineage 14.1 was tested with open gapps for Nougat 7.1 arm (nano confirmed working, others could be problematic)
Tips for better battery life (obsolete):
I installed Naptime to trigger deep doze as soon as the tablet goes to sleep. I also enabled zzmoove cpu gov and noop scheduler in the kernel options. Because of the high display brightness. This leads to me getting standby battery consumption of around 1.2% per hour (measured with GSam Battery Monitor) which is nearly the same amount I got with stock.
Changelog (LineageOS):
02.08.2017 - V8:
- Newest Lineage, Sony and Android Sources
- Android June/July security patches
- Small fixes everywhere
06.06.2017 - V7:
- Integrated new RQBalance-PowerHAL and librqbalance from Sony's GIT
- Newest Lineage, Sony and Android Sources
- Android May security patches
- Small fixes everywhere
27.04.2017 - V6:
- Newest Lineage, Sony and Android Sources
- Android April security patches
- Small fixes everywhere
11.03.2017 - V5:
- Newest Lineage, Sony and Android Sources
- Android February security patches (addendum)
- Audio volume fixes (finally) thx to @dontbelive
- Lots of Audio enhancements (but still lots to do)
- Support for AptX and AptXHD
- More FM fixes (should be mostly stable now)
- Sleep improvements and kernel simplification (less log clutter and removal of unneeded drivers)
05.03.2017 - V4:
- Newest Lineage, Sony and Android Sources
- Android February security patches
- Updated to newest Sony and QCom blobs (crash fixes for Adreno etc.)
- FM and Bluetooth now work independent of each other and can be on at the same time (still some glitches)
- Sleep improvements and kernel simplification (less log clutter and removal of unneeded drivers)
- Fixed NFC glitch that was introduced in V3
19.02.2017 - V3:
- Newest Lineage, Sony and Android patches
- Updated to newest Sony and QCom blobs (crash fixes for Adreno etc.)
- Video recording fixed (works most of the time now)
- Switched to Open Source GPS implementation
10.01.2017 - V2:
- Newest Lineage, Sony and Android patches
- Update to newest Nougat with Jan Security patches
- NFC fixes (Worked mostly reliable in my tests and no Log Spam)
- Many SELinux changes
05.01.2017 - V1:
- Switch to Lineage Sources
- Newest security patches and fixes by Sony, QCom and Google
- Camera now records video
- SELinux is now enforced
- GPS on SGP611 should now work reliably (thanks koron393)
- Bluesleep wakelock should be gone and device should deep sleep now
Changelog (CyanogenMod):
21.12.2016 - V4:
- Newest CM, Sony and Android sources
- Security patches
- Lots of UI fixes
- Support for SDCardFS
- Support for LiveDisplay
08.12.2016 - V3:
- Updated to Android 7.1.1 (NMF26O)
- Updated to newest sources (CM and Sony)
- Added workaround for charging wakelock (thanks rcstar6696)
- FM Radio works (only if Bluetooth is off, breaks if BT is on while Radio gets enabled)
04.12.2016 - V2.1:
- Updated to newest sources (CM and Sony)
- Added UHS SD-Card fix from koron393
03.12.2016 - V2:
- Updated to newest CM14.1 sources
- Updated to newest Sony kernel and driver sources
- Integrated Widevine DRM for Play Movies
- Lots of fixes and enhancements
- Better battery life
- Lowered user configurable mimimal brightness
02.11.2016 - V1:
- Initial release: Everything except Camera and Radio is working. Camera uses HAL1.
Thanks:
- Sony, for providing awesome AOSP support on github
- alviteri for providing me with pointers and help on my porting issues
- koron393 for the UHS SDCard fix
- dontbelive for the Audio fixes from his StereoMod here
Downloads:
There is a Bug in the bootimages of V8, that prevents USB data from working. After flashing the Full ROM, please reboot to bootloader and fastboot flash the corresponding fixed boot.img
V8 - GDrive - LineageOS14.1 Scorpion (SGP621)
V8 - GDrive - Fixed Boot Image Scorpion
MD5: 2ca53a92c40b60be28c0078dd0c2e00b
SHA1: f5d963eff2b45cb1c52bc74ae7955d9162d17be3
V8 - GDrive - LineageOS14.1 Scorpion Windy (SGP611)
V8 - GDrive - Fixed Boot Image Scorpion Windy
MD5: 9b223ed474427c8628d0d8904efdf9ca
SHA1: 0e64a01a8d204e951a1f3c87ed4ba45eec68c919
Older Downloads:
V7 - GDrive - LineageOS14.1 Scorpion (SGP621)
V7 - GDrive - LineageOS14.1 Scorpion Windy (SGP611)
V6 - GDrive - LineageOS14.1 Scorpion (SGP621) Only use if you know how to apply the NFC fix from here
V6 - GDrive - LineageOS14.1 Scorpion Windy (SGP611) Only use if you know how to apply the NFC fix from here
V5 - GDrive - LineageOS14.1 Scorpion (SGP621)
V5 - GDrive - LineageOS14.1 Scorpion Windy (SGP611)
V4 - GDrive - LineageOS14.1 Scorpion (SGP621)
V4 - GDrive - LineageOS14.1 Scorpion Windy (SGP611)
V3 - GDrive - LineageOS14.1 Scorpion (SGP621)
V3 - GDrive - LineageOS14.1 Scorpion Windy (SGP611)
V2 - GDrive - LineageOS14.1 Scorpion (SGP621)
V2 - GDrive - LineageOS14.1 Scorpion Windy (SGP611)
V1 - GDrive - LineageOS14.1 Scorpion (SGP621)
V1 - GDrive - LineageOS14.1 Scorpion Windy (SGP611)
Reserved...
Awesome - Thank You So Much !!!
installed on SGP612 - so far no problems...
I seem to be the old man out when it comes to GPS. My 611 breaks GPS in LineageOS, AICP and Resurrection Remix roms. I'm going flash it back to stock, then try your rom again and see if that fixes it.
camera could't auto focus issue still occur. Is any fix on this?
Your rom is working fine. I reverted back to stock, flash your rom + opengapps. GPS is not broken, the GPS Test is either broken or at least is on Nougat.
smallballl said:
camera could't auto focus issue still occur. Is any fix on this?
Click to expand...
Click to collapse
Still only manual focus. Would need changed blobs for autofocus to work afaik. Highly unlikely that those will be provided by Sony anytime soon.
SGP612. I successfully upgraded from your cm-14.1 build using TWRP 3.0.2. I flashed in a row from internal storage:
lineage-14.1-20170104-UNOFFICIAL-Lowtraxx-scorpion_windy.zip sha1sum: 6abece15341913131e34763d0547d16d489b9217
open_gapps-arm-7.1-nano-20170105.zip
Then wiped dalvik cache. Finally rebooted.
Many thanks once again. Great job. Amazing ROM
Note: GPS doesn't function without gapps - I flashed my tablet and then install LineageOS then installed OsmAnd (offline maps) twice - same result both times, no GPS without gapps. Due to my injury I don't travel so I don't need GPS.
By not installing Gapps the proprietary Play Services Location API is not installed either.
Thank you very much for the great rom.
I only habe two problems:
1. The mirracast / Screen Mirroring doesn't work. I can't find my Mirracast Receiver (NETGEAR Push2TV PTV3000)
2. Where can I change the CPU Governor or the Scheduler? I have no performance options only Developer Options.
Thanks for your help.
Greetings form Germany
Benjamin
Working perfectly, thanks. Simple flash like any other nightly.
JuergensB said:
Thank you very much for the great rom.
I only habe two problems:
1. The mirracast / Screen Mirroring doesn't work. I can't find my Mirracast Receiver (NETGEAR Push2TV PTV3000)
2. Where can I change the CPU Governor or the Scheduler? I have no performance options only Developer Options.
Thanks for your help.
Greetings form Germany
Benjamin
Click to expand...
Click to collapse
1. Miracast needs more proprietary blobs I think. I have no Miracast compatible device to debug, maybe I can procure one from work next week.
2. To change governor and/or scheduler you need to enable root in the developer settings and install a tool like kernel adiutor.
Still have volume issue...
KuLakow said:
Still have volume issue...
Click to expand...
Click to collapse
And I am still working on it. As long as it is not mentioned in the changelog, it is not fixed. If you want to help, feel free to check out the sources and give me a hand.
Thank you very much for your commitment.
If its possible you can try to use the mirracast driver with the blobs from CM12.1 -which worked.
@lowtraxx
Danke für deine Bemühungen
I tested the last cm12.1 build with the first LineageOS build.
But first let me tell you this isn't complaining, just an info
The performance is way worse on LineageOS than on cm12.1.
Simple things like swiping from left to right to open a hamburger menu is choppy with massive dropped frames. You can try for yourself.
Install Solid Explorer or Shuttle Music Player and swipe to reavel the hambuger menu. Laggy. Same on YouTube.
Doesn't feel as snappy. The Z3 Tablet has the same HW like my old S5. But that runs much smoother and faster.
Like I said NO complaint. Just an info.
Gesendet von meinem SM-G935F mit Tapatalk
iamnotkurtcobain said:
@lowtraxx
Danke für deine Bemühungen
I tested the last cm12.1 build with the first LineageOS build.
But first let me tell you this isn't complaining, just an info
The performance is way worse on LineageOS than on cm12.1.
Simple things like swiping from left to right to open a hamburger menu is choppy with massive dropped frames. You can try for yourself.
Install Solid Explorer or Shuttle Music Player and swipe to reavel the hambuger menu. Laggy. Same on YouTube.
Doesn't feel as snappy. The Z3 Tablet has the same HW like my old S5. But that runs much smoother and faster.
Like I said NO complaint. Just an info.
Gesendet von meinem SM-G935F mit Tapatalk
Click to expand...
Click to collapse
That is most likely a CPU governor issue. CM12.1 uses the old 3.4 kernel while in CM14.1 we use kernel 3.10 which hasn't got all of the optimizations yet. Performance will be looked at as soon as all other quirks are ironed out. In the meantime you can set the governor to performance or tweak zzmoove's parameters for performance which then should make for a super smooth experience (worsening battery life of course )
lowtraxx said:
And I am still working on it. As long as it is not mentioned in the changelog, it is not fixed. If you want to help, feel free to check out the sources and give me a hand.
Click to expand...
Click to collapse
Sorry for anxiety. Just this issue doesn't mentioned in bug-list. So, I thought, that only I have this problem.
Loving this build so far. Idle battery drain has decreased from 1%/hour on the previous cm14 build to 0.3%/hour on this one. I don't really need it but it seems like the GPS is still broken on my SGP611.
hi lowtraxx what is your recommended stock base for flashing scorpion?
I primarily use my 4gt z3t for photography work with nfc pairing to sony alpha a6000 and use it with a netgear ptv3000 and chromecast v1
Does this version have RAW file image support for adobe lightroom mobile app
I have had mine on kitkat stock for a while but have only really started photography and kk has no raw support.
Could you see if it supports or recommend a lollipop or marshmellow build with raw support
Detailed install instructions would be great ie stock recovery or custom, been a while since i flashed anything