[ROM][UNOFFICIAL] LineageOS 19.1 for Nexus 6

Search This thread

obitest11

New member
May 17, 2022
2
1
  • Like
Reactions: spiral777

rootfan

Senior Member
Jul 20, 2011
206
244
Would you please push all commits needed for lineage-19.1 to compile to your repo?
TotalChen, I've pushed all of my changes to github. You can now set things up by running repo init -u https://github.com/rootfan/android.git -b shamu-19.1, making a local_manifests dir in .repo, and copying the attached roomservice.xml into it. I've also modified ims.apk and libcne.so since the last release and attached them below in the updated_blobs.zip. You'll need to replace the existing ones in vendor/motorola/shamu after running extract-files.sh.
 

Attachments

  • updated_blobs.zip
    236.7 KB · Views: 4
  • roomservice.xml
    556 bytes · Views: 5
  • Like
Reactions: Armentanzirian

akastixx

Senior Member
Nov 4, 2007
318
40
I'm having a problem where if the phone dies or restarts for any other reason besides restarting from the menu, my data and Wi-Fi will say connected, but I will not get any data. I have to reset Wi-Fi, Bluetooth and Data in settings, and restart the phone. If I don't restart the phone, the problem still persists. The phone usually restarts once or twice a day for whatever reason. I've recently replaced the battery, and that has given this phone a new breath of life, but pairing my Bluetooth over and over and reconnecting to my Wi-Fi isn't the best. I've even tried going back to TWRP, wiping everything that isn't internal storage, and reflashing, and then reflashing mind the gapps.

Thanks in advance for any advice.

Edit: I had the May version installed while I was waiting for the battery. I will try the June version and report back. I was using March's TWRP, but I will update to the June version, too.

Edit 2: nope, updating TWRP and lineage still gives me the same issue. The phone will get taxed in some type of way to do a soft reset, and when it comes back up, there will be an exclamation point over the Wi-Fi signal icon, it will say it is connected, but no data. If I turn off Wi-Fi, there will be an exclamation point over my data bars. I will have to reset the settings, restart the phone, and enter in the Wi-Fi password and pair my BT stuff again.

Screenshot_1970-01-01-09-19-55.png
 

Attachments

  • Screenshot_1970-01-01-09-20-50.png
    Screenshot_1970-01-01-09-20-50.png
    101.9 KB · Views: 27
Last edited:

TotalChen

Member
Dec 11, 2016
38
34
TotalChen, I've pushed all of my changes to github. You can now set things up by running repo init -u https://github.com/rootfan/android.git -b shamu-19.1, making a local_manifests dir in .repo, and copying the attached roomservice.xml into it. I've also modified ims.apk and libcne.so since the last release and attached them below in the updated_blobs.zip. You'll need to replace the existing ones in vendor/motorola/shamu after running extract-files.sh.
rootfan, I really appreciate that, this is the greatest news I've ever heard these days. I'll try it. So many big thanks for keeping this killing whale alive!
 

akastixx

Senior Member
Nov 4, 2007
318
40
The phone will get taxed in some type of way to do a soft reset, and when it comes back up, there will be an exclamation point over the Wi-Fi signal icon, it will say it is connected, but no data. If I turn off Wi-Fi, there will be an exclamation point over my data bars. I will have to reset the settings, restart the phone, and enter in the Wi-Fi password and pair my BT stuff again.
Anyone? 😭
Thanks in advance
 

whathaveibecome

New member
Jul 16, 2022
3
0
This is GREAT! It works perfect so far on my N6 although It has long been relegated to only being used as a gps on my motorcycle. Though honestly it runs so good I am considering switching back to the N6 as my main phone.

I was wondering if anyone would consider enabling signature spoofing? I know LOS devs won't consider it, but perhaps one of you will?

And as already mentioned (but not adressed) the advanced restart menu option is missing.

Other then that, it's amazing that Android 12 is running at all on this old behemoth, never mind that it's actually running smoothly!

I really hope lineageOS devs see this and take note!
 

rootfan

Senior Member
Jul 20, 2011
206
244
New build 2022-7-15:
  • Updated with the latest LineageOS changes including the July security update
  • Selinux is now enforcing
  • Added signature spoofing support for microG
  • Signed with private keys (make sure to read the installation note in the original post)
 

pikebucaro

New member
Sep 5, 2015
1
0
the rom is excellent, the only detail is that my screen turns off when making a call, is it a bug or my phone broke?
 

pyrotf2

