{
"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.
Related
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.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SlimRom is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and Gerrit.
Code:
/* #include <std_disclaimer.h>
*
* Your tablet's warranty is now void.
* This is a custom ROM developed by p3dboard.
* You are flashing this on your Samsung Galaxy Tab 7.7 at your own peril.
* I am not responsible for hard bricks, damages to SD Cards, thermonuclear war,
* or you getting fired because the alarm app failed.
* I would definitely help you out if you are stuck somewhere, provided that you give
* me clear details of the mishap.
* Don't ask for ETA's cause there is a thing called "LIFE" outside XDA.
*/
SlimLP is currently in beta stage, some settings are already in place, much is still missing and would come with time. Stay tuned!
I am also new to development, so not as experienced as Daniel, and I also don't have a lot of extra time, so I'll do what I can, and fix what I can as I learn over time. But I wanted to contribute something new, and from Daniels survey, Slim was the second most popular rom after Carbon.
WHAT'S INCLUDED: (This is just a standard blurb, some of these SLIM extra's are not in their Beta yet)
Android Lollipop
Slim Center
Slim Launcher
Slim File Manager
Slim Heads Up
The Real Dark Slim User Interface
SlimPIE (inspired by ParanoidAndroid's PIE with a light touch of Slim)
Smart Card Service
Adaptive Backlight
Adaptive Brightness
Smart Lock
Privacy Guard
Sounds Tweaks(Audio FX and Music FX)
Status Bar Tweaks
Battery Saver Mode
Removed Bloatwares
Notification Reminder/Snoozer
Drawer Shortcuts
Lockscreen Shortcuts
Custom Quick Settings Tiles
Improved Performance
Camera - True View
Camera - Smart Capture
and Much More!
WHAT'S WORKING:
Camera
Video Recording
Wi-Fi
Bluetooth
ADB
Proximity Sensor
External SD Card
Internal SD Card
Video Playback
Speaker
Airplane Mode
RIL(Mobile and Data Network)
Compass - Can require calibration before being reasonably accurate (moving tablet around in a figure 8 a few times) - Might be a way to recalibrate this?
Automatic Brightness Sensor
GPS
POSSIBLY WORKING - TESTING REQUIRED:
Mobile Hotspot (can someone with a p6800 tell me if it works for them?)
BUGS/NOT WORKING:
Wifi Driver Bug that can reboot (ES Explorer Direct Send between two devices)
QS Torch Tile (Quick Settings Torch)
Touch Keyboard at initial boot - you need to either not flash GAPPS immediately or cancel the Setup with GAPPS flashed, then go into SETTINGS -> LANGUAGE&INPUT -> Current Keyboard and then turn on Hardware Input - After that the AOSP keyboard works - need to figure out how to fix this.
HOW TO INSTALL:
1. Download the ROM and the GApps and place them on your SD Card/Internal Storage.
2. Reboot tablet into TWRP recovery.
3. Wipe data, cache(factory reset), dalvik/art cache and system.
4. Flash the ROM and the GApps.
5. Reboot System. (First boot takes 5-6 minutes. Be patient.)
UPGRADING: If you are upgrading from a previous SlimLP build (not Kit kat Slim rom's, as you will get some issues)
1. Download the ROM, place it on your SD Card/Internal Storage.
2. Reboot tablet into TWRP recovery.
3. Flash the ROM
4. Reboot System.
SOURCES:
Daniel_HK's GitHub
SlimRoms Website
Google+
My code change notes - Download "Slimlp Changes to compile.txt" - How to compile after you have read and understood Daniels Instructions on compiling Rom's - read - read - read - something I didn't and don't always seem to do
CREDITS:
SlimROMs Team
@daniel_hk
and others I may have forgotten.
DOWNLOADS AND CHANGELOG IN THE SECOND POST
XDA: DevDB Information
SlimLP 5.1.1 by SlimRoms, ROM for the Samsung Galaxy Tab 7.7
Contributors
@p3dboard
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
ROM Firmware Required: Galaxy Tab 7.7 (p6800,p6810)
Based On: AOSP
Version Information
Status: Build #1.8
Latest Build Release Date: 2016-04-06
Created 2015-09-15
Last Updated 2015-10-28
Change Log and Downloads
Slim Gerrit - Slim Rom's change log
4 April 2016
SlimLP Beta 0.15 - Build #1.8 - Build Date 20160406 - Download ROM from this URL
- Updated Source Code to Beta 0.15 (Patch Level is up to February 2016 in Security - Possibly this is the last update Slim might make for Android 5.1.1, CM 12.1 sources have been updated to April 2014, but not Slim so far)
- P6800 & P6810 builds completed (just the NoZram version)
- Added Daniel's Performance Control app, but it errors out when going to the Battery tab, I'll leave it in their incase anyone wants to use the CPU / Governor controls - but if you want to tweak memory, use another app like Trickster Mod from the play store.
- Returned Davlik Memory settings back to stock in this build, as if you don't have too many apps installed that run background services, you can open apps that use larger Ram values.
I decided to recompile a newer build as I wanted a Rom with a more recent security patch level that also had Google Play Movies working, Android 6.0 currently has issues the the L3 DRM blobs. It's still got the same old issues as mentioned in the first post with workarounds as above - Touch keyboard, and the QS Flashlight not working, along with the reboot bug if you try to transfer data over Wifi using Es Explorer. But apart from that its pretty stable.
28 Oct 2015
SlimLP Beta 0.10 - Build #1.7 - Build Date 20151028 - Download ROM from this URL
- Updated Source Code to Beta 0.10
- Making two version of the build, one with zRam and one without - you can choose which one you feel performs better
- Updated RIL libraries for p6800 from Daniels latest CM 12.1 build (October 2015 build)
- p6800 rom's uploading now for Build 1.7, zRam and no-zRam version
- The no zRam version still supports zRam but its not turned on by default. If you have the app Trickster Mod from the playstore, (there's probably others) you can turn the zRam off any time you want to while running the rom. If you turn it off and then back on in Trickster Mod however, the new zRam partition is only 10% of the memory, which is smaller then the 256mb zRam I am turning on at boot.
- P6810 Zram build uploaded, uploading non-zram p6810 rom version now, compiling p6800 rom.
- P6810 beta 0.10 compile completed (no zRam version), uploading, compiling p6810 zram build. Once this finishes building, i'll start the p6800 build
- Synced SlimLP Beta 0.10 source code, starting compile of P6810 rom
- I'll make two builds of each for the next rom, one with Zram turned on and one without.
- I still haven't had time to look at the Keyboard issue or the QS torch icon, got to many things on at the moment - so just doing source code updates
14 Oct 2015
SlimLP Beta 0.9 - Build #1.6.2 - Build Date 20151014 - Download ROM from this URL
- Added missing blob libsec-ril.so file for p6800
- Added a 256mb zram swap partition (cm12.1 i9100 nightly just implemented this as they said it can help with low memory situations, so I've added it to see if it helps us at all - give me feedback, we can always turn it off).
@4:05pm - p6800 build is uploaded.
@3:35pm - p6800 build complete, checked that libsec-ril.so was in the /system/lib folder. Uploading now (about 30min it should be there)
@8:44am - build 1.6.2 for p6810 with 256mb zram uploading now. I am building the p6800 rom now.
@8:25am - I just discovered I missed adding /system/lib/libsec-ril.so to the p6800 build (builds 1.6 and 1.6.1) - so stick with 1.5.1 until I fix this on the p6800, so Mobile services won't be available. I'll recompile the rom for the p6800 today.
13 Oct 2015
SlimLP Beta 0.9 - Build #1.6.1 - Build Date 20151013 - Download ROM from this URL
- New Stagefright security patch and October 1st Android Security patches (see Slim Gerrit changes for today for the latest list of changes)
- Bug in this build: P6800 rom missing RIL blob - mobile / data won't work
@6:43pm - p6810 build completed, uploading now.
@4:55pm - p6800 build 1.6.1 compiled, uploading now. Compiling the p6810 build now.
@4:00pm - i just noticed that the slimlp source just received the new stagefright security fix, i've synced the new source code updates and am compiling build 1.6.1, it also has the other Google security updates for October. Building p6800 rom now.
SlimLP Beta 0.9 - Build #1.6 - Build Date 20151012/13 - Download ROM from this URL
- Sources updated to SlimLP Beta 0.9
- Bluetooth built using Daniels new Bluetooth packages that allow Bluedroid and Bluez to co-exist
- Daniels USB-OTG update (from his sources)
- Bug in this build: P6800 rom missing RIL blob - mobile / data won't work
@3:08pm - p6800 build is up.
@2:20pm - p6800 build 1.6 compile completed. Uploading now (should be about 30min)
@8:23am - p6810 build 1.6 is uploaded
@8:20am - I'm uploading the p6810 build at the moment, then I'll start compiling the p6800 build
12 Oct 2015
- I've just downloaded SlimLP Beta 0.9 source code and sync'd Daniels latest device tries, starting on compile for the p6810 (Android 5.1.1_r20)
- I'm also going to test adding persist.sys.debug.multi_window=true to /system/build.prop - which might only be a Marshmallow (Android 6.0) setting, but I'll see if it works in 5.1.1_r20 of SlimLP Beta 0.9 source code
- I'm also going to test building Daniel's updated Bluetooth Package from his Github that allows it to co-exist with Bluedroid Bluetooth, rather then removing it.
- I haven't had any time to look at the Torch QS tile or the keyboard fault in the last two weeks, eventually I'll get onto those.
1 Oct 2015
SlimLP Beta 0.8 - Build #1.5.1 - Build Date 20151001 - Download ROM from this URL
- Modified /system/build.prop Davlik values again based on some more testing. dalvik.vm.heapgrowthlimit=64m. Previous build 1.5 tends to be laggy when launching multiple apps. You can test Build 1.5 and 1.5.1 and decide which settings give better performance if you like. If you know how to modify build.prop with root access, you don't need to reflash the rom, just set the Build.prop values.
@11:00am - p6810 build also uploaded.
@10:20am - p6800 build uploaded. p6810 build uploading now.
@9:17am - p6800 build compiled. Uploading. Compiling p6810 build now.
@8:00am - I think the new Davlik values are a bit excessive. I think increasing to dalvik.vm.heapgrowthlimit=64m, instead of dalvik.vm.heapgrowthlimit=100m, provides better responsiveness, but still enough for background apps like facebook (which uses around 60m of ram). For example, with the 64m value, opening a hyperlink from Gmail in Chrome works nicely, but at 100m, it's very laggy. My previous builds had this value set at 48m.
I think these values are better - I'll put a build 1.5.1 up soon, for those who want to try the different values (or you can manually set it yourself in Build.prop if your comfortable).
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=320m
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=2m
30 Sept 2015
SlimLP Beta 0.8 - Build #1.5 - Build Date 20150930 - Download ROM from this URL
- Updated Device Tree's from Daniel, Mobile Hotspot should be fixed for p6800 users
- GPS fixed
- Modified /system/build.prop Davlik values based on Article about Ram and Davlik settings, seems to be giving better performance, Games like Asphalt 8 seem to be smoother, more Ram seems to be generally available.
@7:14pm - p6800 rom uploaded
@6:34pm - p6800 build completed, uploading now, should be there in 30min
@6:15pm - P6810 Build #1.5 is uploaded. P6800 build still compiling..
@6:10pm - playing with Facebook installed in the background, dalvik.vm.heapsize=256m is more friendly for Facebook (dalvik.vm.heapgrowthlimit=100m is what helps Facebook to run more smoothly as a background process) in that games like Asphalt 8 are still playable with the 256m value, rather than dalvik.vm.heapsize=320m. But dalvik.vm.heapsize=320m / 384m is better for Real Racing 3 on High detail level, medium and low detail are fine with 256m.
@5:30pm - finished p6810 compile, uploading p6810 rom. Compiling p6800 rom now.
@3:35pm - doing a recompile of the p6800/p6810 with the adjusted Davlik VM settings, after which I will upload the rom's
@3:30pm - I finished my Davlik memory testing, I'm going with these values for my Build 1.5, a bit larger for the dalvik.vm.heapsize, as games like Real Racing 3 benefit from the larger value, and probably the Chrome Web browser does as well. The article recommended dalvik.vm.heapsize=174m, which is probably better if you have lots of smaller apps, but I'll optimize for some bigger apps using dalvik.vm.heapsize=320m. The dalvik.vm.heapgrowthlimit=100m seems to have given back more base memory, I can get over 460m of free Ram at times now.
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=100m
dalvik.vm.heapsize=320m
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=8m
@8:35am - Test Build 1.5 - GPS works - so Non-Pie blob support is working again! Just testing the new Davlik memory settings now.
@8:00am - p6810 build 1.5 test build completed, if it's working ok I'll upload it as Build 1.5, otherwise I'll have to investigate why the Non-Pie support is not working.
29 Sept 2015
- 7:50pm - Starting build 1.5 for p6810 - will test to make sure GPS is working before doing p6800 build.
-I've manually updated the Bionic libraries with the Non-Pie support, as the Bionic libraries in SlimLP Beta 0.8 had more changes to them then just the non-pie support additions from the previous library which Daniel had given me, which was basically the same Bionic Library as SlimLP Beta 0.7 with the Non-Pie additions.
- Found interesting article on Davlik Heap values and ART https://01.org/android-ia/user-guides/android-memory-tuning-android-5.0-and-5.1 - I am going to test build my next one with their recommended settings to see the difference in performance (they say this benefits facebook as well due to the way it uses memory).
28 Sept 2015
- Looks like Daniel pushed another change to danielhk/proprietary_vendor_samsung_smdk4210 for the Hotspot after I did the Build 1.4 yesterday - https://github.com/danielhk?tab=activity - so I think that when I compile Build 1.5, this will hopefully fix the hostpot as well. I
- Build's 1.3 and 1.4 have issues with GPS again. I will have to do a recompile, it seems like the non-pie support was not enabled for GPS in those builds. Builds 1.1 and 1.2 the GPS works fine.
27 Sept 2015
SlimLP Beta 0.8 - Build #1.4 - Build Date 20150927 - Download ROM from this URL
- Updated Device Tree's from Daniel, Ambient Sensor should be fixed
- Mobile Hotspot doesn't seem to be fixed
- GPS has broken (non-pie support) - It has on my p6810 - will have to do a recompile for Non-Pie support that got missed some how
@10:15pm - The compile with CONFIG_KEYBOARD_SEC_DOCK=m or CONFIG_KEYBOARD_SEC_DOCK=n failed due to the fact that this causes other issues with the Kernel code. The code would need some adjustments to make this work for us. Anyway, I'll keep on investigating trying to turn the initial value to on for the Hardware switch in the Language and Input settings error. I checked Daniels omnirom build, and he's not turning on the hardware switch, so he must be specifically enabling the Touch Keyboard in the code even if a hardware keyboard is listed as present (I have seen some old code examples of people doing this, but some of the variables are not present in the SlimLP code - so I can't just copy their examples without finding the rest of the additional code needed).
@10:00pm - I got a reply from a Galaxy Tab 2 developer, he told me how they overcame this same issue, they got the commit included into Cyanogenmod to make the Keyboard Dock driver a module, so for anyone who needs it, the module can be started as an init.d module. I am doing a compile now to see if this fixes the keyboard driver, if so I'll make it build # 1.5...
http://review.cyanogenmod.org/#/c/83499/
espresso10: build KEYBOARD_SEC_DOCK as module Our sec_keyboard driver does not properly unregister the input device when no dock is detected, which makes the system believe that a physical keyboard is present at all times, which prevents the software keyboard from being shown. Some user own a Keyboard-Dock and meight miss the ability to use the dock if it gets disabled completely. Building it as module gives the user the ability to add a simple init.d script to start the module at boot if they need it.
/kernel/samsung/smdk4210/arch/arm/configs/cyanogenmod_p6800_defconfig
Code change CONFIG_KEYBOARD_SEC_DOCK=y -> CONFIG_KEYBOARD_SEC_DOCK=m
/kernel/samsung/smdk4210/arch/arm/configs/cyanogenmod_p6810_defconfig
Code change CONFIG_KEYBOARD_SEC_DOCK=y -> CONFIG_KEYBOARD_SEC_DOCK=m
@9:41pm - p6800 build compiled, uploading now.
@7:47pm - p6810 build compiled and uploading, building p6800
SlimLP Beta 0.8 - Build #1.3 - Build Date 20150926 - Download ROM from this URL
- SlimLP Source code updated to Beta 0.8
- GPS has broken (non-pie support) - It has on my p6810 - will have to do a recompile for Non-Pie support that got missed some how
@3:04pm - p6800 build 1.3 uploaded. P6810 build 1.4 commenced.
@2:35pm - resetting Code base and Resyncing Daniels Device Library changes for Build 1.4 (Hotspot fix and Ambient Display fix)
@2:30pm - P6800 SlimLP Beta 0.8 build finished, uploading now (build 1.3)
@ 8:00am - P6810 SlimLP Beta 0.8 build finished and uploaded. Building P6800 rom. (My Rom build # 1.3)
- I've just looked at Daniels new Omnirom Change Log for 20150926 build and his new sources (which came out just after I started this new build) fixes the Wifi Hotspot and the Ambient Display issues. Once the first build of Beta 0.8 is compiled, I'll resync my Sources to get his updates and then build 1.4, which will include these fixes.
26 Sept 2015
5:30pm - I've just updated my SlimLP code base to Beta 0.8, and am recompiling my p6810 build. I'll leave it compile tonight and compile a p6800 build after that.
Next week I'll keep on tracking down this Soft Keyboard bug, where it's not initially enabled (I'm only going to try set the initial Toggle value to on - not try and resolve the false positive on the driver believing that there's a keyboard docked).
5:00pm - My testing has confirmed that this code only removes the hardware option (set to false and the hardware option re-appears), it doesn't set the hardware toggle to on. But I might be able to use this bit of code to help me start to find the option. I just need to find where the Default Value of this toggle switch is set, and then adjust the default to be turned on, instead of off.
2:30pm - I just had a chance to test the build, the value of config_forceDisableHardwareKeyboard = true, completely hid the Hardware option from the Input and Settings area, preventing the value from being changed. I am just trying a test build with the value of False, but I don't think this is going to turn on the value.... I'll have to try see if I can find where the Hardware Setting is kept (probably in the same part of the code) and work on some sort of fix.
8:30am - I've made a p6810 test build to see if it fixes the keyboard. I'll test it later today as I have to go out now.
I've set the config_forceDisableHardwareKeyboard to true via an overlay file (which overrides the default value of false - which I believe turns off the fix and makes things behave as if the extra code was not included). From what I understand from my reading, the keyboard issue is present because the default driver is wrongly reporting that a Keyboard dock is present. Which if you plug in a keyboard via usb, you see that it behaves like one is, the softkeyboard just gives you word predictions on screen, but no keyboard. So I think that is right. Changing that Hardware option in input corrects this wrong assumption and then the soft keyboard appears.
25 Sept 2015
10:43pm @ I think i might have found some code to fix the soft keyboard not working at startup issue at https://gerrit.omnirom.org/#/c/903/2
Edit: Looking over Cyanogenmod code, they have already implemented this fix, but SlimLP hasn't added it to their code base, so I have added it to the source code and am doing a compile now. The only thing I think I need to work out is if I need a true / false value for the config_forceDisableHardwareKeyboard parameter, but once I have that worked out, hopefully this should fix it.
24 Sept 2015
SlimLP Beta 0.7 - Build #1.2 - Build Date 20150924 - Download ROM from this URL
- Media DRM fixed for Google Play Movies / Youtube DRM based content (libraries from p3100)
- increased dalvik.vm.heapsize=320m - Hopefully should provide a bit more memory for Facebook / Facebook Messenger
@9:30pm - p6800 build is uploaded
@8:43pm (10:43am GMT)- Compile finished for p6800, uploading now
@7:00pm - Build #1.2 - Compiled p6810 build and am uploading. Compiling p6800 build
@10am - I fixed the Play Movies streaming issue. Using libdrmdecrypt.so from p3100 (https://github.com/TheMuppets/proprietary_vendor_samsung/tree/cm-12.1/p31xx/common/system/lib) - goes in the /system/lib, also the three libwv*.so files from (https://github.com/TheMuppets/proprietary_vendor_samsung/tree/cm-12.1/p31xx/common/system/vendor/lib) in the /system/lib folder, the libdrmwv...so file from (https://github.com/TheMuppets/propr...ee/cm-12.1/p31xx/common/system/vendor/lib/drm) in the /system/lib/drm folder and finally, in /vendor/lib/mediadrm (the vendor folder should really be a link to /system/vendor, not a seperate folder as it currently is in our builds), the libwvdrmengine.so from (https://github.com/TheMuppets/propr...-12.1/p31xx/common/system/vendor/lib/mediadrm).
- Next build if I will try incorporate this fix
23 Sept 2015
- I was having a bit of a play last night with Google Play Movies, as to why it doesn't stream. It seems that Lollipop (as compared to kitkat) requires /vendor/lib/mediadrm/libwvdrmengine.so and possibly a few other components. I have gotten a copy of this file from the exynos 4412 smdk files, but there are a few more components missing (this might not even be compatible with our exynos 4210 but its worth a try). But with this file in place, it no longer gives the device is unsupported message, it tries to start streaming and errors out. I had a quick look in the log and I think it also wanted another crypto .so driver file, so I'll see if I can find that driver as well. There's a large collection of samsung blobs at https://github.com/TheMuppets/proprietary_vendor_samsung
20 Sept 2015
- 1:25pm - 3:25am GMT - I tested GPS on my P6810 (wifi model) and it now works!
- 7:51am - 9:51pm GMT - p6800 build is uploaded.
Daniel has given me some feedback on the i815 and some other things I was wondering about, so I'll go read over his instructions and my code some time next week and see if I can work this out. Once I have it compiling i'll make an update. Thanks @daniel_hk
- 7:24am - 9:24pm GMT - uploading p6800 build. It should be there in the next 20 minutes.
19 Sept 2015 - 11:18pm - I've uploaded the P6810 build of the rom, I'm waiting on the p6800 build to finish compiling - going to sleep now, so that will probably be in the morning. I've had a report from a tester that the Package Installer was crashing on the p6800 build when trying to manually install an APK package. I haven't had this happen on my P6810 build, so if someone can test the new build and let me know if this is an issue still that would be great.
SlimLP Beta 0.7 - Build #1.1 - Build Date 20150919 - Download ROM from this URL
- Rebuilt rom with Bionic Library supplied by Daniel that has Non-Pie Blob / Driver support
- GPS working
- Manually copied RIL Libraries into /system/lib folder from Daniels latest Omnirom Build - Hopefully for the p6800 this should enable RIL / Sim Card support - Files copied from Omnirom build are as follows:
/system/lib/libreference-ril.so
/system/lib/libril.so
/system/lib/librilutils.so
/system/lib/libsecril-client.so
/system/lib/libsecril-client-sap.so
/system/bin/rild
19 Sept 2015 @ 7:14am - Checked my PC this morning and it failed with the same compile error again for the i815. I'll have to keep on looking.
18 Sept 2015 @7:55pm - 9:55am GMT - Clearing out my build folders to try a fresh compile of the i815 code in case some of the p6800/p6810 build code is causing issues. I'll probably post an update tomorrow on how this went. Once I can compile the i815 code properly, I'll start looking at the other issues.
Update: 10:48pm - it may have gotten past the error below now, during the build I noticed the following in the output... still a number of hours to go before the i815 compile finishes.
Code:
build/core/Makefile:46: warning: overriding recipe for target '/home/peter/android/slimlp/out/target/product/i815/system/lib/hw/sensors.exynos4.so'
build/core/base_rules.mk:550: warning: ignoring old recipe for target '/home/peter/android/slimlp/out/target/product/i815/system/lib/hw/sensors.exynos4.so'
15 sept 2015 @10:42pm - 12:42am GMT - My compile of the i815 code hit an error, I'll have to track it down tomorrow if I get a chance
Code:
make: *** No rule to make target '/home/peter/android/slimlp/out/target/product/i815/obj/SHARED_LIBRARIES/libinvensense_hal_intermediates/export_includes', needed by '/home/peter/android/slimlp/out/target/product/i815/obj/SHARED_LIBRARIES/sensors.exynos4_intermediates/import_includes'. Stop.
make: *** Waiting for unfinished jobs....
15 sept 2015 @5:38pm - 7 :38am GMT - p6800 rom uploaded
Around 7hr 15 min for my old e5400 CPU to compile the 21gb of output per device specific folder to build the p6800 rom (there's a common output, and then device specific output). I'm just about to start the i815 build... just moving my cm12.1 code folder off the drive to an external disk so I have enough room to build the i815 rom.
15 Sept 2015 @ 10:52am - 12:52am GMT - I've uploaded the p6810 rom, I'm currently compiling the p6800 rom and when that's done I'll compile an i815 rom
SlimLP Beta 0.7 - Build #1.0 - Build Date 20150915 - Download ROM from this URL
- Built from SlimLP Beta 0.7 Sources
- Bluetooth Fixed
- OpenGL ES values set to 2.0 values in /system/etc/build.prop
- Davlik VM settings adjusted to possible better values
- Compiled from Daniel's Github sources - check the local_manifest.xml to see which sources where used
- GPS and ASOP keyboard bugs still present, QS tile for torch not working.
- Google Play Movies only work if you download locally first then play, not streamed - I have tested this on other Android 5.1.1 roms on my p6810 and it's the same on all of them at the moment.
- GPS.exynos4.so (GPS driver) from Galaxy S2 i9100 / CM 12.1 rom in this build (it may or may not work with our Exynos 4 processor, but it's a PIE build of the GPS blob for Exynos 4, which means that I didn't need to modify the BIONIC libraries for Non-Pie support). I've uploaded the GPS exynos 4 blob to my Androidhost.com folder for Slim as well - Next build I try for my p6810, I'll use Daniel's older GPS blob's and enable non-pie. However with this PIE based GPS blob, I don't get any GPS Client communication errors / socket not open errors. So I might simply need a different gps config file for this to work
GApps:
Official SlimRoms GApps
Questions and Answers
Testing- Just a note at the moment, I only have a p6810 (wifi only model) so my testing is limited to this. I am compiling p6800 and i815 rom's based on @daniel_hk's github source tree's, doing the modifications that I do for my p6810 to compile. So if you want to test and let me know about p6800 and i815 issues that would be great
i815 - Hopefully in a week or two I'll have time to make a build once I sort out a compile error. Daniel's given me some feedback, I just need to find some time to look over it.
QS Torch - I'll try work out the code for this QS torch tile setting soon
Memory Settings - Interesting article on Davlik Heap values and ART on android 5.0 and 5.1 https://01.org/android-ia/user-guide...id-5.0-and-5.1. Give me some feedback on performance as i still think we can tweak ram a bit more.
No time frames on anything, I'll just do what I can when I can.
Sim card not detected
I tried the new rom on p6800 with no sim card error.
Thanks for reporting back, at least I know that it boots on the p6800. Next build I do for the p6800/p6810 I'll be enabling the Non-PIE blob support which should help with some of the older driver libraries for things like GPS and possibly the RIL library which might fix this error for you as well.
hot spot not working on p6800
dear sir,
I just flash the new 1.1 rom on p6800. Every thing was fine except the hotspot.
My phone can detect the hot spot by p6800, but cannot get connected.
Thank you so much for such a great works.
Wait so is beta 0.7 the newest or alpha 1.1
On beta0.7 now and very smooth
philipnzw said:
Wait so is beta 0.7 the newest or alpha 1.1
On beta0.7 now and very smooth
Click to expand...
Click to collapse
Beta 0.7 is the slim ROM teams designation of their ROM build status. Alpha 1.1 is just my own designation to say it's my test builds, that being my second build, once I have the bugs sorted I will call it stable.
p3dboard said:
Beta 0.7 is the slim ROM teams designation of their ROM build status. Alpha 1.1 is just my own designation to say it's my test builds, that being my second build, once I have the bugs sorted I will call it stable.
Click to expand...
Click to collapse
Aha
It's quite stable already
philipnzw said:
Aha
It's quite stable already
Click to expand...
Click to collapse
I've changed my personal Labelling to Build #, instead of Alpha, that way its less confusing
p3dboard said:
Questions and Answers
QS Torch - I'll try work out the code for this QS torch tile setting soon
Click to expand...
Click to collapse
i think this could be an issue with slimroms in general.
it wasnt working on slimbean last time i tried it and its currently not working on slimkat either. (im on daniels slimkat)
p3dboard said:
Automatic Brightness Sensor - Have to do some more testing - Turning off Automatic Brightness, allows for a greater range of brightness
Click to expand...
Click to collapse
this issue is also present on daniels CarbonLP for me. either its related or somethings wrong with my p6800 thats duplicated on your p6810.
even tho its stable according to some, i think ill wait for a gps update before trying this out.
its times like these i wish we could have the dual/multi boot functionality.
way better and easier for the community to help test out the new/experimental builds.
especially for people like me whos using the p6xx as a daily driver.
good luck to you sir.
HM i will try it and lett you know how it go on my P6800,the lollipop 5.1.1 from daniel,i dont know what is wrong,when the wi-fi is turned on,i cann not tell you how much the difference in performance is,when i turn it on,it become laggy unbearably,so i will check with this................
Still holding up well after installing some xposed modules
Turning on awesome player seemed to help with YouTube crashing randomly
Also, uploading a picture with fb messenger app crashes everything (need to hold down power button)
Think Daniel's roms didn't have this issue.
I might need to increase the maximum memory amount for apps in the Build.prop,i set it to 256m, the default is 384m, but i dropped that lower as when some apps got to that size the rom's can become sluggish. I have had another app (real racing 3) lock up while trying to upload a game profile. I will play with the values some more. These are set in the build.prop file under /system/etc i have posted about them before in one of the other rom threads. If you are comfortable playing with the settings you could put them back to stock values and see if that fixes things for you and you can let me know. Thanks, Peter
Lag
p3dboard said:
I might need to increase the maximum memory amount for apps in the Build.prop,i set it to 256m, the default is 384m, but i dropped that lower as when some apps got to that size the rom's can become sluggish. I have had another app (real racing 3) lock up while trying to upload a game profile. I will play with the values some more. These are set in the build.prop file under /system/etc i have posted about them before in one of the other rom threads. If you are comfortable playing with the settings you could put them back to stock values and see if that fixes things for you and you can let me know. Thanks, Peter
Click to expand...
Click to collapse
Something to REPORT,i dont know it this just on my tab or not,but,it doesn't matter do i use CyanogenMod 12 or Carbon,or this SlimLP,yesterday wehn i instaled Carbon,after 30min when i installed all my apps,the last one that i installed was Facebook,and when i set it,then it become unbelievably Lagg,and i then installed SlimLP,and didnt installed other apps just Facebook,and this Lagged to,just now it just restarted alone.......................is this just because of FB or what is it,i just cann not take it any more,when i see it,the best android was 4.0.1
Definitely Lollipop rom's are more memory hungry than Kitkat Rom's. I am enquiring with one or two other rom maintainers who say they have implemented some optimizations for devices with 1 Gb Ram, to see what changes they are adding to improve performance. So far the best performing Rom i find is still Slimkat 8.2, Android 4.4.4, but it maybe possible to tweak lollipop for better performance. I have read on the Galaxy s2 forum that Facebook is an app with issues on the s2 CyanogenMod 12.1 rom as well. I will do a bit of testing and hopefully with some input from some others we might be able to fix this, we really need a lollipop rom with low memory overheads. Have you tried Facebook on Daniel's omnirom builds? They are the closest to stock Android, and may work better
Edit: i just installed Facebook on my s2 phone with CyanogenMod 12.1 (Android 5.1.1) and it seems to be ok, just wanted to test it on another 1gb ram device. The s2 has about 20mb more usable ram than our galaxy tab 7.7 due to lower screen resolution. Anyway, we will see what we can do to try improve things, a bit of trial and error,playing around
p3dboard said:
Definitely Lollipop rom's are more memory hungry than Kitkat Rom's. I am enquiring with one or two other rom maintainers who say they have implemented some optimizations for devices with 1 Gb Ram, to see what changes they are adding to improve performance. So far the best performing Rom i find is still Slimkat 8.2, Android 4.4.4, but it maybe possible to tweak lollipop for better performance. I have read on the Galaxy s2 forum that Facebook is an app with issues on the s2 CyanogenMod 12.1 rom as well. I will do a bit of testing and hopefully with some input from some others we might be able to fix this, we really need a lollipop rom with low memory overheads. Have you tried Facebook on Daniel's omnirom builds? They are the closest to stock Android, and may work better
Click to expand...
Click to collapse
no,i didnt try omnirom,i just used Daniel's Cyanogenom and Carbon,and this Slim,but when i charge my p6800 i will instal omni and try it.
LeonardoD93 said:
no,i didnt try omnirom,i just used Daniel's Cyanogenom and Carbon,and this Slim,but when i charge my p6800 i will instal omni and try it.
Click to expand...
Click to collapse
Might wanna try fb lite
Always avoided the main app on lollipop roms,after fb the whole system just lags like mad
Fb lite is like a smaller version of the main app,the user interface is absolutely horrible,but hey it works~
Just letting you all know that I have a fix for the Google Play movies not streaming DRM based content. I've posted about it in my Change Log.
philipnzw said:
Still holding up well after installing some xposed modules
Turning on awesome player seemed to help with YouTube crashing randomly
Also, uploading a picture with fb messenger app crashes everything (need to hold down power button)
Think Daniel's roms didn't have this issue.
Click to expand...
Click to collapse
I just tested Facebook Messenger with the davlik memory value set at 320m, and it uploaded a photo fine in my test, no crash. So it may be a memory limitation. SlimLP seems to be lighter on Ram, it may even be ok with 384m, but 320m seems to working ok for me. Next build, I'll increase the /system/build.prop Ram value to at least 320m, possibly 384m.
[ROM][N4][NMF26O] Fake nexus rom for Nexus 4. [Dec/06/2016]
Introduction
This is an Android 7.1 custom rom for Nexus 4 that fully integrated Gapps. (Pixel Launcher, Google dialer, Contacts, Webview, backuptransport, etc.. )
Screenshots
{
"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"
}
Features
Almost same as Pure Nexus Stock image.
Enabled SEAndroid, No Rooting feature provides for security reason.
All build scripts are opened on github
3G data is disabled as default for user that has cheap data plan. But you can enable on data setting menu.
Stock rom users can use this rom without perform reset userdata partition. (In theoretically, it can be applied to other custom rom users, but not tested. )
Known Issues
Nougat version is still unstable. Please use at your own risk.
Some apps can be crashed (ex: firefox, games using unity, etc...)
Camera app shows invalid orientation on preview screen
[*] User switch feature is not working. It should be fix in next release.
Please see FAQ
Installation instructions
1. power down
2. press power and volume down button, and your nexus 4 will go fastboot mode
3. connect usb cable with your PC
4. run fastboot for flashing
If you are using stock factory image or already use this rom.
Code:
$ fastboot update occam-img-20160108.zip
Or if you are using other custom roms, you might perform clear userdata partition.
Code:
$ fastboot -w update occam-img-20160108.zip
After flashing, it needs several (about 5-10) minutes to complete booting.
Changelog
Dec/06/2016: 20161206 (testing)
Update to NMF26O(android-7.1.1_r4)
Nov/08/2016: 20161108 (deprecated)
Update to NDE63V(android-7.1.0_r6)
Rebuild stubs for destroy useless icons
Nov/03/2016: 20161103 (deprecated)
add GmsCoreSetup
add Google VR Service
add help uri on Settings
apply pixel color accents
Nov/01/2016: 20161101 (deprecated)
fix user switch feature
add ringtone migration
fix tethering feature
fix dirtycow exploit
Oct/25/2016: 20161025 (deprecated)
Integrate Wallpaper picker on Settings
Integrate Google Backup & Sync on Settings
Integrate Google Storage Manager
Add Gesture menu on Settings
Enable color temperature setting in developer options
Use Ustwo wallpaper as default
Add Google Wallpapers
Stub apks can show round icons
Oct/21/2016: 20161021 (deprecated)
Update to NDE63P(android-7.1.0_r4)
apply pixel bootanimation, sounds, white navbar
apply latest pixel launcher
apply rounded icons for launcher
Note: it is not capable to use google assistant.
Note2: apps are not odexed, so, boot speed can be slow.
Note3: default ringtone, alarm, and notification sound is changed.
If you cannot hear these sounds, please set manually.
Oct/05/2016: 20161005 (deprecated)
update to NBD90Z (android-7.0.0_r14)
Oct/04/2016: 20161004 (deprecated)
fix ptrace bug on linux 3.4, thanks @zaclimon
switch to non-debuggable build
Sep/30/2016: 20160930 (deprecated)
Remove useless binaries and save space for system partition
apply qualcomm specific build macros
tune codec configuration for legacy binaries
Sep/26/2016: 20160926 (deprecated)
switch to debuggable build.
No more several apps might be crashed . but lesser secure.
revert to 320dpi as default
Sep/23/2016: 20160923 (deprecated)
debuggerd can dump stack when app is crashed on native code
Use Pixel launcher as default home
set 352 dpi as default
sign with release key
Refactor scripts to build other device(Nexus 5)
Sep/07/2016: 20160907 (deprecated)
update to NRD90S (android-7.0.0_r4)
Turned on sdcardfs
Sep/05/2016: 20160905 (deprecated)
Rebase device tree from @zaclimon V4
Remove w/r permission from vidc encoder device to all
It seems while mediacodec server open vidc encoder, camera server cannot use hardware encoder, and cannot record video stream.
Fix facelock funtion
Update widevine drm binary blobs from bullhead.
It might prevent to crash mediadrm and media service. But I cannot be sure it can play drm contents.
Switch to user build.
Sep/03/2016: 20160903 (deprecated)
Enable cpuset
implement exclusive core feature with simple mpcpusetd. @xenyz hints to me how to implement. Thanks.
Tune cpu governor while booting
Aug/31/2016: 20160831 (deprecated)
Rebase device tree from @zaclimon V3
Aug/29/2016: 20160829 (deprecated)
Rebase device tree from @zaclimon V2
Aug/28/2016: 20160828 (deprecated)
update to NRD90M (android-7.0.0_r1)
Rebase kernel source tree from @zaclimon
Rebase device tree from @zaclimon
Update occam device tree (fix compilation, update resources, etc...)
Aug/02/2016: 20160802 (stable)
update to MOB30Y (android-6.0.1_r60)
update google apps
Jul/07/2016: 20160707 (deprecated)
update to MOB30P (android-6.0.1_r50)
replace google photo as stub for reduce rom size
update google apps
Jun/07/2016: 20160607 (deprecated)
update to MOB30M (android-6.0.1_r46)
apply kernel security patches
update latest gapps
remove korean ime
May/03/2016: 20160503 (deprecated)
update to MOB30H (android-6.0.1_r41)
update latest gapps
update google play stub apks' icons
Apr/12/2016: 20160412 (deprecated)
update to MOB30D (android-6.0.1_r30)
apply flo kernel patches
Apr/05/2016: 20160405 (deprecated)
update to MMB29X (android-6.0.1_r20)
update latest gapps
Mar/21/2016: 20160321 (deprecated)
apply flo kernel security update for mm_mr1
Mar/09/2016: 20160309 (deprecated)
sync sources properly and rebuild
Mar/08/2016: 20160308 (deprecated)
update to MMB29V (android-6.0.1_r17)
update latest gapps
Feb/02/2016: 20160202 (deprecated)
update to MMB29Q (android-6.0.1_r11)
update latest gapps
setupwizard property typo fix ( reported by @jolas )
add hdcp binary blobs ( reported by @xenyz )
update opengl binary blobs (Jan 2016 qcom update)
Jan/08/2016: 20160108 (deprecated)
update latest gapps
I hope it could resolve Input Method issue.
Jan/05/2016: 20160105 (deprecated)
update to MMB29O (android-6.0.1_r7)
apply latest callmealdy kernel
Remove SysV IPC from kernel
fix leak of kernel memory to userspace
update qcom opengl binaries
Dec/10/2015: 20151210 (deprecated)
fix Google LatinIME to enable swipe gesture.
In 20151209 version, this rom used latinime from n7 factory image, and it had some problems when try to input with swipe gesture.
So I replaced with latinime from n5 factory image.
It is binary change, so there is no git commit link.
Dec/09/2015: 20151209 (deprecated)
update latest gapps that includes latinime
remove duplicated sound resources
add Google Connection Service and Nfc Provision
Dec/08/2015: 20151208 (deprecated)
update to MMB29K
remove unnecessary patches
replace to stub package for DeviceAssist to save storage
MMB29K image is slightly bigger than olders.
add Stk package as requested from @MarvinOl .
but cannot tested, because my mobile operator is not supported.
update apn list
update latest gapps
Nov/21/2015: 20151121 (deprecated)
Update adreno drivers (Nov 2015)
Update media codec profiles from flo
Apply audio resources from Nexus 5X (same things, but it is smaller than aosp stuff)
Apply memchr optimize patch
Apply patch that make surface buffer allocation asynchronous
Apply workaround for GoogleCamera3 crash
Nov/11/2015: 20151111 (deprecated)
apply libcore patches for speed up finalize daemon and object reference from aosp master
apply skia patches for using NEON from codeaurora
Nov/08/2015: 20151108 (deprecated)
remove useless camera behavior patches
reapply flashlight bug patch
Nov/07/2015: 20151107 (deprecated)
Switch to MDB08M (tree for Nexus 5x/6p)
Update resources and properties for MDB08M
add Dialer workaround for MDB08M
fix Audio HAL for MDB08M
apply recent gapps
Nov/03/2015 : 20151103 (deprecated)
MRA58V(Nov 2015 security patch level) applied
update kernel configurations for android recommands
add init.occam.rc (but it is empty yet)
remove invalid EAP-SIM support
Oct/30/2015 : 20151030 (deprecated)
FaceLock added
set Google Messenger to Default SMS/MMS app
adjust Launcher layout slightly
Oct/29/2015 : 20151029-1 (deprecated)
fix issue that home button is not working when upgrade from Stock factory image
Oct/29/2015 : 20151029 (deprecated)
All locales are available!!!
Also All (Stub) Gapps are available, too
Enable full odex (except prebuilt gapps) to reduce first booting time
Oct/25/2015 : 20151025 (deprecated)
stock rom users can be transitable to this rom without perform clear userdata partition
enable minikin text layout engine
fix gps hal build
Oct/24/2015 : 20151024 (deprecated)
fix a2dp bluetooth profile.
fix calendar sync problem (If calendar app is crashed, Please perform Settings -> Apps -> Calendar -> Storage -> "CLEAR DATA")
add several locales (sk_SK ar_EG pt_BR)
add version codes in gapps build rules
Oct/21/2015 : 20151021 (deprecated)
update adreno gpu driver (Oct/2015)
apply @CallMeAldy mako kernel
apply memcpy, memmove patch from codeaurora
apply flashlight torch mode bugfix
add "Press power button twice for camera" menu in Accessibility Setting (it will be removed after MDB08I source code opened)
Oct/16/2015 : mra58k (deprecated)
initial release
Before you ask something about this rom
Please read this article at first..
If you cannot read English well, it's okay. There are many translations of this article.
This is a very famous article for beginners that want to solve their problems.
Please DO NOT ASK via Private Message or Mail as described as upper article.
I cannot reply all messages and I may not understand all your problems.
If you post your question in this thread, any others can tell about your problems.
If you want to report your issue with this rom specific, please share bugreport data.
You can gather bugreport data with following methods.
Turn on USB debug feature, connect with PC, and run this command
Code:
$ adb bugreport > bugreport.txt
OR
Go to Developer options, select Take bug report. After several minutes, notification will be shown to share data.
Downloads
Stable (Aug/02/2016): https://androidfilehost.com/?fid=24651430732235260
Testing (Dec/06/2016): https://www.androidfilehost.com/?fid=457095661767121028
XDA:DevDB Information
fake_nexus, ROM for the Google Nexus 4
Contributors
ganachoco
Source Code: https://github.com/ganadist/vendor_fake_nexus/tree/nougat-dev
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Testing
Current Stable Version: 20160802
Stable Release Date: 2016-08-02
Current Beta Version: 20161206
Beta Release Date: 2016-12-06
Created 2015-10-21
Last Updated 2016-12-06
Is there any way to apply torchlight fix to frank ROM as a flashable zip?
Sent from my Nexus 4 using XDA Forums
I flashed the testing version. It works like a charm!
So with this I can just login after start and use google restore and also my apps will be able to backup to drive when the developer implemented it? Or do I still need to set permissions for gapps?
//Edit: Cmon, I just flashed da **** Yeah works as stated above.
What's new in testing? And what does it mean no ROOTed. Aren't those custom kernels, rooted already? (noob question).
Many thanks.
finchi said:
What's new in testing?
Click to expand...
Click to collapse
Did you even take a look at the first post
Ah sorry. I mistook lines. I was reading it like Oct/21/2015 : 20151021 (testing) and nothing there. (feeling stupid)
Shouldn't a long press on the recent square switch to the previously used app? It does not work in this rom but did on franks. This was really cool.
Camera is launched on double tap on home circle oO nice
Great ROM, I hope it will stay pure as possible
LoadGamePL said:
Is there any way to apply torchlight fix to frank ROM as a flashable zip?
Sent from my Nexus 4 using XDA Forums
Click to expand...
Click to collapse
That is a source level patch.
Please ask that apply that patch to frank ROM maintainer.
bassbox said:
Shouldn't a long press on the recent square switch to the previously used app? It does not work in this rom but did on franks. This was really cool.
Click to expand...
Click to collapse
This rom provide only stock rom features.
I have no plan to add other features.
bassbox said:
Camera is launched on double tap on home circle oO nice
Click to expand...
Click to collapse
You find it!
That is hidden test feature that samsung phones have.
And I put for vefify https://android-review.googlesource.com/177020
finchi said:
What's new in testing?
Click to expand...
Click to collapse
Please see Changelog.
finchi said:
And what does it mean no ROOTed. Aren't those custom kernels, rooted already? (noob question).
Many thanks.
Click to expand...
Click to collapse
In testing release, this rom uses @CallMeAldy kernel.
And rooting feature that other roms have, is not provided as default for security reason.
ganachoco said:
This rom provide only stock rom features.
I have no plan to add other features.
Click to expand...
Click to collapse
Yeah I thought this is a New stock feature ^^
Can you integrate large version of Google Now Launcher (1.2.large) which originally comes with Nexus 5, 6...? Your rom contains 1.2.small version of Google Now Launcher.
Whenever I browse youtube, screen freezes and System UI FC's.
Rock-86 said:
Can you integrate large version of Google Now Launcher (1.2.large) which originally come with Nexus 5, 6...? Your rom contain 1.2.small version of Google Now Launcher.
Click to expand...
Click to collapse
Which are the changes between 1.2 large and 1.2 small?
Inviato dal mio Nexus 4 utilizzando Tapatalk
sidnoit22 said:
Whenever I browse youtube, screen freezes and System UI FC's.
Click to expand...
Click to collapse
Which version of the ROM are you using?
You should upload bug report data:
ganachoco said:
You can get bugreport data by
Turn on USB debug feature, connect with PC, and run this command
Code:
$ adb bugreport > bugreport.txt
OR
Go to Developer options, select Take bug report. After several minutes, notification will be shown to share data.
Click to expand...
Click to collapse
cianz94 said:
Which are the changes between 1.2 large and 1.2 small?
Inviato dal mio Nexus 4 utilizzando Tapatalk
Click to expand...
Click to collapse
Not sure, but Large is comming with Nexus 5, 6..
I found one note for Small version:
Notes / What's New
Uploader's notes: Google Now Launcher Version 1.2. small from Android One Device running Android Marshmallow 6.0
Click to expand...
Click to collapse
Rock-86 said:
Can you integrate large version of Google Now Launcher (1.2.large) which originally come with Nexus 5, 6...? Your rom contain 1.2.small version of Google Now Launcher.
Click to expand...
Click to collapse
According by this figure, N4 has large screen, and I'll put large version when next version release.
Thank you for notify!
Hmm seems interesting seeing that 3 days left on the battery page screenshot . I have not seen mine say more than a little over a day left since a LP ROM I had a very very long time ago where 3 days was almost actually what I got pretty darn close to a few times . Very cool
Update- just checked and at 91% left its says 14 hrs left lol. But I'm currently running a different Android 6.0 ROM but must say hands down this Marshmallow is the FASTEST/smoothest I've ever seen my N4 run. Hell was gunna get me a N6 or the newer N5 so I could use my google fi invite but Im very happy with my device speed that I'm not sure I want to atm now .
Hi all!
What is this?
This is my mostly-working Razer Phone 2 Kernel and TWRP device tree!
I've been reading threads where people are having issues compiling the Razer-provided source for the RP2 and figured I should post what I have so others can use it to help achieve a fully working source-built kernel.
I'm also including a set of scripts to repack a Magisk-patched boot.img so you can iterate on building a new kernel rapidly, and am including a prebuilt magisk-patched boot.img with the custom kernel so we can QA other features while focusing on the known-broken things.
Also also, I'm including an exfat kernel module (not built into kernel for now) so that can be tested too!
Click to expand...
Click to collapse
Why is this mostly-working?
I've tested many features on this kernel and so far the only feature *not* working is the microphone. (Audio recording, haven't tested in-call audio)
This kernel is a mashup of Razer's source and a few other OSS repos from CAF - specifically the TFA98XX driver, and the audio-kernel repositories, so there's a bit of integration left to do to get all the audio features working.
I also had to edit the defconfig to get the DTB to build, and have to build with some special flags to use the prebuilt DTB compiler (dtc) since the one included in the source isn't capable of compiling the FIH DTBs inside the Razer-provided source (correct me if I'm doing something wrong here, but this was how I ended up getting it to work).
The kernel parameter skip_initramfs has also been renamed to skip__initramfs to break the silly bootloader skipping the ramdisk (and thereby breaking Magisk). This means you don't need to run Magisk's binary patch to rename that kernel argument to make Magisk or TWRP work.
Keep in mind, though, that this means if you use this kernel with a 100% stock ramdisk, you'll only ever get recovery since new Android ramdisks only contain recovery! (Thanks Dees_Troy for the refresher course!)
If you're familiar with the new audio-kernel CAF stuff, please let me know! I could use your assistance getting the microphone working.
It seems like the microphone isn't working because of some mismatches between the in-kernel msm audio drivers and the Razer customized drivers in the vendor partition.
I get errors like
Code:
[31269.485217] send_afe_cal_type cal_block not found!!
in dmesg when attempting to record audio. This seems isolated to the q6afe drivers in the kernel (specifically here: https://github.com/thecubed/android_kernel_razer_sdm845/blob/master/techpack/audio/dsp/q6afe.c#L1593 ) not playing nice with the prebuilt snd_soc_sdm845 kernel module.
Click to expand...
Click to collapse
Where do I get this?
See here for the TWRP device tree (and detailed instructions on how to set up your build tree): https://github.com/thecubed/android_device_razer_cheryl2
See here for just the kernel source: https://github.com/thecubed/android_kernel_razer_sdm845
See here for a kernel-less boot.img skeleton that you can drop your newly minted kernel into and repack with mkbootimg: http://downloads.codefi.re/thecubed/aura2/kernel/magisk_custom_kernel_skel.tar.gz
See here for a prebuilt boot.img with this custom kernel which includes Magisk: http://downloads.codefi.re/thecubed/aura2/kernel/boot_magisk_custom_9.img
See here for an exfat module you can insmod from a booted phone with custom kernel to try mounting exfat SD cards: http://downloads.codefi.re/thecubed/aura2/kernel/exfat_module.tar.gz
See here for a stock Magisk-patched boot.img for when you're done playing with this: http://downloads.codefi.re/thecubed/aura2/kernel/boot_magisk.img
Click to expand...
Click to collapse
How do I use this?
First off, this isn't for the average user. This kernel is *under development* and is not fully working yet. This means don't try this kernel on your mom's phone, your neighbor's phone, or any device that you aren't comfortable developing for.
Secondly, to test this, you'll need to be oem unlocked. There's plenty of guides to do this, but be aware that it erases all data on your phone when doing so. You could try using adb backup first, but I didn't have much success with that.
I'd suggest looking at the first link in the Where do I get this section and reading the README for the device tree as it'll have the most detailed instructions.
The gist is you'll need to download a minimal OmniROM manifest, add some lines to a file in .repo/local_manifests/cheryl2.xml, and run mka kernel to get a kernel image.
After that, you'll want to use mkbootimg to build a bootable magisk-patched boot.img, which you'll flash to your device with fastboot flash boot_X path/to/boot.img (where X is the active boot partition).
Once you've got the Image.gz-dtb file from your $OUT/obj/KERNEL_OBJ/arch/arm64/boot/Image.gz-dtb you'll want to repack it into a magisk-patched boot.img
Repacking the boot.img can be done with this command:
Code:
mkbootimg \
--kernel Image.gz-dtb \
--ramdisk boot_magisk.img-ramdisk.gz \
--cmdline 'console=ttyMSM0,115200n8 earlycon=msm_geni_serial,0xA84000 androidboot.hardware=qcom androidboot.console=ttyMSM0 video=vfb:640x400,bpp=32,memsize=3072000 msm_rtb.filter=0x237 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 service_locator.enable=1 swiotlb=2048 androidboot.configfs=true androidboot.usbcontroller=a600000.dwc3 buildvariant=user' \
--base 0x00000000 \
--pagesize 4096 \
--kernel_offset 0x00008000 \
--ramdisk_offset 0x01000000 \
--second_offset 0x00f00000 \
--tags_offset 0x00000100 \
--os_version 8.1.0 \
--os_patch_level 2018-10 \
-o ../boot_magisk_custom.img
Click to expand...
Click to collapse
FAQ
Does this have TWRP?
No. This does not have TWRP. The device tree is for TWRP eventually, and to make compiling the kernel easier (since Android kernels don't like compiling outside of Android's makefile system anymore)
Does this have Magisk?
Yes! It's "pre-patched" too, as long as you're using my prebuilt one above.
Do I need the custom kernel to use the exfat module?
Yes. This is because the Razer stock kernel has module signing forced. I don't have Razer's kernel module signing key so I can't compile kernel modules for the stock kernel. My kernel has module signing set to allow mismatched signatures, so both the Razer modules in /vendor/lib/modules (required for sound) and my exfat module can coexist.
Why is exfat not compiled into the kernel?
Laziness, primarily. Actually, in this case I just didn't want to add extra variables to testing the kernel. If adding exfat into the kernel directly causes other issues it could potentially derail my quest to get this kernel up to par with the stock kernel.
Why did other kernels not boot?
Most likely due to incompatible audio-kernel revisions, or dtb issues. I'm not sure, but getting this kernel to compile required a bit more hacking than it should have.
Are you working on TWRP for Razer Phone 2?
Yep. Look for another post once the kernel is good to go. I aim to get encryption support working too, unless Dees_Troy beats me to it
Is audio still not working?
I'll update the post to remove the WIP tag and the section about audio as soon as it's working.
Is anything else not working?
Feel free to download and test to let me know what else isn't working and I'll add it to the OP.
Click to expand...
Click to collapse
Acknowledgements
Special thanks to Rashed97 and Dees_Troy for all their help.
Click to expand...
Click to collapse
y u quote OP?
Thanks for your work! Looking forward for a stable version. Wanna help but RP2 is currently my only working phone..
u sir,deserve a beer,thanks for working rp2 and not to forget other devs who help u along the way,we will wait patiently,cheers!!!!
Thank you.
Interesting discovery just now, seems that the stock kernel gives the same 'error' in dmesg when recording audio (but obviously audio recording still works).
Code:
[ 1365.950315] send_afe_cal_type cal_block not found!!
This could mean that Razer doesn't have a calibration profile for the microphone anyway (interesting, wonder if there's an opportunity to improve recording quality here?) and that I'm barking up the wrong tree re: calibration mismatches.
I've also confirmed that I get the same 'ASoC: no backend DAIs enabled for [backend name here]' messages in the stock kernel when brute force trying all PCM inputs with:
Code:
for f in `seq 1 80`; do tinycap /sdcard/wavs/device-$f.wav -D 0 -d $f -r 48000; done
It's also (very) possible that I don't understand how tinycap works.
I dumped the list of PCM inputs/outputs with:
Code:
for f in `ls -d /proc/asound/sdm845tavilsndc/** | grep pcm`; do echo "$f : `grep 'id' $f/info`"; done
and
Code:
cat /proc/asound/pcm
on both kernels (stock and custom) and they seem to match.
I'm thinking I should figure out how to record sound outside of android (from adb only) from stock kernel, and use that same test to try in the custom kernel. If I can find a test like that, I should be able to determine if I need to rename one of my DAI links to match whatever's baked into the XML files in /vendor/etc .
Any ideas?
Are you using the audio.a2dp.default.so driver?
Warrior1988: A2DP isn't in play here, and I'm using the stock /system and /vendor partitions, so any razer-customized tweaks are still present.
Currently, I've been working on figuring out the codec mappings to make sure that when audio is being recorded in the custom kernel that all the appropriate routing is set to enable audio from the tfa98xx chip (NXP amplifier, apparently supports digital microphones too?) or the wcd934x codec.
I'm not sure where the microphones are physically connected internally, so I'm working backwards from what gets enabled/disabled when recording audio in the stock kernel.
So far I have observed a few things (pardon my potentially incorrect terminology, the whole linux ASOC sound layer is new to me):
1. Audio in the stock and custom kernels is being captured by the mixer device called "SDM845 Media1", and it is capturing from SLIMBUS_0_TX input.
Code:
[Recording]
aura:/sys/module # cat /sys/kernel/debug/asoc/sdm845-tavil-snd-card/SDM845\ Media1/state
[SDM845 Media1 - Playback]
State: new
Backends:
No active DSP links
[SDM845 Media1 - Capture]
State: start
Hardware Params: Format = S16_LE, Channels = 1, Rate = 16000
Backends:
- SLIMBUS_0_TX
State: start
Hardware Params: Format = S16_LE, Channels = 1, Rate = 48000
2. You can also see when recording and not recording that in both kernels the SLIMBUS_0_TX input is wired correctly to the right mixer:
Code:
[Not recording]
aura:/sys # cat ./kernel/debug/asoc/sdm845-tavil-snd-card/platform:soc:qcom,msm-pcm-routing/dapm/SLIMBUS_0_TX
SLIMBUS_0_TX: Off in 2 out 0 - R0(0x0) mask 0x1
stream Slimbus Capture inactive
out "static" "SLIM0_UL_HL"
in "static" "Slimbus Capture"
in "static" "BE_IN"
[Recording]
aura:/sys # cat ./kernel/debug/asoc/sdm845-tavil-snd-card/platform:soc:qcom,msm-pcm-routing/dapm/SLIMBUS_0_TX
SLIMBUS_0_TX: On in 2 out 1 - R0(0x0) mask 0x1
stream Slimbus Capture inactive
out "static" "SLIM0_UL_HL"
out "SLIM_0_TX" "MultiMedia1 Mixer"
in "static" "Slimbus Capture"
in "static" "BE_IN"
Now that I've observed those things, I need to do a bit more research on how audio can get enabled/disabled on each of the chips that touch it.
For instance, in the custom kernel, I noticed that during recording sounds the DMIC* lines on the second tfa98xx aren't enabled. I haven't checked in the stock kernel yet - but if the tfa98xx chip is providing mic bias, it's possible that everything is wired right for input but since the mic bias isn't on, the mic isn't powered and thus we get no sound.
(Updated side note, why is Razer Phone 2 is using two TFA9888 chips? The tfa98xx.cnt firmware references TFA9892 which is mono only, too. I need to see a disassembly to figure out what chips it's actually using...)
Code:
aura:/sys # cat ./kernel/debug/asoc/sdm845-tavil-snd-card/codec:tfa98xx.4-0034/dapm/DMIC*
DMIC1: Off in 1 out 0
out "static" "AIF OUT"
DMIC2: Off in 1 out 0
out "static" "AIF OUT"
DMIC3: Off in 1 out 0
out "static" "AIF OUT"
DMIC4: Off in 1 out 0
out "static" "AIF OUT"
aura:/sys # cat ./kernel/debug/asoc/sdm845-tavil-snd-card/codec:tfa98xx.4-0035/dapm/DMIC*
DMIC1: Off in 1 out 0
out "static" "AIF OUT"
in "static" "MIC BIAS1"
DMIC2: Off in 1 out 0
out "static" "AIF OUT"
DMIC3: Off in 1 out 0
out "static" "AIF OUT"
in "static" "MIC BIAS3"
DMIC4: Off in 1 out 0
out "static" "AIF OUT"
Update: just noticed that this path doesn't exist on stock kernel. So the TFA driver I have doesn't match the one Razer is using. Interesting!
Also, I'm not sure why SLIMBUS_2 playback/capture aren't shown as 'dynamic DAI' linked (the '(*)' means it's a dynamic DAI)... Probably not important though.
Code:
aura:/proc/asound # cat pcm
00-00: MultiMedia1 (*) : : playback 1 : capture 1
00-01: MultiMedia2 (*) : : playback 1 : capture 1
00-02: VoiceMMode1 (*) : : playback 1 : capture 1
00-03: VoIP (*) : : playback 1 : capture 1
00-04: MultiMedia3 (*) : : playback 1
00-05: SLIMBUS_0 Hostless (*) : : playback 1 : capture 1
00-06: AFE-PROXY RX msm-stub-rx-6 : : playback 1
00-07: AFE-PROXY TX msm-stub-tx-7 : : capture 1
00-09: AUXPCM Hostless (*) : : playback 1 : capture 1
00-10: SLIMBUS_1 Hostless (*) : : playback 1 : capture 1
00-11: SLIMBUS_3 Hostless (*) : : playback 1 : capture 1
00-12: SLIMBUS_4 Hostless (*) : : playback 1 : capture 1
00-13: MultiMedia5 (*) : : playback 1 : capture 1
00-14: Listen 1 Audio Service (*) : : capture 1
00-16: MultiMedia10 (*) : : playback 1 : capture 1
00-17: MM_NOIRQ (*) : : playback 1 : capture 1
00-18: HDMI_RX_HOSTLESS (*) : : playback 1
00-19: VoiceMMode2 (*) : : playback 1 : capture 1
00-20: Listen 2 Audio Service (*) : : capture 1
00-21: Listen 3 Audio Service (*) : : capture 1
00-22: Listen 4 Audio Service (*) : : capture 1
00-23: Listen 5 Audio Service (*) : : capture 1
00-24: Listen 6 Audio Service (*) : : capture 1
00-25: Listen 7 Audio Service (*) : : capture 1
00-26: Listen 8 Audio Service (*) : : capture 1
00-27: MultiMedia9 (*) : : playback 1 : capture 1
00-33: MM_NOIRQ_2 (*) : : playback 1 : capture 1
00-34: SLIMBUS8_HOSTLESS Capture (*) : : capture 1
00-35: Slimbus4 Capture tavil_vifeedback-35 : : capture 1
00-36: SLIMBUS_2 Hostless Playback tavil_rx2-36 : : playback 1
00-37: SLIMBUS_2 Hostless Capture tavil_tx2-37 : : capture 1
00-38: MultiMedia6 (*) : : playback 1 : capture 1
00-39: USB Audio Hostless (*) : : playback 1 : capture 1
00-80: QUAT_MI2S_RX Hostless (*) : : playback 1
Meanwhile, we've reached out to Razer to see if they'll bless us with the full and complete kernel source this time
I doubt it. They won't even answer simple questions as to an estimate of when we're getting Pie
blackknightavalon said:
I doubt it. They won't even answer simple questions as to an estimate of when we're getting Pie
Click to expand...
Click to collapse
>simple question
>eta
pick one
Any progress on this kernel? I'm really curious now that we have pie.
No progress as of yet, I've been busy with work recently and Razer hasn't dropped source for the new kernel version (still 4.9 but a different patch level).
I'm hopeful that Razer will drop the complete source for Pie's kernel and I can backport that to the Oreo kernel for those who want to keep the old OS.
I haven't updated my RP2 to Pie yet so I can test out any changes once the source for the new kernel is out. I'll be sure to post here when I have any updates
Audio-kernel source is out! https://s3.amazonaws.com/cheryl-factory-images/audio-kernel-aura-2009.tar.gz
I'll be rebuilding my kernel very soon and testing.
https://s3.amazonaws.com/cheryl-factory-images/
Warrior1988 said:
https://s3.amazonaws.com/cheryl-factory-images/
Click to expand...
Click to collapse
Yup, I'm building it right now!
Yup, it works! I have fully working audio and microphone now. Seems like there's a bunch of DAI changes and some offset changes to calibration stuff that FIH added (ugh).
Please hold while I get the commit up on my Github, and I'll get a build with exfat going here in just a minute after.
Plan is:
- Github updates (readme changes, etc) UPDATE: done
- Upload this current build I just tested for anyone that wants it
- Add exfat module to kernel and rebuild / test UPDATE: exfat support works, BUT I need to recompile vold to support exfat. I can mount the SD card just fine, but Android doesn't understand that it's mounted because vold isn't tracking it
Also, <3 u razer, thanks
I'm bummed to hear about the layoffs, and I really appreciate whomever uploaded the source even after that. Hopefully Razer's phone team will grow again and get to make us a Razer Phone 3 at some point in the future.
For anyone that's still running 8.1 and wants to try my custom kernel (no, no exfat support yet until I get vold fixed), here's a link: http://downloads.codefi.re/thecubed/aura2/kernel/boot_magisk_custom_10.img
Github has been updated as well.
I'll be sure to update the OP tomorrow when it's not 2AM.
EDIT: Fixed link, 2AM is not kind to my typing skills
Awesome work! Very excited to try it out tomorrow.
Also sad to see your post about their layoffs. Pretty fun phone with much potential for future.
I think some of the reviews are pretty harsh given the penchant of Pixel / Samsung / Apple worship out there.
Anyway, thanks so much for this.
thecubed said:
For anyone that's still running 8.1 and wants to try my custom kernel (no, no exfat support yet until I get vold fixed), here's a link: http://downloads.codefi.re/thecubed/aura2/boot_magisk_custom_10.img
Github has been updated as well.
I'll be sure to update the OP tomorrow when it's not 2AM.
Click to expand...
Click to collapse
Thank you for this!
It's showing up "Not found" on the download link though.
jal3223 said:
Thank you for this!
It's showing up "Not found" on the download link though.
Click to expand...
Click to collapse
Fixed the link in my previous post - sorry about that!
I'll be updating the OP tonight too when I get home from work.
Looking good! Is the sound as good as stock (or maybe better, considering the low volume crackling we get)?
Hoping to give this a shot soon, as soon as I figure out rooting on 9.0. I saw a thread about it, but nobody answered my question there, and light digging through threads didn't turn up an answer, so trying this kernel will have to wait a bit. Makes me miss the HTC root days, when finding out about root was a simple yes or no situation... lol.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is an Unofficial builds for Xperia Tablet Z LTE/Wi-Fi.
About ROM
LineageOS is a free, community built, aftermarket firmware distribution of Android 9.x (Pie), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
The source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Installation
Download the latest build
Place ROM in your SD card or Internal Storage
Reboot into recovery mode
Full wipe and factory reset (recommended)
Flash ROM
Reboot
Downloads
Pollux: AFHPollux_windy: AFHLineageOS addonsu for root access
(Information) Read the Root section of the Q&A thread
(Download) Download the addonsu for arm : LineageOS Downloads / Extras
(Optional) Flash the zip on a working Lineage installation (once)
(Information) Upon ROM updates, the addonsu is preserved
Reboot
Recommended Recovery (optional)
TWRP 3.2.xGapps (optional)
OpenGapps (ARM/Android-9.x): http://opengapps.orgSources
LineageOS on GithubKernel: apq8064
XDA:DevDB Information
LineageOS 16.0 for the Sony Xperia Tablet Z, ROM for the Sony Xperia Tablet Z
Contributors
CaHbKaUp, CyberWalkMaN, AdrianDC, Chippa_a
ROM OS Version: 9.x Pie
Version Information
Status: Testing
Beta Release Date: 2021-09-16
Created 2019-04-26
Last Updated 2021-09-17
FEATURES AND ISSUES
Code:
- Boot : Ok
- GApps : OpenGApps Nano Ok
- FOTA Recovery : Ok (see below)
- WiFi : Ok (real SONY MAC address)
- Bluetooth : Ok (real SONY MAC address)
- WiFi Hotspot : Ok (2.4GHz only)
- RIL - Phone - Data : Ok
- GPS : Ok
- Camera : Ok
- Camcorder : Ok
- MicroSD : Ok
- Accelerometer : Ok
- Compass : Ok
- Gyroscope : Ok
- AOSP sensors : Ok
- FM Radio : Work In Progress
- Microphone : Ok
- Audio & external audio : Ok
- Bluetooth audio : Ok
- NFC : Ok
- Kernel : Ok, Updating frequently
- Graphics : Ok
- 3D Rendering : Ok
- Clock : Ok
- Offline Charging : Ok
- SEPolicies : Work In Progress
CaHbKaUp said:
FEATURES AND ISSUES
Code:
- Boot : Ok
- GApps : OpenGApps Nano Ok
- FOTA Recovery : Ok (see below)
- WiFi : Ok (real SONY MAC address)
- Bluetooth : Ok (real SONY MAC address)
- WiFi Hotspot : Ok (2.4GHz only)
- RIL - Phone - Data : Ok
- GPS : Ok
- Camera : Ok
- Camcorder : Ok
- MicroSD : Ok
- Accelerometer : Ok
- Compass : Ok
- Gyroscope : Ok
- AOSP sensors : Ok
- FM Radio : Work In Progress
- Microphone : Ok
- Audio & external audio : Ok
- Bluetooth audio : Ok
- NFC : Ok
- Kernel : Ok, Updating frequently
- Graphics : Ok
- 3D Rendering : Ok
- Clock : Ok
- Offline Charging : Ok
- SEPolicies : Work In Progress
Click to expand...
Click to collapse
Does this mean that GPS is working again on pollux_windy devices? If I find the time I definitely will give this a try over the weekend!
lm089 said:
Does this mean that GPS is working again on pollux_windy devices? If I find the time I definately will give this a try over the weekend!
Click to expand...
Click to collapse
Probably yes, while sepolicy on current development version in permissive mode, but it still WIP for previous versions
Which repos did you use to build 0425? Is the nougat kernel you linked the one that works for pie? This roomservice cooks a pollux build that is stuck on the boot animation.
CaHbKaUp said:
Probably yes, while sepolicy on current development version in permissive mode, but it still WIP for previous versions
Click to expand...
Click to collapse
Hi, just a quick first report:
did a complete wipe then installed this ROM >> reboot into recovery >> flash openGapps Pico build 20190426 + Magisk 18.1 >> reboot to system
did basic setup (Google + Lineage) without restoring anything from cloud etc.
installed some GPS testing app >> did a complete A-GPS delete / refresh cycle
Got a GPS fix after approx 6 minutes (yippiiiieee!!! Finally)
Switch off GPS, shut down GPS Test, then repeated GPS Test >> fix 10 seconds!!
So this is great.
Then tested a few other things. Here's what works for me and what doesn't:
Code:
- Boot : Ok
- GApps : OpenGApps Nano Ok
- FOTA Recovery : Ok
- WiFi : Ok
- Bluetooth : Ok
- WiFi Hotspot : n/a
- RIL - Phone - Data : n/a
- GPS : Ok (Yessss!)
- Camera : NO (see below)
- Camcorder : didn't test
- MicroSD : Ok
- Accelerometer : NO
- Compass : NO
- Gyroscope : NO
- AOSP sensors : ??
- FM Radio : NO (I'm aware you wrote that)
- Microphone : didn't test
- Audio & external audio : Ok
- Bluetooth audio : didn't test
- NFC : didn't test
- Kernel : ??
- Graphics : Ok
- 3D Rendering : didn't test
- Clock : Ok
- Offline Charging : Ok
- SEPolicies : didn't test
What else is not working is display rotation: it is fixed to landscape mode (with one exception, see below). This probably is due to the fact that most sensors apparently don't work here: no compass, no gyroskope etc. I'm using "Smart Tools" app. All tools that are using the device's sensors are dead. Tried to calibrate, but no result.
Camera isn't working either: it immediately crashes as soon as I click the shutter (no matter whether I use front or back camera). Tried to get a logcat (using catlog app), hope it contains what's needed to look into this.
Regarding the camera there are two more issues:
1 - the camera shutter button is halfway hidden behind the navigation bar (see screenshot) (see update below)
2 - if I start the camera the tablet's display changes to portrait mode, and then it stays there until I shut down the tablet
-----
sorry for not mentioning earlier that apart from those issues this ROM makes a very good impression: very fast and responsive. Thanks a lot for taking care of this!!!
Will return now to LOS 15.1 as I need a fully working device this afternoon. Let me know if you need more info, probably can do some more testnig tomorrow
Update (after being back at 15.1 official):
All sensors working again, incl. display rotation, compass, water level etc. ;
Also Camera is working fine again, but I just realized that also in this version the shutter button is halfway hidden, as can be seen in the screenshot. So this apparently is a generic (minor) flaw...
Fence, it's good news and I was about to sell my tablet Z. I'll try to see what's going on with android 9. Thanks devep.
confirmed as well
lm089 said:
Hi, just a quick first report:
did a complete wipe then installed this ROM >> reboot into recovery >> flash openGapps Pico build 20190426 + Magisk 18.1 >> reboot to system
did basic setup (Google + Lineage) without restoring anything from cloud etc.
installed some GPS testing app >> did a complete A-GPS delete / refresh cycle
Got a GPS fix after approx 6 minutes (yippiiiieee!!! Finally)
Switch off GPS, shut down GPS Test, then repeated GPS Test >> fix 10 seconds!!
So this is great.
Then tested a few other things. Here's what works for me and what doesn't:
Code:
- Boot : Ok
- GApps : OpenGApps Nano Ok
- FOTA Recovery : Ok
- WiFi : Ok
- Bluetooth : Ok
- WiFi Hotspot : n/a
- RIL - Phone - Data : n/a
- GPS : Ok (Yessss!)
- Camera : NO (see below)
- Camcorder : didn't test
- MicroSD : Ok
- Accelerometer : NO
- Compass : NO
- Gyroscope : NO
- AOSP sensors : ??
- FM Radio : NO (I'm aware you wrote that)
- Microphone : didn't test
- Audio & external audio : Ok
- Bluetooth audio : didn't test
- NFC : didn't test
- Kernel : ??
- Graphics : Ok
- 3D Rendering : didn't test
- Clock : Ok
- Offline Charging : Ok
- SEPolicies : didn't test
What else is not working is display rotation: it is fixed to landscape mode (with one exception, see below). This probably is due to the fact that most sensors apparently don't work here: no compass, no gyroskope etc. I'm using "Smart Tools" app. All tools that are using the device's sensors are dead. Tried to calibrate, but no result.
Camera isn't working either: it immediately crashes as soon as I click the shutter (no matter whether I use front or back camera). Tried to get a logcat (using catlog app), hope it contains what's needed to look into this.
Regarding the camera there are two more issues:
1 - the camera shutter button is halfway hidden behind the navigation bar (see screenshot) (see update below)
2 - if I start the camera the tablet's display changes to portrait mode, and then it stays there until I shut down the tablet
-----
sorry for not mentioning earlier that apart from those issues this ROM makes a very good impression: very fast and responsive. Thanks a lot for taking care of this!!!
Will return now to LOS 15.1 as I need a fully working device this afternoon. Let me know if you need more info, probably can do some more testnig tomorrow
Update (after being back at 15.1 official):
All sensors working again, incl. display rotation, compass, water level etc. ;
Also Camera is working fine again, but I just realized that also in this version the shutter button is halfway hidden, as can be seen in the screenshot. So this apparently is a generic (minor) flaw...
Click to expand...
Click to collapse
I can confirm auto ration does not work. Which isnt really bad big deal right now . But i'm sure ill get annoyed at some point
Hello, first of all I feel bad for not being able to try and give my feedback of this ROM right now (I use the tablet for college and right now it is not convenient to "experiment" with it) however I would sincerely congratulate the developer of it, I never thought to see another ROM on this Tablet that I liked since I bought. Sorry for my bad English, I will be closely following the development of the ROM and when possible I'll try it
I also can confirm auto rotate doesn't work
[OT?] Need help installing this ROM.
I'm currently using Official Lineage OS 15.1 build on pollux, and want to try this ROM.
But I just noticed that I dont have TWRP installed (its missing) on my tablet. I had TWRP installed in FOTA partition, but now its missing. Using Reboot to recovery option gives black screen after sony logo. Same results when manually rebooted after power off using vol buttons.
I don't know what happened, I've been using Lineage builds both unofficial and official from years on this tablet. And twrp in fota partition too, but never encountered this issue.
Don't have access to pc rn to try fastboot boot recovery.img, is there anything else i can try?
Tried Xperia Recovery app from play store which can flash recovery to fota using root but no help (used to work earlier) and dd if=/temp/rec.img of=/dev/block/...... In terminal, but didn't worked
Azazel Azay said:
I'm currently using Official Lineage OS 15.1 build on pollux, and want to try this ROM.
But I just noticed that I dont have TWRP installed (its missing) on my tablet. I had TWRP installed in FOTA partition, but now its missing. Using Reboot to recovery option gives black screen after sony logo. Same results when manually rebooted after power off using vol buttons.
I don't know what happened, I've been using Lineage builds both unofficial and official from years on this tablet. And twrp in fota partition too, but never encountered this issue.
Don't have access to pc rn to try fastboot boot recovery.img, is there anything else i can try?
Tried Xperia Recovery app from play store which can flash recovery to fota using root but no help (used to work earlier) and dd if=/temp/rec.img of=/dev/block/...... In terminal, but didn't worked
Click to expand...
Click to collapse
Are you by any chance using Magisk, and have updated to v19.x lately? Then you ran into a known problem new Magisk versions are having with Xperias' recovery option (see posts in various Xperia and Magisk forums). You have several options:
1) downgrade Magisk to 18.1
2) use a different SuperSu tool like the one from Lineage
Of course you need to reinstall Twrp first
Azazel Azay said:
I'm currently using Official Lineage OS 15.1 build on pollux, and want to try this ROM.
But I just noticed that I dont have TWRP installed (its missing) on my tablet. I had TWRP installed in FOTA partition, but now its missing. Using Reboot to recovery option gives black screen after sony logo. Same results when manually rebooted after power off using vol buttons.
I don't know what happened, I've been using Lineage builds both unofficial and official from years on this tablet. And twrp in fota partition too, but never encountered this issue.
Don't have access to pc rn to try fastboot boot recovery.img, is there anything else i can try?
Tried Xperia Recovery app from play store which can flash recovery to fota using root but no help (used to work earlier) and dd if=/temp/rec.img of=/dev/block/...... In terminal, but didn't worked
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=79514197&postcount=237
New update build 2019/05/22
Changes:
May 2019 Android security patch
Magisk 19.x fix
thank u for this!!
playing clash royale perfectly!
Was the rotate issue fixed?
fireflygwyn said:
Was the rotate issue fixed?
Click to expand...
Click to collapse
not yet, but i install nova launcher to use portrait mode, dont feel the diference
fireflygwyn said:
Was the rotate issue fixed?
Click to expand...
Click to collapse
I've read reports, that this issue can be fixed with this app.
Rootk1t said:
I've read reports, that this issue can be fixed with this app.
Click to expand...
Click to collapse
IF this is app fixable I have Nova launcher and ultimate rotation control. They work great together.
I do have the same problem it is due the use of majestic, you can flash recovery without pc