Database Develop

[ROM]★[TF701 LP 5.1.1][ZOMBi-POP OMNI KANG RC1][AUG 29]★

{
"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"
}
YOU MUST BE ON THE ASUS STOCK KK 4.4.2 BOOTLOADER VERSION 11.4.1.27+ AND TWRP 2.8.6.3+ BEFORE FLASHING THIS ROM. SEE UPGRADE INSTRUCTIONS BELOW IF YOU ARE UNSURE
You must do a full wipe in TWRP if coming from another ROM. Do not do a full wipe from the bootloader. Don't forget to do a Nandroid Backup first and give the ROM 15 mins to stabilise! The first boot will take 5 to 10 minutes!
Features and Tweaks
This ROM is based from OMNI AOSP sources
Supports EXT4 Data partitions
Based off omni-5.1.1-20150823_zombi_tf701t-KANG source by lj50036/hardslog/sbdags
Full Aroma Installer for main rom including choice of 4 kernels
Remixed Asus kernel with OMNI ramdisk - repacked by sbdags
Omni Kernel by lj50036/sbdags
Extreme Modded Omni Kernel by sbdags
CM12 kernel with OMNI ramdisk by pershoot/sbdags
DPI Size: 280 (TF701 recommended small fonts), 320 (Stock fonts), 300 (Medium fonts) & 260 (Small fonts), 240 (Tiny fonts)
Launchers: Omni, Google Experience Launcher, Apex , Nova
Boot Animations: ZOMBi-POP, Android-L, Nexus Flow, Unknown Pleasures
Gapps based on Banks' Gapps (updated by me to Google latest apks and libs)
Misc Apps: ESFile Explorer, Adobe Flash, AdAway
Tweaks: File system and performance optimised, Init.d support, Zip Align, Force GPU Rendering, Browser2RAM
Continued Best Support of any ROM!
Warning - experimental tweaks
[*]Option disable data journaling on /data during install - CAN CAN CAUSE DATA LOSS IF SUDDEN SHUTDOWN OR CRASH
[*]Option disable fsync during install - CAN CAN CAUSE DATA LOSS IF SUDDEN SHUTDOWN OR CRASH
[*]Tip 1: Go to Settings - About Tablet, Click build number 7 times
Now you will see Developer Settings & Performance menus
[*]Tip 2: In Developer Settings - Set Animation and Transitions to 0.5 or 0 for extra free speed!
[*]Tip 3: In Performance Settings - Set CPU max and min speed and I/O scheduler to noop
Bug List
[*]No Floating windows yet
[*]Aroma gets stuck sometimes - hit volume up if so to force it to continue
Change Log
Don't forget full wipe to install this please! No excuses!
20150829 ZOMBi-POP 5.1.1 RC1 changes
- Re-based from omni-5.1.1-20150823-zombi_tf701t-KANG maintained by lj50036, hardslog, sbdags
- Fixed missing ZOMBi Tweaks that bring performance back
- New OMNI kernel - thanks lj50036
- Includes the stagefright security fix
- Added dock battery option to installer
- Removed GPU efl.cfg tweaks as no longer in source - thanks lj50036
- Updated to latest Banks Gapps base package (may require google playstore and play framework data wipe)
- Updated Google Maps to version 9.13.0
- Updated Google Search to version 5.1.17.19
- Updated Google Music to version 6.0.1951S
- Updated Google Mail to version 5.5.101116392
- Updated Google Hangouts to version 4.0
- Updated YouTube to version 10.31.55
- Previously saved installer options will be reset on first install due to changes
20150727 ZOMBi-POP 5.1.1 Beta 4 changes
- Re-based from omni-5.1.1-20150726-zombi_tf701t-KANG maintained by lj50036, hardslog, sbdags
- Added dock battery icon as a additional flash zip
- Fixed partitions not getting unmounted correctly for tuning during installation
- OmniSwitch now working - thanks hardslog
- Tidied up some installer messages
- Amended SuperSU installer script to give correct permissions and install locations
- Google play services updated to multi-dpi version
- Updated Google Maps to version 9.12.0
- Updated Google TTS to version 3.5.6
- Updated Google Calendar to version 5.2.2-98195638
- Updated YouTube to version 10.28.59
- Updated Apex Launcher to version 3.1.0
- Updated ESFile Explorer to version 3.2.5.5
- Updated Nova Launcher to version 4.0.2
20150615 ZOMBi-POP 5.1.1 Beta 3 changes
- Re-based from omni-5.1.1-20150613-zombi_tf701t-KANG maintained by lj50036, hardslog, sbdags
- Installer script now cleans up /data if you do not opt to install gapps for compatibility reasons
20150614 ZOMBi-POP 5.1.1 Beta 2 changes
- Re-compiled Omni kernel with changes to init.macaln.rc and fstab.macallan with only 2 usb mounts
- Still shows 9 USB Mounts in settings
- Switched back to BANKS GAPPS package
- Updated Google Search, Calendar, Hangouts to the latest versions
20150606 ZOMBi-POP 5.1.1 Beta 1 changes
- Re-based from omni-5.1.1-20150605-zombi_tf701t-KANG maintained by lj50036, hardslog
- Created the Extreme Omni Kernel with performance tweaks - possibly unstable
- Basic and Extra Tweaks do not get installed for the Extreme Kernal as it has its own version
- Removed script to to remove RES init.d script when at default 2560x1600 resolution
- Added ZOMBi-POP tweaks to init.d that get installed for all kernels
20150605 ZOMBi-POP 5.1.1 Alpha 4 changes
- Based from omni-5.1.1-20150604-zombi_tf701t-KANG maintained by lj50036, hardslog
20150604 ZOMBi-POP 5.1.1 Alpha 3 changes
- Audio fixed - thanks to pershoot for source and _that and lj50036 for helping to diagnose
- Youtube fixed - thanks to lj50036
20150603 ZOMBi-POP 5.1.1 Alpha 2 changes
- Based from omni-5.1.1-20150601-zombi_tf701t-KANG maintained by lj50036, hardslog
- Repacked Asus Stock 4.4.2 kernel with the zombi ramdisk
- Repacked CM12 kernel with the zombi ramdisk
20150601 ZOMBi-POP 5.1.1 Alpha 1 changes
- Based from omni-5.1.1-20150530-zombi_tf701t-KANG maintained by lj50036, hardslog
- Initial release - omni zombified after source build
- Added SuperSU and su binary for root capability
- Added all the ZOMBi/CROMi-X goodness to the base rom
- Aroma tuned for ZOMBi-POP
Click to expand...
Click to collapse
The Team
@sbdags - Creative Mastermind (From CROMi-X/CROMBi-kk/ZOMBi-X ROMS)
@lj50036 - Source Guy (From CROMBi-kk/ZOMBI-X ROMS)
@hardslog - The Canadian (From Grimlock ROMS)
@ikkeT - The Fin
Credits
pershoot for maintaining the CM12 source and his advice and fixes! Thanks man!
Google
Omni Team - Thanks!
@_that For all the great advice, watching over us and fixing everything we break!!!!!
All the beta testers for your patience and feedback : @berndblb, @gav2fc, @dape16, @dragon_rckr, @glor
To Do
Fix loads of stuff!
XDA:DevDB Information
ZOMBi-POP, ROM for the Asus Transformer TF701
Contributors
sbdags, lj50036, hardslog, _that, ikkeT
Source Code: https://github.com/zombi-x
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.1.x
ROM Firmware Required: 11.4.1.27 - 30 bootloader
Based On: OMNI AOSP
Version Information
Status: Stable
Current Stable Version: 20150829 RC1
Stable Release Date: 2015-08-29
Current Beta Version: 20150727 5.1.1 Beta
Beta Release Date: 2015-07-27
Created 2015-06-15
Last Updated 2015-08-29

