yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] ze7zez:
It's good that "DONATE TO ME" appeared on your profile.

Maybe soon you will be able to increase the amount of RAM and still compile ROM for android 10,

and if it is possible in the future, also for android 11.
[Nexus 4 Android Development] dj_s_021:
In this ROM, I encountered a big problem: that when I call and play the WhatsApp audio file, the screen turns off and I have to press the power button to turn on the screen! What's the problem ?
[Nexus 4 Android Development] voron00:
Well, i tired building 17.1 again and this time it decided to work :confused: New 17.1 build uploaded.
[Nexus 4 Android Development] Giogts:
miracast works?
[Nexus 4 Android Development] voron00:
Miracast works only on 16.0.
[Nexus 4 Android Development] Giogts:
you can add it?
[Nexus 4 Android Development] voron00:
Unfortunately, support for legacy WFD (libstagefright_hdcp) has been removed by google.

There is however patches at lineage gerrit, but they are abandoned, perhaps it no longer works: https://review.lineageos.org/q/topic:"ten-aosp-wfd"+(status:open OR )

So i guess 16.0 is proably the last android release with Miracast support for nexus 4.
[Nexus 4 Android Development] MartinX3:
You could try to disable metalava and the build threads to reduce the ram usage

WITHOUT_CHECK_API=true

And this CL if LOS doesn't have it anymore

https://android-review.googlesource.com/c/platform/build/soong/+/1112165
[Nexus 4 Android Development] phkhphk:
thanks

just flash

looking good

call recording stil dont work

