[ROM][CM12.1][Lollipop][Android 5.1.1] NightOwl 20180124

sedat8879

Senior Member
Sep 4, 2013
52
10
0
I'm using TK Gapps (Nano or Pico) and they work flawlessly. Be sure you wipe data partition too when changing gapps;)
@sedat8879 are you sure you are wiping everything? I mean cache, dalvik/art, system and DATA too? BTW it could be an hardware failure, like always on note it could be the usb flex.
İ have no problem with gapps.

GT-N7000 cihazımdan Tapatalk kullanılarak gönderildi
 
Last edited:

bauner

Retired Recognized Developer
Jan 23, 2008
4,726
10,330
263
Near Nürnberg
Last edited:

bauner

Retired Recognized Developer
Jan 23, 2008
4,726
10,330
263
Near Nürnberg
Can you point current problems in M?
Maybe i can dig out something ;)
Everytime after wakeup from standby the system server crashes (soft reboot)
Code:
12-31 18:15:58.761  2953  2976 F libc    : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x14 in tid 2976 (PowerManagerSer)
12-31 18:15:58.761  2025  2025 I DEBUG   : property debug.db.uid not set; NOT waiting for gdb.
12-31 18:15:58.761  2025  2025 I DEBUG   : HINT: adb shell setprop debug.db.uid 100000
12-31 18:15:58.761  2025  2025 I DEBUG   : HINT: adb forward tcp:5039 tcp:5039
12-31 18:15:58.862  2025  2025 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
12-31 18:15:58.862  2025  2025 F DEBUG   : Build fingerprint: 'samsung/GT-N7000/GT-N7000:4.0.3/IML74K/ZCLP6:user/release-keys'
12-31 18:15:58.862  2025  2025 F DEBUG   : Revision: '0'
12-31 18:15:58.862  2025  2025 F DEBUG   : ABI: 'arm'
12-31 18:15:58.862  2025  2025 F DEBUG   : pid: 2953, tid: 2976, name: PowerManagerSer  >>> system_server <<<
12-31 18:15:58.863  2025  2025 E DEBUG   : AM write failed: Broken pipe
12-31 18:15:58.863  2025  2025 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x14
12-31 18:15:58.892  2025  2025 F DEBUG   :     r0 00000002  r1 4bce9230  r2 00000004  r3 4bce9340
12-31 18:15:58.892  2025  2025 F DEBUG   :     r4 4bb7ebd0  r5 00000002  r6 4bb7eb88  r7 4bbcd2a0
12-31 18:15:58.892  2025  2025 F DEBUG   :     r8 00000001  r9 00000001  sl 00000000  fp 4bb3d290
12-31 18:15:58.892  2025  2025 F DEBUG   :     ip 00000000  sp a930d240  lr 639e1f80  pc 6397ff2c  cpsr 800d0010
12-31 18:15:58.901  2025  2025 F DEBUG   : 
12-31 18:15:58.901  2025  2025 F DEBUG   : backtrace:
12-31 18:15:58.901  2025  2025 F DEBUG   :     #00 pc 0000bf2c  /system/lib/libMali.so
12-31 18:15:58.901  2025  2025 F DEBUG   :     #01 pc 0000cd4c  /system/lib/libMali.so
12-31 18:15:58.901  2025  2025 F DEBUG   :     #02 pc 00052894  /system/lib/libMali.so
12-31 18:15:58.901  2025  2025 F DEBUG   :     #03 pc 000535f4  /system/lib/libMali.so
12-31 18:15:58.901  2025  2025 F DEBUG   :     #04 pc 0004e610  /system/lib/libMali.so
12-31 18:15:58.901  2025  2025 F DEBUG   :     #05 pc 0004ee58  /system/lib/libMali.so
12-31 18:15:58.901  2025  2025 F DEBUG   :     #06 pc 0004fe6c  /system/lib/libMali.so (shim_eglMakeCurrent+176)
12-31 18:15:58.901  2025  2025 F DEBUG   :     #07 pc 00012821   /system/lib/libEGL.so  (android::egl_display_t::makeCurrent(android::egl_context_t*,  android::egl_context_t*, void*, void*, void*, void*, void*, void*)+148)
12-31 18:15:58.901  2025  2025 F DEBUG   :     #08 pc 0001629d  /system/lib/libEGL.so (eglMakeCurrent+280)
12-31 18:15:58.902  2025  2025 F DEBUG   :     #09 pc 000622dd  /system/lib/libandroid_runtime.so
12-31 18:15:58.902  2025  2025 F DEBUG   :     #10 pc 737abd77   /data/dalvik-cache/arm/[email protected]@boot.oat (offset 0x1f4d000)
12-31 18:16:03.833  8232  8232 W linker  : /system/lib/libsec-ril.so has  text relocations. This is wasting memory and prevents security  hardening. Please fix.
12-31 18:16:04.317  2025  2025 F DEBUG   : 
12-31 18:16:04.317  2025  2025 F DEBUG   : Tombstone written to: /data/tombstones/tombstone_09
12-31 18:16:04.369  2040  2946 W AudioFlinger: power manager service died !!!
This problem also exists on the i9100 in current builds... @Lysergic Acid told me that it was working in older builds but I did not find out the changes which caused it...
 
