LineageOS 15 mako (nexus4) rom

roland3939

Member
Jan 7, 2016
37
68
28
Many time the lcd won't wake up. Notification led still work. But black screen. I have to hold power button to reboot the phone. Thank for your help
hi Jogtx16v,
are you able to provide log-files ( e.g. : /proc/last_kmsg ; logcat files) by adb debugging when LCD won't wake up ? This log information should be taken before executing a hard power cycle (such as holding the power button or powering off)
 

D4V|D

New member
Feb 9, 2020
3
1
0
Rom work great. But I have a little issue. I experiment the issue on my 2 mako phone.

Many time the lcd won't wake up. Notification led still work. But black screen. I have to hold power button to reboot the phone. Thank for your help
This could be a Hardware related problem too. I'm using my 3rd Nexus 4 and with the two ones before I had trouble with the power switch as well (They were not running Lineage OS)
 

next4

Member
Jul 31, 2019
6
1
0
New build uploaded
lineage-15.1-20200507-UNOFFICIAL-mako-signed
included:
May security patches (including "O_asb_2020-05")
Update default WebView to 81.0.4044.117

second source for downloading: androidfilehost.com
I still enjoy my nexus4 with continued updates. Thx again Roland it´s p:highfive:retty cool you are running this thread and providing updates for my beloved phone =)
At the moment my friends Galaxy S4 recieved 17.1 Android 10... Good day. Best wishes!
 

TigTex

Member
Nov 28, 2012
32
17
38
Lisbon
I've just installed this on my nexus because I needed it to temporary replace a failed phone. Some information is missing on the first post so I'll post it here.

Just like official lineageOS, there are no gapps included. So remember to install them from opengapps. Select ARM cpu and android 8.1. Choose the smaller pack.
There is not enough space to run this ROM and pico gapps (the smaller pack). So you need to change the system and cache partitions size. To do that, check lineageOS 16/17 posts on this forum. There is a flashable zip.
Stock TWRP will give an error when you flash this rom. You need a modded TWRP that it's not easy to find. Check here Also, it's possible that this twrp version will fail to reboot the system. Mine did.
After flashing the ROM and before flashing gapps, you need to resize the partition size and you use twrp for that: Just go to wipe, select system and "change or repair file system". There's an option to repartition. Make sure that the partition size is above 1200mb. Remember to format "cache" partition.
First boot will take 5 minutes. Be patient.
Good luck and have fun!
 

roland3939

Member
Jan 7, 2016
37
68
28
hi TigTex

@TigTex can you please give a bit more justification for your remarks on installing gapps on this ROM.

There was no need to resize any partition when installing pico gapps (open_gapps-arm-8.1-pico-20180510.zip)!
Further more, Stock TWRP 3.2.1-0 ( and newer TWRP versions) are working fine when flashing this ROM!
 

Attachments

  • Like
Reactions: ze7zez

Waldold

Member
Aug 22, 2020
6
1
13
36
Seems all running well after yesterdays update of outdated official LOS. (y)
But it was a little complicated quest to install working ADB to run script of migration keys, it may be a problem for beginners.
 
Last edited:

TigTex

Member
Nov 28, 2012
32
17
38
Lisbon
hi TigTex

@TigTex can you please give a bit more justification for your remarks on installing gapps on this ROM.

There was no need to resize any partition when installing pico gapps (open_gapps-arm-8.1-pico-20180510.zip)!
Further more, Stock TWRP 3.2.1-0 ( and newer TWRP versions) are working fine when flashing this ROM!
Fair enough.
This is the error message that you see when installing LATEST opengapps pico. I see that you are installing a version from 2 years ago, is it a requirement? There's no information about that on 1st post.
Oficial TWRP 3.4.0 no longer fails to install this rom. Probably this is because the system clock was wrong (phone has been disabled for almost 2 years).

GAPPS log
Code:
# Begin Open GApps Install Log
------------------------------------------------------------------
            ROM Android version | 8.1.0
                   ROM Build ID | lineage_mako-userdebug 8.1.0 OPM7.181205.001 45da97e2b7
          ROM Version increment | 45da97e2b7
                ROM SDK version | 27
        ROM/Recovery modversion | 15.1-20200810-UNOFFICIAL-mako
                Device Recovery | TWRP 3.4.0-0-349ea555
                    Device Name | mako
                   Device Model | Nexus 4
                    Device Type | phone
                     Device CPU | armeabi-v7a,armeabi
          Device A/B-partitions | false
             Installer Platform | arm
                   ROM Platform | arm
           Display Density Used | 320
                   Install Type | Clean[Data Wiped]
Google Camera already installed | Clean
              VRMode Compatible | false
       Google Camera Compatible | true
      New Camera API Compatible | false
          Google Pixel Features | false
          Current GApps Version | No GApps Installed
          Google Camera version | Legacy
       Installing GApps Zipfile | /sdcard/TWRP/open_gapps-arm-8.1-pico-20200825.zip
       Installing GApps Version | 20200825
          Installing GApps Type | pico
                    Config Type | 
             Using gapps-config | Not Used
      Remove Stock/AOSP Browser | false[NO_Chrome]
       Remove Stock/AOSP Camera | false[NO_CameraGoogle]
       Remove Stock/AOSP Dialer | false[NO_DialerGoogle]
        Remove Stock/AOSP Email | false[NO_Gmail]
      Remove Stock/AOSP Gallery | false[NO_Photos]
     Remove Stock/AOSP Launcher | false[NO_GoogleNow/PixelLauncher]
      Remove Stock/AOSP MMS App | false[NO_Messenger]
     Remove Stock/AOSP Pico TTS | false[default]
         Ignore Google Contacts | false
           Ignore Google Dialer | true[NoRemove]
         Ignore Google Keyboard | false
