yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] Elzett1:
I also have the same problem. I've tried the following things:

-Tested on 8GB and 16GB Nexus 4

-Different ROMs and kernels

-With and without Magisk root

Unfortunately none of these worked. The only solution is to use Messenger Lite, that one works perfectly but it lacks some of the great features.

I also failed to use "adb logcat" to see, whats happening, because the logging won't let the phone "sleep that way". As soon as I unplugged the usb cable and got a message, SOD happened.

By the way the same Messenger version works with the latest stock Android 5.1.1.

I hope someone can investigate this problem, because this is the only problem I have with this rom so far. It is anyway great and runs smootly.
[Nexus 4 Android Development] myxal:
Well, clean installation didn't help with the issues. Can anyone confirm/deny that voice calling (outgoing) actually works? On mine, the phone app just gets stuck on "Calling", the call is never made. Incoming calls work on fresh boot, but after trying outgoing calls, incoming calls also don't work. (seems like the caller will never even get a ringtone). That's a showstopper.
[Nexus 4 Android Development] voron00:
Hey, new 16.0 build uploaded:

- Fixed Facebook Messenger issue.

- Lates security patch (March 2020) and latest source code.

Also i didn't have any issues with calling, maybe it's related to sim card.

I will continue with 17.1 a bit later, when i'll have more time. Have fun.
[Nexus 4 Android Development] sule_krug:
I switched to this messenger (https://www.google.com/amp/s/xdafor...fied-version-facebook-okay-to-t3586318/amp/), and issue have disappeared!!!!
[Nexus 4 Android Development] voron00:
Hey, new 17.1 build is now also uploaded:

- Fixed Facebook Messenger issue.

- Fixed Magisk issue.

- Lates security patch (March 2020) and latest source code.
[Nexus 4 Android Development] Elzett1:
I've installed it yesterday, and it works way better, then the original one. The first 24 hour elapsed without any error. But today I got one SOD again.

I just saw the previous post, that a new version has been released, with a fix for messenger. I wil try it out and see if it's really works.

Thank you for your advice and also for the developers :)
[Nexus 4 Android Development] phkhphk:
WOW amazing

all work good for me

hope battery will be at least like 16

thank you :good:
[Nexus 4 Android Development] phkhphk:
Hello, I think I found a bug in 17.1

Call recording dont work.

Screen recording works. Voice recording dont work.

Thanks
[Nexus 4 Android Development] jatza78:
Hi,

Where is an "expanded desktop" option in 17.1 ?
[Nexus 4 Android Development] voron00:
It's deprecated: https://review.lineageos.org/c/LineageOS/android_packages_apps_LineageParts/+/266409
[Nexus 4 Android Development] nitin.chobhe:
What was the fix for Magisk issue? I used latest device, kernel and vendor trees from your github but Magisk isn't working for me on Carbon ROM. What should I look for?

Nitin
[Nexus 4 Android Development] PenroseProcess:
I tried building from the latest device, kernel and vendor on Lineage 17.1 and still can't get Magisk to work.

Maybe voron forgot to check-in something or we need a file to be modified in another repo? I tested voron's latest 17.1 uploaded image file and Magisk works on it (installed by flashing the magisk zip in recovery).
[Nexus 4 Android Development] nitin.chobhe:
That might be the case. Let's wait for [MENTION=3772648]voron00[/MENTION] to reply.

