[ROM][UNOFFICIAL][P][F500,LS991,H81x,US991,VS986] LineageOS 16.0

[owlery_hk]

What do mean by "CPU hot plugging seems not to be working for me"?
A logcat is useful only before and while the issue happens.



Sent from my OnePlus 6T using XDA Labs

https://paste.ubuntu.com/p/hHnYsxNRt2/
Here.
I managed to recreate the issue twice, once at ~1207 once at ~1228.
The first one did not have problem with the no sim card issue.

Re: CPU hot plugging, I used smartpack kernel manager to see CPU times, and found that the small clusters and big clusters have the same up time?

 

[Pyrocks]

I am also with the calm down build. The google app doesn't work well like in previous build and chrome is sluggish when viewing videos. Also experienced system lockups once or twice.
Memory intensive apps like pokemon go and gmail cause recent apps button to take a while to respond.

 

[steadfasterX]

https://paste.ubuntu.com/p/hHnYsxNRt2/
Here.
I managed to recreate the issue twice, once at ~1207 once at ~1228.
The first one did not have problem with the no sim card issue.

Re: CPU hot plugging, I used smartpack kernel manager to see CPU times, and found that the small clusters and big clusters have the same up time?

well

1. we get issues when you have high priority apps watching CPU while doing CPU intensive tasks. Why? The LMK will try to free up memory and cannot kill the CPU monitor app, which then leads to system crashes as it might kill other processes unexpectly. So the very first thing here is stop using CPU monitoring apps and instead go to my previous post and monitor by ADB. Idc about what an app is saying about cpu up time as you can see the hotplug actions live via my adb cmd.

2. you have XPOSED stuff installed getting a lot of denials, some were selinux the others are system strictmode related. all of them cause: lagging, sim issues, other issues. so stop using xposed or you need to use an insecure build with strictmode off and selinux permissive.


The above goes to you all as I repeatedly see stuff like that.



.-

 

[owlery_hk]

well

1. we get issues when you have high priority apps watching CPU while doing CPU intensive tasks. Why? The LMK will try to free up memory and cannot kill the CPU monitor app, which then leads to system crashes as it might kill other processes unexpectly. So the very first thing here is stop using CPU monitoring apps and instead go to my previous post and monitor by ADB. Idc about what an app is saying about cpu up time as you can see the hotplug actions live via my adb cmd.

2. you have XPOSED stuff installed getting a lot of denials, some were selinux the others are system strictmode related. all of them cause: lagging, sim issues, other issues. so stop using xposed or you need to use an insecure build with strictmode off and selinux permissive.


The above goes to you all as I repeatedly see stuff like that.



.-

thanks for that. more reading to do then!

 

[lgg4-user]

Just had a camera crash with the calmdown build. Froze during a video call, and then after that opening the camera up meant it was jammed so you could only see the first frame on the screen (and not capture anything). Had to reboot to get it going again. Sorry –*couldn't get a log while I was on the call.

 

[steadfasterX]

Just had a camera crash with the calmdown build. Froze during a video call, and then after that opening the camera up meant it was jammed so you could only see the first frame on the screen (and not capture anything). Had to reboot to get it going again. Sorry –*couldn't get a log while I was on the call.

yes these camera freezes are a different thing and camera related.. I still trying to identify the root-cause but it can be re-produced easily by starting a video recording for a long time (>10min) or quickly by heavily flipping the phone around for a while during a video recording: after some seconds it freezes.

again this happens on all builds not just the calmdown one..

.-

 

[lgg4-user]

Ah OK! If I can replicate it then later on today I shall get it logging and try have a go at crashing it! Might be that other builds have seemed better to me on this front just by chance.

I haven noticed no heat issues with this build. (On the WhatsApp call there was the camera crash but no heating.)

 

[Knowbody42]

I've got this installed on an H815, and I'm trying to get MicroG to work properly.

Under self check for MicroG, it's got:
System has signature spoofing support: ticked
System grants signature spoofing permissions: ticked
System spoofs signature: unticked

I have tried deodexing it, as well as granting these permissions in a terminal:

su
pm grant com.android.vending android.permission.FAKE_PACKAGE_SIGNATURE
pm grant com.google.android.gms android.permission.FAKE_PACKAGE_SIGNATURE

 

[ThePsymoon]

I've got this installed on an H815, and I'm trying to get MicroG to work properly.

Under self check for MicroG, it's got:
System has signature spoofing support: ticked
System grants signature spoofing permissions: ticked
System spoofs signature: unticked

I have tried deodexing it, as well as granting these permissions in a terminal:

Did you install microg apk in /system/priv-app/ as explained in FAQ#9? If I remember correctly, it solved the issue for me?

 

[Knowbody42]

Did you install microg apk in /system/priv-app/ as explained in FAQ#9? If I remember correctly, it solved the issue for me?

That's where I installed MicroG.

I figured it out. In the developer options, there's a toggle to enable spoofing. Which is a bit weird, since it's separate to the option to enable spoofing in the application settings.

 

[steadfasterX]

That's where I installed MicroG.

I figured it out. In the developer options, there's a toggle to enable spoofing. Which is a bit weird, since it's separate to the option to enable spoofing in the application settings.

Well . All that is described in the faq. And its not weird it's for a reason . Not everyone want to use microG and so enabling spoofing support must be granted separately for security reasons.

Here more background details about it:
https://github.com/steadfasterX/android_signature_spoofing
https://github.com/Suicide-Squirrel/issues_pie/issues/30

Edit:

Added FAQ #11 as an extension to FAQ 9


Sent from my OnePlus 6T using XDA Labs

 

[Gigio755]

