Database Develop

[ROM] TheROM - take it or leave it [stable: build 26 | exp: build 27]

TheROM - take it or leave it
Okay guys, as promised I am sharing the ROM I made for myself to suit my personal needs.
I prefer stability and smoothness over features - so it focuses on some core features I love but isn't overloaded with each and every possible option out there.
All features are carefully and cleanly picked into the ROM without the use of nasty hacks wherever possible.
Please read the FAQ at the end of the first post before using this ROM!​
​
If you appreciate my work on the LG Optimus 2x you can support me by donating!
I am doing this for free in my leisure time because I like working on Android stuff and helping others out.
You're not required to donate, but I highly appreciate a couple free beers or pizzas as a gratidue for my work.
To quote one of the most famous xda developers:
Chainfire said:
Don't be a leech, buy me a beer (and use the "Thanks" button!). Imagine if every CF-Root user has donated me $1...
Click to expand...
Click to collapse
I am nowhere near his usercount, but just imagine if every happy (and only those) user of one of my ROMs has donated 5€+.​
Important:
Let me explain the "take it or leave it" phrase from the title:
You got two options, either you like the ROM and use it as it is without any complaints, or you don't and use another one.
I made this ROM for myself and am sharing it to you as there's a broad interest.
But I am not interested at all in feature requests, ETA questions, silly bug reports(!), etc. etc.
If I derped something (e.g. a FC within the settings app) you can of course post about it.
But you have to a) do a full wipe and confirm the bug is still there, b) describe your bug in detail, c) post a logcat.
It is the ROM I personally use (or for the CM10.1 version: used), so you can talk about the ROM, but you don't get to ask about any changes.
If we're clear on the rules let's go to the fun part.
This thread is in the general section for a reason. As we're not going to discuss which features this ROM absolutely needs we got a whole thread to our liking.
Which means: It's meme time!
{
"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"
}
FAQ:
Read the FAQ carefully before asking any questions!
Okay, I know you said no feature requests, but I really need [feature xyz]!
Why should I try this ROM?
I want to try this ROM, can I just flash it and be good to go?
I have a question..
New: I have a question regarding bluetooth...
Listen, I'd like to know if you could ...
I will donate to you if you include my beloved feature:
This is a joke right?
Really, I just want to know when you're going to release the next update?
I don't like the way you're doing this thread!

TheROM
Okay, this ROM comes in two versions. CM10.1 and CM10.2 based.
The former is based on my work on CM10.1.
The latter is based on my work-in-progress CM10.2.
If you're new to the LG 2x then you should check both linked threads and read about the differences, bugs and features of these ROMs.
I just don't see a reason to have two threads for this ROM, thus I'm merging them together in here.
The CM10.1 ROM is deprecated, it's been the ROM I've been using until I made the switch to CM10.2.
I just share it here for those of you who might prefer it. So don't expect any further updates.
​
FEATURES / INFORMATION:
Only features I made or ported are listed here, nothing that's already in CM.
TheROM CM10.2:
Hybrid Engine (per app dpi / layout)
Halo 2.0
Additional hardwarebutton customizations
(like Screen off, open Torch, Power menu etc.)
Notification Brightness slider
Center Clock option
Text-only battery style
PreferenceDrawer in the Settings
Custom Carrier text
Advanced low battery options
My memory management option
Fixed performance menu for Tegra2
Option for all home screen widgets on the lockscren
notification drawer background & transparency
standard softkey vibration lowered
ships with the awesome kowalski kernel by pengus77
comes with my non-neon compatible mini gapps package
Option to use the external storage as default one
comes with bluedroid which means speedup bug and no BT phone calls possible
If I find some time I might try to include bluez, but right now I don't and bluedroid will stay in until further notice.
App Ops option in the settings (with PAs changes)
based on the newest CM10.2 sources
and loads of small stuff here and there I forgot to list
Differences in the depracted CM10.1-based version:
comes with an older Halo version (1.0)
ships a couple more hardwarebutton customizations (esp. custom app)
comes with bluez and is compiled with GCC 4.7 which means a) no speedup bug but therefore b) no BT phone calls
based on CM10.1.2 stable + custom picks of the nightlies
​
Download:
Get the ROMs here:
http://tonyp.basketbuild.com/index.php?dir=main/TheROM/
All ROMs are for the newbl - if you're using the oldbl use the converter (or wait for someone to upload the converted build).
Kowalski Kernel M1 rh and my non-neon compatible mini gapps are included.
Installation instructions:
CM10.2 (coming from another ROM than my CM10.2):
Do a full wipe. Do another reboot after the first boot. Don't *****.
CM10.1 (coming from another ROM than my CM10.1):
Do a full wipe!
Updating to a newer TheROM build:
Flash the ROM. Reboot. No wipes needed.
Do not update from any CM10.1 ROM to CM10.2 (full wipe it is!)
Known Bugs:
Do not ask about features on the known bugs list. They're known, there's no need for a reminder.
all CM bugs (no HDMI rotation etc.) are present - check the CM10.1 / CM10.2 threads for more details
This especially means that on CM10.2 bluetooth calls are not working!!
If this is a dealbreaker for you: move to a ICS / CM10 or my CM10.1 t-build ROM!
See this post for more details regarding the bluetooth situation.
Hybrid Engine: Sometimes changing the system dpi will produce a small layout error (an empty line below the statusbar).
Just do a reboot and it's gone

Credits:
TheROM contains features from the following ROMs.
I either ported them myself or rewrote them based on their inspiration:
CyanogenMod
[*]ParanoidAndroid
[*]Jellybeer
[*]SlimBean
[*]ChameleonOS
[*]PAC-man
A special thanks to these people:
pengus77 for his awesome kernel
arcee for his work on CM7 - CM10.1
spyrosk for the bootloader converter (and AIO toolkit)
all the guys helping out in the threads (which are too many to list)
Thanks for the people who provide me with buildbox access and free hosters:
xda
Korumera (xdafileserver.nl)
basketbuild
vadonka
goo.im
​