Nitin
[Nexus 4 Android Development] voron00:
Hmm, a fix for magisk is this patch: https://github.com/voron00/android_device_lge_mako/commit/f599908964cf48a074582498fe929b88e6d91e94 and also removal of fake dt from the kernel, make sure you git checkout kernel for the latest commit.
[Nexus 4 Android Development] nitin.chobhe:
Thank for the details... In latest the commits in kernel tree, I do not see the commits that remove the fake DT (or at least can't understand which commit did that ;))

Nitin
[Nexus 4 Android Development] voron00:
Kernel was force pushed so all commits related to fake dt was removed.
[Nexus 4 Android Development] nitin.chobhe:
Got it! Thanks a ton... :highfive:

And that worked...

Nitin
[Nexus 4 Android Development] xda-kes:
e975

Could this ROM be used/ported to LG Optimus G (E975)? their hardware seems almost identical
[Nexus 4 Android Development] nitin.chobhe:
No, I don't think that it would work...

Nitin
[Nexus 4 Android Development] blackmonk19:
Thanks [MENTION=3772648]voron00[/MENTION] for all the hardwork on Mako... Amazing stuff bro! :good:
[Nexus 4 Android Development] ze7zez:
My answer in a proper thread to [MENTION=9125175]Holzhacker[/MENTION] post.

The Microsoft Display Adapter is visible but unavailable.
[Nexus 4 Android Development] seXneo:
I think USB OTG doesn't work with this ROM? I tried with a mouse and an usb stick - they get recognized by another phone
[Nexus 4 Android Development] Co.Tibi:
I'm trying to use this phone in my car for gps navigation but anytime I'm using Google Maps or Waze I'm constantly loosing gps signal. Waze only gets a lock for a couple of seconds and that's all. Is anyone facing similar problems or knows a way to fix it?
[Nexus 4 Android Development] :
If your running magisk you could try the optimised GPS file replacer module, did the trick when I've had the same issue on my Nexus 6p and 5x in the past.
[Nexus 4 Android Development] indieguy:
Hello everyone,

I just resized partitions and installed the latest LineageOS 17.1 + OpenGapps pico, but when I try to boot it brings me back to recovery.

Anyone has any idea why? If yes, would you please tell me how to fix it?

Thanks for the help and the effort.
[Nexus 4 Android Development] dahawthorne:
Format (not just wipe) data.
[Nexus 4 Android Development] indieguy:
It didn't work. Do you think I should do it right after the installation? Before booting the system for the 1st time
[Nexus 4 Android Development] dahawthorne:
When installing a new ROM, I wipe all partitions and format data, then install ROM, Pico Gapps & Magisk Canary. I've never had any boot problems.
[Nexus 4 Android Development] indieguy:
Thanks it worked! :D
[Nexus 4 Android Development] Holzhacker:
Pay attention: OpenGapps 2020-04-07 reproducably lead to a boot loop when I just tried to install it together with LOS17.1-20200312.

OpenGapps 2020-04-04 (nano) worked.
[Nexus 4 Android Development] heisenberge89:
Hi, I have taken my old nexus 4 which was stopped at lineage os 14 (version 7.1.2). I tried to update the twrp to the latest version 3.3.1.0, installed both version 17 and 16 (which at the beginning gave error 7 but I corrected the zip repartition found in an answer here on this section), everything went well fine, installed micro and nano gapps (both 9 and 10 of course and ond nano gapps 2020-04-04). I reboot the phone and nothing, it remains charging for several minutes and then returns to the twrp. I don't know what I'm wrong.

p.s. when I restart it asks me to install twrp as a system app. Should I do it or not?
[Nexus 4 Android Development] dahawthorne:
[MENTION=9915990]heisenberge89[/MENTION]

It sounds as if you didn't format (not just wipe, format) your data partition. You can do that in TWRP advanced wipe. If you didn't at any point type "yes" then you haven't formatted.

And do not install TWRP as a system app. Untick the box so that you aren't reminded on every reboot. If you install it, it causes a bootloop.

Edit: Hello...? Another junior member who asks a question and then ignores the answer? Rude.
[Nexus 4 Android Development] solinent:
Installed lineage 17, it looks great, thank you! There's just one issue--my SIM isn't detected. When I go into settings, "Mobile Network" is greyed out. Is there anything I can do, or any mistake that I made?

Oh, I resolved it, I needed to install a new image for the radio, I used the JDQ39 modem available on this forum. Works perfectly now, thank you!
[Nexus 4 Android Development] 7wells:
@voron00

Thanks a lot for LOS 17.1 that keeps our rather old Nexus 4s in action.

I have a problem, though, when I connect the HDMI cable (going to my monitor) into my Slimport adapter that is connected to my Nexus 4, the Nexus 4 freezes, so I have to force it to shutdown (long-press power button). This does not happen, when only the Slimport adapter (without the HDMI cable connected to its other side) is connected to my Nexus 4 and is also no problem, when both Slimport adapter and HDMI cable (one after the other) are connected to my Nexus 4 - as long as the other end of the HDMI cable is not connected to my monitor (or to my Samsung TV, which I also tried).

Do you - or anybody else - have an idea, what is causing this and how I could help to find out more about it? With the latest stock FW, I could use my Nexus 4 with the same Slimport adapter and HDMI cable on my same monitor and Samsung TV without any issues.

Is Slimport maybe not supported anymore for a while? Does anybody know the last LOS version where this worked?

Thanks once more to all of you for all your help, support and great work. Stay healthy, everybody! :good:

PS1:

I flashed LOS 17.1 the clean way, i.e. I had done a "format data" first and for good measure then wiped all(!) other(!) partitions. Well, I also installed latest OpenGApps nano (arm) and Magisk 20.3.

Right now, I am formatting once more, will install LOS 17.1 again but without OpenGApps and without Magisk - just to be sure that the latter two are not causing the problem with the Slimport.

PS2:

It works with LOS 14.1-20200330-NIGHTLY-MLQ-mako from this forum. So I wonder if Slimport support was dropped with Android 8, 9 or 10, or whether there is a problem with the LOS 17.1 build. Sorry, no criticism meant at all. I am really eager to give a little bit back if possible, even if the issue with the Slimport might affect not so many users.

I am going to try LOS 15 and 16 and report again.
[Nexus 4 Android Development] 7wells:
Here is somebody who lost Slimport functionality on a Nexus 7 after upgrading to an official LOS build coming from an unofficial one:

Does this help?
[Nexus 4 Android Development] voron00:
I don't have slimport adapter so we can easily mark this feature as unsupported. You can try to get logs, but i don't think i can do much without the adapter to test with.
[Nexus 4 Android Development] 7wells:
[MENTION=3772648]voron00[/MENTION]

Can you please give me a hint how I can produce logs? Is there something like dmesg, cat /var/messages, etc.? Thank you.
[Nexus 4 Android Development] voron00:
This won't be easy in this case because there is no access to adb and the device freezes so either hope for /proc/last_kmsg or hack init.rc to trace the kernel log to a file like this: https://github.com/LineageOS/android_device_lge_mako/commit/71b53dadd08a7bd3c9215c62f3d7a88ca8808be0

Also an app like MatLog might work (needs root).
[Nexus 4 Android Development] 7wells:
@voron00

Thanks, I will try - also rooted with MatLog.

Could I adb sh into it with messages "tail'ed" to the client machine when plugging the cable?

EDIT: I meant adb over network/IP.

Under developer, there is a setting for a debugging app (currently "none"). Which one would I have to install und set there? MatLog? Or do I not need this setting?
[Nexus 4 Android Development] voron00:
With adb you can just 'adb logcat -b kernel > log.txt' to tail the log to a file.
[Nexus 4 Android Development] 7wells:
Yes, great, it worked. Thank you! And also dmesg and /proc/last_kmsg. I am still flashing back and forth to narrow it down as much as I can, will then do a "before" and "after" (or "works"/"does not work") comparison of the various logs. For others interested (and sorry, if this is maybe becoming too off-topic here), you might have a look there:

https://translate.google.com/translate?sl=auto&tl=en&u=https%3A%2F%2Fwww.droidwiki.org%2Fwiki%2FWireless_ADB

(I am sure that there are very good sites primarily in English; this one is in German, so I used Google translate.)
[Nexus 4 Android Development] 7wells:
I have found out that already with LOS 15.1, the Slimport functionality is lost (with LOS 14.1 it works). Therefore, I am not sure if it is right to further discuss this here in this (LOS 16.0 & 17.1) thread. Any thoughts on this?

PS:

https://xdaforums.com/showpost.php?p=70726806&postcount=36

PS2:

It seems that Android dropped Slimport and also MHL support, at least according to comments like these:

https://www.reddit.com/r/LineageOS/comments/et1ce0/lineageos_16_and_mhlhdmi_support/
[Nexus 4 Android Development] voron00:
i don't think it was droped, it just was't ported over to device because of no hardware/adapter to test with.
[Nexus 4 Android Development] 7wells:
Ah, ok. Thanks for your kind clarification. And please accept my apologies for having written nonsense here. :o
[Nexus 4 Android Development] ze7zez:
Does this mean that such equipment does not exist at all, or does it mean that you do not have it?

In the second case, I can sponsor your purchase of SlimPort.

Send me your decision and method of donation to a private message.
[Nexus 4 Android Development] voron00:
Meh, i think its not worth for a 8 yr old device, but if [MENTION=10196823]7wells[/MENTION] can drop in some logs, maybe it can be fixed.
[Nexus 4 Android Development] 7wells:
@voron00

Is logcat of kernel enough?

When I do (adb) logcat -d -b kernel > kernel.log before plugging in, after pluggin in, and after plugging out the slimport adapter, the kernel log file always starts from the beginning. Do you see what I mean? Is there a way to clearly show what happens when?

I am on Windows and have the following batch script for the logging:

@echo off

adb logcat -d -b kernel > kernel.log
echo "Now plug in slimport adapter."
pause
echo "---------- slimport adapter plugged in" >> kernel.log
echo "Now wait for 5 seconds."
timeout /t 5 /nobreak

adb logcat -d -b kernel >> kernel.log
echo "Now unplug slimport adapter."
pause
echo "---------- slimport adapter unplugged" >> kernel.log
echo "Now wait for 5 seconds."
timeout /t 5 /nobreak

adb logcat -d -b kernel >> kernel.log
echo "Done."

However, as written above (maybe not clear enough, sorry) this shows repeating lines in the kernel.log file, which I find dumb (of myself :o).

So if you or somebody else have/has examples (also in Linux/bash), I am happy to try them out.

EDIT: Ah, shall I rather (adb shell) cat /proc/last_kmsg >> kernel.log to overcome this problem?

Is it necessary to do the logs only after a fresh reboot of the device? Do I have to power-off and power-on, or can I reboot as well (without biasing the log)?

(BTW, I am doing all this via adb via network/IP. The device is rooted with Magisk. No OpenGApps installed.)

Last question: Are there any sensitive data in these (kernel or other) logs, e.g. IMEI, Wifi credentials, etc.?

Thanks for keeping up the great support! :good:

---------- Post added at 16:50 ---------- Previous post was at 16:27 ----------

I am writing this "new post", because else things might get too confusing.

I have found out that redirecting /proc/last_kmsg to a file and adding there (with echo) notes (as "marks") as to when the adapter was plugged in and out does not work - at least not as I am trying to do it. The same seems to be the case when using logcat. I have the (vague) feeling that by concept this cannot work like this; however, since I am by far no tech expert, I am not sure.

Bottom line: I can produce logs but would really love to hear from you guys if/how it is possible to set some "marks" in the outputs with regard to the timing, i.e. when the Slimport adapter was plugged in and out again. Or is this not needed at all?

And maybe someone likes to also reply to my previous question about any sensible data in the logs I should first redact before posting logs here. Thank you so much. :)
[Nexus 4 Android Development] voron00:
Log tail contains last xxx lines (quite a lot), so all needed information will be at the bottom of the file.

