[ROM][5.1.1][T710][UNOFFICIAL] CyanogenMod 12.1 for Tab S2 8.0 [BETA] - Galaxy Tab S2 Android Development

{
"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 ROM is BETA at the moment​
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community
First I would like to thank the following developers :
@moonbutt74
@yeshwanthvshenoy
@gladiac
@RaymanFX
@sub77
@T_I
@hennymcc
@Sarum4n - for Donating XDA add free
Each of them helped me with this project so a big thanks goes to them!
Before you start
THIS ROM IS ONLY FOR THE SM-T710
A T810 port of this rom by @T_I is available here
Code:
*
* Your warranty will be voided !
*
* 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.
*
About the ROM
Current state of ROM : BETA
What is Fixed
Camera
Sound
Wifi
Storage
Headphones
External sdcard
Screen Rotation
Bluetooth shows note 4 instead of tab s2
Resolution
What is not working
Important
MTP
Minor
Microphone
Minor graphical glitches
Lag after trying to send a text via sms app (Just don't do it and disable the app. It will try to reach RIL even tough its wifi only)
Instructions
How to install CM12.1
If you don't have TWRP yet, get it from here : TWRP by ashyx
Download the ROM and the Gapps that are located below to your device
Reboot into TWRP by holding VOL UP + POWER + HOME on boot
In case things go wrong make a backup
After the backup has completed return to home and select Wipe and then Advanced Wipe
Now ONLY tick Dalvik Cache, System, Data and Cache
After ticking those, Swipe below to wipe
Once the wipe has completed return to home and select the ROM
After you selected the ROM swipe below to install it
After the ROM has installed flash the Gapps
When all of this is done, reboot into system, wait, and enjoy CM12.1
How to ROOT
In CM 12.1, enable the developer options
Select Root access
Select Apps Only
Done
Questions and bug reporting
The following questions will be ignored
Inappropriate questions
Requests for other devices
Forced orders, EX. : "PLS FIX!!!!!!"
ETA's
Often repeated questions usually by the same user
Requests that are out of CM's framework (Ex. Adding Samsung Apps)
How to report a bug/issue
Explain exactly what happens
Mention a log if you can (Please use hastebin or any other paste site to keep the thread clean)
If you can't mention a log, explain as precise as possible when, why and where it occurs!
Changelog
Code:
18/4/2016 - Fixed Camera (Yes I'm still alive)
**********
27/1/2016 - Fixed Headphones not working
**********
30/12/2015 - Fixed External sdcard
**********
28/12/2015 - Fixed Sound
- Removed Calling option from lockscreen
- Added missing OMX formats
- ROM is now BETA
**********
21/12/2015 - Fixed Storage problems
**********
19/12/2015 - ROM is now ALPHA
- Fixed Wifi
**********
15/12/2015 - Fixed Rotation/Orientation
- Lowered to 320 DPI
- Updated Screenshots
**********
12/12/2015 - Fixed Bluetooth showing note 4
- Fixed bad resolution
- Updated Screenshots
**********
11/12/2015 - CM12.1 Booted for the first time
**********
Downloads
Latest CM 12.1 build : Android File Host
All CM 12.1 releases can be found here : Android File Host
Recommended GAPPS Open Gapps
Source
Special Thanks to @RaymanFX for releasing his Exynos 5433 source, without him this ROM would most likely not be possible!
All my sources can be found here : https://github.com/Galaxy-Tab-S2
Screenshots
XDA:DevDB Information
CyanogenMod 12.1 for Samsung Galaxy Tab S2 8.0 T710, ROM for the Samsung Galaxy Tab S2
Contributors
CTXz, Sub77, Moonbutt74, RaymanFX, Hennymcc
Source Code: https://github.com/Galaxy-Tab-S2
ROM OS Version: 5.1.x Lollipop
Based On: CyanogenMod
Version Information
Status: Beta
Created 2015-12-11
Last Updated 2016-04-18

Q&A
Q : Why does it say Galaxy Tab S2 9.7 on Android File Host if this is for the 8.0 version ?
A : Android File Host doesn't feature the 8.0 version in their devices. Because of that, all is located under a folder called 8.0
Q : Why is everything so small?
A : The DPI rate is 320 which is the same as on the Stock rom. However, Samsung has made everything bigger. Since this is personal preference, you may always higher your DPI to make things bigger or lower your DPI to make things smaller under Settings > Display > DPI
Q : Will you ever work on CM13?
A : Yes, once we feel like CM12 is good enough, we will move to CM13

Reserved 2

New build 12/12/2015
- Fixed Bluetooth bug showing Galaxy note 4 instead of tab s2
- Fixed bad resolution
- Updated Screenshots

Great work!

Can't wait to use this once it reaches a point where it's functional for everyday use! Excellent work so far!

Good job man!!! Will test this as soon as the WiFi works
Sent from my SM-T710 using Tapatalk

good news for all T810 users! @T_I is working on a port of my ROM. It came to the CM setup wizzard however had some problems with the touchscreen. Should hopefully be a easy fix.

So the sensor module just isn't loading.
Code:
I/ ( 3857): System server: starting sensor init.
D/SensorService( 3857): nuSensorService starting...
E/HAL ( 3857): load: module=/system/lib/hw/sensors.exynos5.so
E/SensorService( 3857): couldn't load sensors module (Invalid argument)
I/ ( 3857): System server: sensor init done.
Tried to use the note 4 ones. They did load up successfully but use different drivers.
Ex the gyroscope uses ICM20610 where mine uses LSM6DS3. I really only came this far. My nightmare would be to make my own sensor libs. That would mean that I would have to learn lot's of lot's of coding!

CTXz said:
So the sensor module just isn't loading.
Code:
I/ ( 3857): System server: starting sensor init.
D/SensorService( 3857): nuSensorService starting...
E/HAL ( 3857): load: module=/system/lib/hw/sensors.exynos5.so
E/SensorService( 3857): couldn't load sensors module (Invalid argument)
I/ ( 3857): System server: sensor init done.
Tried to use the note 4 ones. They did load up successfully but use different drivers.
Ex the gyroscope uses ICM20610 where mine uses LSM6DS3. I really only came this far. My nightmare would be to make my own sensor libs. That would mean that I would have to learn lot's of lot's of coding!
Click to expand...
Click to collapse
I really dont know but doea this help:
https://github.com/STMemsLinuxDrivers/lsm6ds3-input
Sent from my SM-G928I using Tapatalk

Beukhof1 said:
I really dont know but doea this help:
https://github.com/STMemsLinuxDrivers/lsm6ds3-input
Sent from my SM-G928I using Tapatalk
Click to expand...
Click to collapse
Sadly those are for the kernel.
However,
I found this open source sensor for the s3 I9300 that uses a , what I believe, older version of the gyro found in our device. I will see what I can decompile/reverse out of the current module for the tab and will compare it with the open source ones for the I9300. This will be hard and I would be very thankfull if you could redict any expierienced dev you know, here

Suprise!
Turns out I was just missing a shared libary. That caused the module not to load. Sooo.... all that s3 sensor work for nothing
Hey.... atleast I learned something.
Also, build will be released in about 1-2h

CTXz said:
Suprise!
Turns out I was just missing a shared libary. That caused the module not to load. Sooo.... all that s3 sensor work for nothing
Hey.... atleast I learned something.
Also, build will be released in about 1-2h
Click to expand...
Click to collapse
Nice! Good job mate!
Did you have time to look at wifi yet? I would love to try it if that works!
Sent from my SM-T710 using Tapatalk

Beukhof1 said:
Nice! Good job mate!
Did you have time to look at wifi yet? I would love to try it if that works!
Sent from my SM-T710 using Tapatalk
Click to expand...
Click to collapse
Not yet, but I will take a look at it soon!

New build is out !
**********
15/12/2015 - Fixed Rotation/Orientation
- Lowered to 320 DPI
- Updated Screenshots
**********
Links have been updated!

Ok so to wifi :
I know most of you want as number 1. priority a working WIFI connection, but this doesn't seem to be that easy to fix, at least not for my empty brain. As you've probably already noticed, my debugging skills are still quite bad (Yes I'm still learning... Yes I'm not perfect.... well maybe yes... ok no just kidding). The current issue i'm facing has probably to do something with the api drivers and wpa_supplicant. I've noticed that the KMSG doesn't even show a tiny trace of the cfg80211 driver and the nl80211 driver. If any developer out there knows what to do with the following log output when trying to access the wifi HAL / Enabling WIFI please tell me.
Code:
D/SoftapController( 3507): Softap fwReload - Ok
W/CommandListener( 3507): Failed to retrieve HW addr for wlan0 (No such device)
D/CommandListener( 3507): Setting iface cfg
E/WifiStateMachine( 3901): Unable to change interface settings: java.lang.IllegalStateException: command '90 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 90 Failed to set address (No such device)'
E/WifiMonitor( 3901): killSupplicant p2ptrue init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown
I/wpa_supplicant( 7883): Successfully initialized wpa_supplicant
I/wpa_supplicant( 7883): rfkill: Cannot open RFKILL control device
E/wpa_supplicant( 7883): Could not read interface wlan0 flags: No such device
I/wpa_supplicant( 7883): nl80211: Driver does not support authentication/association or connect commands
E/wpa_supplicant( 7883): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 7883): wlan0: Failed to initialize driver interface
E/WifiStateMachine( 3901): Failed to start supplicant!
D/WifiService( 3901): setWifiEnabled: false pid=5956, uid=1000
E/WifiService( 3901): Invoking mWifiStateMachine.setWifiEnabled
D/SoftapController( 3507): Softap fwReload - Ok
W/CommandListener( 3507): Failed to retrieve HW addr for wlan0 (No such device)
D/CommandListener( 3507): Setting iface cfg
E/WifiStateMachine( 3901): Unable to change interface settings: java.lang.IllegalStateException: command '93 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 93 Failed to set address (No such device)'
E/WifiMonitor( 3901): killSupplicant p2ptrue init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown
I/wpa_supplicant( 7915): Successfully initialized wpa_supplicant
I/wpa_supplicant( 7915): rfkill: Cannot open RFKILL control device
E/wpa_supplicant( 7915): Could not read interface wlan0 flags: No such device
I/wpa_supplicant( 7915): nl80211: Driver does not support authentication/association or connect commands
E/wpa_supplicant( 7915): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 7915): wlan0: Failed to initialize driver interface
E/WifiStateMachine( 3901): Failed to start supplicant!
D/WifiService( 3901): setWifiEnabled: true pid=5956, uid=1000
E/WifiService( 3901): Invoking mWifiStateMachine.setWifiEnabled
D/WifiController( 3901): WifiController msg { when=0 what=155656 target=com.android.internal.util.StateMachine$SmHandler } deferred for 313ms
D/WifiService( 3901): setWifiEnabled: false pid=5956, uid=1000
E/WifiService( 3901): Invoking mWifiStateMachine.setWifiEnabled
D/WifiController( 3901): DEFERRED_TOGGLE handled
D/WifiService( 3901): setWifiEnabled: true pid=5956, uid=1000
E/WifiService( 3901): Invoking mWifiStateMachine.setWifiEnabled
D/SoftapController( 3507): Softap fwReload - Ok

And then.... all of a sudden a wild google appeared!
Big thanks to @gladiac
Build coming soon!

CTXz said:
And then.... all of a sudden a wild google appeared!
Big thanks to @gladiac
Build coming soon!
Click to expand...
Click to collapse
Thanks a lot for the effort you're putting into this.

New build 19/12/2015
This build is no longer PRE-ALPHA but ALPHA
**********
19/12/2015 - ROM is now ALPHA
- Fixed Wifi
**********

CTXz said:
And then.... all of a sudden a wild google appeared!
Big thanks to @gladiac
Build coming soon!
Click to expand...
Click to collapse
Ok, this convinced me, sdcard 4th, wifi 3rd. Build on the T810 stack is running.

Related

[DEV-only][WIP] ALSA BCM21553 Audio libs built from source - BroadcomCM

I've created this thread to join developers into the final audio fix for android 2.3.7. Although the prupose of this thread is to fix Audio on Android 4.0.4 we first need audio drivers source.
On all our based Android 2.3.7 ROMs we fixed audio using some AOSP Alcatel .so files (to remove Samsung lib dependency) and some Samsung .so libraries too, this is the whole list:
# Samsung audio libs
acoustics.default.so
alsa.default.so
libaudiopolicy.so
# Alcatel audio libs
libaudio.so
libaudioflinger.so
libaudioeffect_jni.so
libmediaplayerservice.so
Click to expand...
Click to collapse
Our device uses ALSA audio system, which is also used on stock ROM. This is related to software more than hardware, although we are not planning at the momnt to "change" this audio way. To activate ALSA audio some changes need to be done on kernel, that samsung provide to us on their kernel sources. Mostly we need to enable ALSA on device .config file:
Code:
CONFIG_BRCM_SOUND_ALSA=y
CONFIG_BRCM_SOUND_ATHENA_ALSA=y
That's not an issue as prebuilt alsa libs work, so new libs should work too. Ramdisk needs some edit too, as ALSA audio system is stored on dev/snd, and this is well defined too on our ramdisk, ueventd.rc
Code:
/dev/snd/* 0660 system audio
We realised after that that actually CyanogenMod 7.2 Sources include ALSA lib sources, what we didn't know if those sources could work with our devices. This sources build the following libs, as releated to its Android.mk files:
We can found inside hardware/sound_alsa the following sources to build
libaudio
libaudioflinguer
hw/alsa.default
hw/acoustics.default
On external/alsa-lib we can found the sources of anoher lib
libasound
And apart from that, some other audio libs such as libaudiopolicy are built inside framework/base repository, but they doesn't make any conflict. Other libs are included on Android source files.
To enable the build of those libs, using ALSA software instead af "Android default (not sure about that)". I've enabled on Boardconfig.mk the following configs:
Code:
# Audio
BOARD_USES_GENERIC_AUDIO := false
BOARD_USES_ALSA_AUDIO := true
BOARD_PREBUILT_LIBAUDIO := false # even not writted.
BUILD_WITH_ALSA_UTILS := true
This configs enable the building of those libs on their Android.mk files.
Also, I've added on device_cooperve.mk the following lines to build those hw modules releated to audio:
Code:
# Audio
PRODUCT_PACKAGES += \
alsa.default \
acoustics.default
After the build finished, and fixed some errors, AUDIO WAS WORKING, but not as expected. There were issues on Audio Routing:
Headphones are detected through system, but audio is not reproduced on headphones (speakers does)
When you make a call, sometimes you can't and phone freezes, or when you hangout the call, phone freezes.
Everything else apart from that seems to be working, even microphone, although this bugs are pretty weird, I took a look to logcat.
Code:
[COLOR="Gray"]D/AndroidRuntime( 1419): CheckJNI is OFF
I/ ( 1420): ServiceManager: 0xad50[/COLOR]
[COLOR="Red"]E/ALSALib ( 1420): external/alsa-lib/src/control/control.c:882:(snd_ctl_open_noupdate) Invalid CTL AndroidOut[/COLOR]
W/AudioHardwareALSA( 1420): Unable to attach mixer to device AndroidOut: No such file or directory
[COLOR="Red"]E/ALSALib ( 1420): external/alsa-lib/src/control/control.c:882:(snd_ctl_open_noupdate) Invalid CTL AndroidIn[/COLOR]
W/AudioHardwareALSA( 1420): Unable to attach mixer to device AndroidIn: No such file or directory
D/AudioHardwareALSA( 1420): openOutputStream called for devices: 0x00000002
D/ALSAModule( 1420): open called for devices 00000002 in mode 0...
I/ALSAModule( 1420): Initialized ALSA PLAYBACK device AndroidPlayback_Speaker_normal
I/AudioHardwareALSA( 1420): buffer size (bytes) to AF = 16384
D/AudioFlinger( 1420): setParameters(): io 1, keyvalue routing=2, tid 1593, calling tid 1420
I/AudioFlinger( 1420): AudioFlinger's thread 0x1d978 ready to run
D/ALSAModule( 1420): route called for devices 00000002 in mode 0...
I managed to fix those errors (E/) by moddifying asound.conf, found on system/etc, adding this lines on the top and deleting old ones:
Code:
ctl.AndroidOut {
type hw
card 0 # Can replace with drivers name from /proc/asound/cards
}
ctl.AndroidIn {
type hw
card 0
}
Now logcat shows this at the moment
Code:
[COLOR="Gray"]D/AndroidRuntime( 1425): CheckJNI is OFF
I/ ( 1426): ServiceManager: 0xad50[/COLOR]
D/AudioHardwareALSA( 1426): openOutputStream called for devices: 0x00000002
D/ALSAModule( 1426): open called for devices 00000002 in mode 0...
I/ALSAModule( 1426): Initialized ALSA PLAYBACK device AndroidPlayback_Speaker_normal
I/AudioHardwareALSA( 1426): buffer size (bytes) to AF = 16384
D/AudioFlinger( 1426): setParameters(): io 1, keyvalue routing=2, tid 1604, calling tid 1426
I/AudioFlinger( 1426): AudioFlinger's thread 0x1d960 ready to run
D/ALSAModule( 1426): route called for devices 00000002 in mode 0...
Actually that's the actual logcat, using headphones, and sound goes through speakers:
Code:
D/dalvikvm( 1926): GC_EXTERNAL_ALLOC freed 324K, 49% free 3317K/6471K, external 571K/579K, paused 58ms
V/HeadsetObserver( 1607): Headset UEVENT: {SUBSYSTEM=switch, SWITCH_STATE=2, DEVPATH=/devices/virtual/switch/h2w, SEQNUM=1335, ACTION=change, SWITCH_NAME=h2w}
W/Vold ( 1415): Ignoring unknown switch 'h2w'
V/HeadsetObserver( 1607): Intent.ACTION_HEADSET_PLUG: state: 1 name: h2w mic: 0
I/HeadsetService( 1907): Headset plugged: true
I/Effect-DRC( 2115): Compression factor set to: 1.000000
I/Effect-BassBoost( 2115): New strength: 0
D/SurfaceFlinger( 1607): Layer[1c62e0] [2] non-RGB565 reloads
I/Effect-Equalizer( 2115): Setting band 2 to 0
I/Effect-Equalizer( 2115): Setting band 2 to 1
I/Effect-Equalizer( 2115): Setting band 2 to 2
I/Effect-Equalizer( 2115): Setting band 2 to 3
I/Effect-Equalizer( 2115): Setting band 2 to 4
I/Effect-Equalizer( 2115): Setting loudness correction reference to 100.000000 dB
D/AudioFlinger( 2115): setParameters(): io 1, keyvalue routing=8, tid 2117, calling tid 2115
D/ALSAModule( 2115): route called for devices 00000008 in mode 0...
D/ALSAModule( 2115): open called for devices 00000008 in mode 0...
I/ALSAModule( 2115): Initialized ALSA PLAYBACK device AndroidPlayback
D/dalvikvm( 1926): GC_EXTERNAL_ALLOC freed 323K, 49% free 3327K/6471K, external 571K/579K, paused 44ms
We must take a look if that is kernel relevant or not, as we really need this libs to work, to then start working on CyanogenMod 9.1 / Android 4.0.4 audio. Any suggestions are welcomed, although if they are from newbie or developer, don't want this thread to be spammed as others
Why this is helpfull ?
Currently we based it upon cm7.2 GB
this is because our device uses to run GB as stock.
When we figure the sources out and figure out what is part 1 or such we can adapt and try to port to CM9 so in that we can have new libs aswell.
(W.I.P Post;P )
to me
Sorry for intrusion Biel and spacecaker But can i have the output of cat /proc/asound/cards ???
4dead said:
Sorry for intrusion Biel and spacecaker But can i have the output of cat /proc/asound/cards ???
Click to expand...
Click to collapse
Sure, here it is:
Code:
# cat /proc/asound/cards
0 [ALSA ]: Broadcom - Broadcom ALSA
Broadcom ALSA PCM 0
I can help
bieltv.3 said:
Sure, here it is:
Code:
# cat /proc/asound/cards
0 [ALSA ]: Broadcom - Broadcom ALSA
Broadcom ALSA PCM 0
Click to expand...
Click to collapse
give me any link - any guide i got linux want to help i will do my best
at myaser
for this
there are no guides.
Sent from my S500 using xda app-developers app
SpaceCaker said:
at myaser
for this
there are no guides.
Sent from my S500 using xda app-developers app
Click to expand...
Click to collapse
I will try using my mind
Sorry for non-useful comments
u need tiny alsa not alsa sources to work with bcm21553 modules , Android 4.0.4 introduced tiny alsa replacing alsa
percy_g2 said:
u need tiny alsa not alsa sources to work with bcm21553 modules , Android 4.0.4 introduced tiny alsa replacing alsa
Click to expand...
Click to collapse
We are fixing on 2.3.7 at the moment. Tinyalsa gives support for msm8960 chips as I can see on their sources, so we should start from 2.3.7.
Enviado desde mi C5303 mediante Tapatalk
The sound will work after 3 months?
The sound will work after 3 months?
bieltv.3 said:
We are fixing on 2.3.7 at the moment. Tinyalsa gives support for msm8960 chips as I can see on their sources, so we should start from 2.3.7.
Enviado desde mi C5303 mediante Tapatalk
Click to expand...
Click to collapse
What about CyanMobile eXperience Biel ??
Are you will starting the build ??
@bieltv.3
Look At ur inbox
jeko99 said:
The sound will work after 3 months?
Click to expand...
Click to collapse
Maybe... Be patient bro, it's so hard to fixing audio issue
jeko99 said:
The sound will work after 3 months?
Click to expand...
Click to collapse
No ETA's, please.
Can't you see that this thread is a Dev thread? No discussion here, please.
Enviado de meu XT1032 usando Tapatalk
I think you should really take a look on the stock asound.conf
4dead said:
I think you should really take a look on the stock asound.conf
Click to expand...
Click to collapse
We are using stock asound.conf
Enviado desde mi C5303 mediante Tapatalk
Are the drivers initialized in the kernel?
check here ---> http://seasonofcode.com/posts/using-alsa-audio-drivers-in-android.html
and here ----> http://code.paulk.fr/article3/tinyalsa-audio
faZevoLv said:
Are the drivers initialized in the kernel?
check here ---> http://seasonofcode.com/posts/using-alsa-audio-drivers-in-android.html
and here ----> http://code.paulk.fr/article3/tinyalsa-audio
Click to expand...
Click to collapse
Biel already said in the op that he added /dev/snd in the Ramdisk and i dont think our device use tinyalsa because With Alsa Drivers biel got sound working.
No Way To Use Audio files from other devices
Not booting at all
BroadcomCM Team \o/
Good luck It seems to be hard

[ROM] [UNOFFICIAL] [4.4.4] [RC] SlimKat [tomato] [2015-01-20]

{
"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"
}
SlimRoms 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 you can stop by the public Gerrit to submit patches of any type.
SlimKat is the project name for SlimRoms based on Android 4.4 and offers the following original features:
​
The Real Dark Slim
Full system-wide dark interfaces. - If you like it smooth and classy.
Custom Shortcuts. Everywhere.
Hardware keys, Navigation Ring, Navigation Bar, Lockscreen, Tiles, Notifications etc. - We've got you covered.
System-Wide Keyboard Controls
Rotation, cursor control, optional emoticions, etc. - You'll be tapping away to your heart's content.
SlimCenter
Downloads, contact information, system app removal. - More fun than you can shake a stick at.
Camera Features
Trueview, Smart Capture. - Capture life moments with ease
.​
Check out the full feature list here​
WHAT IS WORKING?
WiFi
Bluetooth
RIL (single sim support only)
Sensors
GPS
Camera
Leds
Buttons
Audio
Video
Camcorder
WHAT IS NOT WORKING?
Nothing .....!! Or you tell me.....!!!
Installation Instructions
Download the latest build
Wipe data / Factory reset
Wipe cache
Wipe dalvik cache
Flash it using ClockworkMod recovery or TWRP
Flash Gapps
Flash Addons
Reboot
Enjoy
DOWNLOADS
Unofficial Builds
Slim Gapps​
SOURCES:https://github.com/YU-YUREKA
Disclaimer: SlimRoms are not responsible for any damages to your device.
XDA:DevDB Information
Slimkat for Yureka, ROM for the YU Yureka
Contributors
sooorajjj, @sufoalmighty [For mirror links -available in 3rd post] , @Santhosh M and @faux123 [ for awesome kernel patches ] , Official CM team and Slim team
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.1.x
ROM Firmware Required: Yureka
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 1
Stable Release Date: 2015-01-20
Created 2015-01-17
Last Updated 2015-01-20
NOTE: this is not stable for daily use
i do not recommend any one to flash this
this is just initial test build
EDIT : Stable for daily use
Thanks to @Santhosh M @faux123 for kernel commits : this is his kernel thread please support him and thank him here
SCREENSHOTS​
CHANGELOG​*"UNOFFICIAL-BUILD-1"
Initial TRY(to get slimkat - booting )
Fixed battery capacity bug
*"UNOFFICIAL-BUILD-2"
fix up boot.img and permissions
Audio bug is caused bcs of missing hal libs - still no fix........ trying
DT2W patches failed to compile will fix in next build
*"UNOFFICIAL-BUILD-3" -Mirror --Mirror2
fixed audio
fixed video
fixed Camcorder
*"UNOFFICIAL-BUILD-4" -Mirror --Mirror2
Build with custom toolchain linario linaro-4.9-14.06
And lots of kernel patches
Thanks, Flashing!
EDIT: tested, so smooth camera isnt as good as stock, sim 2 doesnt work at all
Great work mate! :good:
1st rom for YU thanks bro.
sufoalmighty said:
Thanks, Flashing!
EDIT: tested, so smooth camera isnt as good as stock, sim 2 doesnt work at all
Click to expand...
Click to collapse
thanks for testing
TheStrix said:
Great work mate! :good:
Click to expand...
Click to collapse
Samuel117 said:
1st rom for YU thanks bro.
Click to expand...
Click to collapse
thanks guys for support
@DooMLoRD @championswimmer
please take a look at these logs
audio hal issue - i think its because the audio effects and much more implementations by cm
http://paste.ubuntu.com/9770340/
http://paste.ubuntu.com/9770344/
http://paste.ubuntu.com/9763980/
Code:
I/MediaFocusControl( 827): AudioFocus requestAudioFocus() from [email protected]
V/Avrcp ( 2319): New genId = 9, clearing = 1
E/EffectProxy( 248): EffectCreate() could not get the sub effects
W/EffectsFactory( 248): EffectCreate() library proxy: could not create fx Qualcomm Bass Boost, error -22
E/AudioEffect( 4710): set(): AudioFlinger could not create effect, status: -22
E/AudioEffects-JNI( 4710): AudioEffect initCheck failed -4
E/AudioEffect-JAVA( 4710): Error code -4 when initializing AudioEffect.
D/AndroidRuntime( 4710): Shutting down VM
E/AndroidRuntime( 4710): FATAL EXCEPTION: main
E/AndroidRuntime( 4710): Process: com.android.gallery3d, PID: 4710
E/AndroidRuntime( 4710): java.lang.RuntimeException: Unable to resume activity {com.android.gallery3d/com.android.gallery3d.app.MovieActivity}: java.lang.IllegalArgumentException: Effect type: 0634f220-ddd4-11db-a0fc-0002a5d5c51b not supported.
E/AndroidRuntime( 4710): at android.app.ActivityThread.performResumeActivity(ActivityThread.java:2777)
E/AndroidRuntime( 4710): at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:2806)
E/AndroidRuntime( 4710): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2241)
E/AndroidRuntime( 4710): at android.app.ActivityThread.access$800(ActivityThread.java:138)
E/AndroidRuntime( 4710): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1199)
E/AndroidRuntime( 4710): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 4710): at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 4710): at android.app.ActivityThread.main(ActivityThread.java:5034)
E/AndroidRuntime( 4710): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime( 4710): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:795)
E/AndroidRuntime( 4710): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:611)
E/AndroidRuntime( 4710): Caused by: java.lang.IllegalArgumentException: Effect type: 0634f220-ddd4-11db-a0fc-0002a5d5c51b not supported.
E/AndroidRuntime( 4710): at android.media.audiofx.AudioEffect.<init>(AudioEffect.java:405)
E/AndroidRuntime( 4710): at android.media.audiofx.BassBoost.<init>(BassBoost.java:101)
E/AndroidRuntime( 4710): at com.android.gallery3d.app.MovieActivity.initEffects(MovieActivity.java:393)
E/AndroidRuntime( 4710): at com.android.gallery3d.app.MovieActivity.onResume(MovieActivity.java:504)
E/AndroidRuntime( 4710): at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1192)
E/AndroidRuntime( 4710): at android.app.Activity.performResume(Activity.java:5320)
E/AndroidRuntime( 4710): at android.app.ActivityThread.performResumeActivity(ActivityThread.java:2767)
E/AndroidRuntime( 4710): ... 10 more
W/ActivityManager( 827): Force finishing activity com.android.gallery3d/.app.MovieActivity
W/ActivityManager( 827): Force finishing activity com.android.gallery3d/.app.GalleryActivity
W/ActivityManager( 827): Activity pause timeout for ActivityRecord{6504dd28 u0 com.android.gallery3d/.app.MovieActivity t8 f}
I/Timeline( 2051): Timeline: Activity_idle id: [email protected] time:835130
I/Timeline( 827): Timeline: Activity_windows_visible id: ActivityRecord{64ffaa90 u0 com.slim.slimlauncher/.Launcher t1} time:835454
I/MSM-irqbalance( 239): Decided to move IRQ130 from CPU5 to CPU6
W/ActivityManager( 827): Activity destroy timeout for ActivityRecord{6534bac0 u0 com.android.gallery3d/.app.GalleryActivity t8 f}
W/ActivityManager( 827): Activity destroy timeout for ActivityRecord{6504dd28 u0 com.android.gallery3d/.app.MovieActivity t8 f}
I/MSM-irqbalance( 239): Decided to move IRQ131 from CPU5 to CPU6
Code:
D/AudioPolicyManagerBase( 248): getOutput() device 2, stream 1, samplingRate 0, format 0, channelMask 3, flags 0
D/AudioPolicyManagerBase( 248): getOutput() returns output 2
D/AudioPolicyManagerBase( 248): getOutput() device 2, stream 1, samplingRate 0, format 0, channelMask 3, flags 0
D/AudioPolicyManagerBase( 248): getOutput() returns output 2
D/AudioPolicyManagerBase( 248): getOutput() device 2, stream 1, samplingRate 48000, format 1, channelMask 3, flags 4
D/AudioPolicyManagerBase( 248): getOutput() returns output 3
W/AudioTrack( 827): AUDIO_OUTPUT_FLAG_FAST denied by client due to mismatching sample rate (48000 vs 44100)
D/AudioFlinger( 248): start(4099), calling pid 827 session 52
D/AudioFlinger( 248): ? => ACTIVE (4099) on thread 0xb87083f0
I/QCOM PowerHAL( 248): Processing audio hint. Metadata: state=1
D/AudioPolicyManagerBase( 248): startOutput() output 3, stream 1, session 52
I/ActivityManager( 827): START u0 {act=android.intent.action.MAIN cmp=com.android.settings/.SubSettings (has extras)} from pid 1892
D/SubSettings( 1892): Launching fragment com.android.settings.deviceinfo.Memory
here is the vendor blobs iam using
https://github.com/YU-YUREKA/proprietary_vendor_yu
any kind of help is appreciated
thank you
sooraj
video cant be played ???
---------- Post added at 11:27 AM ---------- Previous post was at 11:24 AM ----------
can u give me link of stock rom
op updated new build is up for download
-------changes------
*"UNOFFICIAL-BUILD-2"
fix up boot.img and permissions
Audio bug is caused bcs of missing hal libs - still no fix........ trying
DT2W patches failed to compile will fix in next build
Kanth's said:
video cant be played ???
---------- Post added at 11:27 AM ---------- Previous post was at 11:24 AM ----------
can u give me link of stock rom
Click to expand...
Click to collapse
yes video can be played but not in gallery youtube wrks
and sorry i dont have link to stok rom
I would recommend this to move to android development
vishal_android freak said:
I would recommend this to move to android development
Click to expand...
Click to collapse
But why .?...!!! its completely a build from source and i have met all GPL requirements
sooorajjj
Thanks for the update version 3 for stable release
ela1103 said:
sooorajjj
Thanks for the update version 3 for stable release
Click to expand...
Click to collapse
you are welcome
the build will be up soon .....!
uploading on slow connection
sooorajjj
use the mediafire site to upload and download .because the speed is stable
ela1103 said:
sooorajjj
use the mediafire site to upload and download .because the speed is stable
Click to expand...
Click to collapse
sorry i cant use mediafire ........ but maybe someone can mirror the links
BUILD is UP
Is it possible to port it to coolpad f2 or install this one on this smartphone?
albin88 said:
Is it possible to port it to coolpad f2 or install this one on this smartphone?
Click to expand...
Click to collapse
Do not install this build directly to coolpad f2
you need to replace boot.img so yes porting is posssible
Just replace boot.img or something more? Could you port it or this is not so simple?
albin88 said:
Just replace boot.img or something more? Could you port it or this is not so simple?
Click to expand...
Click to collapse
do you have recovery installed to flash this on your coolpad f2 ?
if yes then make a backup and try try flashing the rom as it is if it doesn’t boot dont worry it wont brick your device .....! just go back to recovery and restore your backup ............ try this then report ....

(Closed) [DEV] Samsung Crash (Issue Resolved)

Issue fixed, thanks for all the feedback and report!!!
Hello, as many of you should be aware, the latest Magisk Manager (v4.2.5) crashes only on Samsung devices.
Here are the logs users submitted through Play Store:
Code:
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java)
at android.app.ActivityThread.access$1100(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java)
at android.os.Handler.dispatchMessage(Handler.java)
at android.os.Looper.loop(Looper.java)
at android.app.ActivityThread.main(ActivityThread.java)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java)
Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'android.content.res.Resources android.content.Context.getResources()' on a null object reference
at com.android.internal.policy.multiwindow.Docking.<init>(Docking.java)
at com.android.internal.policy.MultiPhoneWindow.<init>(MultiPhoneWindow.java)
at android.app.Activity.makeNewWindow(Activity.java)
at android.app.Activity.attach(Activity.java)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java)
at android.app.ActivityThread.access$1100(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java)
at android.os.Handler.dispatchMessage(Handler.java)
at android.os.Looper.loop(Looper.java)
at android.app.ActivityThread.main(ActivityThread.java)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java)
As you might realize that according to the backtrace, non of them involves my code (which should start with com.topjohnwu.magisk.*), all of them are errors within internal and Zygote, and Samsung's multiwindow internal calls.
I am not able to identify where it crashes, and which part of the Magisk Manager code is breaking it, so of course without knowing why, I have no idea how to fix it. What makes the situation even worse is that I don't own any of the devices, so I cannot properly debug the issue.
This thread is for seeking help from users with a modern Samsung device, as I need more details.
Please describe when do the crash occurs (does splash screen even shows up?), and please upload a full logcat recording the FC.
Also, I'm looking for Samsung experts who are willing to assist me more in Samsung support for Magisk, as I never bought Sammy so I have little experience, but they seem to cause the most problems.
OT, I'm actually willing to buy a Sammy flagship, but I never buy outdated devices (older than 2 months = outdated IMO lol), so I might get the S8. The next Pixel device is already on my list, guess I'll have to spend all my tutor money on smartphones....
For Pixel support, I'll borrow my friend's Pixel XL for a couple of weeks to try things out, but this might not happen soon since school is quite busy.
@topjohnwu
it crash on opening the app, so unable to opeen the app it self
new root programs are unable to use root as it will crash when trying to enable root in the apps
old programs that use root already keep function
my device is
Samsng Galaxy s6 edge+ SM-G928F
Rom: Audax 13 Android MM 6.0.1
Kernel: Arter97
i don't know how to provide anymore info or how to use this logcat
so if you tell me how i can gather more info i do it with pleasure
From what I can tell it only happens in the versions after 4.1 so the problem is in one of the changes after 4.1. A Wild guesses that may or may not could help is that you could set a flag that tells the Samsung framework that it isn't compatible with multi window.
Gesendet von meinem SM-G925F mit Tapatalk
Logcats requested... If you don't know how, here's some hand-holding:
https://forum.xda-developers.com/showthread.php?t=1726238
Edit: Clarification... Start logcat, open app, watch it crash, stop logcat, upload file.
Didgeridoohan said:
Logcats requested... If you don't know how, here's some hand-holding:
https://forum.xda-developers.com/showthread.php?t=1726238
Edit: Clarification... Start logcat, open app, watch it crash, stop logcat, upload file.
Click to expand...
Click to collapse
I already added my logcat in the old thread, if it helps.
Gesendet von meinem SM-G925F mit Tapatalk
Hello topjohnwu, first of all I would like to thank you for you amazing work, really it made life simplier to many of us, so on behalf of everyone using Magisk I would like to say : THANK YOU.
To answer your question, when launching Magisk Manager, yes there's the splash screen before the crash.
I've attached a logcat to my post which shows "Magisk Manager v4.2.5" behaviour when crashing.
1 - Here are some informations about my device configuration :
- Device: Galaxy S7 Edge G935F (Exynos)
- Rom: Decent Ultralite 5.0 (Android 6.0.1) Based on TouchWiz (Stock Samsung)
- Kernel: SuperStock Kernel by Tkkg1994 (It's the stock Samsung kernel with only one change : SELINUX set to Permissive instead of Enforcing)
- Root: MagiskSU
- Recovery: TWRP v3.0.2.4
2 - Now some infos about my Magisk Config :
- Modules : Emoji One, Unified Hosts Adblock, Xposed Framework (SDK 23).
- Magisk Hide : Only Snapchat (which I don't even use lol)
- Settings Enabled : BusyBox, Magisk Hide, Systemless hosts
3 - Just in case, my modules of Xposed are :
- BootManager
- GalaxyXMod
- Greenify
- Unicon
- XInternalSD
That's it, if you need any more informations, I'm here.
P.S: Myself and another member (@koko115) are experiencing and issue since Magisk v11.1 : a very long reboot time (about 1m42sec), when you'll have time, I would like to talk more about it, thank you.
ken2802 said:
I already added my logcat in the old thread, if it helps.
Gesendet von meinem SM-G925F mit Tapatalk
Click to expand...
Click to collapse
Better to post it or a link here so topjohnwu doesn't have to search too much.
Didgeridoohan said:
Better to post it or a link here so topjohnwu doesn't have to search too much.
Click to expand...
Click to collapse
I made a new one.
https://drive.google.com/file/d/0B94u0_R6vixWbmtuUmFYQzhfWXM/view?usp=drivesdk
here is my logcat s7 edge android 6.0.1
I/Timeline( 5058): Timeline: Activity_launch_request id:com.topjohnwu.magisk time:68806449
D/GameManagerService( 4137): identifyGamePackage. com.topjohnwu.magisk
D/MultiWindowPolicy( 4137): Gamemode - return 0, when calling identifyForegroundApp(com.topjohnwu.magisk)
V/WindowManager( 4137): addAppToken: AppWindowToken{d07f2779e token=Token{81ce1d9 ActivityRecord{6fff420 u0 com.topjohnwu.magisk/.SplashActivity t594}}} to stack=1 task=594 at 0
D/ISSUE_DEBUG( 4137): InputChannelName : 9fd4a02 Starting com.topjohnwu.magisk
D/ActivityManager( 4137): Launching com.topjohnwu.magisk, updated priority
D/GameManagerService( 4137): NotifyRunnable. pkg: com.topjohnwu.magisk, type: 4, isMinimized: false, isTunableApp: false
E/AndroidRuntime(13507): Process: com.topjohnwu.magisk, PID: 13507
E/AndroidRuntime(13507): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.topjohnwu.magisk/com.topjohnwu.magisk.SplashActivity}: java.lang.NullPointerException: Attempt to invoke virtual method 'android.content.res.Resources android.content.Context.getResources()' on a null object reference
W/ResourcesManager(13507): getTopLevelResources: /data/app/com.topjohnwu.magisk-2/base.apk / 1.0 running in com.topjohnwu.magisk rsrc of package com.topjohnwu.magisk
W/ResourcesManager(13507): getTopLevelResources: /data/app/com.topjohnwu.magisk-2/base.apk / 1.0 running in com.topjohnwu.magisk rsrc of package com.topjohnwu.magisk
V/MARsPolicyManager( 4137): updatePackagesScore PackageInfo name -- com.topjohnwu.magisk
W/ActivityManager( 4137): Force finishing activity com.topjohnwu.magisk/.SplashActivity
D/GameManagerService( 4137): identifyGamePackage. com.topjohnwu.magisk
D/GameManagerService( 4137): identifyGamePackage. com.topjohnwu.magisk
V/WindowStateAnimator( 4137): Finishing drawing window Window{9fd4a02 u0 d0 Starting com.topjohnwu.magisk}: mDrawState=DRAW_PENDING
I/WindowManager( 4137): Screenshot max retries 4 of Token{81ce1d9 ActivityRecord{6fff420 u0 com.topjohnwu.magisk/.SplashActivity t594 f}} appWin=Window{9fd4a02 u0 d0 Starting com.topjohnwu.magisk} drawState=3
D/ISSUE_DEBUG( 4137): InputChannelName : 852d82d Application Error: com.topjohnwu.magisk
D/GameManagerService( 4137): identifyGamePackage. com.topjohnwu.magisk
D/GameManagerService( 4137): identifyGamePackage. com.topjohnwu.magisk
D/GameManagerService( 4137): identifyGamePackage. com.topjohnwu.magisk
D/StatusBarManagerService( 4137): manageDisableList userId=0 what=0x0 pkg=Window{852d82d u0 d0 Application Error: com.topjohnwu.magisk}
V/WindowStateAnimator( 4137): Finishing drawing window Window{852d82d u0 d0 Application Error: com.topjohnwu.magisk}: mDrawState=DRAW_PENDING
V/WindowStateAnimator( 4137): Finishing drawing window Window{852d82d u0 d0 Application Error: com.topjohnwu.magisk}: mDrawState=HAS_DRAWN
W/ActivityManager( 4137): Activity pause timeout for ActivityRecord{6fff420 u0 com.topjohnwu.magisk/.SplashActivity t594 f}
D/PackageManager( 4137): getComponentMetadataForIconTray : com.topjohnwu.magisk.SplashActivity does not exist in mServices
D/PackageManager( 4137): getComponentMetadataForIconTray : com.topjohnwu.magisk.SplashActivity does not exist in mProviders
D/PackageManager( 4137): getComponentMetadataForIconTray : com.topjohnwu.magisk.SplashActivity does not exist in mReceivers
I/ApplicationPackageManager( 4751): load=com.topjohnwu.magisk, bg=192-192, dr=192-192
W/ResourcesManager( 4751): getTopLevelResources: /data/app/com.topjohnwu.magisk-2/base.apk / 1.0 running in com.android.systemui rsrc of package com.topjohnwu.magisk
I/ActivityManager( 4137): Process com.topjohnwu.magisk (pid 13507)(adj 9) has died(267,1161)
D/ActivityManager( 4137): isAutoRunBlockedApp:: com.topjohnwu.magisk, Auto Run ON
Click to expand...
Click to collapse
I'm gonna try to find out which build breaks it.
Does v4.1 works?
4.1 is the last that works on my s6 edge g925f
Gesendet von meinem SM-G925F mit Tapatalk
topjohnwu said:
I'm gonna try to find out which build breaks it.
Does v4.1 works?
Click to expand...
Click to collapse
Yes it works.
ok i hope ive done it right, i used catlog and saved log after crash magisk
hope its helpfull
see attachment
Samsung Galaxy S6 (SM-G920F) Alexis Rom 8.1, Arter97: Works
Samsung Galaxy S4 (GT-I9505) AICP 12.1: Works
Samsung Galaxy Tab S (SM-T800) IronRom 3.2: Doesn't Work
Samsung Galaxy S4 Mini (GT-I9195) AICP 12.1: Will check when battery is full again
Will try to get log cats from all and the crash occurs during the splash screen of Magisk Manager
edit: Added the log files dunno if they are properly for you.
@topjohnwu - there was a problem with the refactoring you did before v4.2 with getting the application context out of the activity classes.
I made a quick fix you can find here: https://github.com/maclarsson/MagiskManager/commit/dbb7cb90529d1c9b9c95d1a0a8479c8f25464869
this works now with my S6, but certainly not the best programming style - so I leave it to you to resolve it up to your standards... :angel:
aforss said:
here is my logcat s7 edge android 6.0.1
Click to expand...
Click to collapse
I would like to discuss with you about an issue on the S7 Edge, can you check you PMs ?
I don't want to pollute this thread.
Thank You
apc said:
@topjohnwu - there was a problem with the refactoring you did before v4.2 with getting the application context out of the activity classes.
I made a quick fix you can find here: https://github.com/maclarsson/MagiskManager/commit/dbb7cb90529d1c9b9c95d1a0a8479c8f25464869
this works now with my S6, but certainly not the best programming style - so I leave it to you to resolve it up to your standards... :angel:
Click to expand...
Click to collapse
Thanks, if it's the context issue.....
To all:
Here is a test build in the attachments, please try it out and check if it crashes for you.
(Re-uploaded)
topjohnwu said:
Thanks, if it's the context issue.....
To all:
Here is a test build in the attachments, please try it out and check if it crashes for you.
(Re-uploaded)
Click to expand...
Click to collapse
It works
No FCs
Works perfectly now
Working great (again) on my Galaxy S5 SM-G900F. Earlier (before MagiskSU) I had removed root to pass SN because Magisk had CTS profile mismatch error. But now SN is passed and I couldn't be happier. Thank you so much topjohnwu . Running RR-N rom 11 Feb 17 build with stock RR kernel, twrp 3.0.2-2
lahceneamine said:
P.S: Myself and another member (@koko115) are experiencing and issue since Magisk v11.1 : a very long reboot time (about 1m42sec), when you'll have time, I would like to talk more about it, thank you.
Click to expand...
Click to collapse
@topjohnwu
I've also noticed slow bootup times since Magisk v11.1 on a Samsung Galaxy Note 3 (stock android 5.0). It hangs at the first screen you see when you turn on the phone (before the Samsung logo screen). It eventually boots up and seems to work fine, but I didn't see this delay on earlier versions of Magisk.
Edit:
I'm using MagiskSU with no extra modules.

[ROM][p6800][p6810][i815]LineageOS CM-13.0 [UNOFFICIAL]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is an unofficial 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.

[SM-T800] Zoom, microsoft teams, google earth closing. Cannot share screen.

Dear all,
Does anyone knows the cause or how to debug why apps like zoom or the screen sharing in microsoft teams or google hangouts close when just trying it? Google earth works for some minutes but then needs to be restarted. In microsoft teams and google hangouts I can connect to any meeting, but, if I try to share the tablet screen, the app dies.
Also, sometimes when using these meeting apps the sound just resets to zero and I need to restart the tablet. By using logcat I have seen some PCM errors.
I am actually clueless on what to do. Any help is welcomed.
Details:
Samsung Galaxy Tab S 10.5 SM T800 Chagal Wifi
Lineage Os Unofficial 14.1 Android 7.1.2 build date Fri aug 7 2020
Kernel with deathly 3.4.113
Edit: I am copying a log file that shows several errors after trying to use Google Hangouts Meets. I do not know if maybe the cores are too old and vp8 encoding is not enough
<<< log_count = 7 >>>
[08-16 17:04:45.313 10503:10592 W/libjingle]
harmonyclient.cc: [113:720] [10592] (line 266): participant_log_id: "meet_android_1216387652843708342"
[08-16 17:04:45.527 10503:10562 E/MEET_MEDIACALL]
Failed to dispatch frames started event
java.lang.IllegalStateException: Expected device ID localParticipant for renderer update to correspond to a known meeting device
at hvo.b(PG:11)
at dqv.a(Unknown Source)
at dqp.a(PG:10)
at dzz.run(Unknown Source)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:428)
at lsf.b(PG)
at lrj.run(PG:3)
at lsg.run(PG)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
at jon.run(Unknown Source)
at java.lang.Thread.run(Thread.java:761)
[08-16 17:04:47.655 10503:10503 E/MEET_AUDIO_SWITCHING]
Failed to retrieve proximity distance update
java.lang.IllegalStateException: ProximitySensorDataService could not be initialized
at bkt.a(Unknown Source)
at jpp.a(Unknown Source)
at lpu.a(PG:5)
at lqg.b(PG)
at lrj.run(PG:3)
at lqk.execute(PG)
at lqi.d(PG:1)
at lqj.g(PG)
at lpb.a(PG:14)
at loy.run(PG:4)
at lqk.execute(PG)
at lrh.a(PG:2)
at lqv.a(PG)
at lpb.f(PG:3)
at lqj.<init>(PG:2)
at lrc.a(PG:2)
at lpy.a(PG:7)
at jvx.b(PG:5)
at jxu.b(PG:9)
at jxj.a(PG:23)
at jxf.run(Unknown Source)
at jsl.run(PG:5)
at jsm.d(PG:8)
at jsm.c(PG:2)
at com.google.apps.tiktok.dataservice.SubscriptionFuturesMixinImpl$1.a(PG:2)
at com.google.apps.tiktok.tracing.contrib.androidx.TracedDefaultLifecycleObserver.a(PG:2)
at android.arch.lifecycle.FullLifecycleObserverAdapter.a(PG:7)
at l.a(PG)
at i.b(PG:13)
at i.a(PG:13)
at i.a(PG:12)
at com.google.apps.tiktok.inject.baseclasses.TracedFragmentLifecycle.a(PG:2)
at android.arch.lifecycle.FullLifecycleObserverAdapter.a(PG:7)
at l.a(PG)
at i.b(PG:13)
at i.a(PG:13)
at i.a(PG:12)
at ew.i(PG:5)
at eo.a(PG:74)
at eo.c(PG:7)
at eo.d(PG:10)
at eo.a(PG:17)
at eo.c(PG:4)
at eo.i(PG:1)
at ew.i(PG:7)
at eo.a(PG:74)
at eo.c(PG:7)
at eo.d(PG:10)
at eo.a(PG:17)
at eo.c(PG:4)
at eo.i(PG:1)
at ew.i(PG:7)
at eo.a(PG:74)
at eo.c(PG:7)
at eo.d(PG:10)
at eo.a(PG:17)
at eo.c(PG:4)
at eo.i(PG:1)
at ew.i(PG:7)
at eo.a(PG:74)
at eo.c(PG:7)
at eo.d(PG:10)
at eo.a(PG:17)
at eo.b(PG:58)
at eo.a(PG:9)
at eo.b(PG:88)
at de.b(PG)
at bzt.a(PG:20)
at jae.a(PG)
at jaf.c(PG:11)
at icj.a(PG:2)
at idi.b(PG:10)
at icn.a(PG:5)
at iec.onPostCreate(PG)
at com.google.android.apps.meetings.conference.ConferenceActivity.onPostCreate(PG)
at android.app.Instrumentation.callActivityOnPostCreate(Instrumentation.java:1200)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2666)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2751)
at android.app.ActivityThread.-wrap12(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1496)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:154)
at android.app.ActivityThread.main(ActivityThread.java:6186)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:889)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:779)
[08-16 17:04:52.384 11224:11224 F/DEBUG]
pid: 10503, tid: 11052, name: GLThread.vclib >>> com.google.android.apps.meetings <<<
[08-16 17:04:54.501 2753:11229 W/ActivityManager]
Force finishing activity com.google.android.apps.meetings/.conference.ConferenceActivity
[08-16 17:04:54.632 2753:5917 W/ActivityManager]
Scheduling restart of crashed service com.google.android.apps.meetings/.taskmonitor.TaskMonitorService in 1000ms
[08-16 17:04:56.620 2753:11229 W/ActivityManager]
Ignoring remove of inactive process: ProcessRecord{50253b0 0:com.google.android.apps.meetings/u0a128}

Categories

Resources