This Known Issues List
should prevent one-liner finding reports related to already known issues
should keep later disappointment from end-users of tonyp's theROM and clean CM 10.2
defines an everlasting unique identifier for each known issue. Use the identifier for simplified unambiguous communication. Please write e.g. "issue #2" if you want to refer to the silent blue-tooth call bug
should show possible workarounds, or, even better, should motivate discussions to fix the issue.
should neither let you imply that the issue will be fixed soon, nor that it is fixable at all! It is technically really hard to analyze, find and fix the root cause. Please never ask for an ETA! The community is aware of, and is of cause already unhappy (see e.g. this post) about these known issues.
will not cover issues that exist in only 1 or 2 intermediate builds of theROM and that are already fixed in the latest build. Please also consult change log by @[email protected]
Known Issues List as of 2013/12/28 (theROM build 22-26 resp. clean CM10.2 incl. 2013-12-13):
HDMI doesn't work
Workaround: use stock LG GB ROM (I don't know whether stock LG ICS works)
Calls from BT headset connect but are silent for caller and callee
Workaround: use e.g. CM10.1 T-builds or ParanoidAndroid (PA) ROM
Root cause: not yet found; speculation: volume gain factor is set to 0 somewhere
Discussion: see e.g. post3, post2 , post1 issue b)
Mobile data counting doesn't work (blue arrows on mobile data indicator don't appear; e.g. Avast shows error message)
Workaround: use e.g. CM10.1 T-builds or ParanoidAndroid (PA) ROM
Root cause: bug in Android 4.3 (inherited to CM10.2)!?
Discussion: see e.g. note 3 in post3, post2, post1, report to Google
Stock camera
takes heavily over-exposed pics with flash
Workaround: tap the screen first before you click the camera fire button; this will correct exposure parameters
crashes often, or produces crashes of Trebuchet and gallery
Workaround 1: use e.g. cam app ported for CM10.1 by feav; it provides also features like panorama pix missing in the stock cam
Workaround 2 (not fully proven): flash the gallery.apk from build 23; some say the stock cam works without crashes then
BT media playback speeds up after minutes to hours.
Fix: at least fixed in build 22 (I dont't remember the exact build)
Some apps (e.g. Candy Crush) crash with the KK in the RAM hack version
Workaround: flash the no RAM hack (norh) version of Kowalski kernel (KK) by Pengus77
Slow GPS fix. Cause: missing file \data\gps\lto.dat that is up to date too.
Fix: seems to be fixed in build 23; some issues with the fix have been reported; under investigation
Literature: xda forum thread2, [URL="http://forum.xda-developers.com/showthread.php?p=15271402#post15271402"]thread1[/URL]
Long lags after heavy filling and emptying the flash memory. Reboot does not help
Workaround: backup data partition, wipe it, and restore the backup
Root cause: kernel does not implement TRIM functionality that makes use of the SD/MMC ERASE (CMD38) command.
References: wikipedia TRIM, wikipedia TRIM#SD/MMC
Discussion: post4, post3, post2, post1
Mobile data mode keeps being disabled when switching airplane mode off
Workaround: either disable and re-enable data or toggle 2g/3g twice. In some rare cases these workarounds won't work and a reboot is needed
Root cause: yet unknown
Current time shown is that for GMT time zone instead of for your local timezone. Time shift is always in full hours.
Workaround 1: Reboot; normally this restores correct time display.
Workaround 2: Disable automatic time sync and install a time sync app
Workaround 3: If you'd like to keep using automatic time you should add "telephony.test.ignore.nitz=true" to your build.prop
Root cause: yet unknown
Discussion: post2, topic #3 in post1
Some apps always crash under theROM and they also don't work on stock ICS on P990. Some of such seem to be Viber, Instagram, etc.
Request: please report as soon as the app started working correction on a new theROM build.
Recommendation 1: Search in this thread if your app is known to be incompatible with theROM
Recommendation 2: Search the internet if your app is known to be incompatible with stock ICS on P990
Recommendation 3: Try your app on P990 under stock ICS
Rule: never post problems with your app in this thread if its incompatibility to theROM or ICS on P990 is already known!
Recommendation 4: Ask the author of your app for help
Workaround: Use your app on P990 under stock ICS, or on another phone. (sorry for bad news!)
Root cause: potentially missing NEON support by P990; many others possible
no FM radio
note: theROM builds from version 27 ship Kowalski Kernel 3.1 (instead of KK 2.6 M1). As this might solve old known issues and might bring new ones I decided to archive and hide the above list for builds up to version 26. The below list for build version from 27 starts as a 1:1 copy of the above. As I am not on build 27 yet, I am not able to bring in my own experience. Additionally I don't have the time to read and evaluate all posts regarding build 27+. Please notify me for necessary corrections and additions of the below list.
Known Issues List as of 2013/12/28 (theROM build from 27):
HDMI doesn't work
Workaround: use stock LG GB ROM (I don't know whether stock LG ICS works)
Calls from BT headset connect but are silent for caller and callee
Workaround: use e.g. CM10.1 T-builds or ParanoidAndroid (PA) ROM
Root cause: not yet found; speculation: volume gain factor is set to 0 somewhere
Discussion: see e.g. post3, post2 , post1 issue b)
Mobile data counting doesn't work (blue arrows on mobile data indicator don't appear; e.g. Avast shows error message)
Workaround: use e.g. CM10.1 T-builds or ParanoidAndroid (PA) ROM
Root cause: bug in Android 4.3 (inherited to CM10.2)!?
Discussion: see e.g. note 3 in post3, post2, post1, report to Google
Stock camera
takes heavily over-exposed pics with flash
Workaround: tap the screen first before you click the camera fire button; this will correct exposure parameters
crashes often, or produces crashes of Trebuchet and gallery
Workaround 1: use e.g. cam app ported for CM10.1 by feav; it provides also features like panorama pix missing in the stock cam
Workaround 2 (not fully proven): flash the gallery.apk from build 23; some say the stock cam works without crashes then
BT media playback speeds up after minutes to hours.
Fix: at least fixed in build 22 (I dont't remember the exact build)
Some apps (e.g. Candy Crush) crash with the KK in the RAM hack version
Workaround: flash the no RAM hack (norh) version of Kowalski kernel (KK) by Pengus77
Slow GPS fix. Cause: missing file \data\gps\lto.dat that is up to date too.
Fix: seems to be fixed in build 23; some issues with the fix have been reported; under investigation
Literature: xda forum thread2, [URL="http://forum.xda-developers.com/showthread.php?p=15271402#post15271402"]thread1[/URL]
Long lags after heavy filling and emptying the flash memory. Reboot does not help
Workaround: backup data partition, wipe it, and restore the backup
Root cause: kernel does not implement TRIM functionality that makes use of the SD/MMC ERASE (CMD38) command.
References: wikipedia TRIM, wikipedia TRIM#SD/MMC
Discussion: post4, post3, post2, post1
Mobile data mode keeps being disabled when switching airplane mode off
Workaround: either disable and re-enable data or toggle 2g/3g twice. In some rare cases these workarounds won't work and a reboot is needed
Root cause: yet unknown
Current time shown is that for GMT time zone instead of for your local timezone. Time shift is always in full hours.
Workaround 1: Reboot; normally this restores correct time display.
Workaround 2: Disable automatic time sync and install a time sync app
Workaround 3: If you'd like to keep using automatic time you should add "telephony.test.ignore.nitz=true" to your build.prop
Root cause: yet unknown
Discussion: post2, topic #3 in post1
Some apps always crash under theROM and they also don't work on stock ICS on P990. Some of such seem to be Viber, Instagram, etc.
Request: please report as soon as the app started working correction on a new theROM build.
Recommendation 1: Search in this thread if your app is known to be incompatible with theROM
Recommendation 2: Search the internet if your app is known to be incompatible with stock ICS on P990
Recommendation 3: Try your app on P990 under stock ICS
Rule: never post problems with your app in this thread if its incompatibility to theROM or ICS on P990 is already known!
Recommendation 4: Ask the author of your app for help
Workaround: Use your app on P990 under stock ICS, or on another phone. (sorry for bad news!)
Root cause: potentially missing NEON support by P990; many others possible
no FM radio
Consider not flashing theROM in case you can't live with one or more of the listed open issues.
Please report any ideas, how to further analyze or fix the issue. Or please provide better workarounds.
The above list is to my best knowledge. I can neither guarantee it is correct nor it is complete. Please help to improve it.
Every bug is an issue. But there might be issues not caused by bugs (= errors in source code).

thanks to
@tonyp
@spyrosk
@pengus77
OLD BUILDS DOWN HERE :
"THEROM" OLD BOOTLOADER VERSION 26.2 CM 10.2
"THEROM" BUILD#3 OLD BOOTLOADER VERSION 26.2 CM 10.2
"THEROM "BUILD #4 OLD BOOTLOADER VERSION 29 AUG
"THEROM" BUILD #9 OLD BOOTLOADER VERSION
"THEROM BUILD10" OLD BOOTLOADER VERSION
"THEROM BUILD13" OLD BOOTLOADER VERSION
"THEROM BUILD15" OLD BOOTLOADER VERSION
"THEROM BUILD16" OLD BOOTLOADER VERSION
"THEROM BUILD17" OLD BOOTLOADER VERSION
"THEROM BUILD 18" OLD BOOTLOADER VERSION
"THEROM BUILD 20" OLD BOOTLOADER VERSION
"THEROM BUILD 21 OLD BOOTLOADER VERSION
"THEROM BUILD 25 OLD BOOTLOADER VERSION Thanks @dcr-NI (first conversion)
if someone is also interested in the experimental version, please check for the link below: These two builds are not exactly same, please see which suits you more and give feedback to @tonyp accordingly.
"THEROM CM10.2 - exp-opt OLD BOOTLOADER VERSION
Thanks and enjoy guys

Changelog TheROM - take it or leave it
Changelog build 27:
Ships with the awesome kk 3.1 bcmdhd alpha 15 by @pengus77.
Big thanks to @hjunii - without him this wouldn't be possible.
added option & quicksettings tile to enable/disable Halo
reverted my netd tethering hacks, they were bcm4329 specific.
I do not know if tethering works with bcmdhd, yet - feedback required
re-enabled wifi optimizations by default (they were incompatible with bcm4329, so i had disabled them)
in case you notice any problems (which you shouldn't) go to settings - wifi - advanced and untick it.
Changelog build 26:
merged CM10.2.0 stable codebase
merged all TheROM translations pull requests
Changelog build25:
fixed Stock Camera
cyanogen has merged in some Features which our camera blobs don't support anyways, so I've rolled them back
merged upstream
I believe this should fix the ThemeChooser some people posted here, at least I've seen a commit regarding that on Gerrit.
Please provide feedback.
Changelog build 24:
fixed the brightnessslider to only show when enabled
merged CM10.2 RC1
ships with a customized KowalskiManager by @wfd which automatically enabled auto hotplug as well
Changelog build 23:
added auto downloading the lto.dat file (for gps assistion data). Hopefully this brings up GPS back to the CM10.1 standards (at least after the first fix aka TTFF).
It's enabled by default, but will only update the file via WiFi by default (check the new option at Settings - Location access)
Properly enabled GPU accelleration.
I've found out that our device didn't fully utilize hardware accelleration. The reason is our low RAM - and enabling hwa takes about 8mb.
But with a GPU as powerful as ours I think those 8mb are well spent, we'll see how it turns out, make sure to post feedback.
In a first quick test the UI does seem more responsive.
Note that this is NOT equal to the "Force GPU rendering" option in the developer section! This one should stay off, as apps that for various reasons do not use GPU rendering shouldn't get forced into it.
enabled 2nd core auto hotplug by default. This will hopefully get rid of the plug-in BSODs of people not reading the threads (and thus not enabling the option at the KowalskiManager).
updated Torch overlay (this does hopefully fix the missing torch widgets some people had - please post feedback)
updated the OpenGL version. I have no idea how and if we'll notice that.
Thanks @DJNoXD for sending me a pull request.
removed the CMUpdater which slipped in under my nose.
I've slapped in a new more generic bootanimation, courtecy of +Dima Skvarskyi
Changelog build 22:
-Os buildflag optimizations
(smaller modules loaded into the RAM means more free RAM available to the phone)
synced to CM10.2-M1
Changelog build 21:
merged upstream
(3 weeks of CM10.2 patches and updates - didn't particularly check them, if you notice something new post it here)
included Google Maps (v7.3.0) by default
(as Google removed Tegra2 compatibilty for v7.0+)
reverted the Camera Wrapper for now, I am not convinced about it's usefulness and want to try it without for some time again.
Changelog build 20:
It's mostly identical to build 19, I just merged upstream and included the new translations (see below).
A couple days ago I read a tip somewhere to use -Os instead of -O2 when compiling arm modules.
So I just made another exp build to try this - you can find it labeled as "exp opt" (experimental optimization) in the download directory.
In theory the exp build should have a slightly worse performance (if noticable at all) but more free RAM which could help our low RAM phone (if noticeable at all).
Oh and I've included the translations I got sent (Spanish, French, Russian, Portuguese BR & PT):
https://github.com/tonyp/TheROM-translations/commits/master
Changelog build 19:
It's basically an upstream merge - but CM fixed the Camera image being "stuck" after taking a photo, which is the last bug that I wanted to see fixed before calling it the next stable.
Changelog build 18:
Quickmemo support
As @Firtecy already posted he fixed the Quickmemo apk to work with CM10.2.
Thus I re-added the Quickmemo support into the framework.
I've recoded it with a better, adaptive implementation. Now you'll only have the Quickmemo entry in the Buttons settings when Quickmemo is actually installed - if not it will be completely hidden.
Flashable zip download here: http://tonyp.basketbuild.com/index.php?dir=main/TheROM/addons/
To open it you got two options: press vol- and vol+ simultaneously or assign the button at Settings - Buttons.
added a new bootanimation.
Thanks to @vviper for creating it!
replaced statusbar icons with the one from PA (which are a little lighter)
removed the Statusbar Transparency "always" option
Settings - buttons FC fix + another minor memory leak fix + merged upstream
Changelog build 17:
Network Location Toggle
Custom System Animations
Fixed a bunch of FCs & brought back Storage Settings content
merged upstream (Camera Launcher QS Tile etc.)
Changelog build 16:
removed ActiveDisplay again
disabled listview animation by default
You can turn it on at Settings - TheROM. I think they're quite fun to play around with!
merged upstream fixes
Changelog build 15:
Statusbar Transparency
Active Display re-added (I've disabled the proximity sensor properly now - it only gets used in the pocket mode now)
Still this does drain some battery when you get lots of Notifications. I'll look into creating a widget to toggle it on and off.
ListView animations
To show off and for the lulz it's enabled by default - you can disable (or change) it at TheROM settings.
I've added a a quick option to the Notification Drawer style options to restart the SystemUI.
I've been annoyed by the fact that I either had to reboot or use an external app.
changed default dpi to 213
(you can change back to the stock 240 at TheROM settings - hybrid)
merged upstream
(but removed the CMAccount, me no likey)
Changelog build 14:
Implemented the RIL_UNSOL_LGE_RESTART_RILD response.
This has been reported as missing by @gios_ some time ago here.
I'm not sure if the implementation is correct, I've adaptoed it from the P880.
We'll have to test and see if it changes anything for those who still have data drops every now and then (for me they seem fixed since kk 126).
(Note: This isn't related to the no signal after airplane mode bug, which you usually can solve easily by double tapping data in the QuickSettings (= disable and enable it)).
Replaced PerformanceControl with the KernelControl app by @Beene.
If you encounter any bugs make sure to report them to him and post your feedback about the app in his thread.
Merged upstream.
One of the changes is the integration of CMs PrivacyGuard into App Ops - called Privacy Guard 2.0.
You'll find it at Settings - Security - Privacy Guard.
Unfortunately the longpress on an item (where you could fine tune your settings in theory) isn't working yet (FCs), will get fixed soon.
Update: here is an updated Settings.apk which will solve the FC for those who need access to App Ops.
Needs to be pushed to /system/app. Then longpress the app in the Privacy Guard options.
Changelog build 13:
removed Active Display for now
(fixes the battery drain)
Changelog build 12:
cleaned some commits, especially Active Display
It works as expected for me - hopefully now for everyone else as well.
Additionally it's a "make clean" build, I assume the android version update broke something here in the last one.
fixed some logspamming
I've discovered a minor bug in the Processor settings in the Performance menu.
Thus I disabled it - to compensate it I included an updated PerformanceControl app again, which gots some decent additions compared to the old version
I removed ViPER FX again as I discovered you can just get it from the PlayStore
Don't worry, it'll be in English once you install it
restructured the TheROM Settings. I've got a PM from someone who wanted to translate it to other languages, this makes it easier.
You can download the strings here
After translating the file move it into the correct subfolder for your language and post it here, then I'll include it.
Changelog build 11:
I got great news. I don't know if someone remembers, but ages ago in my PA ROM I had experimented with hacking the framework and changed some ADJ values to protect the launcher from redrawing.
One shouldn't just change the values (that's what the SuperCharger does), as that would break androids default memory management, thus I re-arrenged the code in the ActivityManagerService to reflect those changes back then.
I just had a look at my old code and figured out a way better and way cleaner method to hook into that.
I've just compiled my testbuild and it seems to work. It's not yet ready, just a test if my theoretical concept works.
I want to introduce an option for that, where you can control the intensity. By the end of next week I will have a bit more time, then I'll expose an option in the settings.
My current idea is to call it "Prevent launcher redraws" with the levels "disabled", "moderate", "needtothinkofsomething" and "extreme".
Currently extreme is hardcoded.
I've uploaded the build to my TheROM folder if anyone wants to try it out. Please give feedback if you notice an improvement.
With extreme it'll be quite hard to get it killed, as only perceptible apps (like playing music) will be more important.
I've switched around between Google+, Boat Browser and the Reader+ app and I didn't manage to kill the launcher
Edit: good, opening webpages with loads of images in the browser does kill the launcher. We don't want to have it unkillable (keep in memory), when the system needs the ram it should be possible to get it.
It's a lot cleaner than the hacky way the Supercharger does to accomplish the same goal.
The supercharger hacks into the framework and changes the ADJ values directly - unfortunately these are directly accessed in the ActivityManagerService.java which causes some unwanted sideeffects with the default android memory management.
I'm just modifing the ADJ value at runtime.
Additionally what I really don't like with the Supercharger: It's prioritizing the Launcher above perceptible and even visible apps.
Killing the music player while listening to music or killing visible elements instead of the launcher when the system needs memory? That's insane imo.
To prevent confusion: visible apps are not identical to the foreground app - but could be some elements visible behind an overlay. Would still look bad if those suddenly dissappear.
Edit: I've decided to just brand it as build 11.
Additional changelog: Android 4.3 JLS36G merged
Changelog build 10:
- added Active Display options from ChameleonOS
- added notification drawer background options and transparency (requires a reboot to apply)
- QuickSettings: option to open the apps in floating mode ("in Halo") on longpress
- RAM usage circle on recent apps
- cherrypicked some memory leak fixes from various sources
- fixed some FCs
- fixed (?) the Trebuchet FCs (at least I can activate the searchbar again)
- merged upstream
Changelog build 09:
Based on the idea of alok.tari clicking the clock in the statusbar dropdown will open Timely if it's installed.
(Longpressing it will always open the clock app you set as default).
Then I reverted the dalvik low memory initializing, I suspect that to be related to some of the slowdowns. The system will use ~6mb more RAM again, but it might be worth it, we'll see.
Additionally I merged upstream of course - I've seen some fixes for headset plug-in (which fixes a bug if you don't have a music player app installed) and Trebuchet, I guess these will fix the issues reported here.
I will say it again: CM10.2 is in nightly status - which means there will be bugs every now and then in the sources.
Let's hope CM will try to build stable releases soon again, as soon as those are out the amount of new bugs will decrease.
I won't have the time to look into individual issues up until the end of this month.
I just quickly made this build for myself (and am sharing it here with you).
Changelog build 08:
- new options for Halo (ninja mode, ping etc.)
- ViPER FX replaces DSPManager
- back to the ramhack kernel (M1) - I just missed the additional RAM it gives which results in more Launcher redraws etc.
- Cyanogenmod account (check CMs G+ page for details)
- Trebuchet: Support for custom icons per shortcut
- merged upstream
Changelog build 07:
- notification sound bug fix while playing media
- enabled backlight button brightness options at Settings -> Buttons
- reverted gps.tegra.so to the one official CM10 and CM10.1 use (this fixes all GPS problems for me)
- included Kowalski M1 norh kernel
- merged upstream (loads of bugfixes from CM)
Last but not least I tried something highly experimental - I decreased(!) the playback buffer as I want to know if this has an impact on A2DP playback.
Unfortunately I don't have my BT headset at hand, so you guys need to test it.
> Is BT audio (listening to mp3s) still working?
> Does the audio still speed-up?
Additionally I added some missing bluetooth configurations which might or might not increase it's stability.
Changelog build 06:
Gosh I just hate bugs, so I just had to push out a quick fixup build
I fixed the SystemUI FCs (this has been a bit nasty!), the Bluetooth share FC after booting and @Firtecy fixed his disappearing brightnessslider after rebooting.
(you can push the Bluetooth.apk to the clean CM10.2 ROM to fix the bluetooth share FC there as well).
Changelog build 05:
I've added the Notification BrightnessSlider, ported by @Firtecy (thx!).
Additionally some other small fixes I stumbled across + I removed the QuickMemo option again for now - it only works for CM10 and CM10.1 until someone ports it.
Changelog build 04:
I've added the following hardwarekeys button actions to the ROM:
- Screen off
- Open Power menu
- Toggle Last app
- Toggle Torch
- Take Screenshot
- Quickmemo (this is optional, you need to use my Quickmemo installer)
The CM10.1 ROM had some more options (like custom app, re-assign the back key), but that would have required more work and time than I can currently spend).
The important ones are in now (I consider Torch and Powermenu/Screen off extremely useful).
Oh and in CM10.2 you got the sweet "double tap home action".
Google keyboard updated to v1.1
Trebuchet loosing icons should be fixed
Changelog build 03:
Hybrid Engine \o/
Focal removed - it's buggy and takes 12mb of space
Extract it from my CM10.2 ROM if you need it
Donation menu moved to the buttom to get it out of the way
Some new stuff for Trebuchet , including the option to use icon packs
Oh and the apk now takes about 6 instead of the former 12mb
Some small fixes here and there
Changelog build 02:
I have pushed a small bugfixing update online: cm-10.2-TheROM-20130826.2-tonyp.zip
I just did some quick workarounds which certainly isn't perfect, but fixes the FCs for now:
1.) I removed the SetupWizard.apk. The PreferenceDrawer Settings app is causing problems with it. I will fix it properly when I find the time, but the Wizard isn't really needed anyways.
You will just have to manually go to Settings - Accounts and add your Google account now after a full wipe.
2.) I have removed the two SDCards from the storage menu (it now only contains the option to use the external SD as default one).
I tried some quick fixes but they didn't work and I really gtg, so this will do for now. Again I will properly fix it when I get more time.
If you absolutely need access to the menu for something (although I don't know what this could be) you should be able to use the Settings.apk from my CM10.2 build for that.
I've hidden old changelogs to shorten the post. You have link to every original post/changelog from tonyp...

angel_boulevard said:
every day you bring us to new exciting..many many thank to you @tonyp..your rom is priority for me
P/s:a question.do any plan gapps 4.3 which google now working ?
Click to expand...
Click to collapse
Google now works in every ROM he puts out, I found that when you restore your apps your have to let everything instal [including google play services], uninstall google now and reinstall and it should work.

harucrux said:
Google now works in every ROM he puts out, I found that when you restore your apps your have to let everything instal [including google play services], uninstall google now and reinstall and it should work.
Click to expand...
Click to collapse
read again this is cm10.2 which one with mini gapps not working google now

Its working for me with the steps in the post above.
---------- Post added at 05:21 AM ---------- Previous post was at 05:12 AM ----------
angel_boulevard said:
read again this is cm10.2 which one with mini gapps not working google now
Click to expand...
Click to collapse
Its working for me with the steps in the post above.

Just couldn't stop laughing reading the FAQ
An awesome Rom and an awesome thread.
Thanks a lot for your hard work, we really appreciate it:thumbup::beer:
Sent from my HTC One using xda app-developers app

Dig bick! xD
Enviado desde mi LG-P990 usando Tapatalk 2

[FONT="<font><font>Comic Sans MS</font></font>"]Thanks for the new ROM, (again XD).
Keep it up!!.
Enjoy your holiday.
Greetings.[/FONT]

Thx 4 all Tonyp ! Downloading now...
EDIT : is possible to update from CM 10.2 by Tonyp 20130824.1 ???

Great work Tonyp thank you for everything!!
Going to buy you a beer!!
Since this is your personal ROM could you give us the settings and values you use or recommend?
Sent from my LG-P990 using Tapatalk HD

Where will you post changelog from now on since there are like 5 topics? i see new build but cant find changelog?
thanks

PYCON said:
Thx 4 all Tonyp ! Downloading now...
EDIT : is possible to update from CM 10.2 by Tonyp 20130824.1 ???
Click to expand...
Click to collapse
ya..no problem

I converted CM10.1 version for oldbl, flashed it and it works perfect. I'm currently uploading it, it will take about half an hour, if anyone wants to download it. Many thanks tony, I will donate as soon as I get my paycheck.
edit: here is the link https://dl.dropboxusercontent.com/u/11122462/cm-10.1-TheROM-slap-20130730-tonyp-oldbl.zip

sad to be the onliest guy, which have settings error crash after install.
I can't expect any help from TonyP (I can understand), anyone can help of the other users?
I do full wipe, install cm10.2 version, boot, the first I do is a reboot, and after next boot I choosed the language eng (us) and ok. then I got everytime settings error. then crash to language chooser......
all good now!

packyman said:
sad to be the onliest guy, which have settings error crash after install.
I can't expect any help from TonyP (I can understand), anyone can help of the other users?
I do full wipe, install cm10.2 version, boot, the first I do is a reboot, and after next boot I choosed the language eng (us) and ok. then I got everytime settings error. then crash to language chooser......
Click to expand...
Click to collapse
Try 4 WIPES !
Wipe Cache + Wipe Davilk + Wipe Data ( Factory ) + Wipe System ( Rom ).
Flash THE ROM e retry...

[ROM] [UNOFFICIAL] [LINARO 4.8.3] [DUALSIM] [APP2SD] CyanogenMod 11 [Update 20141113]

CyanogenMod 11.0
This ROM is compiled from NIGHTLY source instead of monthly M - builds source.
For monthly M builds, check THIS ORIGINAL THREAD by the respected developer, @pawitp.
All credits for this ROM, as well as all other AOSP based ROMs for Galaxy Grand goes to him.​
pawitp has repeatedly mentioned that he will only provide pure CM11 ROM builds. I needed dual-SIM in AOSP but with a few feature additions and optimizations. I tried Carbon and PA with pawitp's patches to enable dual SIM in them, but I was unsuccessful. So I compiled CM11 with few things that I wanted and sharing it.
This ROM will stay very close to pure CM11, with very few additions and changes. I'll upload the zip whenever I compile for myself. I'll only provide full ROM zip files and no delta zips.​
EXTRA ADDITIONS
Compiled from bleeding edge NIGHTLY source of CM11
Compiled using Linaro 4.8.3 toolchain
O3 optimization flag
Link Time Optimization flags - read more about it HERE
APP2SD support - ability to move apps to external SD card
Multi-user support
DUAL-SIM
Dual-SIM works
Instructions on how to activate and deactivate dual SIM can be found in FAQ in the original post by @pawitp - HERE
You can also use my app, MultiSIM Toggle, to activate or deactivate dual-SIM functionality. Read more HERE.
IMPORTANT
If you are using my build of CM11, do not report bugs or issues in pawitp's thread. Post them here.
WHAT IS WORKING?
WiFi
Bluetooth
RIL (Calls, Mobile Data, SMS)
Sensors
GPS
Camera
Everything else not listed under "Known Issues" section
KNOWN ISSUES
Inbuilt screen record does not work
FM Radio does not work
Stock browser does not use hardware acceleration (Please use Google Chrome)
Sometimes wake up causes music stutter
Cannot changed advanced settings from dialer settings (e.g. reverse lookup) when dual SIM is enabled
Does not work on 4.1 stock ROM's bootloader, please upgrade to 4.2 before flashing
Additionally, Dual SIM has the following limitations:
Both SIMs are always enabled (no way to disable one SIM)
"Receive incoming call while data is enabled" is always enabled
The QuickSettings tile will display the status for the currently selected SIM for data
There is no arrow activity indicator in the status bar.
Changing 2G/3G network mode using the QuickSettings toggle is not supported, only do it from Settings.
3G may not work properly if Dual SIM mode is enabled with only 1 SIM inserted
Cannot set different ringtone for each SIM
Call logs doesn't know the incoming SIM
PATCHES
(Patches are already included in the ROM)
Patch to system/core for RIL to work: https://gist.github.com/pawitp/5372673.
Patch to hardware/broadcom/libbt for bluetooth to work: https://gist.github.com/pawitp/7891380.
Patch to frameworks/native to support legacy binaries: https://gist.github.com/pawitp/7891421
Patch to frameworks/native to workaround hwc issues: http://review.cyanogenmod.org/53162/ and https://gist.github.com/pawitp/7891444.
Patch to frameworks/av to fix audio/video issues: https://gist.github.com/pawitp/7945188
Patch to external/chromium_org to workaround hwc issues: https://gist.github.com/pawitp/7910708
Patch to packages/app/SamsungServiceMode to fix service mode: http://review.cyanogenmod.org/57400/
Dual SIM Patches: https://gist.github.com/pawitp/9433442
Patch to frameworks/opt/telephony to fix non-looping ringtone issue: https://gist.github.com/pawitp/0f400e7b5cfb9bc70c25
-----
Patch to frameworks/base to fix haptic vibration feedback: https://gist.github.com/xenon92/af8df0708c39a24a9dc5
Patch to packages/apps/MediaProvider for larger thumbnail images (still testing): https://gist.github.com/xenon92/0977a22ec53ca5d0c33b
INSTALLATION INSTRUCTIONS
Please keep in mind if a special instruction is needed it will be noted in the Changelog
Make a backup of your EFS. Read more HERE
Make sure you are either on any KitKat ROM (CM11, SlimKat, etc) or on 4.2.2 TW based ROM and NOT on 4.1.2 TW based ROM
Download the latest build
Download Gapps
Recommended - Full wipe and factory reset
Flash ROM using latest ClockworkMod recovery
Flash Gapps
Reboot.
Enjoy!
UPDATE INSTRUCTIONS
Download the latest build
Flash it using ClockworkMod recovery
Wipe cache
Wipe dalvik cache
Reboot
Enjoy!
SOURCES
Device tree can be found on my Github.
Kernel source can be found on my Github.
CyanogenMod source can be found here.
DOWNLOADS
CyanogenMod 11
Old builds are here
PA Gapps
Latest Recovery​
CREDITS
Big thanx to @pawitp for his time, work and patches on Galaxy Grand Duos.
CyanogenMod team
Linaro team
Kishan14, LuK1337 for haptic vibration on softkeys
XDA:DevDB Information
CM 11.0, ROM for the Samsung Galaxy Grand Duos i9082
Contributors
xenon92
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Stable
Current Stable Version: 20141113
Stable Release Date: 2014-11-13
Created 2014-07-24
Last Updated 2014-11-13

CHANGELOG​
20141113
- Added back -O3 optimization flag
- Compiled using default toolchain (TEST - fix rendering issues in games)
---x---x---x---
20141102
- Removed O3 optimization flag (TEST - fix rendering issues in games)
---x---x---x---
20141025, 20141014, 20140922
- NIGHTLY source build
---x---x---x---
20140813
- Fix audio on call waiting in dual SIM mode (thanx to pawitp)
---x---x---x---
20140809
- Fix protected apps (Settings > Apps > Protected Apps (menu)) (BUG)
---x---x---x---
20140801
- Removed a few useless live wallpapers
---x---x---x---
20140725
- Fixed APNs and mobile network in dual-SIM mode (thanx to pawitp)
---x---x---x---
20140724
- Initial release
​

SCREENSHOTS​
​

Looks good, will watch closely, thx for this Rom, best of luck:good:

Apn bug
Apn doesn't get save
Overall good rom, very smooth thanks dev

This is what I m waiting for
Thank you very much for a lovely ROM
Xenon you alwaz Rock with App2Sd.
Love your ROM.
:good::good::good::good::good::good::good::good:
Hemant
---------- Post added at 10:08 AM ---------- Previous post was at 10:07 AM ----------
where is the screenshots??????
---------- Post added at 10:21 AM ---------- Previous post was at 10:08 AM ----------
What is APN??
You mean Access Point Name???? in mobile network???
:good::good::good::good::good::good:

APN problem on this or not ?
Sent from my GT-I9082 using Tapatalk

Status 7 Error On installation
Dear Xenon,
I am getting Status 7 Error on Installation
I m on 4.2.2 Xperia z Flavor by Balli Boxer.
Please help.
Hemant
---------- Post added at 11:34 AM ---------- Previous post was at 11:13 AM ----------
Very slow response xenon
Pls reply eager to install this rom

Aren't O3 flags unstable ?
---------- Post added at 12:19 PM ---------- Previous post was at 11:41 AM ----------
SIM networks not working properly.

hemant4409 said:
Dear Xenon,
I am getting Status 7 Error on Installation
I m on 4.2.2 Xperia z Flavor by Balli Boxer.
Please help.
Hemant
---------- Post added at 11:34 AM ---------- Previous post was at 11:13 AM ----------
Very slow response xenon
Pls reply eager to install this rom
Click to expand...
Click to collapse
Status 7 error is most of the time a problem with using the wrong recovery to flash.
I will give it a shot and take some screenshots.
Please don't think that a developer has nothing else to do then answer all the question immediately and be on XDA 24/7

Thanks RichyE
How to get rid of this error?

hemant4409 said:
Thanks RichyE
How to get rid of this error?
Click to expand...
Click to collapse
Use the latest version of recovery.
I see Xenon92 provided a download link in OPS

akiratoriyama said:
Aren't O3 flags unstable ?
---------- Post added at 12:19 PM ---------- Previous post was at 11:41 AM ----------
SIM networks not working properly.
Click to expand...
Click to collapse
O3 flag is not unstable. My Carbon ROM has O3 flag enabled too.
I see that SIM networks in dual-SIM mode are not working as well as that APNs are not getting saved. Added to known issues.
Screenshots added.

xenon92 said:
O3 flag is not unstable. My Carbon ROM has O3 flag enabled too.
I see that SIM networks in dual-SIM mode are not working as well as that APNs are not getting saved. Added to known issues.
Screenshots added.
Click to expand...
Click to collapse
SystemUI (Especially notification drawer) starts acting strange/glitchy/slow while audio is routed either through Speaker or Earphones.
To reproduce the bug -
1) Play any song though Apollo either through speaker or with earphones.
2) Press the home button.
3) Try to 'swipe' to quick settings from the normal notification screen.