Pretty sure there is no need to do before/after, just start tailing your log, plug, unplug the cable, stop tailing the log.

/proc/last_kmsg is no good here unless you reboot.

There shouldn't be any sensitive data in logs, but you can send it in pm if you are worried to post it here.
[Nexus 4 Android Development] 7wells:
Thank you. I will provide the log tomorrow. Good night! :)
[Nexus 4 Android Development] 7wells:
Hm, this does not seem to work when trying adb from another mobile device to the Nexus 4:

# adb logcat -b kernel > kernel.log
- waiting for device -

I have to stop it with Ctrl+c, and the log file is of course empty. Please be patient with me, since I have no notebook with me right now.
[Nexus 4 Android Development] sule_krug:
I found out that screen cast disconnect while I'm charging phone , anyone else!? Using 17.1.
[Nexus 4 Android Development] 7wells:
Well, I managed (timewise) to create logs also for LOS 17.1 without the display attached to the Slimport adapter (expectedly, the Nexus 4 does not freeze with no display attached):

[COLOR=Red]#----- Slimport adapter plugged in here[/COLOR]
04-24 19:08:26.772 0 0 I anx7808_cbl_det_isr: gpio_get_value(anx7808->pdata->gpio_cbl_det) = 0
04-24 19:08:26.772 0 0 I anx7808_cbl_det_isr: detect cable removal
04-24 19:08:26.860 0 0 I anx7808_cbl_det_isr: gpio_get_value(anx7808->pdata->gpio_cbl_det) = 1
04-24 19:08:26.860 0 0 I anx7808_cbl_det_isr: detect cable insertion
04-24 19:08:26.983 0 0 I sp_tx_hardware_poweron: anx7808 power on
04-24 19:08:26.986 0 0 I : sp_tx_power_on
04-24 19:08:26.987 0 0 I : sp_tx_power_on
04-24 19:08:26.988 0 0 I HDMI_RX : HDMI_CLOCK_DET
04-24 19:08:27.055 0 0 I : HPD low is issued
04-24 19:08:27.056 0 0 I : Termination low is issued
04-24 19:08:27.056 0 0 I : HDMI Rx is initialized...
04-24 19:08:27.071 0 0 E : 3.3V output enabled
04-24 19:08:27.376 0 0 I : Downstream is HDMI dongle.
[COLOR=red]#----- Slimport adapter unplugged here[/COLOR]
04-24 19:09:19.744 0 0 E : aux operation failed 02
04-24 19:09:19.744 0 0 E : aux read failed
04-24 19:09:19.794 0 0 E : aux operation failed 02
04-24 19:09:19.795 0 0 E : aux read failed
04-24 19:09:19.854 0 0 E : aux operation failed 02
04-24 19:09:19.854 0 0 E : aux read failed
04-24 19:09:19.932 0 0 E : aux operation failed 02
04-24 19:09:19.932 0 0 E : aux read failed
04-24 19:09:19.997 0 0 E : aux operation failed 02
04-24 19:09:19.997 0 0 E : aux read failed
04-24 19:09:20.034 0 0 E : Cwire polling is corrupted,power down ANX7808.
04-24 19:09:20.037 0 0 I : HDCP Clean!
04-24 19:09:20.039 0 0 I : 3.3V output disabled
04-24 19:09:20.041 0 0 I : sp_tx_power_down
04-24 19:09:20.042 0 0 I : sp_tx_power_down
04-24 19:09:20.085 0 0 I anx7808_cbl_det_isr: gpio_get_value(anx7808->pdata->gpio_cbl_det) = 0
04-24 19:09:20.085 0 0 I anx7808_cbl_det_isr: detect cable removal
04-24 19:09:20.103 0 0 I sp_tx_hardware_powerdown: anx7808 power down
04-24 19:09:20.103 0 0 I : SP_TX To System State:
04-24 19:09:20.104 0 0 I : STATE_CABLE_PLUG

