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

carabao72 · Nov 22, 2015 at 2:43 PM

Hello,
Thank you for your work. Curious and eager to see the CM 13 to the bauner sauce. But for now, my n7000 runs smoothly with CM12.1 nighowl

bonjour,
Merci pour ton travail. Curieux et impatient de voir la CM 13 à la sauce bauner. Mais pour le moment, mon n7000 tourne sans problème avec la CM12.1 nighowl

Lysergic Acid · Nov 22, 2015 at 9:52 PM

GeeckoDev said:
Looks like a problem with libMali, you might want to apply this patch to add r4p0 drivers (blobs here)

I don't know if @bauner tried this but I decided to give it a shot. It went all okay to boot r4p0:

Code:

E: Device driver API match
E: Device driver API version: 401
E: User space API version: 401 
E: mali: REVISION=Linux-r4p0-00rel0 BUILD_DATE=Wed May 14 21:45:08 CST 2014

But in the end I got the same crash:

Code:

11-22 10:41:29.616  1914  1914 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
11-22 10:41:29.616  1914  1914 F DEBUG   : Build fingerprint: 'samsung/GT-I9100/GT-I9100:4.1.2/JZO54K/I9100XWMS2:user/release-keys'
11-22 10:41:29.616  1914  1914 F DEBUG   : Revision: '0'
11-22 10:41:29.616  1914  1914 F DEBUG   : ABI: 'arm'
11-22 10:41:29.617  1914  1914 F DEBUG   : pid: 2354, tid: 2417, name: PowerManagerSer  >>> system_server <<<
11-22 10:41:29.617  1914  1914 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x14
11-22 10:41:29.634  1914  1914 F DEBUG   :     r0 00000002  r1 53dd9208  r2 00000004  r3 53dd92a0
11-22 10:41:29.635  1914  1914 F DEBUG   :     r4 5454a8b8  r5 00000002  r6 5454a880  r7 46994050
11-22 10:41:29.635  1914  1914 F DEBUG   :     r8 00000001  r9 5645ee08  sl 00000001  fp 00000000
11-22 10:41:29.635  1914  1914 F DEBUG   :     ip 00000000  sp 54315ee0  lr 550761d4  pc 5500c464  cpsr 80030010
11-22 10:41:29.648  1914  1914 F DEBUG   : 
11-22 10:41:29.648  1914  1914 F DEBUG   : backtrace:
11-22 10:41:29.648  1914  1914 F DEBUG   :     #00 pc 0000d464  /system/lib/libMali.so
11-22 10:41:29.648  1914  1914 F DEBUG   :     #01 pc 0000e13c  /system/lib/libMali.so
11-22 10:41:29.648  1914  1914 F DEBUG   :     #02 pc 0005a9c8  /system/lib/libMali.so
11-22 10:41:29.648  1914  1914 F DEBUG   :     #03 pc 0005b6bc  /system/lib/libMali.so
11-22 10:41:29.648  1914  1914 F DEBUG   :     #04 pc 000565e8  /system/lib/libMali.so
11-22 10:41:29.648  1914  1914 F DEBUG   :     #05 pc 00056e80  /system/lib/libMali.so
11-22 10:41:29.648  1914  1914 F DEBUG   :     #06 pc 00057eb0  /system/lib/libMali.so (shim_eglMakeCurrent+176)
11-22 10:41:29.648  1914  1914 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)
11-22 10:41:29.648  1914  1914 F DEBUG   :     #08 pc 0001629d  /system/lib/libEGL.so (eglMakeCurrent+280)
11-22 10:41:29.648  1914  1914 F DEBUG   :     #09 pc 000622f1  /system/lib/libandroid_runtime.so
11-22 10:41:29.648  1914  1914 F DEBUG   :     #10 pc 74467e2f  /data/dalvik-cache/arm/[email protected]@boot.oat (offset 0x1f53000)

I don't know what CM did, but I doubt the problem is with our blob

bauner · Nov 22, 2015

Lysergic Acid said:

I don't know if @bauner tried this but I decided to give it a shot. It went all okay to boot r4p0:

Code:

