[ROM][LineageOS13.0][Marshmallow][Android 6.0.1] NightOwl 20171029-Fixed

[tamaraxxx]

I have random crashes of my cellular connection (which require to boot), and with them I loose e.g. my XDA app login. I will do a clean install next week. But I wanted to ask: Is anyone else experiencing such crashes? Anything I should check or make sure prior to or while flashing clean?

Xda labs login failure is due to back-end problems.
I have no crashes what so ever, rock stable

Sent from my Samsung GT-N7000 using XDA Labs

 

[Gaukler_Faun]

I have random crashes of my cellular connection (which require to boot), and with them I loose e.g. my XDA app login. I will do a clean install next week. But I wanted to ask: Is anyone else experiencing such crashes? Anything I should check or make sure prior to or while flashing clean?

I also have xda login problems, but no rom related problems. All working fine since several weeks.

 

[Rivan_92]

What does "Patching system image unconditionally " mean?

I kind of always get stuck there about 2-3 minutes before it starts installing/updating the ROM. Although, the ROM seems to get installed just fine, but should I be worried?

 

[mucaco]

After some time again..Boots up to the startup screen, then just displays "Shutting Down"..have no idea what's causing the issue. Clean install does not solve the problem.Power button & battery (I read somewhere that these two stuff can cause this) is all right. Anyone have suggestions?

 

[action_papst]

After some time again..Boots up to the startup screen, then just displays "Shutting Down"..have no idea what's causing the issue. Clean install does not solve the problem.Power button & battery (I read somewhere that these two stuff can cause this) is all right. Anyone have suggestions?

Have you tried flashing clean from Odin (stock rom), the do all the root/custom recovery things and flash the rom again?

 

[IronRoo]

Xda labs login failure is due to back-end problems.
I have no crashes what so ever, rock stable

I also have xda login problems, but no rom related problems. All working fine since several weeks.

Yes I'm getting logged off every night from XDA app and have to sign back in on my S4 Mini. It's been happening in the last few days. Hope they fix it soon (Through cleared data earlier this morning, but doesn't sound like that will help if it's back end)

Sent from my Galaxy S4 Mini using XDA Labs

 

[bauner]

What does "Patching system image unconditionally " mean?

I kind of always get stuck there about 2-3 minutes before it starts installing/updating the ROM. Although, the ROM seems to get installed just fine, but should I be worried?

The updater would be able to install only the differences to the current installed rom. But this method would fail if anything on the /system partition was modified (like while installing the gapps) and it would also make it impossible to skip one version and then update to a later version.

The unconditionally way is to backup the installed gapps then install the full /system image and restore the backed up gapps.

The time before the real installing will start is the backup process

 

[m_gandalf81]

Hi, If someone has hardware failure could have a look to this logic Board:

http://www.ebay.es/itm/Samsung-Gala...201102?hash=item41b2c6188e:g:vFoAAOSwAuZX1dPy

 

[mucaco]

Have you tried flashing clean from Odin (stock rom), the do all the root/custom recovery things and flash the rom again?

Yes, certainly 10 times .Always the same thing, stock rom works well, MM not.

 

[bauner]

Yes, certainly 10 times .Always the same thing, stock rom works well, MM not.

Maybe it is really the battery??? Will it make a difference if you have connected the device to the charger?
Did you try how long the battery life is with the stock rom?

 

[mucaco]

Yes, certainly 10 times .Always the same thing, stock rom works well, MM not.

Maybe it is really the battery??? Will it make a difference if you have connected the device to the charger?
Did you try how long the battery life is with the stock rom?

It make no difference. Before they problems appeared battery life is estimated at just over 15 hours. Stock rom work perfectly, battery life is good but I do not want to go back to the Jelly Bean. I'll try some other things.Thanks

 

[bauner]

It make no difference. Before they problems appeared battery life is estimated at just over 15 hours. Stock rom work perfectly, battery life is good but I do not want to go back to the Jelly Bean. I'll try some other things.Thanks

Did you also test it with cm11 or with my cm12.1 rom?

 

