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

[salamkath]

very well run in my note n7000 LP beta3 but some issues are there

I switched from kitkat 4.4.4 omni rom to cm12, its my first experience with cm family
Issue is that my cell is now heating alot after lollipop and battery drains too much faster if i use any games or facebook app or use browser please fix it or otherwise it will be disappointing for me, one another thing is that in omni kitkat there was a performance option in setting which is missing in that one in which i use to control CPU performance by myself

 

[G0711]

Is your battery ok? or did you get some screen flickering before?
Does it only happens if you have wifi enabled?

@bauner no.i never used wifi...
and i think my battery is fine
but i did get some flickering after installing the rom...
i never got that before.

-Edit
I went back to slim saber KK for a while
and it run fine.,so i don't think my battery is the problem
im going to see the next build..and i'm definitely going to try again
thanks bauner for helping.

 

[bauner]

@bauner no.i never used wifi...
and i think my battery is fine
but i did get some flickering after installing the rom...
i never got that before.

-Edit
I went back to slim saber KK for a while
and it run fine.,so i don't think my battery is the problem
im going to see the next build..and i'm definitely going to try again
thanks bauner for helping.

I get screen flickering and a few days after this random reboots even when the charger was connected. For me the problem was the battery

 

[bauner]

I know this option, it's only many option boot


Sent from my GT-N7000 using XDA Free mobile app

In the next beta it will look like this

 

[bauner]

Unfortunately, I don't know why but I can't do that.

have you tried to push the 2 buttons together for a few seconds?

 

[bauner]

I switched from kitkat 4.4.4 omni rom to cm12, its my first experience with cm family
Issue is that my cell is now heating alot after lollipop and battery drains too much faster if i use any games or facebook app or use browser please fix it or otherwise it will be disappointing for me, one another thing is that in omni kitkat there was a performance option in setting which is missing in that one in which i use to control CPU performance by myself

Cyanogen have it integrated in their current source. In beta 4 you will have the options to set the cpu governor and the i/o scheduler

 

[Haitham Nadeem]

i'm not a robot

Hello bauner
its awsome rom and very good work .. you turned life back to my note too thanks
so i tried all beta 1 2 3
beta 3 for me is the best stable with almost no more heat & freeze .. but have some errors while i use messenger fb and close
waiting next build also i was wonder why there's not power save button in the top navbar it would help much ..

 

[Bauldrick]

could you post the logcat output on turning off wifi and switch to mobile data?
I never had this problem in any version and only a few users have reported this issue, so it's very hard to find out what is causing this problem

I can dump logcat, but I can't seem to get anything that resembles anything of interest?!

with what command 'adb logcat -d ....' or what? and what am I looking for in particular to post - I see l_android had alot of mReceiver blabla..... is that the relevent part?

 

[G0711]

I get screen flickering and a few days after this random reboots even when the charger was connected. For me the problem was the battery

I think you re right about the battery
I got the same issue just now..
Now im sure..
One question though,do we need to calibrate battery in every rom installation?

Sent from my GT-N7000 using XDA Free mobile app

 

[kazuna69]

I think you re right about the battery
I got the same issue just now..
Now im sure..
One question though,do we need to calibrate battery in every rom installation?

Sent from my GT-N7000 using XDA Free mobile app

it's kinda hard to re-calibrate your battery as it must "settle-down" for few days/weeks to give better result/feedback
but it is kinda hard, if we always changing/upgrade betweens roms :silly: :silly: :silly:

I did this experiment on my s plus, after almost a week in Lollipop, its battery is far better than my n7000, with more hours of screen time....but it is totally dependable on kernel/recovery as the i9001/splus have toolchain by christoper.... :silly:

but anyway, it's whole separate issues :silly:

try to give a try to your n7000,
mine got settle up in slimsaber

 

[G0711]

it's kinda hard to re-calibrate your battery as it must "settle-down" for few days/weeks to give better result/feedback
but it is kinda hard, if we always changing/upgrade betweens roms :silly: :silly: :silly:

I did this experiment on my s plus, after almost a week in Lollipop, its battery is far better than my n7000, with more hours of screen time....but it is totally dependable on kernel/recovery as the i9001/splus have toolchain by christoper.... :silly:

but anyway, it's whole separate issues :silly:

try to give a try to your n7000,
mine got settle up in slimsaber

im now using slim saber too
but it is indeed hard for do the calibration while changing rom often
but,what about battery calibration app?
is that effective for the battery?
im sorry if it's OOT, just curious.

 

[Copkiller2010]

I am shure that most bugs are in beta 2 and 3. Beta1 i found no bugs till today. No Overheating and fast. I think reason over 90 percent are the kernel. If anyone want really stable use Beta1 from bauner or RR Rom 5.2.5 from 2014 with the combination of this kernel: raw_kernel_r7_l50_alpha.zip . Till now the best kernel. No Overheating. Nothing..

Maybe this helps also bauner an he can verify the complete changes why Rom and kernels are unstable, Overheating and battery drain between beta1 beta2 and 3
@bauner. Maybe Noob Idea : Can u edit the Source that raw_kernel_r7_l50_alpha.zip works again with your "beta 4" or directly integrate ? So wee can see if issues again mostly gone.

 

[kazuna69]

im now using slim saber too
but it is indeed hard for do the calibration while changing rom often
but,what about battery calibration app?
is that effective for the battery?
im sorry if it's OOT, just curious.

owh, sure it's Better Battery Stats apps,
It's not OOT, I would consider calibrating battery is an issue need attention, :highfive:
I mean, there shouldn't be any complain about the rom's battery life if un-calibrated battery is the main factor :silly:
right?

 

[bauner]

I can dump logcat, but I can't seem to get anything that resembles anything of interest?!

with what command 'adb logcat -d ....' or what? and what am I looking for in particular to post - I see l_android had alot of mReceiver blabla..... is that the relevent part?

the lines like this are relevant

D/ConnectivityService( 2242): NetworkAgentInfo [MOBILE (EDGE) - 103] EVENT_NETWORK_INFO_CHANGED, going from null to CONNECTED
D/ConnectivityService( 2242): Adding iface rmnet0 to network 103
D/PhoneApp( 2734): getPhone phoneId:0
D/PhoneApp( 2734): mReceiver: ACTION_ANY_DATA_CONNECTION_STATE_CHANGED
D/PhoneApp( 2734): - state: CONNECTED
D/PhoneApp( 2734): - reason: connected
D/NotificationMgr( 2734): hideDataDisconnectedRoaming()...
D/PhoneApp( 2734): getPhone phoneId:0
D/PhoneApp( 2734): getPhone phoneId:0

 

[bauner]

I am shure that most bugs are in beta 2 and 3. Beta1 i found no bugs till today. No Overheating and fast. I think reason over 90 percent are the kernel. If anyone want really stable use Beta1 from bauner or RR Rom 5.2.5 from 2014 with the combination of this kernel: raw_kernel_r7_l50_alpha.zip . Till now the best kernel. No Overheating. Nothing..

Maybe this helps also bauner an he can verify the complete changes why Rom and kernels are unstable, Overheating and battery drain between beta1 beta2 and 3
@bauner. Maybe Noob Idea : Can u edit the Source that raw_kernel_r7_l50_alpha.zip works again with your "beta 4" or directly integrate ? So wee can see if issues again mostly gone.

I don't think that the kernel is the problem. I think that an hanging/crashed app or part of the rom is causing this problem

If you want to use an older kernel for my newer rom you need to ask the kernel developer to integrate the newer init parts

 

[bauner]

If someone have the high battery drain the output from

top -m 15 -n 5 -s cpu

where usefull
And also the logcat output

 

[Magic_Man36]

terminal

If someone have the high battery drain the output from

top -m 15 -n 5 -s cpu

where usefull
And also the logcat output

[email protected]:/ $ top -m 15 -n 5 -s cpu



User 12%, System 15%, IOW 0%, IRQ 0%
User 37 + Nice 0 + Sys 48 + Idle 220 + IOW 0 + IRQ 0 + SIRQ 3 = 308

PID PR CPU% S #THR VSS RSS PCY UID Name
2242 0 19% S 87 896392K 106976K fg system system_server
7729 0 3% R 1 4400K 988K fg u0_a74 top
2831 0 2% S 35 749404K 53908K bg u0_a20 com.google.android.googlequicksearchbox:search
2538 0 1% S 1 6308K 1712K wifi /system/bin/wpa_supplicant
2474 0 1% S 1 0K 0K root dhd_dpc
1900 0 0% S 22 83552K 3864K fg system /system/bin/surfaceflinger
2397 0 0% S 32 753444K 73012K fg u0_a12 com.android.systemui
6551 0 0% S 1 0K 0K root kworker/0:3
1896 0 0% S 1 4400K 864K root /system/bin/lmkd
1882 0 0% S 1 0K 0K root jbd2/mmcblk0p10 2473 0 0% S 1 0K 0K root dhd_watchdog_th 843 0 0% S 1 0K 0K root s3c-fb-vsync
7037 0 0% S 20 694104K 44236K bg u0_a3 android.process.acore
591 1 0% S 1 0K 0K root khungtaskd
596 0 0% S 1 0K 0K root kswapd0



User 19%, System 15%, IOW 0%, IRQ 0%
User 62 + Nice 0 + Sys 50 + Idle 201 + IOW 0 + IRQ 0 + SIRQ 0 = 313

PID PR CPU% S #THR VSS RSS PCY UID Name
2242 0 19% S 87 896392K 106988K fg system system_server
2397 0 4% S 32 753444K 73024K fg u0_a12 com.android.systemui
7729 0 3% R 1 4400K 996K fg u0_a74 top
2787 0 3% S 19 752224K 66072K bg u0_a20 com.google.android.googlequicksearchbox
1900 0 2% S 22 83552K 3864K fg system /system/bin/surfaceflinger
2474 0 2% S 1 0K 0K root dhd_dpc
7688 0 1% S 20 714788K 44904K fg u0_a74 jackpal.androidterm
6551 0 0% S 1 0K 0K root kworker/0:3
2538 0 0% S 1 6308K 1712K wifi /system/bin/wpa_supplicant
2765 0 0% S 33 708504K 44104K fg radio com.android.phone
3088 0 0% S 41 784716K 61444K fg u0_a16 com.google.process.location
7660 0 0% S 1 0K 0K root kworker/u:0
488 1 0% S 1 0K 0K root cfg80211
591 1 0% S 1 0K 0K root khungtaskd
596 0 0% S 1 0K 0K root kswapd0



User 16%, System 17%, IOW 0%, IRQ 0%
User 53 + Nice 0 + Sys 57 + Idle 209 + IOW 0 + IRQ 0 + SIRQ 3 = 322

PID PR CPU% S #THR VSS RSS PCY UID Name
2242 0 20% S 87 896392K 107000K fg system system_server
7729 0 5% R 1 4400K 996K fg u0_a74 top
2397 0 3% S 32 753444K 73044K fg u0_a12 com.android.systemui
2474 0 1% S 1 0K 0K root dhd_dpc
1900 0 1% S 22 83552K 3864K fg system /system/bin/surfaceflinger
6551 0 0% S 1 0K 0K root kworker/0:3
2538 0 0% S 1 6308K 1712K wifi /system/bin/wpa_supplicant
7688 0 0% S 20 714788K 45080K fg u0_a74 jackpal.androidterm
1089 0 0% S 1 0K 0K root mmcqd/0
2473 0 0% S 1 0K 0K root dhd_watchdog_th 843 0 0% S 1 0K 0K root s3c-fb-vsync
434 0 0% S 1 0K 0K root irq/359-max8997 488 1 0% S 1 0K 0K root cfg80211
591 1 0% S 1 0K 0K root khungtaskd
596 0 0% S 1 0K 0K root kswapd0



User 12%, System 17%, IOW 0%, IRQ 0%
User 39 + Nice 0 + Sys 57 + Idle 223 + IOW 0 + IRQ 0 + SIRQ 2 = 321

PID PR CPU% S #THR VSS RSS PCY UID Name
2242 0 17% S 87 896392K 107012K fg system system_server
7729 0 4% R 1 4400K 996K fg u0_a74 top
2474 0 1% S 1 0K 0K root dhd_dpc
7688 0 1% S 20 714788K 45256K fg u0_a74 jackpal.androidterm
2538 0 0% S 1 6308K 1712K wifi /system/bin/wpa_supplicant
1900 0 0% S 22 83552K 3864K fg system /system/bin/surfaceflinger
6551 0 0% S 1 0K 0K root kworker/0:3
2831 0 0% S 34 748340K 53696K bg u0_a20 com.google.android.googlequicksearchbox:search
377 0 0% S 1 0K 0K root bdi-default
379 1 0% S 1 0K 0K root kblockd
394 0 0% S 1 0K 0K root khubd
434 0 0% S 1 0K 0K root irq/359-max8997 488 1 0% S 1 0K 0K root cfg80211
591 1 0% S 1 0K 0K root khungtaskd
596 0 0% S 1 0K 0K root kswapd0



User 15%, System 17%, IOW 0%, IRQ 0%
User 49 + Nice 0 + Sys 56 + Idle 215 + IOW 0 + IRQ 0 + SIRQ 0 = 320

PID PR CPU% S #THR VSS RSS PCY UID Name
2242 0 18% S 87 896392K 107020K fg system system_server
7729 0 5% R 1 4400K 996K fg u0_a74 top
2397 0 3% S 32 753444K 73060K fg u0_a12 com.android.systemui
1900 0 2% S 22 83552K 3864K fg system /system/bin/surfaceflinger
7688 0 1% S 20 714788K 45432K fg u0_a74 jackpal.androidterm
2474 0 1% S 1 0K 0K root dhd_dpc
2538 0 0% S 1 6308K 1712K wifi /system/bin/wpa_supplicant
6551 0 0% S 1 0K 0K root kworker/0:3
2765 0 0% S 33 708504K 44104K fg radio com.android.phone
7660 0 0% S 1 0K 0K root kworker/u:0
3088 0 0% S 41 784716K 61444K fg u0_a16 com.google.process.location
2473 0 0% S 1 0K 0K root dhd_watchdog_th 843 0 0% S 1 0K 0K root s3c-fb-vsync
591 1 0% S 1 0K 0K root khungtaskd
596 0 0% S 1 0K 0K root kswapd0
[email protected]:/ $

 

[dev_freak]

If someone have the high battery drain the output from

top -m 15 -n 5 -s cpu

where usefull
And also the logcat output

I gues the battery issues are gone, but the kernel recovery can't read my internal SD, I formatted it to NTFS, since default didn't work, NightOwl can read it properly.

 

[bauner]

I gues the battery issues are gone, but the kernel recovery can't read my internal SD, I formatted it to NTFS, since default didn't work, NightOwl can read it properly.

I recommend to not use ntfs. Does formatting to vfat in recovery not working for you?

 

[bauner]

[email protected]:/ $ top -m 15 -n 5 -s cpu


User 15%, System 17%, IOW 0%, IRQ 0%
User 49 + Nice 0 + Sys 56 + Idle 215 + IOW 0 + IRQ 0 + SIRQ 0 = 320

PID PR CPU% S #THR VSS RSS PCY UID Name
2242 0 18% S 87 896392K 107020K fg system system_server
7729 0 5% R 1 4400K 996K fg u0_a74 top
2397 0 3% S 32 753444K 73060K fg u0_a12 com.android.systemui
1900 0 2% S 22 83552K 3864K fg system /system/bin/surfaceflinger
7688 0 1% S 20 714788K 45432K fg u0_a74 jackpal.androidterm
2474 0 1% S 1 0K 0K root dhd_dpc
2538 0 0% S 1 6308K 1712K wifi /system/bin/wpa_supplicant
6551 0 0% S 1 0K 0K root kworker/0:3
2765 0 0% S 33 708504K 44104K fg radio com.android.phone
7660 0 0% S 1 0K 0K root kworker/u:0
3088 0 0% S 41 784716K 61444K fg u0_a16 com.google.process.location
2473 0 0% S 1 0K 0K root dhd_watchdog_th 843 0 0% S 1 0K 0K root s3c-fb-vsync
591 1 0% S 1 0K 0K root khungtaskd
596 0 0% S 1 0K 0K root kswapd0
[email protected]:/ $

thx for the log. But do you have the high battery drain (a few percents within minutes)?