E: Device driver API match
E: Device driver API version: 401
E: User space API version: 401 
E: mali: REVISION=Linux-r4p0-00rel0 BUILD_DATE=Wed May 14 21:45:08 CST 2014

But in the end I got the same crash:

Code:

11-22 10:41:29.616  1914  1914 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
11-22 10:41:29.616  1914  1914 F DEBUG   : Build fingerprint: 'samsung/GT-I9100/GT-I9100:4.1.2/JZO54K/I9100XWMS2:user/release-keys'
11-22 10:41:29.616  1914  1914 F DEBUG   : Revision: '0'
11-22 10:41:29.616  1914  1914 F DEBUG   : ABI: 'arm'
11-22 10:41:29.617  1914  1914 F DEBUG   : pid: 2354, tid: 2417, name: PowerManagerSer  >>> system_server <<<
11-22 10:41:29.617  1914  1914 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x14
11-22 10:41:29.634  1914  1914 F DEBUG   :     r0 00000002  r1 53dd9208  r2 00000004  r3 53dd92a0
11-22 10:41:29.635  1914  1914 F DEBUG   :     r4 5454a8b8  r5 00000002  r6 5454a880  r7 46994050
11-22 10:41:29.635  1914  1914 F DEBUG   :     r8 00000001  r9 5645ee08  sl 00000001  fp 00000000
11-22 10:41:29.635  1914  1914 F DEBUG   :     ip 00000000  sp 54315ee0  lr 550761d4  pc 5500c464  cpsr 80030010
11-22 10:41:29.648  1914  1914 F DEBUG   : 
11-22 10:41:29.648  1914  1914 F DEBUG   : backtrace:
11-22 10:41:29.648  1914  1914 F DEBUG   :     #00 pc 0000d464  /system/lib/libMali.so
11-22 10:41:29.648  1914  1914 F DEBUG   :     #01 pc 0000e13c  /system/lib/libMali.so
11-22 10:41:29.648  1914  1914 F DEBUG   :     #02 pc 0005a9c8  /system/lib/libMali.so
11-22 10:41:29.648  1914  1914 F DEBUG   :     #03 pc 0005b6bc  /system/lib/libMali.so
11-22 10:41:29.648  1914  1914 F DEBUG   :     #04 pc 000565e8  /system/lib/libMali.so
11-22 10:41:29.648  1914  1914 F DEBUG   :     #05 pc 00056e80  /system/lib/libMali.so
11-22 10:41:29.648  1914  1914 F DEBUG   :     #06 pc 00057eb0  /system/lib/libMali.so (shim_eglMakeCurrent+176)
11-22 10:41:29.648  1914  1914 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)
11-22 10:41:29.648  1914  1914 F DEBUG   :     #08 pc 0001629d  /system/lib/libEGL.so (eglMakeCurrent+280)
11-22 10:41:29.648  1914  1914 F DEBUG   :     #09 pc 000622f1  /system/lib/libandroid_runtime.so
11-22 10:41:29.648  1914  1914 F DEBUG   :     #10 pc 74467e2f  /data/dalvik-cache/arm/[email protected]@boot.oat (offset 0x1f53000)

I don't know what CM did, but I doubt the problem is with our blob

@Lysergic Acid I had also tested r4p0 and had the same problems with it.
But I think I have found the reason.
I'm currently cleaning up my source and then I build a new testversion.
If it will fix the reboots I tell you the change

bauner · Nov 22, 2015 at 11:37 PM

Lysergic Acid said:
But in the end I got the same crash....

@Lysergic Acid
Reverting this commit fixes the crash
https://github.com/CyanogenMod/andr...mmit/c784dfc39fa1471b0f653206970ac9a256269256

GeeckoDev · Nov 22, 2015 at 11:55 PM

bauner said:
@Lysergic Acid
Reverting this commit fixes the crash
https://github.com/CyanogenMod/andr...mmit/c784dfc39fa1471b0f653206970ac9a256269256

Good job

I wouldn't be surprised if this was a gralloc issue undercovered by this change.

Lysergic Acid · Nov 23, 2015 at 12:08 AM