DOWNLOADS
UPGRADE INSTRUCTIONS
Steps
1. Please Unlock using the Asus Unlock Tool first found here.
Note installing and running this app will wipe your device and void your warranty.
2. Install the latest version of Team Win Recovery Project (TWRP) 2.8+ or ClockWorkMod Recovery 6.0.5.0+ Note this ROM will NOT install with older versions of recovery!
TWRP XDA Thread
[email protected]
You can now access the recovery by pushing [volume up] on the RCK icon in the bootloader screen
FLASHING THE ROM FROM RECOVERY
Steps
1. Download the ROM below and save to your internal or external SD Card. Do not unzip the file.
ZOMBi-POP ROM DOWNLOAD
Note: The first boot after install will take 10 mins whilst everything is built. Some people might think it is looping but it is not. The ROM also takes about 10 mins to stabilise after the first boot
ZOMBi-POP 5.1.1 RC1 20150829 Full Mirror 1
ZOMBi-POP 5.1.1 RC1 20150829 Full Mirror 2
MD5 Sum: d291e2ff8ea5d82504ed46378ea1790c
FILES ARE SIGNED. IF YOU ENABLE SIGNATURE VERIFICATION IN RECOVERY IT WILL VALIDATE THE FILE BEFORE FLASHING.
2. Flash the zip files and reboot after - enjoy your new rom.
Do not forget to wipe data first in recovery if you are coming from another rom or installing this for the first time.

MINE
mine

I will do the download post tomorrow but it will be available in the download tab of this thread in about 10 minutes
Enjoy!

Thank you for this ROM!
Before I attempt to install it, I have a question: will the Aroma installer allow me to avoid installing most of the Google apps? Ideally, I'd like the ROM to be installed with no more apps than I would get with a "micro" or even "pico" version of gapps.
.​

HippoMan said:
Forgive me if I'm overlooking something obvious, but I don't see a "download" tab. Is it on a different web page, perhaps?
Click to expand...
Click to collapse
Top of the page in the black bar ....
Says 'Downloads'
Thx Josh

lj50036 said:
Top of the page in the black bar ....
Says 'Downloads'
Thx Josh
Click to expand...
Click to collapse
Yes, I finally found it. Thank you very much.
.​

Flashed, trying it out now

sbdags said:
...
Aroma gets stuck sometimes - hit volume up if so to force it to continue
Click to expand...
Click to collapse
Aroma got stuck for me on the screen for selecting experimental features, but hitting volume up had no effect. It remained stuck.
No other key interactions worked, either, except to reboot.
Any ideas?
.​
---------- Post added at 23:27 ---------- Previous post was at 23:10 ----------
Well, I redid the entire flash procedure, and this time, it worked.
.​