Interim summary:

Except for a few less "aux operation failed", "aux read failed" and "aux error" lines, it is the same as before when no display is connected, i.e. the same as with LOS 14.1 and 16.0.

The next log (LOS 17.1 with display attached to the Slimport adapter) will follow soon, though I call it a day for today.

Greetings!
[Nexus 4 Android Development] voron00:
Thanks, but i guess it's not something that can be fixed without local testing. I can try to order some cheap adapter from aliexpress, but i guess it can take up to a few mounths to arrive because of covid-19, so idk if its worth it.
[Nexus 4 Android Development] ze7zez:
Similarly, I think it's not worth it, but because of the acceleration of the Holocene extinction of the species, to which human will soon join.
[Nexus 4 Android Development] 7wells:
No Problem. :) I can stay on LOS 14.1 on my Nexus 4, which I only use for a few games on TV. ;)

For the time being, it seems that no log for LOS 17.1 with display/TV attached is necessary.

Thanks nevertheless for these new ROMs for this rather old (but still good) phone. :good:
[Nexus 4 Android Development] voron00:
I mean, is it worth to wait almost 3 mounts for a cheap adapter from aliexpress that may not even work properly (massive delays in delivery because of covid-19).

Anyway, i just ordered one for about 3$ , estimated delivery: july 2020.
[Nexus 4 Android Development] ze7zez:
Are you not able to buy on any auction or shop portal in your country, e.g. on avito?
[Nexus 4 Android Development] voron00:
Nope, on avito i saw literally only 1 offer and it was 4 times more expensive than aliexpress.
[Nexus 4 Android Development] Vegeta IV:
Sensors dont work at all on this rom. On stock rom they work without any issues so any solution to fix it?
[Nexus 4 Android Development] phkhphk:
Should work