thanks for your work :good:
[Nexus 4 Android Development] Giogts:
please try to add it:crying:
[Nexus 4 Android Development] asdasd40:
For me Miracast does not work on 16.0. :(
[Nexus 4 Android Development] ze7zez:
Have you ever tried to connect your equipment?

What model is it?

Show screenshots.

This LineageOS 16 did not properly negotiate the connection

with my Microsoft Wireless Display Adapter model 1628,

although WDA works with any android up to 7.1.2 on Nexus 4

and three custom ROMs with Android 9 in OnePlus One:

Bootleggers, Arrow and Lineage by Tomoms.
[Nexus 4 Android Development] voron00:
Uploaded new 17.1 build with a fix for slow GPS lock bug.

Miracast worked for me on 16.0 with another phone set up as miracast receiver.

Maybe it doesnt work with real receiver, i don't know.

But it definitely not going to work on 17.1 because the necessary code just isn't there.
[Nexus 4 Android Development] ze7zez:
"miracast receiver"? :confused:

The miracast wireless display must also have hardware support for audio,

so I doubt that the screen mirroring function (miracast) between smartphones works.
[Nexus 4 Android Development] leeroy7:
I'm happy to contribute and produce builds, but still trying to understand what the best way to build multiple devices on the same box. I posted earlier about this error, but no idea how to get around it, Mako builds fine and Hammerhead fails below:

$(shell uname -rsm) was changed, regenerating...
[ 22% 108/487] including device/lge/hammerhead/Android.mk ...
FAILED:
build/make/core/base_rules.mk:325: error: device/lge/hammerhead/bdAddrLoader: MODULE.TARGET.EXECUTABLES.bdAddrLoader already defined by device/lge/mako/bdAddrLoader.
23:41:28 ckati failed with: exit status 1
#### failed to build some targets (01:05 (mm:ss)) ####

roomservice.xml:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="voron00/android_device_lge_mako" path="device/lge/mako" remote="github" revision="lineage-17.1" />
<project name="voron00/android_kernel_lge_mako" path="kernel/lge/mako" remote="github" revision="lineage-17.1" />
<project name="voron00/proprietary_vendor_lge" path="vendor/lge/mako" depth="1" remote="github" revision="lineage-17.1" />
<project name="z3DD3r/android_device_lge_hammerhead" path="device/lge/hammerhead" remote="github" revision="lineage-17.1" />
<project name="z3DD3r/android_kernel_lge_hammerhead" path="kernel/lge/hammerhead" remote="github" revision="lineage-17.1" />
<project name="z3DD3r/android_vendor_lge" path="vendor/lge/hammerhead" depth="1" remote="github" revision="lineage-17.1" />
</manifest>

If this is not possible and I simply need to have separate repos etc, I can do that, I was just hoping be more efficient. I'll post this in hammerhead as well.

---------- Post added at 01:02 AM ---------- Previous post was at 12:48 AM ----------

I also seem some complications in previous posts I glazed over. I'll try and make more sense of this after taking a closer look like https://xdaforums.com/showpost.php?p=81871053&postcount=135
[Nexus 4 Android Development] SBWater:
17.1 is mostly working, but a minor issue.

Signal strength in the status bar does not work when using a data-only SIM.

It seems to work if it is a normal SIM.

thanks for your work.
[Nexus 4 Android Development] aarem:
Is there any chance of releasing an official build so that we may get OTA updates?
[Nexus 4 Android Development] PavelPerm:
[MENTION=3772648]voron00[/MENTION]

I use nexus 4 with Los 17 as an everyday device. And I noticed a problem with LMK. When I launch a lot of applications during the day, the device work very slow and free up memory for new applications for a long time. sorry for english
[Nexus 4 Android Development] Fif_:
Following up to myself in case someone runs into the same problem:

I found out that Android 10 on mako (lineage-17.1-20200520-UNOFFICIAL-mako-signed.zip) will not connect to an access point which has 802.11w enabled (either optional or required). If 802.11w is disabled on the WiFi access point, the Nexus 4 can connect to it.

On Pie (lineage-16.0-20200517-UNOFFICIAL-mako-signed.zip), the phone can connect with 802.11w set to optional or disabled.

Would it be possible to fix that regression?
[Nexus 4 Android Development] phkhphk:
Hello @voron00

I found that private dns dont work since may update

I thought i destroyed my mako until i found out what is the problem

thanks for your time
[Nexus 4 Android Development] 666biker:
Hello all, has someone from you tip for a new nexus 4 battery replacement? Is possible nowadays to buy a good baterry for this old Phone model? Sorry for this small offtopic, thx
[Nexus 4 Android Development] maracuya:
just replaced my bulging battery today. purchased from ebay. my tip is to buy from seller that has sold many and also has high ebay remarks
[Nexus 4 Android Development] dookie23:
[MENTION=3772648]voron00[/MENTION] Is SELinux set to permissive or enforced for this rom? If enforced, do you think it's ready to make it official?

In my opinion, this rom works very well and pretty good performance. Just wanted to thank you for your hard work.
[Nexus 4 Android Development] Eric_Lev:
[MENTION=3772648]voron00[/MENTION]:

I regularly build for Mako (LOS 16 and 17) for my children and my father-in-law.

Last builds :

- lineage-16.0-20200609-UNOFFICIAL-mako.zip

- lineage-17.1-20200613-UNOFFICIAL-mako.zip

All builds are based on your manifests and all credit goes to you.

I can provide the download links... only if you wish.
[Nexus 4 Android Development] apartha7:
Maybe restart the Official Builds?

Do you think it would be possible to get the official builds restarted?
[Nexus 4 Android Development] BornTrippy:
I would like to try 17.1

Thanks
[Nexus 4 Android Development] leeroy7:
I've been producing regular builds based on [MENTION=3772648]voron00[/MENTION]'s work. I'll try and update this share regularly, as updates roll in from LOS team. I haven't tried these builds yet, so do please let me know if anything seems broken. I do plan on installing this weekend, so you might want to wait until you hear back from me if there is any issues. There are some migration scripts in there too, but I haven't run those in over a year, so don't know if they are still valid if you are moving from signed to unsigned builds for example...

https://drive.google.com/drive/folders/1zyBw908tisUAzKIXaPRD9OVyqYsqm1td
[Nexus 4 Android Development] dahawthorne:
Just a heads-up. I've just flashed the new TWRP 3.4.0 on my two Nexus 4s and although it installs fine it reboots into itself - not into system, or even power-off, every time back into TWRP. I went back to 3.1.1 and it works fine. If you flash the new version, be sure to keep the 3.3.1 available in case you hit this problem.

This seems to be only on the Nexus 4 - my Nexus 6 works fine with 3.4.0.
[Nexus 4 Android Development] ze7zez:
You can always use in the terminal

twrp reboot poweroff

and always works well.
[Nexus 4 Android Development] Eric_Lev:
Please stop requests via PM... https://androidfilehost.com/?w=files&flid=303230
[Nexus 4 Android Development] voron00:
New 16.0 build uploaded, 17.1 build is in progress.

Also uploaded new twrp image as official twrp has some issues with rebooting.
[Nexus 4 Android Development] leeroy7:
[MENTION=3772648]voron00[/MENTION], is the new recovery this --> https://drive.google.com/drive/folders/1uVfsBAtJC3GZ0Jo0TSy2EWU_CTUTSQwa ? And if so, is this based on twrp 3.4.0-0 and would you know if it is compatible with clamor's script in https://xdaforums.com/nexus-4/orig-development/repartition-nexus-4-repartition-t3844383 if I just install this new version?

Cheers

Leeroy
[Nexus 4 Android Development] jglaurenzana:
Is it necessary to repartition a Factory Reset Nexus 4 16 GB Model when Installing Lineage OS 17.1?

I'll be installing it tomorrow and I really don't want to risk it if it's not necessary, is there any downside to not partitioning?
[Nexus 4 Android Development] leeroy7:
I believe the system partition has to be larger then stock to install 17.1 regardless of being factory reset or not. I certainly haven't had any issue after resizing and using voron00's builds.
[Nexus 4 Android Development] le_prince_petit:
[MENTION=3772648]voron00[/MENTION] thanks for the 16.0 build; how is the 17.1 build coming along?

I have an issue with mobile data drain while GPS is on (150MB/h) with the build from 20.5. and I'm curious if this is still an issue with the actual build.

Beside of this minor issue 17.1 is running quite well for me. Thanks a lot for your effort!
[Nexus 4 Android Development] jglaurenzana:
Do I need ti root my device to install this custom rom?
[Nexus 4 Android Development] ze7zez:
Try the 17.1 ROM built by [MENTION=9708417]Eric_Lev[/MENTION] and write your conclusions here.

If you have a stock ROM then you need to unlock the bootloader first, install the TWRP 3.4 made by voron00, enlarge your system partition and then the custom ROM.
[Nexus 4 Android Development] jglaurenzana:
Problem: On LineageOS 17.1 by voron00, my Nexus 4 will usually function normally, but the screen randomly goes black (with the backlight still lit) and stays this way until I click the power button off and on and unlock the device. I don't know why it's happening and I haven't heard anyone else with this problem. It's only slightly annoying but if anyone knows a fix please let me know!
[Nexus 4 Android Development] mik5:
I observed the same problem
[Nexus 4 Android Development] jglaurenzana:
Another problem to add onto my last message, I was able to customize my notification shade with the "Style" section in "Styles and Wallpapers" one time... after that it immedietely crashes when I try to access the "Style" section. A solution to this would also be helpful
[Nexus 4 Android Development] le_prince_petit:
Redid the test with the 20200804 build of [MENTION=9708417]Eric_Lev[/MENTION]. Issue is still the same. When using GPS intensivly and having Mobile Data on, the app "Android OS" drains significant amount of data according to the data gauge. I suppose aGPS might be responsible for this. Switching off Mobile Data the drain is gone obviously, GPS receiption is working okay anyway. Someone else noticed this?
[Nexus 4 Android Development] groesler:
Sorry for my question but perhaps I missed something:

Where could I download the current 17.1 build from voron00?

And if I already have a 17.1 on the nexus 4 how do I update?

Simple flash with twrp? Do I have to flash the GApps again? Or could I use the updateprocess implemented in lineageos?
[Nexus 4 Android Development] Giogts:
Hi voron00, i flash this los17 rom, for one month all ok, after audio during call dont work;

so i flah carbon and all is ok, after one month also with carbon rom audio dont work...

what can i do?
[Nexus 4 Android Development] Holzhacker:
Link to ROM is in the start post, you only have to browse to the "old" subfolder.

Yes

No

No
[Nexus 4 Android Development] Waldold:
A few questions

1). If I already have installed LOS 15.1 on Nexus 4 do I need repartition anyway? and by the way, how it possible to know have you enough space on your device for LOS 16.0 or 17.1?