HippoMan said:
Aroma got stuck for me on the screen for selecting experimental features, but hitting volume up had no effect. It remained stuck.
No other key interactions worked, either, except to reboot.
Any ideas?
.​
---------- Post added at 23:27 ---------- Previous post was at 23:10 ----------
Well, I redid the entire flash procedure, and this time, it worked.
.​
Click to expand...
Click to collapse
+1. Ok now.

Took the beta 1 and 2 from androidfilehost (just need to know where to look ). It also happend to me that the installation would sometimes hang or even reboot the recovery (TWRP). With beta 2 i needed three tries. For the rest: very good as always!!

I think that omni roms don't allow immersive mode like cm does. In CM 12.1 I hide the navigation bar to get some extra screen space and I control the tablet via LMT pie menus and gestures. Is there a way to do the same in omni?

HippoMan said:
Aroma got stuck for me on the screen for selecting experimental features, but hitting volume up had no effect. It remained stuck.
No other key interactions worked, either, except to reboot.
Any ideas?
.​
---------- Post added at 23:27 ---------- Previous post was at 23:10 ----------
Well, I redid the entire flash procedure, and this time, it worked.
.​
Click to expand...
Click to collapse
toolmanz said:
+1. Ok now.
Click to expand...
Click to collapse
doom_71 said:
Took the beta 1 and 2 from androidfilehost (just need to know where to look ). It also happend to me that the installation would sometimes hang or even reboot the recovery (TWRP). With beta 2 i needed three tries. For the rest: very good as always!!
Click to expand...
Click to collapse
ariadnejro said:
I think that omni roms don't allow immersive mode like cm does. In CM 12.1 I hide the navigation bar to get some extra screen space and I control the tablet via LMT pie menus and gestures. Is there a way to do the same in omni?
Click to expand...
Click to collapse
Yes Aroma is a bit dodgy on the device - sometimes it hard locks and all you can do is try again - however this was here before we had touch. Not much I can do about it. The latest aroma builds don't even support our device so we are stuck for now.
As for CM12 stuff - nope it's omni but it soes have omni switch which will eventually allow full screen - but you never know what will be developed in the future. It is kept light for a reason - so it is fast and smooth.

The ROM is running very fast and all seems good except for 1 program I like.
I have a very robust infrastructure in the house and I use an app call SmartWIFIAnalyser.
It will automatically switch to the best WIFI signal as I move around the house.
When I start it - the tablet barfs and returns to the bootup screen (wavy lines) - once it returns from losing its mind, it will slowly get back to normal.
This isn't a deal killer - but it works on Zombie-Pop on my TF700 ??
I tried to grab a logcat and I have provided a link to it .... hope I did this right!
http://d.pr/f/1kqpW

toolmanz said:
The ROM is running very fast and all seems good except for 1 program I like.
I have a very robust infrastructure in the house and I use an app call SmartWIFIAnalyser.
It will automatically switch to the best WIFI signal as I move around the house.
When I start it - the tablet barfs and returns to the bootup screen (wavy lines) - once it returns from losing its mind, it will slowly get back to normal.
This isn't a deal killer - but it works on Zombie-Pop on my TF700 ??
I tried to grab a logcat and I have provided a link to it .... hope I did this right!
http://d.pr/f/1kqpW
Click to expand...
Click to collapse
Seems to be a failure with the renderer. Can you reinstall the ROM but don't install the GPU tweaks on the tweaks page and try again for me please.
Thanks!
Code:
E/BufferQueueProducer( 418): [StatusBar] connect(P): BufferQueue has been abandoned
E/libEGL ( 1730): eglCreateWindowSurface: native_window_api_connect (win=0xb498b108) failed (0xffffffed) (already connected to another API?)
E/libEGL ( 1730): eglCreateWindowSurface:423 error 3003 (EGL_BAD_ALLOC)
F/OpenGLRenderer( 1730): Failed to create EGLSurface for window 0xb498b108, eglErr = EGL_BAD_ALLOC
F/libc ( 1730): Fatal signal 6 (SIGABRT), code -6 in tid 2771 (RenderThread)

sbdags said:
Seems to be a failure with the renderer. Can you reinstall the ROM but don't install the GPU tweaks on the tweaks page and try again for me please.
Thanks!
Code:
E/BufferQueueProducer( 418): [StatusBar] connect(P): BufferQueue has been abandoned
E/libEGL ( 1730): eglCreateWindowSurface: native_window_api_connect (win=0xb498b108) failed (0xffffffed) (already connected to another API?)
E/libEGL ( 1730): eglCreateWindowSurface:423 error 3003 (EGL_BAD_ALLOC)
F/OpenGLRenderer( 1730): Failed to create EGLSurface for window 0xb498b108, eglErr = EGL_BAD_ALLOC
F/libc ( 1730): Fatal signal 6 (SIGABRT), code -6 in tid 2771 (RenderThread)
Click to expand...
Click to collapse
Bingo! It now works but once I enable it and come back out to the home screen it is super small on large screen. There has been some other weirdness with the screen like the drawer shows really large icons (2 to a page ??? ). But nothing I can't handle - ESC out of the screen and go right back in and its working.
Cheers and thanks for another great ROM!