try reflash
[Nexus 4 Android Development] Vegeta IV:
Tnx you! Dont know why but after reflashing they start to work!
[Nexus 4 Android Development] leeroy7:
17.1 Builds

Hi, I noticed there hasn't been any 17.1 builds since March. (Maybe the google drive is the wrong place). Is there anyway I can help produce builds (maybe weekly) and post them here if there is not a dedicated build server for this effort? Thanks again for keeping the Nexus 4 alive!

If this is helpful I have a couple questions about config, being that not everything is on mainline repos (@voron00) and want to make sure I'm pulling in the right content.
[Nexus 4 Android Development] dj_s_021:
Hello

What is the best and most stable Android 9 ROM for Nexus 4 in terms of battery Usage Stable and speed?
[Nexus 4 Android Development] MarMed10:
I can confirm that using voron00's repository it is still possible to successfully build a current build.
[Nexus 4 Android Development] dj_s_021:
please help please help me

I was the installation Repartition from Link https://xdaforums.com/nexus-4/orig-development/repartition-nexus-4-repartition-t3844383

recovery mode TWRP 3.3.1-1 UA when I unfortunately encountered the following error:

Failed to mount '/vendor; ( invalid argument )

What should I do ??

Of course Despite this error I'm ROM and installed! Is it okay for the phone to crash over time?