akiratoriyama said:
SystemUI (Especially notification drawer) starts acting strange/glitchy/slow while audio is routed either through Speaker or Earphones.
To reproduce the bug -
1) Play any song though Apollo either through speaker or with earphones.
2) Press the home button.
3) Try to 'swipe' to quick settings from the normal notification screen.
But your nightlies satisfy my ORD for which I can't than enough [emoji13]
Click to expand...
Click to collapse
Settings > Notification drawer > Quick settings panel > Uncheck Equalizer.
Equalizer tile is causing the issue as it is being constantly updated.

New build uploaded. 20140725.
- Fixed APNs and mobile data network in dual SIM mode (thanx to pawitp)

Can any one tell me how's the battery backup and features of the rom

about a2sd
thanks a lot for this great ROM you get all good features from ROM worlds
i have one question if you please
regarding a2sd i always use oald dictionary which has a very big data ,after installing and downloading data =2.1 GB on internal memory and then moved the application to SD card the internal memory size remains as it(contains the oald data)
i have 4 GB ext4 secondary partition on SD card
is there anything wrong
thanks in advance

waleed_hanafy said:
thanks a lot for this great ROM you get all good features from ROM worlds
i have one question if you please
regarding a2sd i always use oald dictionary which has a very big data ,after installing and downloading data =2.1 GB on internal memory and then moved the application to SD card the internal memory size remains as it(contains the oald data)
i have 4 GB ext4 secondary partition on SD card
is there anything wrong
thanks in advance
Click to expand...
Click to collapse
It depends on what is being moved. Check the screenshot in OP. The amount of data moved shows under USB storage app. Whatever is moved, goes into android_secure folder.

