Related
Good morning guys, I would like if someone could help me with this error below, I already compile ROMs like CyanogenMod and AOKP, but this Slim is giving me the biggest job now stopped this error and i could not get out, someone has any idea?
Code:
GEN / media/ruberval/DADOS2/slimroms/out/target/product/galaxysmtd/obj/KERNEL_OBJ/Makefile
scripts / KConfig / conf - silentoldconfig Kconfig
Note: Some input files use or override a deprecated API.
Note: Recompile with-Xlint: deprecation for details.
GEN / media/ruberval/DADOS2/slimroms/out/target/product/galaxysmtd/obj/KERNEL_OBJ/Makefile
CHK include / linux / version.h
CHK include / generated / utsrelease.h
Using / media/ruberval/DADOS2/slimroms/kernel/samsung/samsung-kernel-aries the source for kernel
make [3]: `include / generated / mach-types.h 'is up to date.
target Java: AriesParts (out / target / common / obj / APPS / AriesParts_intermediates / classes)
CALL / media/ruberval/DADOS2/slimroms/kernel/samsung/samsung-kernel-aries/scripts/checksyscalls.sh
CHK include / generated / compile.h
/ media/ruberval/DADOS2/slimroms/kernel/samsung/samsung-kernel-aries/scripts/gen_initramfs_list.sh: Can not open '.. / ramdisk-ics / jb_combo /'
make [3]: ** [usr / initramfs_data.cpio.lzma] Error 1
make [2]: ** [usr] Error 2
make [1]: ** [sub-make] Error 2
make [1]: Leaving directory `/ media/ruberval/DADOS2/slimroms/kernel/samsung/samsung-kernel-aries'
make: ** [TARGET_KERNEL_BINARIES] Error 2
make: ** Waiting for other processes to finish.
Note: device / samsung / aries-common / AriesParts / src / com / CyanogenMod / settings / device / DeviceSettings.java uses or overrides a deprecated API.
Note: Recompile with-Xlint: deprecation for details.
Note: device / samsung / aries-common / AriesParts / src / android / hardware / TvOut.java uses unchecked or unsafe operations.
Note: Recompile with-Xlint: unchecked for details.
Ruberval Fenix @ :/ $ media/ruberval/DADOS2/slimroms
why don't you try to contact the dev of slims
I contacted but nobody answered me until today, I'll lock the topic because I decided it alone.
Alias could not see where I can close the post, a moderator could do it?
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...
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
NOTE:
THIS IS A DEVELOPMENT THREAD.
BUILDS ARE INTENDED FOR ADVANCED USERS, SO THEY CAN TEST AND GIVE FEEDBACK.
FEATURE REQUESTS WILL BE IGNORED, THIS IS PLAIN CYANOGENMOD.
Also, there are sisters threads for working on pollux, odin and dogo.
Changes:
- Jan 30: Initial release
- Feb 5: kernel updates, audio HAL modernization
- Feb 9: WiFi updates
- Feb 13: volume rocker wakeup, sdcard hotplug, camera focus changes, cleanups
- Feb 16: new call fix
- Feb 27: F2FS support
- Mar 1: audio update
- Mar 3: smooth boot animation
- Mar 6: more audio updates
- Apr 3: first 12.1 build
- Apr 20: radio fixed
- Apr 22: Android 5.1.1
- Apr 27: tons of cpu and gpu governor updates/fixes, wifi updates
- May 1: gpu gov and wifi updates
- May 7: app2sd fixes, selinux updates, fixed power hal, oss thermal mgmt, wifi fixes
- May 10: plethora of core kernel and platform updates, init changes
- May 22: scheduler and platform updates, reworked kernel configuration
- July 1: lollipop blobs, init update, new sensor drivers, kernel updates
- July 7: fixed incall audio
- July 8: fixed black screen on boot, fix booting into recovery by toggling volume keys
- July 9: fixed wlan&bt mac config
- July 11: fixed off charging mode
- July 20: fixed gps problems under certain circumstances
- July 21: lp kernel updates, als adjustments
- July 22: led color configuration from ui
- July 30: gps problems fixed again (duh), leds in off charging mode
- Aug 3: row io scheduler, open source gps hal, sepolicy update
- Aug 6: fix sd card access, fix thermal throttle clearance, update power profile
- Sep 10: (ahead of nightlies) bfq and fiops io schedulers (bfq as default), sony 5.1.1 blobs
- Sep 16: (ahead of nightlies) data, sound fixes
- Mar 30: initial CM13 release
- Apr 6: latest cm fixes, kernel updates
- May 2: init updates, improved mac address handling, new camera, kernel lz4 compression, updated audio and gpu, new browser
- May 9: mac addr fixes, bluetooth fixes, camera wrapper improvements
- May 25: f2fs fix, kernel 3.4.112, init update, ipv6 fix
- Jul 5: loads of kernel changes, audio hal, and probably plenty of stuff i forgot
- Jul 7: underp previous build
- Aug 1: bluetooth and audio updates
- Aug 23: offline charger & kernel & f2fs updates
All builds are synchronized with the latest CM tree. For the specific updates to fusion3 and yuga, see the source link below!
Download:
For the brave CM13 DEVELOPMENT BUILD:
cm-13.0-20160823-UNOFFICIAL-yuga.zip
Dirty-flashing on existing 12.1 upgrades normally to CM 13. Beware you will need compatible GApps though!
CM-12.1 nightlies are available:
Official download site
This thread will however remain the prime location for testing new stuff and support on yuga.
Installation:
If you have anything other than CyanogenMod on your device, do a full wipe, and get compatible gapps!
F2FS support: take a look here
Testing:
Some very important "rules" for this:
- Run unmodified versions (no FOTA recovery, no modified kernel, no Xposed framework, etc.)
- Please dont post "X isnt working" or "random reboots" - provide LOGS for each report you post here. This thread is actually meant for users who are capable of gathering and providing logs, so after a reboot, provide last_kmsg, and for all other problems, dmesg and logcat at the very least.
- If you can reproduce your problem, you might want to increase the logging level before posting it here, which will increase chances of me finding the problem.
I will have to ignore all other "problem reports" as they are essentially useless.
Thanks:
@andyvdsteen - testing, lending me his phone
Source:
If you are willing (and able) to help, check out the patch sets, test them for the respective projects (fusion3 is also pollux, odin, and so on).
http://review.cyanogenmod.org
Some screen?
Let's Test
Let's flash it
I will port this to Xperia ZR. Waiting for official builds to be released for Xperia Z and ZR!
Sent from my Xperia ZR using XDA Free mobile app
Please report crash UI...other cm12 crash
---------- Post added at 09:42 PM ---------- Previous post was at 09:41 PM ----------
comax70 said:
Please report crash UI...other cm12 crash
Click to expand...
Click to collapse
30 build
Push 10.5.1.A.0.292 Blobs For
https://github.com/TheMuppets/proprietary_vendor_sony/tree/cm-12.0/yuga
Thanks.
iKillCypher said:
Push 10.5.1.A.0.292 Blobs For
https://github.com/TheMuppets/proprietary_vendor_sony/tree/cm-12.0/yuga
Thanks.
Click to expand...
Click to collapse
if you think it's worth it (and you actually have the illusion that updating blobs is just copying over some files), then please go ahead and do it, test it, and create a pull request. other than that, i would be thankful if you stop nagging me (and other devs) about it in forums, gerrit, and on irc.
iKillCypher said:
Push 10.5.1.A.0.292 Blobs For
https://github.com/TheMuppets/proprietary_vendor_sony/tree/cm-12.0/yuga
Thanks.
Click to expand...
Click to collapse
Hmm review.cyanogenmod.org/#/c/86923/ merged on jan 26
Sent from my Xperia Z using Tapatalk 2
that's my commit, yes. he is talking about blobs, though, not the kernel patches.
anyway, it would be helpful if you guys could test this and report back with things that aren't working.
qsnc
I will test most of your updates for now I need you set selinux to enforcing. yes push blobs 10.5.1.A.0.292 Blobs since you have updated the kernel code based on sony.
after that we can hudson yuga to nightly same for odin
@qsnc
there are random reboot happening for yuga, possible due to the kernel changes you did, It seems to be affecting after 28 builds
also you seems to have set the selinux to enforcing there are some permission and denial you need to look at it seems to have messed up the base band etc
Started using this as a daily . Really nice job dev. Chrome beta sometimes crashed but it's not bothering me that much..
Is a solution to a working BT audio close ?
Mobile signal & data works, but not after enabling SELinux. Currently waiting for build with new policy update.
UPDATE: codereview 87608 and 87609 fixes mobile signal and data, but no "3G" or "H+" on top right corner. There is network activity indicators, though.
Cannot hear or speak in call, even after applying http://review.cyanogenmod.org/#/c/86943/ .
Hexchain said:
Mobile signal & data works, but not after enabling SELinux. Currently waiting for build with new policy update.
UPDATE: codereview 87608 and 87609 fixes mobile signal and data, but no "3G" or "H+" on top right corner. There is network activity indicators, though.
Cannot hear or speak in call, even after applying http://review.cyanogenmod.org/#/c/86943/ .
Click to expand...
Click to collapse
http://review.cyanogenmod.org/#/c/86943/ also needs changes in the hal: http://review.cyanogenmod.org/#/c/86942/, that should help with in-call audio... policy update is on the way.
qsnc said:
http://review.cyanogenmod.org/#/c/86943/ also needs changes in the hal: http://review.cyanogenmod.org/#/c/86942/, that should help with in-call audio... policy update is on the way.
Click to expand...
Click to collapse
Do I need to switch hardware/qcom/audio/default to cm-12.0-caf-8960 branch before cherry-picking this change?
EDIT: nvm, found the correct path. Building.
EDIT2: 86942 and 86943 fixed calling issue!
EDIT3: userinit does not function due to selinux.
from /data/misc/audit/audit.log:
Code:
type=2000 msg=audit(1.010:1): initialized
type=1403 msg=audit(1422959102.743:2): policy loaded auid=4294967295 ses=4294967295
type=1404 msg=audit(1422959102.763:3): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295
type=1400 msg=audit(1422959111.141:4): avc: denied { execute } for pid=273 comm="logwrapper" name="busybox" dev="rootfs" ino=4489 scontext=u:r:sysinit:s0 tcontext=u:object_r:rootfs:s0 tclass=file op
_res=-13 ppid=272 pcomm="logwrapper" tgid=272 tgcomm="logwrapper"
type=1400 msg=audit(1422959111.141:5): avc: denied { read } for pid=273 comm="busybox" name="userinit.d" dev="mmcblk0p26" ino=718083 scontext=u:r:sysinit:s0 tcontext=u:object_r:system_data_file:s0 t
class=dir op_res=-13 ppid=272 pcomm="logwrapper" tgid=272 tgcomm="logwrapper"
type=1400 msg=audit(1422959111.151:6): avc: denied { write } for pid=275 comm="setprop" name="property_service" dev="tmpfs" ino=5902 scontext=u:r:sysinit:s0 tcontext=u:object_r:property_socket:s0 tc
lass=sock_file op_res=-13 ppid=271 pcomm="90userinit" tgid=271 tgcomm="90userinit"
Hexchain said:
Do I need to switch hardware/qcom/audio/default to cm-12.0-caf-8960 branch before cherry-picking this change?
EDIT: nvm, found the correct path. Building.
EDIT2: 86942 and 86943 fixed calling issue!
EDIT3: userinit does not function due to selinux.
from /data/misc/audit/audit.log:
Code:
type=2000 msg=audit(1.010:1): initialized
type=1403 msg=audit(1422959102.743:2): policy loaded auid=4294967295 ses=4294967295
type=1404 msg=audit(1422959102.763:3): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295
type=1400 msg=audit(1422959111.141:4): avc: denied { execute } for pid=273 comm="logwrapper" name="busybox" dev="rootfs" ino=4489 scontext=u:r:sysinit:s0 tcontext=u:object_r:rootfs:s0 tclass=file op
_res=-13 ppid=272 pcomm="logwrapper" tgid=272 tgcomm="logwrapper"
type=1400 msg=audit(1422959111.141:5): avc: denied { read } for pid=273 comm="busybox" name="userinit.d" dev="mmcblk0p26" ino=718083 scontext=u:r:sysinit:s0 tcontext=u:object_r:system_data_file:s0 t
class=dir op_res=-13 ppid=272 pcomm="logwrapper" tgid=272 tgcomm="logwrapper"
type=1400 msg=audit(1422959111.151:6): avc: denied { write } for pid=275 comm="setprop" name="property_service" dev="tmpfs" ino=5902 scontext=u:r:sysinit:s0 tcontext=u:object_r:property_socket:s0 tc
lass=sock_file op_res=-13 ppid=271 pcomm="90userinit" tgid=271 tgcomm="90userinit"
Click to expand...
Click to collapse
make sure you pulled in all the latest updates, especially http://review.cyanogenmod.org/#/c/87609/
should you still have trouble booting, please post it, and ill update the sepolicy.
qsnc said:
make sure you pulled in all the latest updates, especially http://review.cyanogenmod.org/#/c/87609/
should you still have trouble booting, please post it, and ill update the sepolicy.
Click to expand...
Click to collapse
No problem with 87609, because before this I have completely no radio. Phone boots, only custom init scripts (in /data/local/userinit.d, called by /system/etc/init.d/90userinit) isn't invoked at all due to SELinux denials.
Here is the script content if relevant (something like MarketEnabler to enable Google Play Service Location Reporting): https://gist.github.com/hexchain/f4c8a3583abe0214922a
Some other minor problem:
Carrier name does not show on lockscreen left up corner (see attachment), and sometimes there is "No service. - <actual carrier name>".
Hexchain said:
No problem with 87609, because before this I have completely no radio. Phone boots, only custom init scripts (in /data/local/userinit.d, called by /system/etc/init.d/90userinit) isn't invoked at all due to SELinux denials.
Here is the script content if relevant (something like MarketEnabler to enable Google Play Service Location Reporting): https://gist.github.com/hexchain/f4c8a3583abe0214922a
Some other minor problem:
Carrier name does not show on lockscreen left up corner (see attachment), and sometimes there is "No service. - <actual carrier name>".
Click to expand...
Click to collapse
you have something funky in your init scripts... because in the "stock" cm12 init scripts, i removed all calls to logwrapper... are you using old scripts or have you modified them in some way?
the userscript does seem to get invoked, as you can see by the setprop denial it "only" is denied access to set a property... you can find out which exactly by searching for the inode on your phone... anyway i am not aware why a "fake carrier id" script should be required? then again, i dont even have a yuga...
Thanks for the quick reply, and thanks for maintaining CM for yuga!
qsnc said:
you have something funky in your init scripts... because in the "stock" cm12 init scripts, i removed all calls to logwrapper... are you using old scripts or have you modified them in some way?
Click to expand...
Click to collapse
There are still calls to logwrapper: https://github.com/CyanogenMod/andr...2.0/prebuilt/common/etc/init.d/90userinit#L13
the userscript does seem to get invoked, as you can see by the setprop denial it "only" is denied access to set a property... you can find out which exactly by searching for the inode on your phone...
Click to expand...
Click to collapse
The setprop denial is for line 14, relevant file is /dev/socket/property_service. If it really was in my script, there should be 4 denials instead of 1.
anyway i am not aware why a "fake carrier id" script should be required? then again, i dont even have a yuga...
Click to expand...
Click to collapse
As I've said, Location Reporting is disabled by Google in my region (by detecting carrier MCCMNC) so I need this to make it available.
Again, thank you for maintaining CM for yuga!
Can any CM12 users confirm WiFi disconnecting during deep sleep? I need to know if it's my derp or not
SuperHanss said:
Can any CM12 users confirm WiFi disconnecting during deep sleep? I need to know if it's my derp or not
Click to expand...
Click to collapse
it does. but Im kinda used to it, as I got the same problem in CM 11. But this time it seems to happen more frequently. Cant find the option "Wifi Optimization" anymore in CM 12. Disabling it in CM 11 fixed it.
Disclaimer: I am not responsible for anything that happens as a result of flashing these files. Your destiny is your own.
.: Identity Crisis 6 LTE :.(Stock Android 6.0)
Motorola said: NO, XDA said: Yes! - I proudly present:
Stock Marshmallow for Peregrine!
This ROM has been built from the latest firmware for XT1072 (Thea) - Stock Android 6.0 (v24.65.34). Big thanks to @Kamin4ri for Kernel Development.
First boot will take exactly 10 minutes.
Features:
Stock Kernel | Zipaligned | Rooted | Busybox | init.d Script Support
OTA Updates Disabled | Non-essential Motorola Services removed | More RAM available
'Cast Screen' Enabled | Debloated | RRO Layers Support | 'Safe volume warning' Disabled | EAP Sim support
MultiROM Compatible | Post-install zipaligning (Fly-On Mod) | Improved Battery Life | Lock-screen rotation
How to flash:
1) Boot into latest TWRP and Format Data (Wipe > Format DATA > Yes) - This step is essential, and will wipe Internal Storage (Downloads, Music, Photos etc, **backup important files**)
2) Transfer ROM to SDCARD or Internal Storage. This may be done in Windows via MTP, or using adb sideload or adb push ROM.zip /sdcard/
3) TWRP > Wipe > Factory reset and flash ROM.
4) Reboot.
Downloads:
Identity Crisis 6 LTE v1.0 (373mb)
Identity Crisis 6 LTE v1.0a (355mb)
Identity Crisis 6 LTE v1.1 (358mb)
Identity Crisis 6 LTE v1.1a (356mb)
Identity Crisis 6 LTE v1.1b (355mb)
Identity Crisis 6 LTE v1.1c (355mb)
Identity Crisis 6 LTE v1.1d (355mb)
Identity Crisis 6 LTE v1.2 (370mb)
Identity Crisis 6 LTE GNL v1.2 (420mb)
Identity Crisis 6 LTE v1.2a (370mb)
Identity Crisis 6 LTE GNL v1.2a (420mb)
Identity Crisis 6 LTE v1.2b (375mb)
Identity Crisis 6 LTE GNL v1.2b (424mb)
Identity Crisis 6 LTE v1.2c (401mb)
Identity Crisis 6 LTE GNL v1.2c (452mb)
Identity Crisis 6 LTE v1.3 (379mb)
Identity Crisis 6 LTE GNL v1.3 (423mb)
Identity Crisis 6 LTE v1.3a (376mb)
Identity Crisis 6 LTE GNL v1.3a (430mb)
Identity Crisis 6 LTE v1.3b (Mirror) (378mb)
Identity Crisis 6 LTE GNL v1.3b (Mirror) (432mb)
Identity Crisis 6 LTE v1.4a (377mb)
Identity Crisis 6 LTE GNL v1.4a (425mb)
Identity Crisis 6 LTE v1.4b (376mb)
Identity Crisis 6 LTE GNL v1.4b (426mb)
Identity Crisis 6 LTE v1.5 'Pure' (389mb)
Identity Crisis 6 LTE v1.5 'Deviant' (395mb)
Identity Crisis 6 LTE v1.5 GNL 'Pure' (449mb)
Identity Crisis 6 LTE v1.5 GNL 'Deviant' (455mb)
Notes: GNL = 'Google Now Launcher' version. See FAQ below for differences between Pure and Deviant ROMs. All ROMs are compatible with KaminariKernel.
Kernels: -=[ Flash via TWRP ]=-
LTE Stock 6.0 Kernel / Modules
Extras: -=[ Flash via TWRP ]=-
Original Adreno / GPU Driver
Latest Adreno / GPU Drivers (WARNING: May break compatibility with some games / apps)
Google Search (Enables "OK Google" on every screen)
Google Dialer (Caller ID, Spam blocking and search nearby businesses) (Single-SIM only!) (set as 'default phone app' - see FAQ below)
Stock Dialer (Restore)
In-call Speaker Volume Increase (undo)
Motorola Gallery
Tips:
Never restore apps or settings with Titanium Backup - this will break the ROM.
Do not flash gapps, get what you need via pre-installed Google Play
If you need to reflash Superuser - superuser.zip - is confirmed working.
XDA:DevDB Information
Identity Crisis 6 LTE, ROM for the Moto G
Contributors
lost101, Kamin4ri, VitaTaf, parrotgeek1
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: XT1072 (Thea) Stock Android 6.0
Version Information
Status: Stable
Created 2016-03-03
Last Updated 2017-01-22
ROM Release Log:
17/01/17 - Added Identity Crisis 6 LTE GNL v1.5 'Deviant' (Changelog)
17/01/17 - Added Identity Crisis 6 LTE v1.5 'Deviant' (Changelog)
17/01/17 - Added Identity Crisis 6 LTE GNL v1.5 'Pure' (Changelog)
17/01/17 - Added Identity Crisis 6 LTE v1.5 'Pure' (Changelog)
18/09/16 - Added Identity Crisis 6 LTE GNL v1.4b (Changelog)
18/09/16 - Added Identity Crisis 6 LTE v1.4b (Changelog)
05/09/16 - Added Identity Crisis 6 LTE GNL v1.4a (Changelog)
05/09/16 - Added Identity Crisis 6 LTE v1.4a (Changelog)
04/08/16 - Added Identity Crisis 6 LTE GNL v1.3b (Changelog)
04/08/16 - Added Identity Crisis 6 LTE v1.3b (Changelog)
03/07/16 - Added Identity Crisis 6 LTE GNL v1.3a (Changelog)
03/07/16 - Added Identity Crisis 6 LTE v1.3a (Changelog)
05/06/16 - Added Identity Crisis 6 LTE GNL v1.3 (Changelog)
05/06/16 - Added Identity Crisis 6 LTE v1.3 (Changelog)
03/05/16 - Added Identity Crisis 6 LTE GNL v1.2c (Changelog)
03/05/16 - Added Identity Crisis 6 LTE v1.2c (Changelog)
12/04/16 - Added Identity Crisis 6 LTE GNL v1.2b (Changelog)
12/04/16 - Added Identity Crisis 6 LTE v1.2b (Changelog)
09/04/16 - Added Identity Crisis 6 LTE GNL v1.2a (Changelog)
09/04/16 - Added Identity Crisis 6 LTE v1.2a (Changelog)
26/03/16 - Added Identity Crisis 6 LTE GNL v1.2 (Changelog)
26/03/16 - Added Identity Crisis 6 LTE v1.2 (Changelog)
17/03/16 - Added Identity Crisis 6 LTE v1.1d (Changelog)
17/03/16 - Added Identity Crisis 6 LTE v1.1c (Changelog)
08/03/16 - Added Identity Crisis 6 LTE v1.1b (Changelog)
08/03/16 - Added Identity Crisis 6 LTE v1.1a (Changelog)
08/03/16 - Added Identity Crisis 6 LTE v1.1 (Changelog)
03/03/16 - Added Identity Crisis 6 LTE v1.0a (Changelog)
03/03/16 - Added Identity Crisis 6 LTE v1.0
Bugs List:
(1) Wi-Fi very slow to re-connect using quick settings tile (known Android issue) (Workaround in FAQ below)
Recommended Settings:
All Animations speed: 0.5 (Changed via Developer options - see FAQ below)
Wi-Fi Sleep policy: Never. (Changed via Settings > Wi-Fi > Advanced) - Check Battery stats occasionally | some Apps will force Wi-Fi to be always on - i.e Viber
Frequently Asked Questions:
When flashing, I get: "E:Error executing updater binary in zip" or "Updater process ended with ERROR: 7"
This is a custom recovery bug. Try restarting recovery and flashing again. Alternatively you may need to format /data (userdata) in Custom Recovery. Note: This will delete anything on internal storage - photos, music, videos etc.
What is the difference between 'Pure' and 'Deviant' ROMs?
There is a slight low-brightness screen-flicker issue with this ROM in it's original form. Some people don't mind it. In order to fix it, system (framework) files have to be modified. However, there is some debate as to what affect such changes have on the smoothness of the ROM. I have done my best to research and modify the ROM in way that has no impact on performance at all.
Regardless, I've made two versions of this ROM: Pure and Deviant.
'Pure' retains the original unmodified system files is unrooted. 'Deviant' has the low-brightness screen-flicker problem corrected, along with a few other fixes that are only possible via modifying the system files and is rooted. Otherwise, the two ROMs are optimized and essentially the same.
The choice is yours.
How to enable 'Google Now on tap'?
Install Google App. Set 'Google App' as default app for Assist app in System Settings.
Settings > Apps > Settings Gear Icon (top right) > Default Apps > Assist and voice input
Explain Marshmallow and it's 'Default Apps' feature?
Google 'Now on Tap' | Search | "OK Google" and Google Dialer will not function correctly, or at all - if you do not set them as default apps. This also applies to any custom replacement apps for handling search, calls or sms.
Settings > Apps > Settings Gear Icon (top right) > Default Apps
Stock Kernel vs Custom Kernel?
The Kernel included in this ROM is essentially as Motorola created it. However, if you seek something with better performance and to improve Battery-life - consider: KaminariKernel v2.0.
Can you add "X" feature to this ROM?
No. This ROM will always remain as close to Stock as possible. Any modifications made are only done so to make Android fully functional.
Motorola Assist is not working?
You also need to install Motorola Contextual Services.
Wi-Fi very slow to re-connect using quick settings tile?
This is a known bug in Android 6.0. Perhaps a future version of Android will resolve it. For now, a workaround is to enable 'Wi-Fi Scanning.'
Settings > Location > Tap three dots (top right) > Scanning > Wi-Fi Scanning
GPS Optimization and issues with Google Maps
Firstly GPS on any ROM is not optimized for speed and accuracy. In addition, the service 'GoogleLocationManager' present in this ROM appears to cause issues with Google Maps. This is how the ROM was designed to work by Motorola. You have the option of disabling this service yourself, but the effect on other apps is unknown. More on this subject here.
To greatly improve the speed and accuracy of GPS in this ROM, it is recommended you install GPS Status & Toolbox and follow this tutorial to configure it correctly.
What is System UI Tuner and how do I enable it?
System UI Tuner lets you change certain UI aspects without the need for any extra software. You can remove, or change the order items appear in the Quick Settings (pulldown menu) and in status bar. Also it can add Percentage to the status bar battery icon. To enable: swipe down status bar and long press the settings gear icon for a few seconds - it will start to spin.
Internal Storage not accessible from PC?
With Marshmallow, the default USB connection type is 'Charging only' mode. You can change USB mode to 'MTP' via the pull-down notification option. Alternatively, install the Xposed Module: USB for Marshmallow
How do I enable native Multi-window support?
Add the following line to your /system/build.prop and reboot: (screenshots)
persist.sys.debug.multi_window=true
How do I make Animations in Marshmallow faster or turn them off?
Enable Developer options - repeatedly tap 'Build number' in About phone. Change the three 'Animation scale' settings to: .5x or off. "2.5x" is available if you have installed the Xposed Module known as GravityBox.
How to turn off Lock-screen rotation?
This setting is a built.prop edit. Use a text editor with root access to open: /system/build.prop - scroll down to last section "#Additional Tweaks" and remove the following line, or change to 'false': (Reboot after editing and saving)
lockscreen.rot_override=true
Awesome! But how is this even possible!? I've never seen a stock ROM ported, sweet!
Yupi.
OMG stock 6.0 for peregrine.
Awsome!!
Thank you lost101 and others devs like kingkaminari
Wysłane z mojego XT1039 przy użyciu Tapatalka
Well, that is good! I'm gonna test it as soon as I can! Thanks mate
It was fast , I am really impressed, thanks
Thank you, it's really impressive
Just flashed, so far really good job! There seems to be some sound problem indeed, e.g. when you choose some ringtone, sound is a bit low at first for a really short time, but then it normalises. But playing music without any issues.
The screen flickers a bit, the less brightness the more you can see it (best results if you turn slider max to the left, go to dark room and check something with a white background, eg. Settings menu) - it stops flickering whrn you disable adaptive brightness. The screen is also much darker on minimum brightness than it used to be in Lollipop (maybe it's normal, I've never used MM before) - EDIT: but again only with adaptive brightness on.
Can I assume by your comments that all the major stuff works 100%? LTE connectivity? SDCARD support?
lost101 said:
Can I assume by your comments that all the major stuff works 100%? LTE connectivity? SDCARD support?
Click to expand...
Click to collapse
LTE data connections working, but I can't make calls or send SMS (I had the same issue in Lollipop). I can receive an SMS, but incoming calls are redirected to voicemail straight away and I don't get any missed call notification. 3G is not working on my device since forever so I can't tell anything. 2G works perfect. SD card - no issues with it so far. There's really nothing to complain, apart from that adaptive brightness bug.
EDIT: Xposed is also working, if anyone wonders. It's really, really great work that you've done guys.
minimale_ldz said:
LTE data connections working, but I can't make calls or send SMS (I had the same issue in Lollipop). I can receive an SMS, but incoming calls are redirected to voicemail straight away and I don't get any missed call notification. 3G is not working on my device since forever so I can't tell anything. 2G works perfect.
Click to expand...
Click to collapse
Have you tried flashing the 5.1 Radio Firmware via fastboot - available here?
lost101 said:
Have you tried flashing the 5.1 Radio Firmware via fastboot - available here?
Click to expand...
Click to collapse
I tried on Lollipop with no effect. Didn't try on this one yet
minimale_ldz said:
I tried on Lollipop with no effect. Didn't try on this one yet
Click to expand...
Click to collapse
The following commands should fix your issue unless it's a serious hardware fault.
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
lost101 said:
The following commands should fix your issue unless it's a serious hardware fault.
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
Click to expand...
Click to collapse
I successfully flashed radio firmware but nothing changed. Hardware fault is quite possible in my case.
minimale_ldz said:
I successfully flashed radio firmware but nothing changed. Hardware fault is quite possible in my case.
Click to expand...
Click to collapse
I've seen SIM cards cause issues for some people also. I expect you have already tried a new one or alternative carriers / networks.
lost101 said:
I've seen SIM cards cause issues for some people also. I expect you have already tried a new one or alternative carriers / networks.
Click to expand...
Click to collapse
Yes. I checked again now with different carrier sim, and nothing changes.
---------- Post added 4th March 2016 at 12:39 AM ---------- Previous post was 3rd March 2016 at 11:56 PM ----------
@lost101
Couple questions: why it has two build.props and is LauncherConfig in system/app a part of stock launcher or some general settings for all launchers (or something else)? Thanks
minimale_ldz said:
Couple questions: why it has two build.props and is LauncherConfig in system/app a part of stock launcher or some general settings for all launchers (or something else)? Thanks
Click to expand...
Click to collapse
The second build.prop is a backup file created by the text editor I used - it was hidden. LauncherConfig can probably be deleted if it relates to the already removed Google Now Launcher. I'll omit both in the next version.
lost101 said:
The second build.prop is a backup file created by the text editor I used - it was hidden. LauncherConfig can probably be deleted if it relates to the already removed Google Now Launcher. I'll omit both in the next version.
Click to expand...
Click to collapse
Thanks. I cleaned it a bit and I get a black screen after installation and am wondering what have I done wrong.
{
"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 port of LineageOS cm-13.0. I'm a beginner in building custom roms, so please be patient with me. This rom is based on the device tree of DanielHK with small modifications to run smooth with its low memory.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Release Notes
2017-10-23: Update to current cm-13 including fixes to avoid WPA2 KRACK for p6800, p6810, i815.
2017-09-12: Finally, I managed to compile a version for i815 but telephony/mobile data does not work
2017-08-23: Stabilized the new Browser, alias Gello - it formerly crashed, e.g. when opening our XDA page; Deactivated bluetooth again, since it is not done and crashed. It is still a long way: I assume I have to adopt the current Lineageos bluetooth app like Daniel did before: https://github.com/danielhk/android_packages_apps_Bluetooth. Daniels is outdated, unfortunately, cannot be used right away.
2017-07-27: Optimizations ZRAM, ISM and read_ahead also for P6810. Tried to activate bluetooth following danielhks guide. Succeeded with 3.1 in the guide - testing on command line. But in ROM it crashes when I try to activate BT via Settings.
2017-07-24: Video streaming and playback fixed with help from Bauner - native media codecs work now - meaning Youtube in preinstalled browser works now and also playing local mp4 files. I found that some optimizations (e.g. ZRAM) are not yet applied in P6810, because of a separate init.rc (-wifi) -> will be fixed in next release
2017-07-15: Auto-rotation fixed! And GPS works again, too. (got lost again in last build)
2017-07-13: Changed default orientation to Portrait. Deactivated DRM again on P6800, since mediaserver crashed in libwvdrmengine.so - and by that Youtube also broke in playing - now Youtube runs fine, but Play Movies does still not. On P6810 hopefully both works (Could not find a difference yet). Still the rotation issue is there, not from the beginning but during usage the orientation freezes somewhen...
2017-07-10: Further speed improvements, deactivating swipe in AOSP keyboard, what crashed
2017-07-09: GPS fixed, thanks to p3dboard - I was able to add a NON_PIE_SUPPORT
2017-07-07: Add several tweaks for memory usage and disk r/w speed, changed dpi to 202
2017-06-28: first release
Installation
Download the ROM and optionally GApps (ARM-6.0-pico) onto your device
Reboot tablet into TWRP recovery. I use version 3.0.2-0 here.
Wipe data, cache, dalvik/art-cache and system. Coming from stock rom, also wipe internal sd.
Flash ROM and GApps.
Reboot System. (First boot takes 5-6 minutes. Be patient.)
Root
Download SuperSU version BETA-SuperSU-v2.52.zip and install via TWRP recovery, newer releases will not work.
Not working
Bluetooth - crash when activating via Settings
DRM playback (google play movies) crashes. But after the crash starts playing on P6810!?! Currently, playback on P6810 is not smooth anymore, caused by the new codecs setup. Will investigate further.
Recent Amazon Kindle app crashes -> use an older one 4.24.0.27 or just delete libunwind.so in /data/app/...kindle directory
Internal mount of sd-card does not work -> use portable mode
Source
See source information on androidfilehost, too
XDA:DevDB Information
LineageOS CM-13.0, ROM for the Samsung Galaxy Tab 7.7
Contributors
frami2, danielhk, p3dboard, bauner
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Beta
Created 2017-06-29
Last Updated 2017-10-25
thank you, downloaded & now it is under testing.
Great job, i will check back on my notes, i definitely have information on a drm playback fix, and should have notes on Bluetooth from what Daniel told me, you have to use an external Bluetooth library, and remove one of the built-in Bluetooth apks from memory via the manifest.xml...i might have a chance later today to dig out the information. I think i had the notes in the build notes on my androidfilehost area.
Actually for Drm we needed newer blob files from memory. If you know the files that need updating from my notes, grab newer copies of the files from the Galaxy s2 lineageos builds, as i think we got the l3 drm Widevine library from the android one google devices
Edit:
Just looking back at old posts to do with the Galaxy s2 phone, this is the url where they got updated widevine L3 blobs for drm Google play movies to work.
Nougat / cm 14.1
https://github.com/RonGokhale/proprietary_vendor_sony/tree/nougat/nicki
Cm 13
https://github.com/RonGokhale/proprietary_vendor_sony/tree/cm-13.0/nicki
Look under the /proprietary/vendor/lib area for the files
Original Source for the WideVine blobs
https://github.com/TheMuppets/proprietary_vendor_sony/tree/cm-13.0/nicki/proprietary/vendor/lib
Just flashed it on my P6810, its feeling quite smooth. So far apart from the bugs noted above, I noticed that the Recent Apps view isn't showing a little image of the application, but that's not a major issue, you can still see the applications to swap between via the title bar it shows.
I've attached the Widevine L3 files from the cm13 repository link, from the Muppets github, if we replace the ones in your current build with these, that should fix the DRM playback
Edit: I just tested Google Play Movies with the existing Widevine L3 files in your build, and the Flash Season 3 played fine, the film Independance Day also played fine, so I think your Rom is fine as far as DRM playback goes.
Edit: Removed the .ZIP file, as that wasn't actually the .SO files, but html files (so if anyone downloaded the .ZIP - don't use those files). Anyway, it looks like it isn't needed
Edit: Re-uploaded ZIP with the real .SO files - Just incase you need them for testing.
p3dboard said:
Just flashed it on my P6810, its feeling quite smooth. So far apart from the bugs noted above, I noticed that the Recent Apps view isn't showing a little image of the application, but that's not a major issue, you can still see the applications to swap between via the title bar it shows.
I've attached the Widevine L3 files from the cm13 repository link, from the Muppets github, if we replace the ones in your current build with these, that should fix the DRM playback
Edit: I just tested Google Play Movies with the existing Widevine L3 files in your build, and the Flash Season 3 played fine, the film Independance Day also played fine, so I think your Rom is fine as far as DRM playback goes.
Edit: Removed the .ZIP file, as that wasn't actually the .SO files, but html files (so if anyone downloaded the .ZIP - don't use those files). Anyway, it looks like it isn't needed
Edit: Re-uploaded ZIP with the real .SO files - Just incase you need them for testing.
Click to expand...
Click to collapse
Many thanks Peter! Just wanted to ask you regarding DRM since you are the expert
I already tried different approaches - media/drm always crashed...will try to integrate your suggestions once I have time to.
Currently, I still struggle with lagging once all Google apps are installed and switching between those - playing around with all these low-ram optimization hints.
Hi Peter,
just tried to integrate the DRM blobs (libMc* would'nt be needed really, right?):
Code:
# drm blobs
PRODUCT_COPY_FILES += \
vendor/samsung/smdk4210-tab/props/system/lib/libMcClient.so:system/lib/libMcClient.so \
vendor/samsung/smdk4210-tab/props/system/lib/libMcRegistry.so:system/lib/libMcRegistry.so \
vendor/samsung/smdk4210-tab/props/system/lib/libMcVersion.so:system/lib/libMcVersion.so \
vendor/samsung/smdk4210-tab/props/system/vendor/lib/libdrmdecrypt.so:system/lib/libdrmdecrypt.so \
vendor/samsung/smdk4210-tab/props/system/vendor/lib/libwvm.so:system/vendor/lib/libwvm.so \
vendor/samsung/smdk4210-tab/props/system/vendor/lib/drm/libdrmwvmplugin.so:system/vendor/lib/drm/libdrmwvmplugin.so \
vendor/samsung/smdk4210-tab/props/system/vendor/lib/libwvdrm_L3.so:system/vendor/lib/libwvdrm_L3.so \
vendor/samsung/smdk4210-tab/props/system/vendor/lib/libWVStreamControlAPI_L3.so:system/vendor/lib/libWVStreamControlAPI_L3.so \
vendor/samsung/smdk4210-tab/props/system/vendor/lib/mediadrm/libwvdrmengine.so:system/vendor/lib/mediadrm/libwvdrmengine.so \
additionally, I already had in the init.smdk4210.rc:
# for DRM
symlink -s /vendor /system/vendor
Again, it fails when I try to play any movie in Google Play Movies:
Code:
07-04 20:04:22.675 14454 14487 F libc : Fatal signal 4 (SIGILL), code 1, fault addr 0x434038a4 in tid 14487 (Binder_1)
07-04 20:04:22.692 3398 3410 I art : Background partial concurrent mark sweep GC freed 5950(463KB) AllocSpace objects, 10(1528KB) LOS objects, 19% free, 13MB/16MB, paused 2.001ms total 116.753ms
07-04 20:04:22.720 1830 1830 I DEBUG : property debug.db.uid not set; NOT waiting for gdb.
07-04 20:04:22.720 1830 1830 I DEBUG : HINT: adb shell setprop debug.db.uid 100000
07-04 20:04:22.720 1830 1830 I DEBUG : HINT: adb forward tcp:5039 tcp:5039
07-04 20:04:22.866 3398 5723 D WifiService: New client listening to asynchronous messages
07-04 20:04:22.878 1830 1830 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
07-04 20:04:22.878 1830 1830 F DEBUG : LineageOS Version: '13.0-20170703-UNOFFICIAL-p6800'
07-04 20:04:22.878 1830 1830 F DEBUG : Build fingerprint: 'samsung/GalaxyTab/GT-P6800:6.0.0/MDB08M:userdebug/release-keys'
07-04 20:04:22.878 1830 1830 F DEBUG : Revision: '0'
07-04 20:04:22.878 1830 1830 F DEBUG : ABI: 'arm'
07-04 20:04:22.878 3398 5818 W NativeCrashListener: Couldn't find ProcessRecord for pid 14454
07-04 20:04:22.878 1830 1830 F DEBUG : pid: 14454, tid: 14487, name: Binder_1 >>> /system/bin/mediaserver <<<
07-04 20:04:22.878 1830 1830 E DEBUG : AM write failed: Broken pipe
07-04 20:04:22.878 1830 1830 F DEBUG : signal 4 (SIGILL), code 1 (ILL_ILLOPC), fault addr 0x434038a4
07-04 20:04:22.880 14423 14491 W ResourceType: No package identifier when getting value for resource number 0x00000000
07-04 20:04:22.925 3398 5731 E AudioService: Media server started.
07-04 20:04:22.935 1830 1830 F DEBUG : r0 00000056 r1 00000034 r2 00000020 r3 434038a5
07-04 20:04:22.935 1830 1830 F DEBUG : r4 4349ebe8 r5 40133000 r6 406e384c r7 4013301e
07-04 20:04:22.935 1830 1830 F DEBUG : r8 40133000 r9 434532af sl 00008e64 fp 0019660d
07-04 20:04:22.935 1830 1830 F DEBUG : ip 43446020 sp 43143fb8 lr 40113045 pc 434038a4 cpsr 200f0030
07-04 20:04:22.938 1830 1830 F DEBUG :
07-04 20:04:22.938 1830 1830 F DEBUG : backtrace:
07-04 20:04:22.938 1830 1830 F DEBUG : #00 pc 000c78a4 /system/vendor/lib/mediadrm/libwvdrmengine.so
07-04 20:04:22.938 1830 1830 F DEBUG : #01 pc 00000043 <unknown>
Is there anything I'm missing?
Best regards,
Frank
frami2 said:
Hi Peter,
just tried to integrate the DRM blobs (libMc* would'nt be needed really, right?):
additionally, I already had in the init.smdk4210.rc:
# for DRM
symlink -s /vendor /system/vendor
Again, it fails when I try to play any movie in Google Play Movies:
Is there anything I'm missing?
Best regards,
Frank
Click to expand...
Click to collapse
Hi Frank,
Your line for the libdrmdecrypt.so was sending it to the /system/lib folder, it should go to /system/vendor/lib, and I don't think the libMc* files are needed as you say, as I have never needed them before. I've attached a flashable version of the Widevine L3 blobs for CM13, which works fine on my p6810.
so your code should read as
Code:
# drm blobs
PRODUCT_COPY_FILES += \
vendor/samsung/smdk4210-tab/props/system/vendor/lib/libdrmdecrypt.so:system/vendor/lib/libdrmdecrypt.so \
vendor/samsung/smdk4210-tab/props/system/vendor/lib/libwvm.so:system/vendor/lib/libwvm.so \
vendor/samsung/smdk4210-tab/props/system/vendor/lib/drm/libdrmwvmplugin.so:system/vendor/lib/drm/libdrmwvmplugin.so \
vendor/samsung/smdk4210-tab/props/system/vendor/lib/libwvdrm_L3.so:system/vendor/lib/libwvdrm_L3.so \
vendor/samsung/smdk4210-tab/props/system/vendor/lib/libWVStreamControlAPI_L3.so:system/vendor/lib/libWVStreamControlAPI_L3.so \
vendor/samsung/smdk4210-tab/props/system/vendor/lib/mediadrm/libwvdrmengine.so:system/vendor/lib/mediadrm/libwvdrmengine.so \
Regards,
Peter
p3dboard said:
Hi Frank,
Your line for the libdrmdecrypt.so was sending it to the /system/lib folder, it should go to /system/vendor/lib, and I don't think the libMc* files are needed as you say, as I have never needed them before. I've attached a flashable version of the Widevine L3 blobs for CM13, which works fine on my p6810.
so your code should read as
Code:
# drm blobs
PRODUCT_COPY_FILES += \
vendor/samsung/smdk4210-tab/props/system/vendor/lib/libdrmdecrypt.so:system/vendor/lib/libdrmdecrypt.so \
vendor/samsung/smdk4210-tab/props/system/vendor/lib/libwvm.so:system/vendor/lib/libwvm.so \
vendor/samsung/smdk4210-tab/props/system/vendor/lib/drm/libdrmwvmplugin.so:system/vendor/lib/drm/libdrmwvmplugin.so \
vendor/samsung/smdk4210-tab/props/system/vendor/lib/libwvdrm_L3.so:system/vendor/lib/libwvdrm_L3.so \
vendor/samsung/smdk4210-tab/props/system/vendor/lib/libWVStreamControlAPI_L3.so:system/vendor/lib/libWVStreamControlAPI_L3.so \
vendor/samsung/smdk4210-tab/props/system/vendor/lib/mediadrm/libwvdrmengine.so:system/vendor/lib/mediadrm/libwvdrmengine.so \
Regards,
Peter
Click to expand...
Click to collapse
I again put the files from your zip into the device tree and updated the /vendor/samsung/smdk4210-tab/blobs.mk accordingly. Building, flashing - still it crashes when trying to play any movie with the above logcat. Any idea? Is p6800 any different in these terms to p6810? Or is it depending on the media I try to play? I have some free movies like "BIG" or "BLANK" in my collection which I test with.
frami2 said:
I again put the files from your zip into the device tree and updated the /vendor/samsung/smdk4210-tab/blobs.mk accordingly. Building, flashing - still it crashes when trying to play any movie with the above logcat. Any idea? Is p6800 any different in these terms to p6810? Or is it depending on the media I try to play? I have some free movies like "BIG" or "BLANK" in my collection which I test with.
Click to expand...
Click to collapse
Hi Frank,
I also have those free movies, big and blank, and on my P6810 they play fine. Your original Widevine L3 blobs in your p6810 rom also worked fine for me under LineageOS 13, so I think your original files were fine.
I can see from my original Slim Rom build notes, that I had put libdrmdecrypt.so in the /system/lib folder, so I think it can work from either location.
Did you try just flashing the flashable version of the Blob's I attached in the previous post after flashing your Rom? It would be interesting to see if that makes any difference, it sets the permissions on the blob files as well to 644, which they need to be to work.
There's an app called "DRM Info" that I use from the play store to confirm that it can load the Widevine DRM libraries fine.
What changes do you make between the two Rom builds (for P6810 and P6800)?
Is it just this change?
Code:
FILE: /device/samsung/smdk4210-tab/device.mk
# **************************************
# * modify file and add these contents *
# **************************************
#adjust to wifi only for p6810 - modify according to device type, p6800, i815 - same as CM 12.1 build format - check CM 12.1 library for references
# common_full_tablet_wifionly.mk - p6810
# common_full_tablet_lte.mk - p6800
Btw, I believe (but haven't tested it), that you can flash the p6810 rom on a p6800 (but you won't have Mobile Data support), and you can probably test to see if the Google Play movies works over Wifi with your p6810 build, as the original build you made for me works without the updated Widevine L3 package.
Edit: Just looked over Daniels Repository - https://github.com/danielhk/proprie...10/tree/cm-13.0/smdk4210-tab/props/system/lib
Looks like he has two files in the /system/lib, libdrmdecrypt.so and libwvm.so - so change the code to update these two files, as it could be that you have a duplicate file, one old and one new, and this is causing the issue.
Hi,
Just installed your ROM for tests. Looks promising
I have only issue with GPS. I don't see any NMEA messages.
Regards,
test_user7 said:
Hi,
Just installed your ROM for tests. Looks promising
I have only issue with GPS. I don't see any NMEA messages.
Regards,
Click to expand...
Click to collapse
I just tried the gps on my p6810 and see its not working. It's probably because the non-pie blob support hasn't been enabled in the linker library as the gps blob/driver is old and needs this enabled.
Frank, there's notes in my slim rom compile notes on how to do this in linker.cpp from memory, the line numbers will probably be slightly different, but the code additions should help you locate the bits that need updating.
p3dboard said:
Hi Frank,
I also have those free movies, big and blank, and on my P6810 they play fine. Your original Widevine L3 blobs in your p6810 rom also worked fine for me under LineageOS 13, so I think your original files were fine.
I can see from my original Slim Rom build notes, that I had put libdrmdecrypt.so in the /system/lib folder, so I think it can work from either location.
Did you try just flashing the flashable version of the Blob's I attached in the previous post after flashing your Rom? It would be interesting to see if that makes any difference, it sets the permissions on the blob files as well to 644, which they need to be to work.
There's an app called "DRM Info" that I use from the play store to confirm that it can load the Widevine DRM libraries fine.
What changes do you make between the two Rom builds (for P6810 and P6800)?
Is it just this change?
Code:
FILE: /device/samsung/smdk4210-tab/device.mk
# **************************************
# * modify file and add these contents *
# **************************************
#adjust to wifi only for p6810 - modify according to device type, p6800, i815 - same as CM 12.1 build format - check CM 12.1 library for references
# common_full_tablet_wifionly.mk - p6810
# common_full_tablet_lte.mk - p6800
Btw, I believe (but haven't tested it), that you can flash the p6810 rom on a p6800 (but you won't have Mobile Data support), and you can probably test to see if the Google Play movies works over Wifi with your p6810 build, as the original build you made for me works without the updated Widevine L3 package.
Edit: Just looked over Daniels Repository - https://github.com/danielhk/proprie...10/tree/cm-13.0/smdk4210-tab/props/system/lib
Looks like he has two files in the /system/lib, libdrmdecrypt.so and libwvm.so - so change the code to update these two files, as it could be that you have a duplicate file, one old and one new, and this is causing the issue.
Click to expand...
Click to collapse
The zip file is not flashable in TWRP, anyhow, the chmod 644 even 777 does not help. DRM Info shows that Widevine is missing. I checked for differences between p6800 and p6810. This is in /device/samsung/p80XX/ and actually in the kernel too, the
/kernel/samsung/smdk4210/arch/arm/configs/cyanogenmod_p68XX_defconfig. Every change I made is same for both, only difference is regarding RIL. Anyhow, the defconfig files differ in many areas, maybe also due to RIL - here I try a strange hack now - use the P6810 defconfig for p6800. Let's see.
Furthermore, I found a workaround for the Amazon Kindle startup crash issue. In its crash stack I found libunwind.so. Replacing libunwind.so in /data/app/com.amazon.kindle-1/lib/arm/ with the one from /system/lib -> Kindle works
Just read this thread and start play again
My P6800 flash rom with Pico Gapp but seems running not smooth and found out some common issues:
- flash SuperSU 2.82 zip through TWRP successful but not get rooted can not use Kernel app.
- play YouTube: all have stopped with black screen just few seconds after running then replay. All clips get same problem.
Have no idea but seems it needs fix more.
One more thing the brightness of screen very low even manual with brightness maximum.
p3dboard said:
I just tried the gps on my p6810 and see its not working. It's probably because the non-pie blob support hasn't been enabled in the linker library as the gps blob/driver is old and needs this enabled.
Frank, there's notes in my slim rom compile notes on how to do this in linker.cpp from memory, the line numbers will probably be slightly different, but the code additions should help you locate the bits that need updating.
Click to expand...
Click to collapse
Thanks! But the changes cannot directly applied to cm13.0 there were some changes. I at least found that in cm14.1 the ENABLE_NON_PIE_SUPPORT is included in the standard. Will investigate further.
Harrison Le said:
Just read this thread and start play again
My P6800 flash rom with Pico Gapp but seems running not smooth and found out some common issues:
- flash SuperSU 2.82 zip through TWRP successful but not get rooted can not use Kernel app.
- play YouTube: all have stopped with black screen just few seconds after running then replay. All clips get same problem.
Have no idea but seems it needs fix more.
One more thing the brightness of screen very low even manual with brightness maximum.
Click to expand...
Click to collapse
- SuperSU 2.82 will not work, I updated the details on page 1
- YouTube plays fine on my P6800, tried different videos, e.g. the 4k demo videos (playing in 720p on our device ) <- do the installation with a full wipe, as described, then you should get it working - use the new version I uploaded yesterday, but it worked on the first version already.
- I also don't see the brightness thing. It is the same brightness like in TWRP recovery (auto brightness also working ... in slow steps) - maybe also due to wrong flashing method
frami2 said:
- SuperSU 2.82 will not work, I updated the details on page 1
Click to expand...
Click to collapse
We can install version 2.52 (https://download.chainfire.eu/743/supersu) from recovery and then update to 2.82 from Play store.
Hi Frank @frami2,
Just tested the latest build, 10/7, seems to be smoother, I seem to have more free Ram at boot, according to the program diskinfo, I have 370mb free ram, I think the last builds I had 280mb free ram. Also I tested the GPS and its working fine now on the p6810 Glad my notes helped you.
Hopefully my notes on how Daniel got the Bluetooth going (and how I got it going) might help you to fix that. From memory Daniel was working on a way under CM13 / LineageOS 13 to still have the normal Android Bluetooth stack going, along with the Bluez bluetooth stack - some sort of Compile switch from memory, a build directive. The method under CM 12.1 was to disable / remove the libraries the ASOP bluetooth stack and just enable the Bluez stack. This method probably still works, and might be the quickest way to get it going.
I've attached a screenshot of DRM info on my p6810 - this is what you should see on the p6800 when DRM is working. I know that DRM is a bit tricky, once you have all the bits in place, it just works. If it was broken on my p6810, that might make it easier for me to figure out what is wrong, but its working
Edit: tested your latest build, from July 13th, drm is still working fine on the p6810.
Just clean flash LOS build jul-13th incl. SuperSU-V2.52 and pico gapp, it is smooth than before a lot but still have some issues as below:
1. SuperSU updated to V.2.82 but poplock at SuperSU binary need to be updated.
2. Pull down status bar make screen turn to black and lock screen always black too
3. Set up screen at vertical but after reset the screen always turn to horizontal at black screen.
4. For video play: last ROMs issue are YouTube app be stopped awhile after start, YouTube and clip in browsers play OK but this ROM up side down: YouTube app play OK but video in browsers have crashed.
5. Bluetooth not active
6. ...........
Attached is video play in browsers be crashed
Edited: can not up picture from XDA app...
Harrison Le said:
Just clean flash LOS build jul-13th incl. SuperSU-V2.52 and pico gapp, it is smooth than before a lot but still have some issues as below:
1. SuperSU updated to V.2.82 but poplock at SuperSU binary need to be updated.
2. Pull down status bar make screen turn to black and lock screen always black too
3. Set up screen at vertical but after reset the screen always turn to horizontal at black screen.
4. For video play: last ROMs issue are YouTube app be stopped awhile after start, YouTube and clip in browsers play OK but this ROM up side down: YouTube app play OK but video in browsers have crashed.
5. Bluetooth not active
6. ...........
Attached is video play in browsers be crashed
Edited: can not up picture from XDA app...
Click to expand...
Click to collapse
Hi, thanks for testing!
1. Right, install SuperSU-V2.52 and then try to update and finally update binary. The last step takes a while but always returned on my device, with success or unsuccessful - trying again after reboot it finally succeeded
2. Yes, this and the screenshots in app-drawer are missing - this is intended by the "LOW_RAM" configuration I set (https://source.android.com/devices/tech/config/low-ram)
3. I will upload a new version with fixed auto-rotation soon - still, the picture change comes with a black screen sometimes
4. Have to check the youtube in browser issue - this sounds more serious. Do you have a P6800 or P6810? Could you check the youtube app? This should play fine - and will even rotate on next version
5. Sure, had no time yet to implement ( a guide how to is there by p3dboard)
frami2 said:
Hi, thanks for testing!
1. Right, install SuperSU-V2.52 and then try to update and finally update binary. The last step takes a while but always returned on my device, with success or unsuccessful - trying again after reboot it finally succeeded
2. Yes, this and the screenshots in app-drawer are missing - this is intended by the "LOW_RAM" configuration I set (https://source.android.com/devices/tech/config/low-ram)
3. I will upload a new version with fixed auto-rotation soon - still, the picture change comes with a black screen sometimes
4. Have to check the youtube in browser issue - this sounds more serious. Do you have a P6800 or P6810? Could you check the youtube app? This should play fine - and will even rotate on next version
5. Sure, had no time yet to implement ( a guide how to is there by p3dboard)
Click to expand...
Click to collapse
About 4. again - I'm currently running Youtube in Chrome without issues (on P6800 with deactivated DRM). it works in fullscreen and window mode.