Partial OT:
i found working great with this rom, this google camera port trCamera_V5.apk, finally videos are shown in gallery and you have also a lots of settings and advanced settings, remember to disable 2x and wide camera (in advanced settings) to avoid accidental touch and crashing camera app (just this)

if you have a good experience, it might be useful to integrate it instead of the original camera LOS app (maybe)

 

[lgg4-user]

Not noticed any freezing with the calmdown built over the last few days. Camera issues I already mentioned aside it's running very nicely. I am using Footej camera –*great to have manual control. It's not always super responsive but it's doing a good job. (Still getting green images instead of actual capture sometimes.)

 

[Chris_Za]

Hi, first of all thank you for your amazing job @steadfasterX, I follow G4 roms (and test in my H815 as my daily phone) from years ago...
So I follow this rom and the different builds from a couple of months.
Now I'm on 23032020 ( stable not experiments) and every build Pie I've tested I have the same problem: my phone after a reboot or shutdown, when it's turn on the SIM doesn't work, after many reboots and some prayers it works ok.
I've the same problem years ago with first oreo build... So when camera start freezing using whatsapp videocall and I must to reboot the phone for ripristinate camera I spend so many time to do some reboot before SIM start working.
Is there any solution? Obviusly in my h815 I installed the rom with Full clean Install.

So I have another problem with every Pie rom I've tested: when I editate an Instagram Stories before Publishing it if I stay in this "screen" for many time the phone burn and it reboot.

Sorry for bad english I try my best for explain the issue! If you want logs I can made it but before I've want to say this by words.
Thank you!

 

[steadfasterX]

Hi, first of all thank you for your amazing job @steadfasterX, I follow G4 roms (and test in my H815 as my daily phone) from years ago...
So I follow this rom and the different builds from a couple of months.
Now I'm on 23032020 ( stable not experiments) and every build Pie I've tested I have the same problem: my phone after a reboot or shutdown, when it's turn on the SIM doesn't work, after many reboots and some prayers it works ok.
I've the same problem years ago with first oreo build... So when camera start freezing using whatsapp videocall and I must to reboot the phone for ripristinate camera I spend so many time to do some reboot before SIM start working.
Is there any solution? Obviusly in my h815 I installed the rom with Full clean Install.

So I have another problem with every Pie rom I've tested: when I editate an Instagram Stories before Publishing it if I stay in this "screen" for many time the phone burn and it reboot.

Sorry for bad english I try my best for explain the issue! If you want logs I can made it but before I've want to say this by words.
Thank you!

how long do you wait for the SIM pin request? its a known issue that this can take some time (not more then 5min though).
other then that try the CALMDOWN build. it should at least fix the burning.

.-

 

[Chris_Za]

how long do you wait for the SIM pin request? its a known issue that this can take some time (not more then 5min though).

.-

I disable PIN on my SIM many years ago, so sometimes when I restart it I don't touch the phone for a while (ex. when I'm at home and I don't need to use it right away) but even in these circumstances the sim is not read.
I remember that on the oreo build there was a command from the terminal to restart that process, I would not be wrong, however if this possibility exists I could still use it without problems as a temporary solution.

other then that try the CALMDOWN build. it should at least fix the burning.

.-

Thanks a lot, I had missed that build or rather I confused it with an experimental one.
I will try it soon

 

[steadfasterX]

I disable PIN on my SIM many years ago, so sometimes when I restart it I don't touch the phone for a while (ex. when I'm at home and I don't need to use it right away) but even in these circumstances the sim is not read.
I remember that on the oreo build there was a command from the terminal to restart that process, I would not be wrong, however if this possibility exists I could still use it without problems as a temporary solution.



Thanks a lot, I had missed that build or rather I confused it with an experimental one.
I will try it soon

well.. you have to set a SIM pin in order to make it work then. the watchdog listens for the PIN request and if you do not have a pin set it might / likely fail.

.-

 

[Chris_Za]

Oh damn, I would never have thought of that.
Thank you so much

 

[tullyp]

Will work on some Verizon phones, but recent problem with Caller ID

Hi All, Just wanted to encourage anyone with a Verizon VS986 to at least try this ROM and see if RIL (cell calling) works on your phone. As noted early on in this thread this ROM does not generally work with Verizon phones for cell calling (or any custom ROM). While this was a documented problem that has not been solved for all, I for one have a Verizon phone working. Worked with build Lineage-16.0-20191106, TWRP-3.3.1-..207_g4, nano gapps, and addonsu I have had service since November of last year. I just did a "dirty flash" to latest version 16.0-20200324, with TWRP 211_g4, and it still works .

I only updated to latest version because, about two weeks ago all Verizon service went down in my area, and Verizon insisted it was my phone's problem instead of their system (they were wrong). So they insisted I needed to do a factory reset and I did. After this reset my phone shows all incoming calls that are not in my contact list as "unknown" . So I updated Build hoping to fix this. Did not fix. I don't see anywhere in the ROM where caller ID is activated or blocked. Any help appreciated for this one issue.
Other than this recent problem, phone has worked flawlessly and runs much cooler and faster that stock.
tullyp

 

[Knowbody42]

OK, I have MicroG set up on my phone, and the Play Store works. But the phone's internal GPS doesn't seem to work.
I have location backends: DejaVu, GSM Location, Wifi Location, Nominatim Geocoder set up from F-Droid, and MicroG has ticks for everything except the last one which is "UnifiedNlp does not have Location to test Geocoder"
I have Location enabled with High Accuracy.
In SatSat, it doesn't get a fix on any satellites.

I don't know if it's the ROM, MicroG, or the phone itself.