How do I know if the REPARTITION is working properly?
[Nexus 4 Android Development] dj_s_021:
How to use battery in this way? I texted last night and the battery consumption is very high. Of course, the problem I saw was that I had 78% charge before I restarted the phone, when I restarted it became 81%! that is weird ! What's the problem ??
[Nexus 4 Android Development] leeroy7:
I'm sorry if I double posted, but this didn't seem to go the first time. I can confirm the I can still successfully build with voron00's repos, however I'm trying to build hammerhead 17.1 as well on the same build box and it produces an error. Previously I had separate vms for this, but hoping to conserve space, by not duplicating the repo if everything can correctly be pulled down for the given device. Using roomservice.xml for this at the moment... But clearly something is wrong with my setup. Also if this is not the right place for this please let me know what is. I can also post the roomservice.xml file as well and happy to post builds once I get this up and running.

Error:

/home/name/android/lineage/prebuilts/build-tools/linux-x86/bin/ckati was modified, regenerating...
[ 22% 111/490] 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.
15:25:57 ckati failed with: exit status 1
[Nexus 4 Android Development] Fif_:
I've successfully repartitioned a 16GB mako. Installing either 16.0 or 17.1 works, but 17.1-20200312 cannot connect to WiFi. I've tried with and without gapps, and tried reformating and reinstalling several times without any luck.

16.0-20200309 works flawlessly so far.
[Nexus 4 Android Development] voron00:
Hey, new 16.0 build uploaded. (With may security patches.)

Also, for now, i can't build 17.1 cleanly (builds always fail due to lack of RAM), so maybe i will not be able to provide 17.1 builds anymore.