Last edited:

GeeckoDev

Senior Member
Feb 26, 2013
458
3,331
0
Everytime after wakeup from standby the system server crashes (soft reboot)
Code:
12-31 18:15:58.761  2953  2976 F libc    : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x14 in tid 2976 (PowerManagerSer)
12-31 18:15:58.761  2025  2025 I DEBUG   : property debug.db.uid not set; NOT waiting for gdb.
12-31 18:15:58.761  2025  2025 I DEBUG   : HINT: adb shell setprop debug.db.uid 100000
12-31 18:15:58.761  2025  2025 I DEBUG   : HINT: adb forward tcp:5039 tcp:5039
12-31 18:15:58.862  2025  2025 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
12-31 18:15:58.862  2025  2025 F DEBUG   : Build fingerprint: 'samsung/GT-N7000/GT-N7000:4.0.3/IML74K/ZCLP6:user/release-keys'
12-31 18:15:58.862  2025  2025 F DEBUG   : Revision: '0'
12-31 18:15:58.862  2025  2025 F DEBUG   : ABI: 'arm'
12-31 18:15:58.862  2025  2025 F DEBUG   : pid: 2953, tid: 2976, name: PowerManagerSer  >>> system_server <<<
12-31 18:15:58.863  2025  2025 E DEBUG   : AM write failed: Broken pipe
12-31 18:15:58.863  2025  2025 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x14
12-31 18:15:58.892  2025  2025 F DEBUG   :     r0 00000002  r1 4bce9230  r2 00000004  r3 4bce9340
12-31 18:15:58.892  2025  2025 F DEBUG   :     r4 4bb7ebd0  r5 00000002  r6 4bb7eb88  r7 4bbcd2a0
12-31 18:15:58.892  2025  2025 F DEBUG   :     r8 00000001  r9 00000001  sl 00000000  fp 4bb3d290
12-31 18:15:58.892  2025  2025 F DEBUG   :     ip 00000000  sp a930d240  lr 639e1f80  pc 6397ff2c  cpsr 800d0010
12-31 18:15:58.901  2025  2025 F DEBUG   : 
12-31 18:15:58.901  2025  2025 F DEBUG   : backtrace:
12-31 18:15:58.901  2025  2025 F DEBUG   :     #00 pc 0000bf2c  /system/lib/libMali.so
12-31 18:15:58.901  2025  2025 F DEBUG   :     #01 pc 0000cd4c  /system/lib/libMali.so
12-31 18:15:58.901  2025  2025 F DEBUG   :     #02 pc 00052894  /system/lib/libMali.so
12-31 18:15:58.901  2025  2025 F DEBUG   :     #03 pc 000535f4  /system/lib/libMali.so
12-31 18:15:58.901  2025  2025 F DEBUG   :     #04 pc 0004e610  /system/lib/libMali.so
12-31 18:15:58.901  2025  2025 F DEBUG   :     #05 pc 0004ee58  /system/lib/libMali.so
12-31 18:15:58.901  2025  2025 F DEBUG   :     #06 pc 0004fe6c  /system/lib/libMali.so (shim_eglMakeCurrent+176)
12-31 18:15:58.901  2025  2025 F DEBUG   :     #07 pc 00012821   /system/lib/libEGL.so  (android::egl_display_t::makeCurrent(android::egl_context_t*,  android::egl_context_t*, void*, void*, void*, void*, void*, void*)+148)
12-31 18:15:58.901  2025  2025 F DEBUG   :     #08 pc 0001629d  /system/lib/libEGL.so (eglMakeCurrent+280)
12-31 18:15:58.902  2025  2025 F DEBUG   :     #09 pc 000622dd  /system/lib/libandroid_runtime.so
12-31 18:15:58.902  2025  2025 F DEBUG   :     #10 pc 737abd77   /data/dalvik-cache/arm/[email protected]@boot.oat (offset 0x1f4d000)
12-31 18:16:03.833  8232  8232 W linker  : /system/lib/libsec-ril.so has  text relocations. This is wasting memory and prevents security  hardening. Please fix.
12-31 18:16:04.317  2025  2025 F DEBUG   : 
12-31 18:16:04.317  2025  2025 F DEBUG   : Tombstone written to: /data/tombstones/tombstone_09
12-31 18:16:04.369  2040  2946 W AudioFlinger: power manager service died !!!
This problem also exists on the i9100 in current builds... @Lysergic Acid told me that it was working in older builds but I did not find out the changes which caused it...
Looks like a problem with libMali, you might want to apply this patch to add r4p0 drivers (blobs here)
 