2). Is there Russian language in LOS 16 & 17 for Nexus 4?
[Nexus 4 Android Development] voron00:
1. The ROM just won't install if you aren't repartitioned.

2. Yes there is.
[Nexus 4 Android Development] KAMiKAZOW:
Dirty flashed Eric's latest 17.1 build on top of one from March. Works fine so far. Thanks to all involved.
[Nexus 4 Android Development] groesler:
The 17.1 build in the old-folder is from 20th may. Is there a newer one somewhere?
[Nexus 4 Android Development] eurochild:
https://androidfilehost.com/?fid=8889791610682914084
[Nexus 4 Android Development] Eric_Lev:
lineage-16.0-20200913-UNOFFICIAL-mako.zip

Changelog: https://www.lineageoslog.com/16.0 ... with September security patches.

lineage-17.1-20200913-UNOFFICIAL-mako.zip

Changelog: https://www.lineageoslog.com/17.1 ... with September security patches.

All credit goes to LineageOS team and [MENTION=3772648]voron00[/MENTION].

EDIT: roomservice.xml

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="voron00/android_device_lge_mako" path="device/lge/mako" remote="github" revision="lineage-16.0 or lineage-17.1" />
<project name="voron00/android_kernel_lge_mako" path="kernel/lge/mako" remote="github" revision="lineage-16.0 or lineage-17.1" />
<project name="voron00/proprietary_vendor_lge" path="vendor/lge/mako" depth="1" remote="github" revision="lineage-16.0 or lineage-17.1" />
</manifest>
[Nexus 4 Android Development] 7wells:
Hello, I come from LOS 14.1 with OpenGApps nano on my encrypted Nexus 4 and now want to update to LOS 17.1, keeping encryption.