@xenon92 Sir, Can you use dev-host website to upload ROM builds..
AndriodFilehost is good but it's servers are not... most of the time after downloading approx 180mb the downloading stops and cannot resume afterwards!! Say's to start from beginning :crying: (Using IDM)
But Dev-Host works fine for me!

[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.

[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][DEVELOPMENT][9.0] LineageOS 16.0 [POLLUX/POLLUX_WINDY][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"
}
This is an Unofficial builds for Xperia Tablet Z LTE/Wi-Fi.
About ROM
LineageOS is a free, community built, aftermarket firmware distribution of Android 9.x (Pie), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
The source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Installation
Download the latest build
Place ROM in your SD card or Internal Storage
Reboot into recovery mode
Full wipe and factory reset (recommended)
Flash ROM
Reboot
Downloads
Pollux: AFH​Pollux_windy: AFH​​LineageOS addonsu for root access
(Information) Read the Root section of the Q&A thread
(Download) Download the addonsu for arm : LineageOS Downloads / Extras
(Optional) Flash the zip on a working Lineage installation (once)
(Information) Upon ROM updates, the addonsu is preserved
Reboot
Recommended Recovery (optional)
TWRP 3.2.x​Gapps (optional)
OpenGapps (ARM/Android-9.x): http://opengapps.org​​Sources
LineageOS on Github​Kernel: apq8064​
XDA:DevDB Information
LineageOS 16.0 for the Sony Xperia Tablet Z, ROM for the Sony Xperia Tablet Z
Contributors
CaHbKaUp, CyberWalkMaN, AdrianDC, Chippa_a
ROM OS Version: 9.x Pie
Version Information
Status: Testing
Beta Release Date: 2021-09-16
Created 2019-04-26
Last Updated 2021-09-17

FEATURES AND ISSUES
Code:
- Boot : Ok
- GApps : OpenGApps Nano Ok
- FOTA Recovery : Ok (see below)
- WiFi : Ok (real SONY MAC address)
- Bluetooth : Ok (real SONY MAC address)
- WiFi Hotspot : Ok (2.4GHz only)
- RIL - Phone - Data : Ok
- GPS : Ok
- Camera : Ok
- Camcorder : Ok
- MicroSD : Ok
- Accelerometer : Ok
- Compass : Ok
- Gyroscope : Ok
- AOSP sensors : Ok
- FM Radio : Work In Progress
- Microphone : Ok
- Audio & external audio : Ok
- Bluetooth audio : Ok
- NFC : Ok
- Kernel : Ok, Updating frequently
- Graphics : Ok
- 3D Rendering : Ok
- Clock : Ok
- Offline Charging : Ok
- SEPolicies : Work In Progress

CaHbKaUp said:
FEATURES AND ISSUES
Code:
- Boot : Ok
- GApps : OpenGApps Nano Ok
- FOTA Recovery : Ok (see below)
- WiFi : Ok (real SONY MAC address)
- Bluetooth : Ok (real SONY MAC address)
- WiFi Hotspot : Ok (2.4GHz only)
- RIL - Phone - Data : Ok
- GPS : Ok
- Camera : Ok
- Camcorder : Ok
- MicroSD : Ok
- Accelerometer : Ok
- Compass : Ok
- Gyroscope : Ok
- AOSP sensors : Ok
- FM Radio : Work In Progress
- Microphone : Ok
- Audio & external audio : Ok
- Bluetooth audio : Ok
- NFC : Ok
- Kernel : Ok, Updating frequently
- Graphics : Ok
- 3D Rendering : Ok
- Clock : Ok
- Offline Charging : Ok
- SEPolicies : Work In Progress
Click to expand...
Click to collapse
Does this mean that GPS is working again on pollux_windy devices? If I find the time I definitely will give this a try over the weekend!

lm089 said:
Does this mean that GPS is working again on pollux_windy devices? If I find the time I definately will give this a try over the weekend!
Click to expand...
Click to collapse
Probably yes, while sepolicy on current development version in permissive mode, but it still WIP for previous versions

Which repos did you use to build 0425? Is the nougat kernel you linked the one that works for pie? This roomservice cooks a pollux build that is stuck on the boot animation.

CaHbKaUp said:
Probably yes, while sepolicy on current development version in permissive mode, but it still WIP for previous versions
Click to expand...
Click to collapse
Hi, just a quick first report:
did a complete wipe then installed this ROM >> reboot into recovery >> flash openGapps Pico build 20190426 + Magisk 18.1 >> reboot to system
did basic setup (Google + Lineage) without restoring anything from cloud etc.
installed some GPS testing app >> did a complete A-GPS delete / refresh cycle
Got a GPS fix after approx 6 minutes (yippiiiieee!!! Finally)
Switch off GPS, shut down GPS Test, then repeated GPS Test >> fix 10 seconds!!
So this is great.
Then tested a few other things. Here's what works for me and what doesn't:
Code:
- Boot : Ok
- GApps : OpenGApps Nano Ok
- FOTA Recovery : Ok
- WiFi : Ok
- Bluetooth : Ok
- WiFi Hotspot : n/a
- RIL - Phone - Data : n/a
- GPS : Ok (Yessss!)
- Camera : NO (see below)
- Camcorder : didn't test
- MicroSD : Ok
- Accelerometer : NO
- Compass : NO
- Gyroscope : NO
- AOSP sensors : ??
- FM Radio : NO (I'm aware you wrote that)
- Microphone : didn't test
- Audio & external audio : Ok
- Bluetooth audio : didn't test
- NFC : didn't test
- Kernel : ??
- Graphics : Ok
- 3D Rendering : didn't test
- Clock : Ok
- Offline Charging : Ok
- SEPolicies : didn't test
What else is not working is display rotation: it is fixed to landscape mode (with one exception, see below). This probably is due to the fact that most sensors apparently don't work here: no compass, no gyroskope etc. I'm using "Smart Tools" app. All tools that are using the device's sensors are dead. Tried to calibrate, but no result.
Camera isn't working either: it immediately crashes as soon as I click the shutter (no matter whether I use front or back camera). Tried to get a logcat (using catlog app), hope it contains what's needed to look into this.
Regarding the camera there are two more issues:
1 - the camera shutter button is halfway hidden behind the navigation bar (see screenshot) (see update below)
2 - if I start the camera the tablet's display changes to portrait mode, and then it stays there until I shut down the tablet
-----
sorry for not mentioning earlier that apart from those issues this ROM makes a very good impression: very fast and responsive. Thanks a lot for taking care of this!!!
Will return now to LOS 15.1 as I need a fully working device this afternoon. Let me know if you need more info, probably can do some more testnig tomorrow
Update (after being back at 15.1 official):
All sensors working again, incl. display rotation, compass, water level etc. ;
Also Camera is working fine again, but I just realized that also in this version the shutter button is halfway hidden, as can be seen in the screenshot. So this apparently is a generic (minor) flaw...

Fence, it's good news and I was about to sell my tablet Z. I'll try to see what's going on with android 9. Thanks devep.

confirmed as well
lm089 said:
Hi, just a quick first report:
did a complete wipe then installed this ROM >> reboot into recovery >> flash openGapps Pico build 20190426 + Magisk 18.1 >> reboot to system
did basic setup (Google + Lineage) without restoring anything from cloud etc.
installed some GPS testing app >> did a complete A-GPS delete / refresh cycle
Got a GPS fix after approx 6 minutes (yippiiiieee!!! Finally)
Switch off GPS, shut down GPS Test, then repeated GPS Test >> fix 10 seconds!!
So this is great.
Then tested a few other things. Here's what works for me and what doesn't:
Code:
- Boot : Ok
- GApps : OpenGApps Nano Ok
- FOTA Recovery : Ok
- WiFi : Ok
- Bluetooth : Ok
- WiFi Hotspot : n/a
- RIL - Phone - Data : n/a
- GPS : Ok (Yessss!)
- Camera : NO (see below)
- Camcorder : didn't test
- MicroSD : Ok
- Accelerometer : NO
- Compass : NO
- Gyroscope : NO
- AOSP sensors : ??
- FM Radio : NO (I'm aware you wrote that)
- Microphone : didn't test
- Audio & external audio : Ok
- Bluetooth audio : didn't test
- NFC : didn't test
- Kernel : ??
- Graphics : Ok
- 3D Rendering : didn't test
- Clock : Ok
- Offline Charging : Ok
- SEPolicies : didn't test
What else is not working is display rotation: it is fixed to landscape mode (with one exception, see below). This probably is due to the fact that most sensors apparently don't work here: no compass, no gyroskope etc. I'm using "Smart Tools" app. All tools that are using the device's sensors are dead. Tried to calibrate, but no result.
Camera isn't working either: it immediately crashes as soon as I click the shutter (no matter whether I use front or back camera). Tried to get a logcat (using catlog app), hope it contains what's needed to look into this.
Regarding the camera there are two more issues:
1 - the camera shutter button is halfway hidden behind the navigation bar (see screenshot) (see update below)
2 - if I start the camera the tablet's display changes to portrait mode, and then it stays there until I shut down the tablet
-----
sorry for not mentioning earlier that apart from those issues this ROM makes a very good impression: very fast and responsive. Thanks a lot for taking care of this!!!
Will return now to LOS 15.1 as I need a fully working device this afternoon. Let me know if you need more info, probably can do some more testnig tomorrow
Update (after being back at 15.1 official):
All sensors working again, incl. display rotation, compass, water level etc. ;
Also Camera is working fine again, but I just realized that also in this version the shutter button is halfway hidden, as can be seen in the screenshot. So this apparently is a generic (minor) flaw...
Click to expand...
Click to collapse
I can confirm auto ration does not work. Which isnt really bad big deal right now . But i'm sure ill get annoyed at some point

Hello, first of all I feel bad for not being able to try and give my feedback of this ROM right now (I use the tablet for college and right now it is not convenient to "experiment" with it) however I would sincerely congratulate the developer of it, I never thought to see another ROM on this Tablet that I liked since I bought. Sorry for my bad English, I will be closely following the development of the ROM and when possible I'll try it

I also can confirm auto rotate doesn't work

[OT?] Need help installing this ROM.
I'm currently using Official Lineage OS 15.1 build on pollux, and want to try this ROM.
But I just noticed that I dont have TWRP installed (its missing) on my tablet. I had TWRP installed in FOTA partition, but now its missing. Using Reboot to recovery option gives black screen after sony logo. Same results when manually rebooted after power off using vol buttons.
I don't know what happened, I've been using Lineage builds both unofficial and official from years on this tablet. And twrp in fota partition too, but never encountered this issue.
Don't have access to pc rn to try fastboot boot recovery.img, is there anything else i can try?
Tried Xperia Recovery app from play store which can flash recovery to fota using root but no help (used to work earlier) and dd if=/temp/rec.img of=/dev/block/...... In terminal, but didn't worked

Azazel Azay said:
I'm currently using Official Lineage OS 15.1 build on pollux, and want to try this ROM.
But I just noticed that I dont have TWRP installed (its missing) on my tablet. I had TWRP installed in FOTA partition, but now its missing. Using Reboot to recovery option gives black screen after sony logo. Same results when manually rebooted after power off using vol buttons.
I don't know what happened, I've been using Lineage builds both unofficial and official from years on this tablet. And twrp in fota partition too, but never encountered this issue.
Don't have access to pc rn to try fastboot boot recovery.img, is there anything else i can try?
Tried Xperia Recovery app from play store which can flash recovery to fota using root but no help (used to work earlier) and dd if=/temp/rec.img of=/dev/block/...... In terminal, but didn't worked
Click to expand...
Click to collapse
Are you by any chance using Magisk, and have updated to v19.x lately? Then you ran into a known problem new Magisk versions are having with Xperias' recovery option (see posts in various Xperia and Magisk forums). You have several options:
1) downgrade Magisk to 18.1
2) use a different SuperSu tool like the one from Lineage
Of course you need to reinstall Twrp first

Azazel Azay said:
I'm currently using Official Lineage OS 15.1 build on pollux, and want to try this ROM.
But I just noticed that I dont have TWRP installed (its missing) on my tablet. I had TWRP installed in FOTA partition, but now its missing. Using Reboot to recovery option gives black screen after sony logo. Same results when manually rebooted after power off using vol buttons.
I don't know what happened, I've been using Lineage builds both unofficial and official from years on this tablet. And twrp in fota partition too, but never encountered this issue.
Don't have access to pc rn to try fastboot boot recovery.img, is there anything else i can try?
Tried Xperia Recovery app from play store which can flash recovery to fota using root but no help (used to work earlier) and dd if=/temp/rec.img of=/dev/block/...... In terminal, but didn't worked
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=79514197&postcount=237

New update build 2019/05/22
Changes:
May 2019 Android security patch
Magisk 19.x fix

thank u for this!!
playing clash royale perfectly!

Was the rotate issue fixed?

fireflygwyn said:
Was the rotate issue fixed?
Click to expand...
Click to collapse
not yet, but i install nova launcher to use portrait mode, dont feel the diference

fireflygwyn said:
Was the rotate issue fixed?
Click to expand...
Click to collapse
I've read reports, that this issue can be fixed with this app.

Rootk1t said:
I've read reports, that this issue can be fixed with this app.
Click to expand...
Click to collapse
IF this is app fixable I have Nova launcher and ultimate rotation control. They work great together.

I do have the same problem it is due the use of majestic, you can flash recovery without pc