Who missed touchwiz style?!
Here is some screenshots of nova launcher with DreamUX leaked icons (S8) and some widgets, all information will be added soon.
(Screenshots from my i9300)
When screen off viper4android is getting killed did any one noticed the issue.
Hi @forkbomb444
the current lineageos for i9300 (all commits until March 18th) has a problem with scanning for new Bluetooth devices.
If I start scanning with no other devices ready for pairing in the neighborhood, then there is no problem, i.e. after some seconds the scanning finishes without results. This can be reiterated without trouble.
If however a pairable device (tried with headset as well as Windows PC) is available, the device is not responding, the little "turning wheel" continues rotating, however after a minute or so, the phone reboots (warm reboot).
This sequence is reproducible. A logcat that starts with a scan of the first type and afterwards with a scan of the second type described, followed by the crash of the system is attached and a last_kmesg.
The lineage build with all commits up to March 8th worked correctly with Bluetooth scans. So it should be a commit in between. Do you have an idea?
Regards,
Klaerchen
I can't confirm it. ViperFX is working without any bugs or crashes.
---------- Post added at 09:34 PM ---------- Previous post was at 09:05 PM ----------
@minealex2244 ViperFX guitaredhero 13.2.2017 zip works just the audio cuts for half sec and continues when turning screen off or switching to background, but viper stays processing same as ARISE works too with selinux permissive (Tested with boeffla kernel).
For viperFX guitaredhero is recommended.
XtremeMusic doesn't process well in LOS in samsung devices causes lag and effect fades out.
I can't confirm it. ViperFX is working without any bugs or crashes.
---------- Post added at 09:34 PM ---------- Previous post was at 09:05 PM ----------
@minealex2244 ViperFX guitaredhero 13.2.2017 zip works just the audio cuts for half sec and continues when turning screen off or switching to background, but viper stays processing same as ARISE works too with selinux permissive (Tested with boeffla kernel).
For viperFX guitaredhero is recommended.
XtremeMusic doesn't process well in LOS in samsung devices causes lag and effect fades out.
(1) Interesting, that pairing works on your devices!4 things:
1. Unconfirmed (tested with 2 devices and I could pair with them and then to transfer files).
2. Are you using Boeffla kernel because I see some "HOTPLUG" strings in your lkmsg? (Do not forget to not report bugs if you are using a custom kernel).
3. Your lkmsg shows us a successful reboot! Everything was shut down safely and voluntary.
4. There isn't any Bluetooth related commit in the period you mentioned.
This thing is unconfirmed.
03-19 09:16:04.192 10393 10436 E [EGL-ERROR]: void __egl_platform_dequeue_buffer(egl_surface*):1618: failed to dequeue buffer from native window (0x4a863808); err = -19, buf = 0x0,max_allowed_dequeued_buffers 3
03-19 09:16:04.193 2015 2400 E BufferQueueProducer: [com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity] dequeueBuffer: BufferQueue has been abandoned
03-19 09:16:04.193 10393 10436 E [EGL-ERROR]: void __egl_platform_dequeue_buffer(egl_surface*):1618: failed to dequeue buffer from native window (0x4a863808); err = -19, buf = 0x0,max_allowed_dequeued_buffers 3
03-19 09:16:04.193 2015 3250 E BufferQueueProducer: [com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity] dequeueBuffer: BufferQueue has been abandoned
03-19 09:16:04.193 10393 10436 E [EGL-ERROR]: void __egl_platform_dequeue_buffer(egl_surface*):1618: failed to dequeue buffer from native window (0x4a863808); err = -19, buf = 0x0,max_allowed_dequeued_buffers 3
03-19 09:16:04.193 2015 2585 E BufferQueueProducer: [com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity] dequeueBuffer: BufferQueue has been abandoned
03-19 09:16:04.194 10393 10436 E [EGL-ERROR]: void __egl_platform_dequeue_buffer(egl_surface*):1618: failed to dequeue buffer from native window (0x4a863808); err = -19, buf = 0x0,max_allowed_dequeued_buffers 3
03-19 09:16:04.198 10092 10584 E JavaBinder: *** Uncaught remote exception! (Exceptions are not yet supported across processes.)
03-19 09:16:04.198 10092 10584 E JavaBinder: DeadSystemException: The system died; earlier logs will point to the root cause
03-19 09:16:04.202 10092 10104 E JavaBinder: *** Uncaught remote exception! (Exceptions are not yet supported across processes.)
03-19 09:16:04.202 10092 10104 E JavaBinder: DeadSystemException: The system died; earlier logs will point to the root cause
03-19 09:16:04.203 10092 10105 E JavaBinder: *** Uncaught remote exception! (Exceptions are not yet supported across processes.)
03-19 09:16:04.203 10092 10105 E JavaBinder: DeadSystemException: The system died; earlier logs will point to the root cause
03-19 09:16:04.782 10122 10122 D AndroidRuntime: Shutting down VM
03-19 09:16:04.783 10122 10122 E AndroidRuntime: FATAL EXCEPTION: main
03-19 09:16:04.783 10122 10122 E AndroidRuntime: Process: com.android.systemui, PID: 10122
03-19 09:16:04.783 10122 10122 E AndroidRuntime: DeadSystemException: The system died; earlier logs will point to the root cause
E BufferQueueProducer: [com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity] dequeueBuffer: BufferQueue has been abandoned
Did you noticed that EGL errors? I see that your HwComposer fails to load a texture. Is not Bluetooth related. For majority of the EGL related errors the SystemUI will crash (you can already see this). If a process crashes then the "host" of that process will die (Settings app) then the system. Simon Shields is already working to fix HwComposer . Try a clean flash with Aroma GApps.(1) Interesting, that pairing works on your devices!
(2) The build consists only of the LineageOS repositories without foreign components, i.e. standard kernel. Our devices comes with pegasusq governor which is a hotplugging governor as far as I know.
(3) Could it be, that a warm-reboot of Android does not do a kernel-reboot? Then the last_kmesg dates from my previous reboot to start with a clean environment. Not from the Bluetooth-initiated warm reboot.
(4) The following are the last before Android died:
especially the line:Code:03-19 09:16:04.192 10393 10436 E [EGL-ERROR]: void __egl_platform_dequeue_buffer(egl_surface*):1618: failed to dequeue buffer from native window (0x4a863808); err = -19, buf = 0x0,max_allowed_dequeued_buffers 3 03-19 09:16:04.193 2015 2400 E BufferQueueProducer: [com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity] dequeueBuffer: BufferQueue has been abandoned 03-19 09:16:04.193 10393 10436 E [EGL-ERROR]: void __egl_platform_dequeue_buffer(egl_surface*):1618: failed to dequeue buffer from native window (0x4a863808); err = -19, buf = 0x0,max_allowed_dequeued_buffers 3 03-19 09:16:04.193 2015 3250 E BufferQueueProducer: [com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity] dequeueBuffer: BufferQueue has been abandoned 03-19 09:16:04.193 10393 10436 E [EGL-ERROR]: void __egl_platform_dequeue_buffer(egl_surface*):1618: failed to dequeue buffer from native window (0x4a863808); err = -19, buf = 0x0,max_allowed_dequeued_buffers 3 03-19 09:16:04.193 2015 2585 E BufferQueueProducer: [com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity] dequeueBuffer: BufferQueue has been abandoned 03-19 09:16:04.194 10393 10436 E [EGL-ERROR]: void __egl_platform_dequeue_buffer(egl_surface*):1618: failed to dequeue buffer from native window (0x4a863808); err = -19, buf = 0x0,max_allowed_dequeued_buffers 3 03-19 09:16:04.198 10092 10584 E JavaBinder: *** Uncaught remote exception! (Exceptions are not yet supported across processes.) 03-19 09:16:04.198 10092 10584 E JavaBinder: DeadSystemException: The system died; earlier logs will point to the root cause 03-19 09:16:04.202 10092 10104 E JavaBinder: *** Uncaught remote exception! (Exceptions are not yet supported across processes.) 03-19 09:16:04.202 10092 10104 E JavaBinder: DeadSystemException: The system died; earlier logs will point to the root cause 03-19 09:16:04.203 10092 10105 E JavaBinder: *** Uncaught remote exception! (Exceptions are not yet supported across processes.) 03-19 09:16:04.203 10092 10105 E JavaBinder: DeadSystemException: The system died; earlier logs will point to the root cause 03-19 09:16:04.782 10122 10122 D AndroidRuntime: Shutting down VM 03-19 09:16:04.783 10122 10122 E AndroidRuntime: FATAL EXCEPTION: main 03-19 09:16:04.783 10122 10122 E AndroidRuntime: Process: com.android.systemui, PID: 10122 03-19 09:16:04.783 10122 10122 E AndroidRuntime: DeadSystemException: The system died; earlier logs will point to the root cause
shows, that the Bluetooth settings app is part of the problem.Code:E BufferQueueProducer: [com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity] dequeueBuffer: BufferQueue has been abandoned
Can someone give me the last stable build of CyanogenMod 13 I wanna go back to it and wait for a bit before trying lineage is again. Root detection does not work properly, it gives me only ADB. Also YouTube app froze on me for a couple of times. I had to reboot the phone. Thanks in advance. Also battery drains way too fast, I have everything on greenify except Gmail.
Thank you very much kind sirDownload: cm-13.0-20161220-SNAPSHOT-ZNH5YAO3XN-i9300.zip (307.8 MB)
sha1: 3f081f1017831a97c97ec3ae72dc9788a1c9a9df
Strange, I'm not having a single problem. In fact so far I still haven't seen the famous "MTP crash" message either [emoji1]
I also have no problems so far.
Only a bit slow and the mtp server is crahsing but that's only the stock file manager and takes no effect to the functionality
Maybe.Well,that confirms that everyone has the same crash.(even tho it already was a known issue)
---------- Post added at 12:14 PM ---------- Previous post was at 12:11 PM ----------
I hear that our device is the 3rd most popular device with Lineage users.
#include "std_disclaimer.h"
/*
* Your warranty is 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.
*/
Phone Informations
* Lineage version
* Gapps version
What you did:
* Wipe data: y/n
* Upgrade from previous official cm build: y/n
* Restore with titanium backup: y/n
You're using (if yes write which one) :
* Task killer
* Phone cleaner / Battery enhancer apps
* Non-stock kernel
* Modified kernel settings
* Other mods
Bug info:
* Last version it worked on
* Repro steps