New member
Jul 29, 2022
1
0
Hey wanted to drop a bug report. I attempted to encrypt my Nexus 6, but it hanged on the 00:00 remaining for several hours. Had to do a shutdown, but the system wouldn't boot into safe mode either-- would just stay on a bootloop of the lineage logo in either boot sequence after I entered my password.

Another thing regarding the password: Android would accept it and throw me into the bootloop (I attempted an incorrect password, which failed). However, when I try to decrypt the system in TWRP, the password isn't being accepted.

I also cannot launch an adb shell, but the device is listed on adb.

EDIT: I also wanted to mention I made a mistake of doing the encryption after several days of use on the device and NOT following a fresh install.

EDIT AGAIN: I gave up on the little data I had on the device (mostly bummed I'm going to have to redo my personalization). I wiped the device, and on the first boot, I attempted to encrypt again. It encrypted in a few quick minutes and one reboot. Anyways, it booted normally and even confirmed the phone was encrypted in settings. I decided to do a reboot and once that happened, I ran into my old bootloop problem mentioned above that even safe mode couldn't budge.
 
Last edited:

TotalChen

Member
Dec 11, 2016
38
34
Is it normal to have these logs spams?

Code:
07-29 09:18:35.070 E/RIL-MOTEXT(  686): mothook_oem: header type 0, requestCode 0x0
07-29 09:18:35.071 E/RIL-MOTEXT(  686): Write Ril Request 59
07-29 09:18:35.071 E/RIL-MOTEXT(  686): Process request 59, len=9
07-29 09:18:35.071 E/RIL-MOTEXT(  730): Read 9 bytes from pipe
07-29 09:18:35.071 E/RIL-MOTEXT(  730): msg Id is 0x5001e, type is 1.
07-29 09:18:35.071 E/RIL-MOTEXT(  730): Received Generic Hook request 0x1e0005
07-29 09:18:35.072 E/RIL-MOTEXT(  730): sys_info filter: sending motext util request
07-29 09:18:35.139 E/RIL-MOTEXT(  730): sys_info filter: sending request result is 0
07-29 09:18:35.139 E/RIL-MOTEXT(  730): sys_info filter: sending response, msgLen 0x1, resp value 0.
07-29 09:18:35.139 E/RIL-MOTEXT(  730): Child process waiting for data
07-29 09:18:35.140 E/RIL-MOTEXT(  686): CallRequestComplete buf size=9
07-29 09:18:35.140 E/RIL-MOTEXT(  686): CallRequestComplete msgId=0x5001e, headerType=1
07-29 09:18:35.140 E/RIL-MOTEXT(  686): handle generic response, motext msg len, 1
07-29 09:18:35.140 E/RIL-MOTEXT(  686): CallRequestComplete generic success,  responseLen=1
07-29 09:18:35.140 E/RIL-MOTEXT(  686): Finished processing onRequestComplete
07-29 09:18:35.140 E/RIL-MOTEXT(  686): CommThread Waiting for ril request
07-29 09:18:39.071 E/RIL-MOTEXT(  686): mothook_oem: header type 0, requestCode 0x0
07-29 09:18:39.071 E/RIL-MOTEXT(  686): Write Ril Request 59
07-29 09:18:39.071 E/RIL-MOTEXT(  686): Process request 59, len=9
07-29 09:18:39.071 E/RIL-MOTEXT(  730): Read 9 bytes from pipe
07-29 09:18:39.072 E/RIL-MOTEXT(  730): msg Id is 0x5001e, type is 1.
07-29 09:18:39.072 E/RIL-MOTEXT(  730): Received Generic Hook request 0x1e0005
07-29 09:18:39.072 E/RIL-MOTEXT(  730): sys_info filter: sending motext util request
07-29 09:18:39.144 E/RIL-MOTEXT(  730): sys_info filter: sending request result is 0
07-29 09:18:39.144 E/RIL-MOTEXT(  730): sys_info filter: sending response, msgLen 0x1, resp value 0.
07-29 09:18:39.144 E/RIL-MOTEXT(  730): Child process waiting for data
07-29 09:18:39.144 E/RIL-MOTEXT(  686): CallRequestComplete buf size=9
07-29 09:18:39.144 E/RIL-MOTEXT(  686): CallRequestComplete msgId=0x5001e, headerType=1
07-29 09:18:39.145 E/RIL-MOTEXT(  686): handle generic response, motext msg len, 1
07-29 09:18:39.145 E/RIL-MOTEXT(  686): CallRequestComplete generic success,  responseLen=1
07-29 09:18:39.145 E/RIL-MOTEXT(  686): Finished processing onRequestComplete
07-29 09:18:39.145 E/RIL-MOTEXT(  686): CommThread Waiting for ril request
07-29 09:18:51.438 E/RIL-MOTEXT(  686): mothook_oem: header type 0, requestCode 0x0
07-29 09:18:51.438 E/RIL-MOTEXT(  686): Write Ril Request 59
07-29 09:18:51.439 E/RIL-MOTEXT(  686): Process request 59, len=9
07-29 09:18:51.439 E/RIL-MOTEXT(  730): Read 9 bytes from pipe
07-29 09:18:51.439 E/RIL-MOTEXT(  730): msg Id is 0x5001e, type is 1.
07-29 09:18:51.439 E/RIL-MOTEXT(  730): Received Generic Hook request 0x1e0005
07-29 09:18:51.439 E/RIL-MOTEXT(  730): sys_info filter: sending motext util request
07-29 09:18:51.509 E/RIL-MOTEXT(  730): sys_info filter: sending request result is 0
07-29 09:18:51.509 E/RIL-MOTEXT(  730): sys_info filter: sending response, msgLen 0x1, resp value 0.
07-29 09:18:51.509 E/RIL-MOTEXT(  730): Child process waiting for data
07-29 09:18:51.509 E/RIL-MOTEXT(  686): CallRequestComplete buf size=9
07-29 09:18:51.509 E/RIL-MOTEXT(  686): CallRequestComplete msgId=0x5001e, headerType=1
07-29 09:18:51.509 E/RIL-MOTEXT(  686): handle generic response, motext msg len, 1
07-29 09:18:51.509 E/RIL-MOTEXT(  686): CallRequestComplete generic success,  responseLen=1
07-29 09:18:51.509 E/RIL-MOTEXT(  686): Finished processing onRequestComplete
07-29 09:18:51.509 E/RIL-MOTEXT(  686): CommThread Waiting for ril request
07-29 09:19:52.677 E/RIL-MOTEXT(  686): mothook_oem: header type 0, requestCode 0x0
07-29 09:19:52.677 E/RIL-MOTEXT(  686): Write Ril Request 59
07-29 09:19:52.677 E/RIL-MOTEXT(  686): Process request 59, len=9
07-29 09:19:52.679 E/RIL-MOTEXT(  730): Read 9 bytes from pipe
07-29 09:19:52.679 E/RIL-MOTEXT(  730): msg Id is 0x5001e, type is 1.
07-29 09:19:52.679 E/RIL-MOTEXT(  730): Received Generic Hook request 0x1e0005
07-29 09:19:52.679 E/RIL-MOTEXT(  730): sys_info filter: sending motext util request
07-29 09:19:52.752 E/RIL-MOTEXT(  730): sys_info filter: sending request result is 0
07-29 09:19:52.752 E/RIL-MOTEXT(  730): sys_info filter: sending response, msgLen 0x1, resp value 0.
07-29 09:19:52.752 E/RIL-MOTEXT(  730): Child process waiting for data
07-29 09:19:52.752 E/RIL-MOTEXT(  686): CallRequestComplete buf size=9
07-29 09:19:52.752 E/RIL-MOTEXT(  686): CallRequestComplete msgId=0x5001e, headerType=1
07-29 09:19:52.752 E/RIL-MOTEXT(  686): handle generic response, motext msg len, 1
07-29 09:19:52.752 E/RIL-MOTEXT(  686): CallRequestComplete generic success,  responseLen=1
07-29 09:19:52.752 E/RIL-MOTEXT(  686): Finished processing onRequestComplete
07-29 09:19:52.752 E/RIL-MOTEXT(  686): CommThread Waiting for ril request
07-29 09:19:59.023 E/RIL-MOTEXT(  686): mothook_oem: header type 0, requestCode 0x0
07-29 09:19:59.023 E/RIL-MOTEXT(  686): Write Ril Request 59
07-29 09:19:59.024 E/RIL-MOTEXT(  686): Process request 59, len=9
07-29 09:19:59.024 E/RIL-MOTEXT(  730): Read 9 bytes from pipe
07-29 09:19:59.024 E/RIL-MOTEXT(  730): msg Id is 0x5001e, type is 1.
07-29 09:19:59.024 E/RIL-MOTEXT(  730): Received Generic Hook request 0x1e0005
07-29 09:19:59.024 E/RIL-MOTEXT(  730): sys_info filter: sending motext util request
07-29 09:19:59.093 E/RIL-MOTEXT(  730): sys_info filter: sending request result is 0
07-29 09:19:59.093 E/RIL-MOTEXT(  730): sys_info filter: sending response, msgLen 0x1, resp value 0.
07-29 09:19:59.093 E/RIL-MOTEXT(  730): Child process waiting for data
07-29 09:19:59.093 E/RIL-MOTEXT(  686): CallRequestComplete buf size=9
07-29 09:19:59.093 E/RIL-MOTEXT(  686): CallRequestComplete msgId=0x5001e, headerType=1
07-29 09:19:59.093 E/RIL-MOTEXT(  686): handle generic response, motext msg len, 1
07-29 09:19:59.093 E/RIL-MOTEXT(  686): CallRequestComplete generic success,  responseLen=1
07-29 09:19:59.093 E/RIL-MOTEXT(  686): Finished processing onRequestComplete
07-29 09:19:59.093 E/RIL-MOTEXT(  686): CommThread Waiting for ril request
07-29 09:21:44.824 E/RIL-MOTEXT(  686): mothook_oem: header type 0, requestCode 0x0
07-29 09:21:44.824 E/RIL-MOTEXT(  686): Write Ril Request 59
07-29 09:21:44.824 E/RIL-MOTEXT(  686): Process request 59, len=9
07-29 09:21:44.824 E/RIL-MOTEXT(  730): Read 9 bytes from pipe
07-29 09:21:44.824 E/RIL-MOTEXT(  730): msg Id is 0x5001e, type is 1.
07-29 09:21:44.824 E/RIL-MOTEXT(  730): Received Generic Hook request 0x1e0005
07-29 09:21:44.824 E/RIL-MOTEXT(  730): sys_info filter: sending motext util request
07-29 09:21:44.892 E/RIL-MOTEXT(  730): sys_info filter: sending request result is 0
07-29 09:21:44.892 E/RIL-MOTEXT(  730): sys_info filter: sending response, msgLen 0x1, resp value 0.
07-29 09:21:44.893 E/RIL-MOTEXT(  730): Child process waiting for data
07-29 09:21:44.893 E/RIL-MOTEXT(  686): CallRequestComplete buf size=9
07-29 09:21:44.893 E/RIL-MOTEXT(  686): CallRequestComplete msgId=0x5001e, headerType=1
07-29 09:21:44.893 E/RIL-MOTEXT(  686): handle generic response, motext msg len, 1
07-29 09:21:44.893 E/RIL-MOTEXT(  686): CallRequestComplete generic success,  responseLen=1
07-29 09:21:44.893 E/RIL-MOTEXT(  686): Finished processing onRequestComplete
07-29 09:21:44.893 E/RIL-MOTEXT(  686): CommThread Waiting for ril request
07-29 09:21:51.085 E/RIL-MOTEXT(  686): mothook_oem: header type 0, requestCode 0x0
07-29 09:21:51.085 E/RIL-MOTEXT(  686): Write Ril Request 59
07-29 09:21:51.086 E/RIL-MOTEXT(  686): Process request 59, len=9
07-29 09:21:51.086 E/RIL-MOTEXT(  730): Read 9 bytes from pipe
07-29 09:21:51.086 E/RIL-MOTEXT(  730): msg Id is 0x5001e, type is 1.
07-29 09:21:51.086 E/RIL-MOTEXT(  730): Received Generic Hook request 0x1e0005
07-29 09:21:51.086 E/RIL-MOTEXT(  730): sys_info filter: sending motext util request
07-29 09:21:51.158 E/RIL-MOTEXT(  730): sys_info filter: sending request result is 0
07-29 09:21:51.158 E/RIL-MOTEXT(  730): sys_info filter: sending response, msgLen 0x1, resp value 0.
07-29 09:21:51.158 E/RIL-MOTEXT(  730): Child process waiting for data
07-29 09:21:51.159 E/RIL-MOTEXT(  686): CallRequestComplete buf size=9
07-29 09:21:51.159 E/RIL-MOTEXT(  686): CallRequestComplete msgId=0x5001e, headerType=1
07-29 09:21:51.159 E/RIL-MOTEXT(  686): handle generic response, motext msg len, 1
07-29 09:21:51.159 E/RIL-MOTEXT(  686): CallRequestComplete generic success,  responseLen=1
07-29 09:21:51.159 E/RIL-MOTEXT(  686): Finished processing onRequestComplete
07-29 09:21:51.159 E/RIL-MOTEXT(  686): CommThread Waiting for ril request
07-29 09:23:37.756 E/RIL-MOTEXT(  686): mothook_oem: header type 0, requestCode 0x0
07-29 09:23:37.756 E/RIL-MOTEXT(  686): Write Ril Request 59
07-29 09:23:37.756 E/RIL-MOTEXT(  686): Process request 59, len=9
07-29 09:23:37.756 E/RIL-MOTEXT(  730): Read 9 bytes from pipe
07-29 09:23:37.757 E/RIL-MOTEXT(  730): msg Id is 0x5001e, type is 1.
07-29 09:23:37.757 E/RIL-MOTEXT(  730): Received Generic Hook request 0x1e0005
07-29 09:23:37.757 E/RIL-MOTEXT(  730): sys_info filter: sending motext util request
07-29 09:23:37.825 E/RIL-MOTEXT(  730): sys_info filter: sending request result is 0
07-29 09:23:37.825 E/RIL-MOTEXT(  730): sys_info filter: sending response, msgLen 0x1, resp value 0.
07-29 09:23:37.825 E/RIL-MOTEXT(  730): Child process waiting for data
07-29 09:23:37.825 E/RIL-MOTEXT(  686): CallRequestComplete buf size=9
07-29 09:23:37.825 E/RIL-MOTEXT(  686): CallRequestComplete msgId=0x5001e, headerType=1
07-29 09:23:37.825 E/RIL-MOTEXT(  686): handle generic response, motext msg len, 1
07-29 09:23:37.825 E/RIL-MOTEXT(  686): CallRequestComplete generic success,  responseLen=1
07-29 09:23:37.825 E/RIL-MOTEXT(  686): Finished processing onRequestComplete
07-29 09:23:37.825 E/RIL-MOTEXT(  686): CommThread Waiting for ril request
07-29 09:23:44.049 E/RIL-MOTEXT(  686): mothook_oem: header type 0, requestCode 0x0
07-29 09:23:44.049 E/RIL-MOTEXT(  686): Write Ril Request 59
07-29 09:23:44.049 E/RIL-MOTEXT(  686): Process request 59, len=9
07-29 09:23:44.050 E/RIL-MOTEXT(  730): Read 9 bytes from pipe
07-29 09:23:44.050 E/RIL-MOTEXT(  730): msg Id is 0x5001e, type is 1.
07-29 09:23:44.050 E/RIL-MOTEXT(  730): Received Generic Hook request 0x1e0005
07-29 09:23:44.050 E/RIL-MOTEXT(  730): sys_info filter: sending motext util request
07-29 09:23:44.125 E/RIL-MOTEXT(  730): sys_info filter: sending request result is 0
07-29 09:23:44.125 E/RIL-MOTEXT(  730): sys_info filter: sending response, msgLen 0x1, resp value 0.
07-29 09:23:44.125 E/RIL-MOTEXT(  730): Child process waiting for data
07-29 09:23:44.125 E/RIL-MOTEXT(  686): CallRequestComplete buf size=9
07-29 09:23:44.125 E/RIL-MOTEXT(  686): CallRequestComplete msgId=0x5001e, headerType=1
07-29 09:23:44.125 E/RIL-MOTEXT(  686): handle generic response, motext msg len, 1
07-29 09:23:44.125 E/RIL-MOTEXT(  686): CallRequestComplete generic success,  responseLen=1
07-29 09:23:44.125 E/RIL-MOTEXT(  686): Finished processing onRequestComplete
07-29 09:23:44.125 E/RIL-MOTEXT(  686): CommThread Waiting for ril request
07-29 09:24:21.287 E/RIL-MOTEXT(  686): mothook_oem: header type 0, requestCode 0x0
07-29 09:24:21.287 E/RIL-MOTEXT(  686): Write Ril Request 59
07-29 09:24:21.287 E/RIL-MOTEXT(  686): Process request 59, len=9
07-29 09:24:21.288 E/RIL-MOTEXT(  730): Read 9 bytes from pipe
07-29 09:24:21.288 E/RIL-MOTEXT(  730): msg Id is 0x5001e, type is 1.
07-29 09:24:21.288 E/RIL-MOTEXT(  730): Received Generic Hook request 0x1e0005
07-29 09:24:21.288 E/RIL-MOTEXT(  730): sys_info filter: sending motext util request
07-29 09:24:21.357 E/RIL-MOTEXT(  730): sys_info filter: sending request result is 0
07-29 09:24:21.357 E/RIL-MOTEXT(  730): sys_info filter: sending response, msgLen 0x1, resp value 0.
07-29 09:24:21.357 E/RIL-MOTEXT(  730): Child process waiting for data
07-29 09:24:21.357 E/RIL-MOTEXT(  686): CallRequestComplete buf size=9
07-29 09:24:21.357 E/RIL-MOTEXT(  686): CallRequestComplete msgId=0x5001e, headerType=1
07-29 09:24:21.357 E/RIL-MOTEXT(  686): handle generic response, motext msg len, 1
07-29 09:24:21.357 E/RIL-MOTEXT(  686): CallRequestComplete generic success,  responseLen=1
07-29 09:24:21.357 E/RIL-MOTEXT(  686): Finished processing onRequestComplete
07-29 09:24:21.357 E/RIL-MOTEXT(  686): CommThread Waiting for ril request
07-29 09:24:23.210 E/HWComposer(  313): getSupportedContentTypes: getSupportedContentTypes failed for display 0: Unsupported (8)
07-29 09:24:23.792 E/RIL-MOTEXT(  686): mothook_oem: header type 0, requestCode 0x0
07-29 09:24:23.792 E/RIL-MOTEXT(  686): Write Ril Request 59
07-29 09:24:23.792 E/RIL-MOTEXT(  686): Process request 59, len=9
07-29 09:24:23.792 E/RIL-MOTEXT(  730): Read 9 bytes from pipe
07-29 09:24:23.792 E/RIL-MOTEXT(  730): msg Id is 0x5001e, type is 1.
07-29 09:24:23.792 E/RIL-MOTEXT(  730): Received Generic Hook request 0x1e0005
07-29 09:24:23.792 E/RIL-MOTEXT(  730): sys_info filter: sending motext util request
07-29 09:24:23.862 E/RIL-MOTEXT(  730): sys_info filter: sending request result is 0
07-29 09:24:23.862 E/RIL-MOTEXT(  730): sys_info filter: sending response, msgLen 0x1, resp value 0.
07-29 09:24:23.862 E/RIL-MOTEXT(  730): Child process waiting for data
07-29 09:24:23.862 E/RIL-MOTEXT(  686): CallRequestComplete buf size=9
07-29 09:24:23.862 E/RIL-MOTEXT(  686): CallRequestComplete msgId=0x5001e, headerType=1
07-29 09:24:23.862 E/RIL-MOTEXT(  686): handle generic response, motext msg len, 1
07-29 09:24:23.862 E/RIL-MOTEXT(  686): CallRequestComplete generic success,  responseLen=1
07-29 09:24:23.862 E/RIL-MOTEXT(  686): Finished processing onRequestComplete
07-29 09:24:23.862 E/RIL-MOTEXT(  686): CommThread Waiting for ril request
07-29 09:24:26.083 E/RIL-MOTEXT(  686): mothook_oem: header type 0, requestCode 0x0
07-29 09:24:26.083 E/RIL-MOTEXT(  686): Write Ril Request 59
07-29 09:24:26.084 E/RIL-MOTEXT(  686): Process request 59, len=9
07-29 09:24:26.084 E/RIL-MOTEXT(  730): Read 9 bytes from pipe
07-29 09:24:26.084 E/RIL-MOTEXT(  730): msg Id is 0x5001e, type is 1.
07-29 09:24:26.084 E/RIL-MOTEXT(  730): Received Generic Hook request 0x1e0005
07-29 09:24:26.084 E/RIL-MOTEXT(  730): sys_info filter: sending motext util request
07-29 09:24:26.098 E/RIL-MOTEXT(  730): sys_info filter: sending request result is 0
07-29 09:24:26.098 E/RIL-MOTEXT(  730): sys_info filter: sending response, msgLen 0x1, resp value 0.
07-29 09:24:26.098 E/RIL-MOTEXT(  730): Child process waiting for data
07-29 09:24:26.098 E/RIL-MOTEXT(  686): CallRequestComplete buf size=9
07-29 09:24:26.098 E/RIL-MOTEXT(  686): CallRequestComplete msgId=0x5001e, headerType=1
07-29 09:24:26.098 E/RIL-MOTEXT(  686): handle generic response, motext msg len, 1
07-29 09:24:26.098 E/RIL-MOTEXT(  686): CallRequestComplete generic success,  responseLen=1
07-29 09:24:26.098 E/RIL-MOTEXT(  686): Finished processing onRequestComplete
07-29 09:24:26.098 E/RIL-MOTEXT(  686): CommThread Waiting for ril request
 

TotalChen

Member
Dec 11, 2016
38
34
and kmsg spams per second like:
Code:
[17753.397752] PM: suspend entry 2022-07-29 01:22:25.332757575 UTC
[17753.397820] PM: Syncing filesystems ... done.
[17753.465112] PM: Preparing system for mem sleep
[17753.465178] Freezing user space processes ... (elapsed 0.007 seconds) done.
[17753.472624] Freezing remaining freezable tasks ... (elapsed 0.004 seconds) done.
[17753.476741] PM: Entering mem sleep
[17753.476754] Suspending console(s) (use no_console_suspend to debug)
[17753.545580] D2H_MB_DATA: D3 ACK
[17753.572067] PM: suspend of devices complete after 94.201 msecs
[17753.572881] PM: late suspend of devices complete after 0.801 msecs
[17753.575336] PM: noirq suspend of devices complete after 2.445 msecs
[17753.575445] CPU0:msm_cpu_pm_enter_sleep mode:3 during suspend
[17753.656135] PM: noirq resume of devices complete after 80.015 msecs
[17753.657392] PM: early resume of devices complete after 0.513 msecs
[17753.765380] PM: resume of devices complete after 107.972 msecs
[17753.766450] PM: Finishing wakeup.
[17753.766459] Restarting tasks ... done.
[17753.791262] Resume caused by IRQ 240, msmgpio
[17753.791283] Resume caused by IRQ 200, qcom,smd-rpm
[17753.791302] Resume caused by IRQ 440, msm_pcie_host_wake
[17753.795982] PM: suspend exit 2022-07-29 01:22:50.456649948 UTC
[17754.169350] PM: suspend entry 2022-07-29 01:22:50.829978681 UTC
[17754.169464] PM: Syncing filesystems ... done.
[17754.227636] PM: Preparing system for mem sleep
[17754.227843] Freezing user space processes ... (elapsed 0.017 seconds) done.
[17754.245957] Freezing remaining freezable tasks ... (elapsed 0.007 seconds) done.
[17754.253486] PM: Entering mem sleep
[17754.253523] Suspending console(s) (use no_console_suspend to debug)
[17754.353970] D2H_MB_DATA: D3 ACK
[17754.390862] PM: suspend of devices complete after 134.659 msecs
[17754.393574] PM: late suspend of devices complete after 2.677 msecs
[17754.399712] PM: noirq suspend of devices complete after 6.107 msecs
[17754.399966] CPU0:msm_cpu_pm_enter_sleep mode:3 during suspend
[17754.491359] PM: noirq resume of devices complete after 90.212 msecs
[17754.492711] stm401 12-0039: Deferring interrupt work
[17754.497386] PM: early resume of devices complete after 4.071 msecs
[17754.499384] stm401 12-0039: STM401 Error: 74570: modality SPI RST
[17754.644715] PM: resume of devices complete after 147.291 msecs
[17754.652708] PM: Finishing wakeup.
[17754.652735] Restarting tasks ... done.
[17754.688288] Resume caused by IRQ 240, msmgpio
[17754.688344] Resume caused by IRQ 200, qcom,smd-rpm
[17754.688395] Resume caused by IRQ 578, stm401
[17754.688738] PM: suspend exit 2022-07-29 01:22:53.705849358 UTC
[17755.496067] PM: suspend entry 2022-07-29 01:22:54.513153786 UTC
[17755.496182] PM: Syncing filesystems ... done.
[17755.554973] PM: Preparing system for mem sleep
[17755.555480] Freezing user space processes ... (elapsed 0.009 seconds) done.
[17755.565233] Freezing remaining freezable tasks ... (elapsed 0.005 seconds) done.
[17755.570596] PM: Entering mem sleep
[17755.570617] Suspending console(s) (use no_console_suspend to debug)
[17755.649989] D2H_MB_DATA: D3 ACK
[17755.680551] PM: suspend of devices complete after 108.112 msecs
[17755.682037] PM: late suspend of devices complete after 1.466 msecs
[17755.685530] PM: noirq suspend of devices complete after 3.475 msecs
[17755.685686] CPU0:msm_cpu_pm_enter_sleep mode:3 during suspend
[17755.766288] PM: noirq resume of devices complete after 79.768 msecs
[17755.767066] stm401 12-0039: Deferring interrupt work
[17755.769900] PM: early resume of devices complete after 2.122 msecs
[17755.773146] stm401 12-0039: STM401 Error: 85524: modality SPI RST
[17755.897479] PM: resume of devices complete after 127.553 msecs
[17755.899566] PM: Finishing wakeup.
[17755.899582] Restarting tasks ... done.
[17755.925242] Resume caused by IRQ 240, msmgpio
[17755.925281] Resume caused by IRQ 200, qcom,smd-rpm
[17755.925314] Resume caused by IRQ 578, stm401
[17755.925404] PM: suspend exit 2022-07-29 01:23:04.570341509 UTC
[17756.774327] PM: suspend entry 2022-07-29 01:23:05.419225961 UTC
[17756.774446] PM: Syncing filesystems ... done.
[17756.840178] PM: Preparing system for mem sleep
[17756.840348] Freezing user space processes ... (elapsed 0.007 seconds) done.
[17756.848459] Freezing remaining freezable tasks ... (elapsed 0.005 seconds) done.
[17756.853794] PM: Entering mem sleep
[17756.853809] Suspending console(s) (use no_console_suspend to debug)
[17756.924237] D2H_MB_DATA: D3 ACK
[17756.952989] PM: suspend of devices complete after 97.664 msecs
[17756.953846] PM: late suspend of devices complete after 0.839 msecs
[17756.956621] PM: noirq suspend of devices complete after 2.763 msecs
[17756.956741] CPU0:msm_cpu_pm_enter_sleep mode:3 during suspend
[17757.040290] PM: noirq resume of devices complete after 82.520 msecs
[17757.040963] stm401 12-0039: Deferring interrupt work
[17757.042310] PM: early resume of devices complete after 1.092 msecs
[17757.045789] stm401 12-0039: STM401 Error: 96481: modality SPI RST
[17757.156921] PM: resume of devices complete after 114.590 msecs
[17757.158102] PM: Finishing wakeup.
[17757.158111] Restarting tasks ... done.
[17757.176022] Resume caused by IRQ 240, msmgpio
[17757.176045] Resume caused by IRQ 200, qcom,smd-rpm
[17757.176065] Resume caused by IRQ 578, stm401
[17757.176121] PM: suspend exit 2022-07-29 01:23:15.463727566 UTC
 

McMannes

Senior Member
Oct 12, 2012
157
10
Overall it was a good rom. I'm having a problem with the proximity sensor. There was no such problem in the previous rom. Also, there are instant blackouts on the screen when opening some applications.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 7
    New build 2022-7-15:
    • Updated with the latest LineageOS changes including the July security update
    • Selinux is now enforcing
    • Added signature spoofing support for microG
    • Signed with private keys (make sure to read the installation note in the original post)
  • 14
    EmPczMv.png
    LineageOS 19.1

    lineage-19.1-20220715-UNOFFICIAL-shamu.zip

    MigrationBuild.zip

    lineage-19.1-20220612-UNOFFICIAL-shamu.zip

    lineage-19.1-20220509-UNOFFICIAL-shamu.zip

    Installation note: For the July update I've switched from signing with public keys to private keys to improve security. If you're upgrading from the May or June update to the July update or newer then you should first install the migration build, reboot and let LineageOS boot up, and then install the new version.

    What works:
    - Almost everything, including VoLTE

    Known issues:
    - Encryption is untested

    Device tree and kernel sources can be found on my github: https://github.com/rootfan

    Thanks to:
    - LineageOS team
    - Elektroschmock, npjohnson, and anyone else who has worked on shamu in the past
    - followmsi for the work on flo / deb. It was very helpful.
    - abhishekt295 and wavedashdoc for getting IMS to work on android 10
    - rINanDO for the netd reverts

    Standard disclaimer: You're responsible for what you do to your devices, so don't blame anyone else if something goes wrong.

    Enjoy android 12 on the Nexus 6 :)
    12
    New build 2022-6-12:
    • Updated with the latest LineageOS changes including the June security update
    • Firewall / data monitoring appear to be functional thanks to rINanDO's netd reverts
    • Ims (VoLTE) is working again
    • The GPS problem should be fixed
    7
    New build 2022-7-15:
    • Updated with the latest LineageOS changes including the July security update
    • Selinux is now enforcing
    • Added signature spoofing support for microG
    • Signed with private keys (make sure to read the installation note in the original post)
    4
    Thanks for this major update. What G-apps do you recommend? if possible a link please.
    I used MindTheGapps, haven't got any issues installing via TWRP.

    So far haven't encountered any major issues except the UI being choppy and sometimes UI elements flicker. Will run it for a couple of days and see if it's worth it.
    4
    MindTheGapps-12.1.0-arm-20220416_173154.zip work for me. Play Store updates ok. I can't find the link from which I downloaded it but I can get it to you if you can't find it.
    Edit: https://androidfilehost.com/?w=files&flid=322935&sort_by=name&sort_dir=ASC