Last edited:

bauner

Retired Recognized Developer
Jan 23, 2008
4,726
10,330
263
Near Nürnberg
Looks like a problem with libMali, you might want to apply this patch to add r4p0 drivers (blobs here)
Thx I will try it.
But it looks like that cm has something messed up because it was working in earlier cm builds.
It is not a general android 6 r26 problem because I built an omni 6 based testversion today and there are no such problems.
 
Jan 5, 2008
28
2
0
Pune
Any help on BT issue? pls...

Hi bauner,

Have you found any working settings for Bluetooth audio issue?

As suggested, I tried changing the mic values for following cat: <device type="builtin-mic">

<ctrl name="Mic 1 Gain Volume" value="0" />
<ctrl name="Mic 2 Gain Volume" value="0" />

and replaced with "5"

Still don't see any difference while making the calls from Bluetooth device :( however if I get any incoming call and connect it via Bluetooth the other party can hear me well. The problem seems only while making the calls.

Can you pls suggest some workaround or any other settings/ values needs to be updated from tinyalsa-audio.xml

Thanks,

NK
Hi,

Can someone please help here?
 

vanityq

Member
Dec 5, 2011
14
0
0
Hi @bauner

I cant use the latest download from ota..
Im coming from 10.03 version and after installing 10.30
My fone heats up and i cant run superuser app. I tried installing it twice and clearing cache and dalvik.

I revert back to 10.03 instead.

Thanks. Will just be waiting for next stable update
 

vanityq

Member
Dec 5, 2011
14
0
0
I tried a full wipe prior on sept. Version amd updated to 10.03 and was flawless

As much as possible im avoiding to do full wipe..

Thanks

Does it require fullwipe?
 

KalZakath

Senior Member
Jan 31, 2012
649
325
0
32
BRZEG
@bauner if u have started working on cm13 code can u implement support for synapse. That would be the best thing to happen to the this device. Tia
Synapse can cause instability of kernel, so it absolutely should not be impleneted.

Gps not running finely on 20151030.....it hangs :( @bauner


Sent from my GT-N7000 using Tapatalk
GPS working fine - on sygic and google maps.
@bauner does this commit means that we will have working ril?
http://review.cyanogenmod.org/#/c/114804/
 
Last edited:
  • Like
Reactions: bauner

GeeckoDev

Senior Member
Feb 26, 2013
458
3,331
0
Battery life on my phone was really bad these days. Wakelock detector showed me that the stock Messaging app was keeping my phone awake all the time... I disabled "Automatically retrieve messages" to get rid of this wakelock. It's caused by a MMS waiting to be retrieved... I believe my APNs are not correctly set.
 
Nov 13, 2014
22
4
0
Hey guys, I upgraded to this rom but it can't mount the data partition and my apps can't save any images. Maybe the filesystem is the reason? I have all partitions formated to ext4 but the updater script seems to use f2fs. Still, my fstab contains ext4 only.

btw. I also followed the repartition guide refered in 1st post
and I get Camera FC
 
Last edited: