[ROM][LineageOS14.1][Nougat][Android 7.1.2] NightOwl 20180824

[bauner]

The CM14.1 alpha7 is finish

Changes:
* Merged cm changes
* The kernel is built again with the default gcc 4.9
* Display modes/colorprofiles fixed
* libwvm.so shim to fix cannot locate symbol "_ZN7android16MediaBufferGroupC1Ev"
* Fix for mali driver crash (removed old workaround)

 

[bauner]

thank bauner for replying. You know, checked the behaviour once again and noticed if pausing the recording it then displays the stop button but clicking it does nothing..
As for the vibration it appeared in the previous android-owl too. A hardware issue.. at least if there're no others who complain on that.. anyway, thanks.

Yes I can confirm it. The pausing button will freeze the sound recorder app but if you only use the start and stop button it should work

 

[night02]

So I flashed alpha 5 today.

Firstly, I would like to thank @bauner for all the amazing work he has done for the N7000.

This ROM is almost close to perfect, barely any issues.

First bug is that after powering the phone on the power button doesn't work.
So I lit the display using the home button and unlocked the phone.
There was an error saying "Settings has stopped working". So I tapped "Open app again" and the power key started working.
This happens after every power off and power on. (Doesn't happen during reboots).

Second minor bug is that the recent app switcher's graphics is a bit glitch. Apart from that everything seems fine.

Screenshots attached.

Bauner did the recents app switchers graphics got fixed in the latest alpha 7 ?

 

[bauner]

Bauner did the recents app switchers graphics got fixed in the latest alpha 7 ?

There is nothing wrong with the recent apps switcher

 

[night02]

thnx man downloading right now

u are the best!!!!!!!!!!!!!!!!!!!!!!!

 

[derulf]

in alpha 7 I had an issue with recovery, was not working, could not flash any zip, got an error code...

 

[mnaous]

thanks so much

The CM14.1 alpha7 is finish

Changes:
* Merged cm changes
* The kernel is built again with the default gcc 4.9
* Display modes/colorprofiles fixed
* libwvm.so shim to fix cannot locate symbol "_ZN7android16MediaBufferGroupC1Ev"
* Fix for mali driver crash (removed old workaround)

thanks for that great rom you are best :good:

 

[bauner]

in alpha 7 I had an issue with recovery, was not working, could not flash any zip, got an error code...

Which rom and recovery version did you have installed before and which error code did you got?

 

[derulf]

Which rom and recovery version did you have installed before and which error code did you got?

before - the alpha 6, before cm 13 before cm 12, i ve gone so far all upgraded, can confirm that s working...
/dunno was the first time i ve seen this recovery, reminds me on stock recovery and of course i got rid of it, flashed a cm recovery from august 2016 then. So - case soved... but i wonder if noone else had that strange recovery ???
error code - i don t remember

Thanks a lot for your help and your CM support !!!

 

[alvaro_L]

Hello Mr. Bauer, that another kernel recommends for this your rom, the phone heats up

 

[action_papst]

Hello Mr. Bauer, that another kernel recommends for this your rom, the phone heats up

I'd recommend the default kernel. Just give it a few hours.

 

[night02]

There is nothing wrong with the recent apps switcher

It should be like this

Instead of showing like this

 

[Prinus]

@bauner

Dirty flashed Alpha 7 yesterday via OTA
Had a full reboot this night around 4:45, last_kmsg attached.
The only thing that should happen in the night is an auto-trim at 3:00.

Anyhow, still very happy with N on my N-7000, cheers :good:

 

[bauner]

@bauner

Dirty flashed Alpha 7 yesterday via OTA
Had a full reboot this night around 4:45, last_kmsg attached.
The only thing that should happen in the night is an auto-trim at 3:00.

Anyhow, still very happy with N on my N-7000, cheers :good:

The reboot was caused from an filesystem error on your /data partition.
If you have installed the twrp recovery you could do a filesystem check n the recovery (but it should also be done itself on boot)

But I have seen a temperature related problem in your log which I have never seen before

<3>[41398.320740] c0 temperature code is in inaccurate range->check if vdd_18_ts is on or room temperature.
<6>[41398.329630] c0 current temp is under 25 celsius degree!

You should check the dmesg log if this will happen again.
You can also check if the cpu temp will be displayed correctly with Cpu Temperature
https://play.google.com/store/apps/details?id=com.yanyan.cputemp&hl=de

 

[Prinus]

The reboot was caused from an filesystem error on your /data partition.
If you have installed the twrp recovery you could do a filesystem check n the recovery (but it should also be done itself on boot)

But I have seen a temperature related problem in your log which I have never seen before

<3>[41398.320740] c0 temperature code is in inaccurate range->check if vdd_18_ts is on or room temperature.
<6>[41398.329630] c0 current temp is under 25 celsius degree!

You should check the dmesg log if this will happen again.
You can also check if the cpu temp will be displayed correctly with Cpu Temperature
https://play.google.com/store/apps/details?id=com.yanyan.cputemp&hl=de

I already have cputemp running,as far as I can notice the displayed temperature always feels correct. The phone was in a unheated room last night, ambient temperature about 10-12 degrees celcius.
I use DS-batterysaver to put the phone in deep sleep at night.
So in my eyes the low temperature is not that strange, but I might be wrong there.


Sent from my lazy chair using Tapatalk

 

[derulf]

also want to report that there are several errors caused by mtp host closed, dont know if that is cm14 alpha related... just for info, my charge port is broken, its the 3rd and this time its just not working for usb connections anymore, so i only use it for charging, charging works still fine this time ... but i had no errors or they where not visible in cm 13.

 

[bauner]

It should be like this

Instead of showing like this

Ok now I see what you mean.
It will be fixed in the next version.

I already have cputemp running,as far as I can notice the displayed temperature always feels correct. The phone was in a unheated room last night, ambient temperature about 10-12 degrees celcius.
I use DS-batterysaver to put the phone in deep sleep at night.
So in my eyes the low temperature is not that strange, but I might be wrong there.


Sent from my lazy chair using Tapatalk

This could be the reason

also want to report that there are several errors caused by mtp host closed, dont know if that is cm14 alpha related... just for info, my charge port is broken, its the 3rd and this time its just not working for usb connections anymore, so i only use it for charging, charging works still fine this time ... but i had no errors or they where not visible in cm 13.

The message mtp host close in some conditions is currently cm14.1 related.
But the mtp mode should work without problems

 

[meet30997]

HOW TO GET GOOGLE ASSISTANCE IS THIS POSSIBLE?:angel:

 

[bauner]

HOW TO GET GOOGLE ASSISTANCE IS THIS POSSIBLE?:angel:

http://forum.xda-developers.com/showpost.php?p=69138123&postcount=134

 

[derulf]

http://forum.xda-developers.com/showpost.php?p=69138123&postcount=134

I have google assistant running.
Only i am afraid that it has no access to sd0
the setup assistant is always starting new, tried everything - no success.