Is this possible by flashing without first wiping/factory resetting/formatting?

I would not mind clean-flashing instead, i.e. first formatting everything (no needed data on the phone), but encryption of the device could be broken on a later LOS version, I was told; hence my question about dirty-flashing (as alternative, if recommended at all).

Do I have to also flash (immediately after flashing LOS 17.1 without rebooting between) OpenGApps nano (this time for Android 10) if I want these apps? Or will they be still there from the previous LOS 14.1 installation?

A few questions about the maintenance:

In the first post, @voron00 has a link to lineage-16.0-20200721-UNOFFICIAL-mako-signed.zip. Will there still be updated for 16.0?

Just a post above, @Eric_Lev has posted another link for LOS 16.0. Have you taken up maintenance of this and also LOS 17.1 from @voron00?

Which links/builds are "official" builds by the developers? Why are they not shown in the first post?

About root:

I want to avoid root. Will these LOS ROMs include root and allow to disable/remove it in that case?

Finally, what is the difference between mako "signed" and mako not "signed" LOS?

Thanks for your help!
[Nexus 4 Android Development] 7wells:
[MENTION=3772648]voron00[/MENTION]

Would you be able to make encryption working on LOS 16.0 and 17.1? To my understanding, it has something to do with a wrong block size of the /data partition. Please see there:

https://gitlab.com/LineageOS/issues/android/-/issues/1027
[Nexus 4 Android Development] dzhoshkun:
Hi, have successfully flashed [lineage-17.1-20200913-UNOFFICIAL-mako] but have no success with flashing gapps. any help would be much appreciated. It give me error 64 unmouting partitions
[Nexus 4 Android Development] voron00:
Encryption is working fine.

TWRP is not able to decrypt, but its TWRP bug, not ROM.
[Nexus 4 Android Development] 7wells:
[MENTION=3772648]voron00[/MENTION]

Thank you! I mistakenly thought that the encryption problem was with LOS.

However, I wonder now, how I could update an encrypted device with a newer LOS version when a future update is available. TWRP will not work, so how do other users update? Or are all using devices without encryption?

Again, thanks a lot for your help!
[Nexus 4 Android Development] Holzhacker:
Just update by using "adb sideload".
[Nexus 4 Android Development] 7wells:
@Holzhacker

Thank you, but that does not work (I replaced the serial below by x):

PS C:\Users\user\Desktop> adb devices
List of devices attached
xxxxxxxxxxxxxxxx device

PS C:\Users\user\Desktop> adb sideload .\lineage-17.1-20200913-UNOFFICIAL-mako.zip
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed

@voron00

Sorry to ask another question about encryption: You are of course right that encryption in your LOS builds works and decryption does not work in TWRP (and there have been posts about TWRP being the culprit). However, I wonder about the aforementioned post in GitLab with a link to another thread in GitHub, according to which the size of the /data partition could be amended in order to get everything smooth. Would this not be possible from your LOS builds? (only from TWRP) Thanks for helping me correctly understanding this. :thumbsup:
[Nexus 4 Android Development] Holzhacker:
If you see "device" you're obviously within a running system.

You have to be in the recovery (just type in "adb reboot recovery") and start the sideload feature.

Then you should see "sideload" instead of "device" when you enter "adb devices". Then you can type the adb sideload command.
[Nexus 4 Android Development] 7wells:
@Holzhacker

But when I go into recovery, it is TWRP, and that does not allow decryption of /data (*). Hence I went into the running system and tried it there (which was dumb of me, I confess). So now I am stuck (as I had assumed before already), unless I still oversee something.

(*) TWRP asks:

Enter Password.

When I enter my PIN that I used to encrypt my device (same PIN as for unlocking it), I get this message from TWRP:

Password failed, please try again!

So I can only tick "Cancel" (the other button "Select Language" makes no sense).

As a result, /sdcard is not mounted and appears empty. Ah, now I shall adb sideload, i.e. without the need of a mounted storage partition?

Still, no joy:

PS C:\Users\user\Desktop> adb devices
List of devices attached
xxxxxxxxxxxxxxxx recovery

PS C:\Users\user\Desktop> adb sideload .\lineage-17.1-20200913-UNOFFICIAL-mako.zip
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed

Is there a specific parameter to sideload that I need to use? Sorry, I am very unfamiliar with sideloading. Thanks for your help! :good:
[Nexus 4 Android Development] dahawthorne:
[MENTION=10196823]7wells[/MENTION]

What you describe with the TWRP password is what happens with an encrypted device. In TWRP, format data (enter "yes" to confirm), wipe everything, then you can copy the ROM from your laptop to the device and install it. I haven't read all your posts - presumably you've already resized the partitions? Also use Open Gapps Pico Arm, the smallest. You can install any other apps from Google Play.
[Nexus 4 Android Development] Holzhacker:
You're almost there. In TWRP just press Cancel when you're asked for the data partition password (you don't need the data partition).

Then you may want to Swipe to allow system modifications.

Afterwards press "Advanced" -> "ADB Sideload" -> Swipe to Sideload
[Nexus 4 Android Development] 7wells:
@Holzhacker

That's why I love this forum: There are always people around that know what they are doing and willing to help others. Thank you so much - your hint was what I was missing! :good: And I have learned something new again today about the sideloading feature of TWRP. :)

PS C:\Users\user\Desktop> adb devices
List of devices attached
xxxxxxxxxxxxxxxx sideload

PS C:\Users\user\Desktop> adb sideload .\lineage-17.1-20200913-UNOFFICIAL-mako.zip
Total xfer: 1.00x

Just a side note about TWRP (3.4.0-0): When I go to Reboot => System, it comes immediately back to TWRP (same with Power Off). So I have to switch the device off by long-pressing the power button and then restart it. I do not know whether this is a TWRP bug, but this would get OT here anyway.

@dahawthorne

Thanks to you as well. I shall remember your hint, too. In the current situation, though, I need to have both an encrypted device and an LOS with recent security patches. I had the impression (maybe I am wrong?) that I would not accomplish this by formatting data, because then the /data partition would not be encrypted anymore. Ok, if the latest LOS can handle encryption (and I was told, meanwhile it does), then I could have gone right to it without previous version experiments. Clean-flashing is better anyway, as I do not miss important data. I will look into this, too, and surely learned something from you as well. :)

A longer PS:

Yes, I had my device repartitioned with one of the two mentioned tools. The size of /system_root was 1354 MB. For the records, after flashing LOS, it is only 1254 MB, i.e. below the recommended 1272 MB. After doing 'format data' (and entering "yes" to confirm) and then (for good measure) also wiping everything except for Internal Storage, the size of /system_root is now back to 1354 MB. I will now clean flash LOS 17.1 right from this thread and see to encrypt my device from there (hoping it works). And I will surely use a smaller OpenGApps package (arm/10.0), first nano, then pico, if nano is too large. And I am sure not to boot between flashing LOS and flashing OpenGApps. ;)
[Nexus 4 Android Development] dahawthorne:
Format, thereby removing encryption, set up your device as you want it, then encrypt it. Is that too simple a solution? :)
[Nexus 4 Android Development] 7wells:
No, it is of course not. ;) I was not really up-to-date with the current status of this LOS build. I remember that some earlier builds had problems (the first post mentioned that encryption did not work). A workaround was mentioned to first install LOS 14.1, encrypt (where it still worked), then dirty-flash/upgrade to a recent LOS. Alas, I should have read the stuff. :o

@voron00 and everybody

Please forgive me my mistake and thus unnecessarily wasting your time. To my understanding, there is no need to further look into the encryption topic.
[Nexus 4 Android Development] 7wells:
MS Intune sees LOS 17.1 as rooted (MobileIron says the device is compliant)

Hello, a friend of mine has the problem that MS Intune sees LOS 17.1 on the Nexus 4 as rooted and thus denies use of Corp. apps. Android-Debugging (and also Root-Debugging) are disabled, and only apps included in OpenGApps (nano) and the ones from the Corp. are installed, i.e. no root (as far as I understood her). I heard somewhere else that MS Intune (like other similar apps) might detect an "unsigned" custom ROM or "test-keys". Without root, though, build.props cannot be changed (and she does not want to).

In LOS 17.1 under "Build-Number", the number indeed ends with "test-keys" on my device (not 100% sure what it looks like on her's). Under "Trust", SELinux is shown as "Enforcing", and the phone is encrypted (like mine). She said that MobileIron does not stumble and shows her device as being compliant. So MS Intune seems to be "pickier".

Now does anyone of you have an idea if there can be done something about this (besides her bying a new phone :p), i.e. can LOS (17.1) be used on the Nexus 4 when MS Intune is obligatory on the device? Thanks for sharing your thoughts.