Ignore Google Package Installer | false
          Ignore Google NFC Tag | false
          Ignore Google WebView | false
         Total System Size (KB) | 847656
         Used System Space (KB) | 704500
        Current Free Space (KB) | 143156
 Additional Space Required (KB) | 4188   << See Calculations Below
------------------------------------------------------------------
# End Open GApps Install Log

INSTALLATION FAILURE: Your device does not have sufficient space available in
the system partition to install this GApps package as currently configured.
You will need to switch to a smaller GApps package or use gapps-config to
reduce the installed size.

NOTE: The Stock/AOSP Dialer is not available on your
ROM (anymore), the Google equivalent will not be removed.
# Begin GApps Size Calculations
------------------------------------------------------------------
  TYPE  |         DESCRIPTION        |      SIZE |   TOTAL
        |         Current Free Space |    143156 |  143156
 Remove |             Existing GApps | +       0 |  143156
 Remove |             Obsolete Files | +       0 |  143156
 Remove |              cmsetupwizard | +       0 |  143156
 Remove |           extservicesstock | +      16 |  143172
 Remove |             extsharedstock | +      12 |  143184
 Remove |      packageinstallerstock | +    5916 |  149100
 Remove |                  provision | +       0 |  149100
Install |                       Core | -  100360 |   48740
Install |                    calsync | -    2544 |   46196
Install |            dialerframework | -      12 |   46184
Install |                  googletts | -   35460 |   10724
Install |     packageinstallergoogle | -    5696 |    5028
        |               Buffer Space | -    9216 |   -4188
------------------------------------------------------------------
                      Additional Space Required |    4188
------------------------------------------------------------------

# End GApps Size Calculations

# Begin User's gapps-config

# End User's gapps-config
 
Last edited:

roland3939

Member
Jan 7, 2016
37
68
28
Fair enough.
This is the error message that you see when installing LATEST opengapps pico. I see that you are installing a version from 2 years ago, is it a requirement? There's no information about that on 1st post.
Oficial TWRP 3.4.0 no longer fails to install this rom. Probably this is because the system clock was wrong (phone has been disabled for almost 2 years).
hi TigTex,
size of GoogleTTS has increased by approx. 60% during last 2 years. So, one option is to reduce the size of opengapps pico by configuration.
Please see also here: https://forum.xda-developers.com/showpost.php?p=76444485&postcount=2

BTW: official TWRP 3.4.0 has some issues with rebooting.
 
Last edited:

7wells

Senior Member
Oct 9, 2019
131
6
0
Yes, it reboots again and again back to recovery menu even if you choose "shut down" the device.
I nevertheless recommend using the latest twrp-3.4.0-0-mako. If one wants to shutdown, simply keep pressing the power button until the Nexus 4 powers off. And if one wants to boot into the system, power the device off like this and then on again. This TWRP problem seems rather a problem of missing convenience, and eventually this will be fixed, too.


@roland3939
Thank you very much for offering LOS 15.1 builds for the Nexus 4 and for the hint & link about excluding Google TTS. :good: I confirm that thus, flashing OpenGApps pico works without problems.
Migration script: migration_RZ.sh
(Please see brief text file "Using script migration.txt" for explanation there.)
I flashed your latest LOS 15.1 build (26 Aug 2020) on a formatted & completely wiped Nexus 4, i.e. no previous official build on the phone. How does your guide & script for migration of release-keys apply in my case? How can I sign your latest LOS 15.1 build with keys to become official? :confused: Thanks for your advise.

Do you plan further updates of LOS 15.1? (e.g. with the September 2020 security patches)
 

roland3939

Member
Jan 7, 2016
37
68
28
@roland3939
Thank you very much for offering LOS 15.1 builds for the Nexus 4 and for the hint & link about excluding Google TTS. :good: I confirm that thus, flashing OpenGApps pico works without problems.
I flashed your latest LOS 15.1 build (26 Aug 2020) on a formatted & completely wiped Nexus 4, i.e. no previous official build on the phone. How does your guide & script for migration of release-keys apply in my case? How can I sign your latest LOS 15.1 build with keys to become official? :confused: Thanks for your advise.
As you did a Clean Flash, no migration of signing keys is necessary at all in your case.
My LOS 15.1 builds are signed with my private release key; thus they are considered UNOFFICIAL. Only ROMs build dirctly by LineageOS's build server and signed by their private release key are considered OFFICIAL.
BTW: you are able to remove my release key ( by using my migration script) to get LineageOS's public testkeys. However I would not recommend this.
plan further updates of LOS 15.1? (e.g. with the September 2020 security patches)
Yes, update with October 2020 security patches ist going to be provided next week. Stay tuned :)