toolmanz said:
Bingo! It now works but once I enable it and come back out to the home screen it is super small on large screen. There has been some other weirdness with the screen like the drawer shows really large icons (2 to a page ??? ). But nothing I can't handle - ESC out of the screen and go right back in and its working.
Cheers and thanks for another great ROM!
Click to expand...
Click to collapse
I need a screen-shot of that .....
Thx Josh

lj50036 said:
I need a screen-shot of that .....
Thx Josh
Click to expand...
Click to collapse
Can't seem to get it to do that again ..... Now when I come back to the home page its blank. Hit ESC a couple of times and it comes back normal. ???
Maybe same problem - with different symptoms ... ?
I will gab screen shots if it happens again.
Cheers
---------- Post added at 02:02 PM ---------- Previous post was at 01:39 PM ----------
Ok. Went into the store and found there was an update to the launcher I use - KK Launcher Prime. I did the update and came back to the home screen - normal.
When I went into the drawer it did it again and have attached the screen shots. They are really faint but you can see 3 icons only. Esc back out and go back in and it's working ???
Thinking maybe its the launcher at fault
Link below.
http://d.pr/f/1gdhS
Cheers

toolmanz said:
Can't seem to get it to do that again ..... Now when I come back to the home page its blank. Hit ESC a couple of times and it comes back normal. ???
Maybe same problem - with different symptoms ...
I will gab screen shots if it happens again.
Cheers
---------- Post added at 02:02 PM ---------- Previous post was at 01:39 PM ----------
Ok. Went into the store and found there was an update to the launcher I use - KK Launcher Prime. I did the update and came back to the home screen - normal.
When I went into the drawer it did it again and have attached the screen shots. They are really faint but you can see 3 icons only. Esc back out and go back in and it's working ???
Thinking maybe its the launcher at fault
Link below.
http://d.pr/f/1gdhS
Cheers
Click to expand...
Click to collapse
Well that is odd indeed ...
Can you set a diff wallpaper and see what that does .....
Thx Josh

lj50036 said:
Well that is odd indeed ...
Can you set a diff wallpaper and see what that does .....
Thx Josh
Click to expand...
Click to collapse
Well I am using 500 Firepaper now and it still does it. Go figure. It must be the launcher. ?

[ROM][5.1.1_r34][p6800/p6810](6April2016-Build1.8)SlimLP 5.1.1-.beta.0.15-UNOFFICIAL