[nursoda]

Concerning the SIM crashes I encounter: I now flashed clean and got the same issue. But I deleted "CellBroadcastReceiver" immediately after installation since I get notifications all the time. I suspect my deleting this app (using Total Commander with root / remount rw) causes this issue.
On the other hand I did not find a way to get rid of these extremely annoying notifications. Does anyone know how to suppress these without deleting the app? In Notification settings, I can only suppress the overlay, not the sound and the notification itself. @bauner: Please consider to add an ON/OFF "switch" for CB-Receiver - I had it in some previous ROM and it worked like a charm. Can't tell you where to look for this patch, though.
I now reflashed and did not delete it. If it happens even without deleting it, I will report back, hopefully with CatLog. I'm grateful for any other idea / suggestion on this matter.

 

[Snoere]

@nursoda: You can turn of those broadcast messages in Settings -> Wireless & Network -> More -> Emergency broadcasts. Un-check all options and reboot.
You can also read my post on Android-Hilfe.de in German.
Are you a customer of O2?

 

[bauner]

Concerning the SIM crashes I encounter: I now flashed clean and got the same issue. But I deleted "CellBroadcastReceiver" immediately after installation since I get notifications all the time. I suspect my deleting this app (using Total Commander with root / remount rw) causes this issue.
On the other hand I did not find a way to get rid of these extremely annoying notifications. Does anyone know how to suppress these without deleting the app? In Notification settings, I can only suppress the overlay, not the sound and the notification itself. @bauner: Please consider to add an ON/OFF "switch" for CB-Receiver - I had it in some previous ROM and it worked like a charm. Can't tell you where to look for this patch, though.
I now reflashed and did not delete it. If it happens even without deleting it, I will report back, hopefully with CatLog. I'm grateful for any other idea / suggestion on this matter.

Did you reboot after you deleted it?
I also delete it and I have no problems.

If it will happen again please try to get some logs with catlog (also from the radio log which you can select in the catlog settings)

 

[nursoda]

You can turn of those broadcast messages in Settings -> Wireless & Network -> More -> Emergency broadcasts. Un-check all options and reboot.

Thanks. Robooting seemed to calm them.

Are you a customer of O2?

Yes...

Did you reboot after you deleted it?

Not sure. I should have done, immediately after deleting it.

I also delete it and I have no problems.

OK! I also did this with previous versions.
I'm baffled why SIM crashes anyway.

If it will happen again please try to get some logs with catlog (also from the radio log which you can select in the catlog settings)

I will.

 

[bauner]

The 20160914 Rom is finish as OTA update and manual download

Changes:

* Merged cm changes
* September security patches

 

[jerryhou85]

Process system is not responding. Do you want to close it? <WAIT> <OK>

I've got this error when doing a cold reboot (totally power off for a few days and power on). I can still see the launcher and every app on desktop, phone was functioning totally normal in all other aspects.
Process system is not responding. Do you want to close it? <WAIT> <OK>

Usually I click Wait, and nothing really happens, I don't feel any difference. If I do a reboot now, this error message will not show up at all.
Has anyone ever encountered this? It is not a big deal for me, just want to know why.
By the way, I use OTA update for the last August update and notice this. I kind of remember that when I did clean install, the same error sometimes was there too.

 

[svbarbosa]

I've got this error when doing a cold reboot (totally power off for a few days and power on). I can still see the launcher and every app on desktop, phone was functioning totally normal in all other aspects.
Process system is not responding. Do you want to close it? <WAIT> <OK>

Usually I click Wait, and nothing really happens, I don't feel any difference. If I do a reboot now, this error message will not show up at all.
Has anyone ever encountered this? It is not a big deal for me, just want to know why.
By the way, I use OTA update for the last August update and notice this. I kind of remember that when I did clean install, the same error sometimes was there too.

Nothing to worry about. Perfectly normal if you have to hit wait just once.

 

[William Haven]

Anyone having issues running the latest pokemon go update (0.37) running NightOwl with root disabled?