bauner said:
@Lysergic Acid
Reverting this commit fixes the crash
https://github.com/CyanogenMod/andr...mmit/c784dfc39fa1471b0f653206970ac9a256269256

Wow really? I would never think about that, I scrolled the whole fw/native searching for EGL stuff without any luck, now it's explained. Good job indeed :good:

Green-Bot · Nov 2, 2012 292 69 58

Hiii @bauner i set an alarm and switched off my phone but alarm didn't rung. Is it normal? Phone should sound alarm giving us the option to turnit on?

bauner · Nov 23, 2015 at 7:54 AM

vinay28761 said:
Hiii @bauner i set an alarm and switched off my phone but alarm didn't rung. Is it normal? Phone should sound alarm giving us the option to turnit on?

The alarm is not working and will not power on the device if it is switched off

bauner · Nov 23, 2015 at 5:35 PM

My first cm13 alpha is here
http://forum.xda-developers.com/galaxy-note/development/rom-nightowl-alpha1-t3255536

miku1024 · Nov 23, 2015 at 5:41 PM

bauner said:
My first cm13 alpha is here
http://forum.xda-developers.com/galaxy-note/development/rom-nightowl-alpha1-t3255536

Thank you very much are recovery working?

bauner · Nov 23, 2015 at 5:43 PM

miku1024 said:
Thank you very much are recovery working?

yes it is using the same philz recovery as my cm12.1

alforati · Jul 15, 2008 87 14 0

Google play services has stopped ! any solvation?

D@rekills4 · Nov 24, 2015 at 7:34 AM

alforati said:
Google play services has stopped ! any solvation?

I don't have any such issue.
Have to disabled access to certain things in Privacy Guard for Google Play Services?

Green-Bot · Nov 24, 2015

bauner said:
The alarm is not working and will not power on the device if it is switched off

Any possible chances of including/activating this feature?? Thanks in advance for your reply.

bauner · Nov 24, 2015 at 8:39 AM

vinay28761 said:
Any possible chances of including/activating this feature?? Thanks in advance for your reply.

I don't know if the n7000 support it and it would also need some kernel changes

SoulSlayer69 · Nov 24, 2015 at 12:42 PM

Keep focusing on CM13, in my opinion CM12.1 is fine enough to be dropped in favour of Marshmallow. No need to waste time on Lollipop anymore if we can jump on an improved build, and seems like Android 6 is fair better than 5.1.x

Btw, idk if there is any Android phone cabable to wake up to ring alarm, so my advice is just to put it on airplane mode if you don't want to take it active during night but need alarm

nokiamodeln91 · Nov 24, 2015 at 1:37 PM

alforati said:
Google play services has stopped ! any solvation?

Go to Google play services permissions menu and enable keep awake setting.

alforati · Jul 15, 2008 87 14 0

nokiamodeln91 said:
Go to Google play services permissions menu and enable keep awake setting.

did not make any change..
Anyway thanks for replay.
But i installed this play services . and problem solved and most of lags especially facebook lag gone.
:com.google.android.gms_8.4.89_(2428711-246)-8489246_minAPI21(arm64-v8a,armeabi-v7a)(320dpi).apk
http://www.apkmirror.com/apk/google...ices-8-4-89-2428711-246-android-apk-download/

milsabords · Nov 25, 2015

vinay28761 said:
Hiii @bauner i set an alarm and switched off my phone but alarm didn't rung. Is it normal? Phone should sound alarm giving us the option to turnit on?

Search XDA for "arter97-L-quickboot". It works with CM12.1.

Edit: quickboot is here http://forum.xda-developers.com/android/software/universal-quickboot-cyanogenmod-12-0-12-t3082041

jiguan · May 16, 2014 53 36 0

I cannot setup exchange account, mail app crash during setup. Is it known bug?.

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

Senior Member

Inactive Recognized Developer

Retired Recognized Developer

Retired Recognized Developer

Senior Member

Inactive Recognized Developer

Senior Member

Retired Recognized Developer

Retired Recognized Developer

Senior Member

Retired Recognized Developer

Senior Member

Senior Member

Senior Member

Retired Recognized Developer

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member