{
"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.

[DISCONTINUED][UNOFFICIAL] CM-12.1 [22 Nov 2016]

IMPORTANT NOTICE​:
As many of you know, the CM-12.1 branch will not be supported in the new LineageOS fork. And many of the new Google security patches are difficult and fiddly to back-port as they are now geared towards Marshmallow and Nougat. So as a result there will be no further updates to this rom.
Instead my focus will now be Fire Nexus ROM for this device.
Also looking at possible ways to get later android versions on the device. Will let you know if there is any progress later.
Thanks for all the support :good:
{
"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"
}
Code:
[COLOR="gray"]
/*
* 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 the products you find here before flashing it!
* YOU are choosing to make these modifications.
*/
[/COLOR]
Current Progress
updated: 25 Jan 2016
Rules
- Please search the thread before asking questions
- Please try to stay on topic, I know it's not always possible
- Please report bugs here
- Report only one issue per bug report
- When reporting bugs please post a logcat and/or dmesg containing pertinent information regarding the issue...
- Saying something isn't working without proper explanation will not attract any attention.
Prerequisites for Installation
- If you have FireOS 5.0.1 then use Cyanogen Recovery or TWRP Image
- If you have FireOS >= 5.1.1 then use FlashFire 0.50
Fresh Installation from TWRP
- From your recovery perform a Factory Reset
- Flash the ROM File
- Flash Open Gapps - Use either micro, pico or nano
- Do NOT use stock gapps as there is not enough space on the /system partition
- Reboot and enjoy!
- Fresh Installation from FlashFire 0.50
- Click the Red + and choose 'Wipe'
- Ensure System data, 3rd party apps and Dalvik cache are CHECKED
- Click the Red + button and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Cyanogenmod Zip
- Accept defaults
- Click the Red + button again and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Open Gapps Zip.
- Accept defaults
- Move "Wipe" to the Top of the order
- Press the big FLASH button.
Upgrading from FlashFire 0.50
- Click the Red + button and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Cyanogenmod Zip
- Click the Red + button again and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Open Gapps Zip.
- Accept defaults
- Click the Red + again and choose 'Wipe'
- ONLY tick Dalvik and Cache.
- Press the big FLASH button.
Downloads
*** Please do NOT create any mirrors ***
- CM-12.1 for Amazon Fire 7" 2015 Tablet
- Open Gapps
Source Code
- Device Tree
- Kernel Source: Ford stock kernel, build number update-kindle-global-37.5.6.0_user_560177220
Thanks
- Cyanogenmod
- csolanol
- diegocr
- k4y0z
XDA:DevDB Information
CM-12.1 Amazon Fire 2015, ROM for the Amazon Fire
Contributors
ggow
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
Based On: Cyanogenmod
Version Information
Status: Stable
Created 2015-11-15
Last Updated 2017-02-03

Release Notes / Changelog
2016-11-22
- Fix Xposed - Needs testing
2016-11-21
- November 2016 AOSP Security Patch Level
- Switch to using lastest FireOS 5.3.2 - update-kindle-global-37.5.6.0_user_560177220 binaries and boot.img
- Fix Video Recorder bug [Cannot connect to camera]
- Fix bug in OMX causing freeze of video
2016-10-21
- October 2016 AOSP Security Patch Level
- Fix x265 video playback - Thanks @jeromeof
2016-09-22
- September 2016 AOSP Security Patch Level
2016-08-10
- August 2016 AOSP Security Patch Level
- Fix audio lag issue in games - thanks @$ideWinder
2016-07-10
- July 2016 AOSP Security Patch Level
- Re-tested exFAT with 32GB Sandisk microsd card and seems to work fine.
2016-06-14
- June 2016 AOSP Security Patch Level
- Added CIFS Support (Instructions here)
- Switch to using lastest update-kindle-37.5.4.4_user_544271020 binaries and boot.img
2016-05-30
- Fix Swipe for stock keyboard
- Added back fix for screen rotation glitch
2016-05-28
- May 2016 AOSP Security Patch Level
- Fixed bug: No way back from USB Charge Only Mode
2016-04-20
- Updated CM Code
2016-04-11
- Fix sdcard write access
2016-04-06
- Updated CM Code
- 01 April 2016 AOSP Security Patch Level
2016-04-04
- Updated CM Code
- Prevent recovery been overwritten: Modify build system to prevent recovery-resource.dat and recovery-from-boot.p from been generated. This needs testing preferably by people with the ability to boot TWRP.
- Fixed failure to mount /system partition error due to change in build system
2016-03-30
- Enable Bluetooth Low Energy Support
2016-03-29
- Updated CM Code
- Switch to using lastest update-kindle-global-37.5.4.2_user_542168620 binaries and boot.img
2016-03-11
- Updated CM Code
- 01 March 2016 AOSP Security Patch Level
- Updated FlashFire Flashing instructions on OP
2016-02-29
2016-02-19
- Updated CM Code
2016-02-03
- Updated CM Code
- 01 February 2016 AOSP Security Patch Level
2016-01-26
2016-01-20
2016-01-12
- Updated CM Code
2016-01-04
- Enable WiFi Display
2015-12-30-R01
- Fixed bug where FlashFire will fail to go from FireOS -> CM
2015-12-30
- Thanks to @chetta for testing and prompt feedback
- Reverted use of Google's prebuilt WebView for now (Too many issues)
- Clean Flash via TWRP Re-tested
- Google App Tested
- YouTube and NetFlix Re-tested
- Upgrade via TWRP re-tested
- FlashFire FireOS -> CM re-tested
2015-12-29-PM
- Fixed issue with GAPPS and SuperSU been overwritten on upgrade of ROM
2015-12-29-AM
- Fixed bug when using FlashFire where Gapps would not be preserved
- Use Google's Prebuilt WebView
- Update WebView to version 48.0.2564.48
- Updated CM code on 2015-12-29
- Re-tested ROM upgrade via TWRP, CM recovery and FlashFire
- Fixed Flash failure going from FireOS 5.1.1 -> CM
- Re-tested FlashFire functionality going from FireOS 5.1.1 -> CM
2015-12-23
- Fixed ability to use FlashFire to go from FireOS_5.1.1 to CM-12.1
- BLOCK_BASED_OTA is now enabled
- Updated CM code on 2015-12-22
2015-12-16
- Fixed screen-off animation rotation orientation
- Updated CM code
2015-12-11
- Fixed permissions on /system/etc/install-recovery-2.sh
- Implement fix for Play Video - thanks @diegocr
2015-12-10-PM
- Switch to using update-kindle-full_ford-37.5.4.1_user_541112720 binaries and boot.img
- New version of the selinux_permissive.ko module - thanks @k4y0z
- Added /system/etc/install-recovery-2.sh with the same content as /system/bin/install-recovery.sh
- Fixed Built-In Root Access (Privacy Guard)
2015-12-10-AM
- Fix problem with install-recovery.sh been overwritten
- exFAT should now work (was broken in the previous build)
- init.d now initialises correctly
- Enabled built in Root Access
- NuPlayer should now work correctly
- Fixed Camera Support (HDR mode is not working and not supported)
- Fixed Video Recording
- General Video Support should be good now
- I tested Netflix and YouTube
2015-12-09
- Switch to using update-kindle-37.5.2.2_user_522054520 binaries and boot.img
- Add kernel module to switch selinux operational mode to permissive - thanks @k4y0z
- This means SuperSU is now not required and much faster boot times
- Add exfat support
- Enable init.d support - thanks @k4y0z
- Remove GPS configs
- Removed NFC configs
- Removed GPS, telephony and NFC permission files
- Add further properties to disable some SIM/RIL related stuff
2015-12-04
- Fixed USB OTG - thanks @csolanol and @diegocr
- Updated CM Code
2015-12-02
- Fixed Bluetooth Audio
- Updated CM Code
2015-12-01
- Fixed Bluetooth - thanks @diegocr
- Enable Multi-user (5)
- Updated CM Code
2015-11-22
- Enable MTP
- Enable OTG Support
- Add properties to declare device has no radio
- Added configuration item to build for BLOCK_BASED or not.
- BLOCK_BASED build currently not flashing due to symlink error
- Add further config for MTK Bluetooth
- Fixed build errors in lib_driver_cmd_mt66xx private static lib
- Clean up config for WIFI
- Added IPv6 support
- Fixed battery stats - thanks @csolanol for providing the required power_profile.xml
2015/11/16
- This version will boot standalone - no more tethered boot
2015/11/15
- Initial Release

Frequency Asked Questions
Question 1:
How do I adjust the keyboard sound level?
Answer:
- Go to settings -> Languages & input -> Android Keyboard -> Advanced -> Keypress sound volume
- Then adjust the slider to your preferred level
Question 2:
Why does the screen image seem stretched or distorted?
Answer:
- The actual pixels in the Fire's LCD are not perfectly square
- That causes some distortion. It is particularly noticeable with round icons & when the screen rotates.
- This issue also effects the stock amazon OS as well as all custom roms.
- It is not yet known if this will be fixable in software (my current thinking is probably not)
Question 3:
Why is my brightness slider not working?
Answer:
- Try installing Brightness Level and use it to change brightness. After doing this brightness slider should work fine and you can remove Brightness Level.
Question 4:
When installing Google Play Games and Google Calendar I get error -505?
Answer:
- Install older versions from apkmirror then update from Google Play Store.
Question 5:
How do I use CIFS?
Answer:
See the guide here

Actual CM12.1 on the Fire 2015? So, a premium device for $50 with CM12.1? Awesome! Might have to pick one up now... I'd guess I don't have to fastboot each time I power on right? Just the first time to get CM/TWRP, then have CM/TWRP install+boot CM12.1, then I can get CM12.1 without fastboot?

bobbob1016 said:
Actual CM12.1 on the Fire 2015? So, a premium device for $50 with CM12.1? Awesome! Might have to pick one up now... I'd guess I don't have to fastboot each time I power on right? Just the first time to get CM/TWRP, then have CM/TWRP install+boot CM12.1, then I can get CM12.1 without fastboot?
Click to expand...
Click to collapse
- You will have to fastboot each time
- It's all in the OP including the reasons why this is the case at the moment.
- It's not ideal - but thought I would share what I have so far
- I am looking into solutions for this now.

- Links are now up

ggow said:
- You will have to fastboot each time
- It's all in the OP including the reasons why this is the case at the moment.
- It's not ideal - but thought I would share what I have so far
- I am looking into solutions for this now.
Click to expand...
Click to collapse
Thanks for the hard work!

Once booted into CM12.1 we can make general system configuration changes, install apps, etc, correct? And will changes be be retained if we need to reboot (through fastboot)? If so, where will CM12.1 files be stored?

blueberry.sky said:
Once booted into CM12.1 we can make general system configuration changes, install apps, etc, correct? And will changes be be retained if we need to reboot (through fastboot)? If so, where will CM12.1 files be stored?
Click to expand...
Click to collapse
- Yes customise as much as you want - all will be retained.
- Your data and OS is stored on the /data and /system partition respectively
- The only thing you have to reload on a reboot through fastboot is the modified_boot.img which won't affect anything else.

Awesome work @ggow!. @diegocr and me have been working on bring slimrom to this device. We are having some issues with WiFi and bluetooth. Would you mind to share your device and vendor for cyanogen?.
Thanks.

csolanol said:
Awesome work @ggow!. @diegocr and me have been working on bring slimrom to this device. We are having some issues with WiFi and bluetooth. Would you mind to share your device and vendor for cyanogen?.
Thanks.
Click to expand...
Click to collapse
Hi csolanol,
- I am in the process of updating my bibucket with the most recent changes
- Having trouble with bluetooth too.
- Wifi is working fine - I got it working like this:
- put this in your device tree
- then add this to your boardconfig.mk:
Code:
[INDENT]WPA_SUPPLICANT_VERSION := VER_0_8_X
BOARD_WPA_SUPPLICANT_DRIVER := NL80211
BOARD_HOSTAPD_DRIVER := NL80211
BOARD_WLAN_DEVICE := mediatek
BOARD_WPA_SUPPLICANT_PRIVATE_LIB := lib_driver_cmd_mt66xx
BOARD_HOSTAPD_PRIVATE_LIB := lib_driver_cmd_mt66xx
WIFI_DRIVER_FW_PATH_PARAM:="/dev/wmtWifi"
WIFI_DRIVER_FW_PATH_STA:=STA
WIFI_DRIVER_FW_PATH_AP:=AP
WIFI_DRIVER_FW_PATH_STA:=P2P[/INDENT]
- Then add this to your device.mk or equivalent
Code:
[INDENT]# wifi
PRODUCT_PACKAGES += \
lib_driver_cmd_mtk[/INDENT]
- Do not include the propriertary bin/wpa_supplicant when building otherwise you will get a build error
- Instead copy it into your ROM after building.
- Hope this helps for now.

Didnt whats his face say he used the original boot.img file to flash permenatnly asop without using fastboot every time?

ggow said:
Hi csolanol,
- I am in the process of updating my bibucket with the most recent changes
- Having trouble with bluetooth too.
- Wifi is working fine - I got it working like this:
- put this in your device tree
- then add this to your boardconfig.mk:
Code:
[INDENT]WPA_SUPPLICANT_VERSION := VER_0_8_X
BOARD_WPA_SUPPLICANT_DRIVER := NL80211
BOARD_HOSTAPD_DRIVER := NL80211
BOARD_WLAN_DEVICE := mediatek
BOARD_WPA_SUPPLICANT_PRIVATE_LIB := lib_driver_cmd_mt66xx
BOARD_HOSTAPD_PRIVATE_LIB := lib_driver_cmd_mt66xx
WIFI_DRIVER_FW_PATH_PARAM:="/dev/wmtWifi"
WIFI_DRIVER_FW_PATH_STA:=STA
WIFI_DRIVER_FW_PATH_AP:=AP
WIFI_DRIVER_FW_PATH_STA:=P2P[/INDENT]
- Then add this to your device.mk or equivalent
Code:
[INDENT]# wifi
PRODUCT_PACKAGES += \
lib_driver_cmd_mtk[/INDENT]
- Do not include the propriertary bin/wpa_supplicant when building otherwise you will get a build error
- Instead copy it into your ROM after building.
- Hope this helps for now.
Click to expand...
Click to collapse
Thanks, I will wait bitbucket update :good:

Awesomeslayerg said:
Didnt whats his face say he used the original boot.img file to flash permenatnly asop without using fastboot every time?
Click to expand...
Click to collapse
- Yes, that was me who said that but Amazon have changed things since then.
- On the HDX at the time they were not enforcing an selinux policy
- Now that Amazon are enforcing it cannot work in the same way at least for the moment until a workaround is found.

diegocr said:
Thanks, I will wait bitbucket update :good:
Click to expand...
Click to collapse
- Did you guys find a way of been able boot Slim without having to fastboot a boot image each time?

ggow said:
- Did you guys find a way of been able boot Slim without having to fastboot a boot image each time?
Click to expand...
Click to collapse
no, only fastboot

diegocr said:
no, only fastboot
Click to expand...
Click to collapse
@csolanol and @diegocr
I have linked my Device Tree in the OP.

ggow said:
@csolanol and @diegocr
I have linked my Device Tree in the OP.
Click to expand...
Click to collapse
Thanks a ton :good:

diegocr said:
Thanks a ton :good:
Click to expand...
Click to collapse
- I built my ROM without block based image generation
- This means you can extract the ROM and use the proprietary-files.txt with the extract-files.sh to re-generate the vendor tree

[ROM][Unlocked BL][V7 02.07.2017] LineageOS BETA (NJH47D) for SGP611/SGP621

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

[ROM][unlocked][ford,austin] Lineage-14.1 [21 JUN 2023]

Disclaimer
Code:
/*
* 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 the products you find here before flashing it!
* YOU are choosing to make these modifications.
*/
LineageOS needs no introductions. This version of LineageOS-14.1 is a highly customised version solely for the ford and austin models of the Amazon Fire 7"
- EVEN MORE IMPORTANT: This ROM only works on devices using the bootloader hack. See <<< HERE >>> to unlock your devices.
- IMPORTANT: Do not update Magisk via the Magisk Manager App, your device will enter a bootloop if you do. Instead update Magisk via TWRP only. If you do this by accident then it is recoverable by just flashing the latest version of the ROM again (with gapps etc as required).
Rules
- Please search the thread before asking questions
- Please try to stay on topic, I know it's not always possible
- Please report bugs here
- Report only one issue per bug report
- When reporting bugs please post a logcat and/or dmesg containing pertinent information regarding the issue...
Prerequisites for Installation
- Unlocked Bootloader
- TWRP Installed
Downloads
*** Please do NOT create any mirrors ***
- Google Drive
Source Code
- Kernel Source
- Common Tree
- Device Tree (ford)
- Device Tree (austin)
Thanks
- @k4y0z and @xyz` for the bootloader hack
- LineageOS
NOTE
Here is the link to all available fixes for Austin & Ford. Will be updated when anything new is introduced. Questions about mod add-ons you can ask me @Ziona
https://forum.xda-developers.com/showpost.php?p=80167249&postcount=26
XDA:DevDB Information
mt8127_LineageOS-14.1, ROM for the Amazon Fire
Contributors
ggow, Ziona
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Unlocked Bootloader
Based On: LineageOS

Changelog / Release Notes
Dated 21 June 2023
- Rebuild for hosting on Google Drive
- I have just built these blind and they are not tested.
- Updated download link on OP
Dated 05 February 2022
- Refresh vendor files for austin
- No changes for ford. Use 01 February build.
Dated 01 February 2022
- Fix wifi nvram bug - thanks @Ziona
- Fix camera identification on austin - thanks @Graysters
- Had to blind bake austin because I haven't found them yet - let me know if there are any problems
Dated 17 January 2021
- Special thanks to @Ziona for all the great support provided
- Fix external sdcard access
- Fix OMX and media playback
- Fix microphone
- Setup zram with 0.5GB
- Fixed cameras for ford and austin
- Fixed screen off rotation animation for ford
- Tested youtube and Newpipe
- Tested amazon prime video
- Tested clash of clans
- Tested wired headphones
- Tested microphone with sound recorder
- Tested Spotify
Dated 28 August 2019
- Initial Beta Release
- Should be relatively stable
- Wifi works
- Bluetooth works
- Audio works
- Sensors work
- Everything else needs testing
- Please when reporting bugs, include a logcat
- Device trees will be updated once I've gone through the initial prototype

TODO
- nvramAgent and media_policy service looping resulting in longer boot time
- sdcard access, needs investigating - does it work the same as in lollipop - guessing not
- OMX not working
- NVRAM warning in WiFi settings Post #9
- austin: Camera won't connect Post #9
- ford: screen off animation orientation
- ford: screen rotation sensor not working
- ZRAM not working
- Netflix not working
- Video cameras do not work
- OMX not loading Post
- MTP not showing up on austin with adb enabled Post

New Build is Up
Dated 28 August 2019
- Initial Beta Release
- Should be relatively stable
- Wifi works
- Bluetooth works
- Audio works
- Sensors work
- Everything else needs testing
- Please when reporting bugs, include a logcat
- Device trees will be updated once I've gone through the initial prototype

@ggow
Ford
Dirty flash on Lineage 12.1
MicroSD card not visible. Everything was ok on 12.1

Kramar111 said:
@ggow
Ford
Dirty flash on Lineage 12.1
MicroSD card not visible. Everything was ok on 12.1
Click to expand...
Click to collapse
OK, cool will fix that first.

Del

OMG Testing right now in austin!

austin info
Ok @ggow:
Excelent ROM as always
It's almost fully stable but I found two bugs:
Camera won't open, it says: Can't connect to camera (See image)
And there's the nvram warning error too in Wi-Fi settings. I remember that you commited something in hd6/hd7 that fixed it.
The camera log is attatched above.
Regards and good job!

Rortiz2 said:
Ok @ggow:
Excelent ROM as always
It's almost fully stable but I found two bugs:
Camera won't open, it says: Can't connect to camera (See image)
And there's the nvram warning error too in Wi-Fi settings. I remember that you commited something in hd6/hd7 that fixed it.
The camera log is attatched above.
Regards and good job!
Click to expand...
Click to collapse
On my ford tablet, I have that same Wi-Fi error as shown in your screenshot, but camera seems to work fine for me.

Here's benchmarks with the nougat rom installed if anyone is interested.
GeekBench: https://browser.geekbench.com/v4/cpu/14459300
Antutu Benchmark results, attached on this post.

Awesome rom! Never though my fire 7 2015 would run this!
Any chance we get a newer android version than Nougat?
You've done enough already thanks, just asking for curiosity
Camera works fine for me

tonibm19 said:
Awesome rom! Never though my fire 7 2015 would run this!
Any chance we get a newer android version than Nougat?
You've done enough already thanks, just asking for curiosity
Camera works fine for me
Click to expand...
Click to collapse
It is running rather nice already. Once I have fixed up all the bugs on the this nougat release then I'll think about pie or Q. Pie is not easy to stabilize running on the old blobs we have which is why I'm using nougat as a stepping stone.

also @ggow omx is not working on austin. Youtube just reproduces a black screen.

Looking into long boot times this is been caused by a problem with NVRamAgent and media_policy services not starting straight away and as a result meeting a timer expiry.

I've noticed a sleep "bug" on ford when you press the power button or when the sleep goes to sleep, the screen goes into landscape for almost a half-second before the screen turns off as seen in the slow-motion video provided in the attachment (in the zip file).
I don't know if it's just me or not, but anyone running this rom, try pressing power or having it go to sleep and see if the issue occurs.

BobPony said:
I've noticed a sleep "bug" on ford when you press the power button or when the sleep goes to sleep, the screen goes into landscape for almost a half-second before the screen turns off as seen in the slow-motion video provided in the attachment (in the zip file).
I don't know if it's just me or not, but anyone running this rom, try pressing power or having it go to sleep and see if the issue occurs.
Click to expand...
Click to collapse
Hello it's not a sleep bug, it's a problem with the weird hardware orientation of the screen. Most tablets and phones have no offset and operate at normal rotation orientations (ie base 0 degress) however with the ford tablet has a base hw rotation of 270 degrees which is why you see this.
It's nothing serious just a visual artifact. Will fix in the next release.

I added a TODO list to Post #2

I was waiting for an update to Nexus ROMS because I feel it runs better that LOS but with 14.1 beta available there is no way to avoid trying it Backing to LOS from Nexus in a few seconds full wiping my Ford. Thanks
UPDATE: Aaaand I forgot GAPPS , trying with 7.1 pico
---------- Post added at 05:01 PM ---------- Previous post was at 04:27 PM ----------
ggow said:
- nvramAgent and media_policy service looping resulting in longer boot time
- sdcard access, needs investigating - does it work the same as in lollipop - guessing not
- OMX not working
- NVRAM warning in WiFi settings Post #9
- austin: Camera won't connect Post #9
- ford: screen off animation orientation
- ford: screen rotation sensor not working
Click to expand...
Click to collapse
In my Ford wifi and screen rotation sensor works without problems (NVRAM?). sdcard not working as stated
---------- Post added at 05:03 PM ---------- Previous post was at 05:01 PM ----------
I can't get Gmail app recognize accounts, calendar does but gmail doesn't. Ford with Pico. UPDATE: It works, permisions needs to be granted manually

Youtube app stream sound but not vídeos, vídeos un browser works fine