yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] Holzhacker:
I had exactly the same problem on a different phone.

When I installed lineage without gapps, the phone booted normally.

When using OpenGapps 20191011 (tried different packages: mini, micro, nano...) and one from 20191010, the phone booted quite a long time and then just rebooted into recovery.

Then I used OpenGapps from 20190929 and everything worked.
[Nexus 4 Android Development] woutercools:
YES! This worked for me as well. I was using the latest OpenGapps build of that day 20191010.

Thank you for sharing this solution.

---------- Post added at 04:40 PM ---------- Previous post was at 04:38 PM ----------

I used the 20191029 build as Holzhacker suggested and it worked.

I was using the latest OpenGapps build of that day 20191010.

Thank you for sharing this solution.
[Nexus 4 Android Development] AraldoL:
There was a bug in OpenGapps from Oct 10 to 12, those packages were now removed. Should be fixed with new Oct 13 builds of OpenGapps according to a post of the developer today.
[Nexus 4 Android Development] voron00:
Build with october security patch uploaded.
[Nexus 4 Android Development] voron00:
Build with november security patches uploaded.
[Nexus 4 Android Development] orangek3nny:
[MENTION=3772648]voron00[/MENTION]: Just saw the android-17.0 branches and wanted to say thank you for keeping mako alive. Keep up the good work!
[Nexus 4 Android Development] carsti77:
[MENTION=3772648]voron00[/MENTION] thanks also from me! You are our hero :)
[Nexus 4 Android Development] carsti77:
[MENTION=3772648]voron00[/MENTION]: can you already say if Google's new project Mainline will be part of your Nexus4 android-17.0 branch ?

https://arstechnica.com/gadgets/201...gineers-take-us-on-a-deep-dive-of-android-q/#
[Nexus 4 Android Development] voron00:
I'm not yet sure but i have doubts about that: https://source.android.com/devices/tech/ota/apex#kernel_requirements

'APEX mainline modules are supported on devices using kernel versions 4.4 or higher. New devices launching with Android 10 or higher must use kernel version 4.9 or higher to support APEX modules.'
[Nexus 4 Android Development] carsti77:
I assume updating to a newer kernel (4.9) is technically impossible? The reason is that drivers won't work with newer kernels? Or something else?

On a technical level - why is it that newer linux kernels can't use old drivers? I thought the linux kernel system calls should be basically the same, aren't they?

Is it such an impossible task for the makers of the linux kernel to get more backwards-compatibility and allow older drivers?
[Nexus 4 Android Development] voron00:
Since msm is not part of mainline kernel, it will take too much work to port all the drivers (some of them are very complicated like gpu, camera). Also there are proprietary drivers (camera, graphics, modem) that will proably not work with newer kernels.
[Nexus 4 Android Development] carsti77:
Can you shortly explain why the old drivers (proprietary or not) don't work with newer kernels? Do the new kernels change the ABI of the old kernels? Maybe you can link to an article that explains it?
[Nexus 4 Android Development] voron00:
Because linux kernel is always updating, many things gets changed like headers, syscalls, api's, functions and more.
[Nexus 4 Android Development] carsti77:
I assumed as much. Seems unnecessary to change things so often. They could at least have a stable API for 5 years or something like a compatibility layer between two major kernel versions (e.g. 3.x is still compatible to 4.x but not 5.x). I haven't used Windows for a long time but I remember being able to run very old software and install very old drivers on Windows7 and it still worked. I know Windows makes a big deal out of backward-compatibility and it has its own problems. But the situation with the Linux kernel seems equally unnecessarily painful.

But this is probably the wrong place to discuss this :laugh:
[Nexus 4 Android Development] ALEXIS_0071:
Why is this rom not official?
[Nexus 4 Android Development] voron00:
Build with december security patches uploaded.
[Nexus 4 Android Development] Petlo_Lithi:
Hi,

I try to install this rom on my Nexus 4 but I have this error :

"Too small /system partition detected (must be at least 1333788672 bytes). You need to repartition your device before intsalling this ROM.

Updater process ended with EROOR: 7"

Could you help me to find a issue ?

Thank's

Loris
[Nexus 4 Android Development] voron00:
Flash repartition zip: https://drive.google.com/drive/folders/1sYrE8PtMy3L6ptWK-j0tHfjU8KTeyo1U

Then flash rom.
[Nexus 4 Android Development] nitin.chobhe:
Read the OP before posting anything that's already covered there (and discussed many times in this very thread).

Nitin
[Nexus 4 Android Development] _yr:
Excuse me for reply

It's a very good ROM and thanks for making my device run on Android Pie and recently I encountered a problem.

I can't wake up the device when there is a notification from the app for a long time. Such as notifications from Facebook messenger or Gmail

Do you have a solution for me?

Thank you :o
[Nexus 4 Android Development] asdasd40:
I have just entered this ROM and I have a problem with WhatsApp. With the screen off, I don't receive any message, nor does WhatsApp Web work. Almost as if the WiFi didn't work when the screen was off. Solutions?

EDIT: Fixed disabling Battery Manager
[Nexus 4 Android Development] ze7zez:
When you have a dead touch area at the bottom of the screen, you can install LineageOS and OpenGapps.

1. You only install LineageOS.

2. On the first LINEAGE screen, expand the top bar and enable screen rotation.

3. Power Off.

4. Enter Recovery mode and install OpenGapps.

5. Reboot to the System.

6. All LineageOS and WebView installation options are available by rotating the screen.
[Nexus 4 Android Development] fsiegert:
Hi [MENTION=4810659]ze7zez[/MENTION],

Thanks for the helpful suggestion! I'm having the same (apparently common) touch strip problems on the Nexus 4 and was trying your instructions. But how do you even get to navigate in the recovery image without the bottom of the screen? I'm trying with twrp-3.3.1-0-mako.img and it doesn't seem to have auto-rotate enabled but requires plenty of actions at the bottom of the screen. For example I can't get to Wipe etc. as described in the LineageOS Wiki.

I would get to Sideload, but I'm not sure that's sufficient without the Wipe steps beforehand?

Are you using a different recovery?

Thanks,

Frank
[Nexus 4 Android Development] dahawthorne:
Dead strips on the Nexus 4 seem to be common - I thought that I was just lucky... :)

There is an alternative method to access the full TWRP panel - it involves effectively shrinking the TWRP panel so that it doesn't overlap with the dead strip. See this post:

https://xdaforums.com/showpost.php?p=80749867&postcount=536

It seems a bit convoluted, but in fact it was very simple and worked first time for me. It was a one-off flash - when I rebooted TWRP was back to normal size.

Edit: See also Nitin's following post in that thread:

"I've to just use a different resolution (width="768" height="1080")."

This is the resolution that also worked for me. It results in the TWRP panel occupying the left-hand third and top three-quarters of the screen. In my case that was perfect because my dead pixels are in a strip in the right quarter of the screen. If your dead pixels are at the bottom, you may be lucky with Nitin's suggested resolution, or try adjusting it to go higher on the screen.

@ze7zez - sorry, our posts crossed. At least my post directs to your own advice and may help fsiegert so that he doesn't have to follow up.
[Nexus 4 Android Development] ze7zez:
Please follow the forum rules. This is not the right place. I described the method in another post. Find, read and if you have a problem, take a screenshot and submit it.
[Nexus 4 Android Development] nismo87:
hi, i cant install gapps, all variant give me error always

after fllash repartition.zip..... and flash lineage os and try to flash gapps too (error with gapps) my nexus 4 was bricked :(

reinstall again oem OS 5.1.1

maybe repartition file was the gulty
[Nexus 4 Android Development] voron00:
Build with January security patches uploaded.
[Nexus 4 Android Development] joelcool69:
Just installed this ROM and its working great! It's possible to add the option to modify the voltage values with some kernel tweaker? The SmartPack kernel manager doesn't show the options to modify the kernel voltages. Just installed a new battery to my beloved N4 ;)
[Nexus 4 Android Development] voron00:
17.1 build uploaded.

I didn't test flashing that on top of 16.0 so do it at your own risk.

Also note that lineage 17.1 currently don't have all the features yet so you should proably stick with 16.0 for now if you want stability.

Opengapps for 10.0 are now also available. Have fun.
[Nexus 4 Android Development] nitin.chobhe:
Awesome! Thanks for your work on mako, man... And also the help that you provide!

I really appreciate that :good:

Nitin
[Nexus 4 Android Development] carsti77:
I agree! [MENTION=3772648]voron00[/MENTION] is the best! The Nexus4 is such an amazing device (even today) and he breathes fresh live into it :)
[Nexus 4 Android Development] dirkp1:
Thanks, but:

Magisk can't install. Flash in twrp say successfully, but the manager say is not install. Install from the manager not possible, the direct flash isn't there. I had this problem on my other phone( S5), but here was the problem that the twrp manager was installed on the SD-CARD.

Update from the 16. not work.

The others seem ok
[Nexus 4 Android Development] Cice96:
[MENTION=3772648]voron00[/MENTION] is offline charging working correctly? In my crdroid personal build with your sources, it is stuck at the first frame of the animation.
[Nexus 4 Android Development] voron00:
It worked in early builds, i guess not anymore, ill check it out later.

Edit: seems to be fixed, check out latest commits in device tree.
[Nexus 4 Android Development] Cice96:
It works now. Thank you. What about Magisk? Do you need any log?
[Nexus 4 Android Development] carsti77:
Is the restoring done somehow automatically? Did you backup everything somehow before doing the install?
[Nexus 4 Android Development] Holzhacker:
I always make a backup before re-installing (using adb while in TWRP + some manual stuff).

The restoring was done automatically by the Play Store.
[Nexus 4 Android Development] Jgjd691995:
Cant get 17 to boot
[Nexus 4 Android Development] nitin.chobhe:
You are missing something. The build works fine.

I built with the source and everything worked.

Nitin
[Nexus 4 Android Development] sbhajband:
Nitin any solution on magisk???
[Nexus 4 Android Development] carsti77:
Hmm. Is there some functionality in the Play Store to re-install all the apps I had on the phone previously? Or do you install them by hand looking in the Play Store through your list of previously installed apps for your account?
[Nexus 4 Android Development] dahawthorne:
Make sure that Backup is set in Settings. Google can restore pretty much everything when you sign your phone back into your account. I save my SMS separately with SMS Backup & Restore even though Backup claims to do it. There may be a couple of apps you need to reinstall manually. And always take a complete TWRP backup and save anything valuable before you start.
[Nexus 4 Android Development] Sam Nakamura:
Mako never dies!

Will get one soon, had one few years ago, exited to get another chance playing the old Lady! lol

sorry for the OT but I'm just happy to get another Nexus 4 in my hands soon!
[Nexus 4 Android Development] carsti77:
Doesn't turning on Backup mean, Google will funnel out things like my Wifi-Info and password and other stuff? Seems not very attractive.
[Nexus 4 Android Development] dahawthorne:
Google will have all of this whether you turn backup on or not. It's convenient for you. That comes with a price. If you don't pay, you're the product. Bottom line - you asked if you can restore everything from Google. Answer - yes, pretty much.
[Nexus 4 Android Development] hboyer:
flashed 17.1 over 16 ... no issue so far. Thanks for your work!
[Nexus 4 Android Development] phkhphk:
Thanks for the surprise

The device worked smoothly. Missing functions compared to 16. I had a problem with a bank app. I tried to solve it with MAGISK but couldn't get ROOT. My child played and said that games have a delay compared to 16, I didn't feel it. So I went back to 16. I will try to install again next weekend if it goes well it will be my main device after the G2 crashed. Thanks for your time. :good:
[Nexus 4 Android Development] sbhajband:
When will Magisk work on Mako with Android Q???
[Nexus 4 Android Development] :
Have you tried the Canary or Canary debug versions of magisk? If not then give them a try, they have more fixes going on for Android 10 and system as root configurations. I had to use it on the first Los 17.0 builds for pixel to get rooted as the stable releases caused havoc with certain apps.

Note: there are some bugs with the modules on canary channels so check the Canary thread for info if needed although that may have been fixed by now.
[Nexus 4 Android Development] Longhorn3683:
Feedback

G-sensor doesn't work in LineageOS 17.1:crying:
[Nexus 4 Android Development] Didgeridoohan:
[MENTION=3772648]voron00[/MENTION] I've been playing around with LOS 17.1 on my old Mako, mainly to try to get Magisk running on it. As noted in a few posts above, when trying to install Magisk it installs, but when booted up the Manager reports that "Magisk is not installed". Something isn't working as it should during boot.

Got some help in taking a closer look and it is likely the issue lies in the ROM using a "fake dt" design (dt_dir: /proc/device-tree/firmware/android is being built from runtime). For Magisk to be able to do it's thing you're going to have to use fstab files in ramdisk. Quoting [MENTION=4470081]topjohnwu[/MENTION]: "From init source code, it will prefer fstab in device tree over fstab files, so there is no way Magisk can fix that".

I'm not even gonna pretend that I understand half of this, but I figured I could at least try to relay some info...
[Nexus 4 Android Development] sule_krug:
Does anyone else have a problem with Facebook messenger... Every time I send or receive msg ,my phone goes to deep sleep and I can't wake it up ,I have to reboot my phone , every single time ...was wondering if it's just me or other people have same problem , it started to happening on 16 and now I'm on 17 and its still happens....
[Nexus 4 Android Development] dryphi:
Any idea why it won't download? The little download arrow pops up for a second then disappears.
[Nexus 4 Android Development] shakalaca:
In two stage init, Magiskinit (as init) changes /system to /system_root in fstab or dt first, then continues the original init program. During the early mount process init will try to mount /system or /vendor or /product, change root to /system and hand over the control to /system/bin/init to do the rest (second stage) init tasks. If the patch of Magiskinit is correct init won't mount the real /system partition, Magiskinit as /system/bin/init will bring up the Magisk framework along with original init. From the log above init mounts the original /system and goes on with standard Android booting process instead of switching back to Magiskinit for second stage init, so apparently Magisk couldn't do its job correctly in "fake dt design".

I did a quick test with other A-only SAR device according to this page: https://source.android.com/devices/architecture/kernel/mounting-partitions-early and found a possible way to solve this issue:

1. Make a copy of /vendor/etc/fstab.qcom and append "first_stage_mount" in fs_mgr_flags section of "/system" mount point.

2. Rebuild kernel without fake dt

3. Build new boot.img using new kernel and ramdisk with fstab.qcom in root directory.

I don't have working Nexus 4 (touch panel is broken..) so let me know if it helps :)
[Nexus 4 Android Development] JimKatsanos:
I have no idea... I used to have this issue with Snapchat on Android lollipop, even on stock.... Hardware problem? No idea..
[Nexus 4 Android Development] dahawthorne:
With great respect, this is not a helpful way to answer a question. I see on Amazon, for example, people responding to a question such as "Does it work with Windows 10?" by saying "I have no idea - I use Windows 7".

Please find another way to increase your post score without submitting pointless comments.
[Nexus 4 Android Development] voron00:
first stage mount flag won't work because fstab is in the system partition which isn't mounted if you kill fake DT.
[Nexus 4 Android Development] shakalaca:
You have to place the modified fstab in ramdisk, which will be loaded if there's no dt entry:

https://github.com/LineageOS/android_system_core/blob/lineage-17.1/init/first_stage_mount.cpp#L147

Unless there's no "ro.boot.hardware" property, init will go into GetFstabPath() in ReadDefaultFstab() and parse the /fstab.* in ramdisk eventually:

https://github.com/LineageOS/android_system_core/blob/lineage-17.1/fs_mgr/fs_mgr_fstab.cpp#L448
[Nexus 4 Android Development] voron00:
But ramdisk is also in system partition now, that's why its called system as root.
[Nexus 4 Android Development] shakalaca:
You still need a boot.img to bring up the system, so all you have to do is put the modified fstab into the ramdisk inside boot.img.
[Nexus 4 Android Development] Islam Looca:
No there is no issue with my proximity sensor, this is an issue in Oreo roms only, it is not happening on android 5 or 6 or 7 roms.

My nexus 4 is my daily driver and i make calls from it everyday, if it was a problem from the proximity sensor then it will happen on any android version i use.
[Nexus 4 Android Development] voron00:
No issues with proximity sensor here, but if you could include logs, it could help a lot, also camera is known to be unstable, especially google camera shich is designed for HAL3 mostly, mako is HAL1 only, use stock app or open camera, works more or less fine.
[Nexus 4 Android Development] nitin.chobhe:
That logic there is not correct. Something works in previous android version doesn't imply that it will work on next version. There are lots of things that change across Android versions.

As [MENTION=3772648]voron00[/MENTION] said, it works fine on this ROM (and on Nitrogen or Unlegacy ROMs). So definitely it's just you (and [MENTION=8289179]Karan.S[/MENTION] that you mentioned)

Nitin
[Nexus 4 Android Development] moriel5:
I can confirm that using version 2.7.008 of Google Camera is the last version that works properly on Mako (2.7.010 has always crashed for me, no matter what device I used, and even if I flashed it with OpenGAPPS), and it even works without GAPPS (at least on API24).
[Nexus 4 Android Development] voron00:
Since there are no groundbreaking bugs, builds will be signed with release-keys now, shipping with test keys is not very nice in terms of security, that means you have to clean flash if you are coming from a previous builds.

Update is up:

2018-03-14:
- Synced lastest LineageOS sources.
- Builds are now signed with release-keys (if you are coming from a previous builds, you have to clean flash).
- Wi-Fi driver has been reimported and resolved its mess.
- Upstream kernel workqueue and smp thread idling.
- Other minor fixes (check github).
[Nexus 4 Android Development] vedantdude:
Miracast isn't working, i know this is a beta build but it didn't work on earlier lineage 14 builds, too.
[Nexus 4 Android Development] voron00:
It's a known issue with the hardware encoder unable to record RGBA8888 format, on pre nougat roms, there was a way around that, but seems like after it was deprecated or removed. There are no known way around this for now unfortunately.
[Nexus 4 Android Development] vedantdude:
It worked on unlegacy nougat rom, maybe also on oreo rom if i remember correctly.
[Nexus 4 Android Development] voron00:
AOSP roms use different display color format.
[Nexus 4 Android Development] vedantdude:
Okay. Thanks for your work on mako, I'm loving the oreo lineage.

Btw, to root there wasn't any supersu addon for 15.1. I rooted with SuperSU, guess it didn't root properly, updated binary from within the app as the app told to, phone went into bootloop, reflashed SuperSU zip, and root is fine, now.

Nobody mentioned SuperSU but Magisk, that's why i thought of mentioning it.
[Nexus 4 Android Development] PVL_93_RU:
Does the system partition still have enough space for a Pico or Nano GAPPS package after installing the ROM itself? I usually just go with that and then download/install anything else if needed
[Nexus 4 Android Development] vedantdude:
https://xdaforums.com/showthread.php?p=75779065
[Nexus 4 Android Development] MartinX3:
Will this get official like this previous version?

https://xdaforums.com/nexus-4/orig-development/rom-lineageos-14-1-weeklies-google-t3545269
[Nexus 4 Android Development] voron00:
Proably not, doubt they will accept current HAL1 patches as they likely will break other devices, and we don't have enough system space also.
[Nexus 4 Android Development] MartinX3:
Which amount of space does we need?

My Nexus 6 only needs 790 MB space on the system partition on lineageOS 14.1.

Why we don't rise the amount of space with the custom rom?

And the custom rom could abort the installation, if there isn't enough space left.
[Nexus 4 Android Development] ze7zez:
If [MENTION=2633638]Ziyan[/MENTION] finds a way to reorganize the partition, maybe one day there will be a breakthrough in accessing resources for the system partition.

[MENTION=4473900]amaces[/MENTION] mentioned this possibility in >this< post.
[Nexus 4 Android Development] voron00:
LineageOS policy requires a fully working device, especailly without installation bugs.
[Nexus 4 Android Development] n0b0dy666:
But there is enough space. Or am I missing something here?
[Nexus 4 Android Development] voron00:
Yes but you can't install gapps without manually editing gapps-config file, also in future there proably will not be space for gapps at all.
[Nexus 4 Android Development] n0b0dy666:
I don't think that's LineageOS' concern. As long as there's enough space for the system (LOS), it's good enough to go official.
[Nexus 4 Android Development] Didgeridoohan:
Isn't it called system-as-root because the system partition is mounted to root (/)?
[Nexus 4 Android Development] nitin.chobhe:
[MENTION=3772648]voron00[/MENTION] [MENTION=1813976]shakalaca[/MENTION] I don't know much about the stuff you are talking about, but does this give some more information (and directions to get Magisk working on mako)?:

https://mobile.twitter.com/topjohnwu/status/1226644269261213696

Nitin
[Nexus 4 Android Development] voron00:
Ahh ok now i get it, it seems like they added TARGET_COPY_OUT_RAMDISK to support this https://github.com/LineageOS/android_build/blob/lineage-17.1/core/envsetup.mk#L227

Unfortunately i will not be able to access my PC ultil proably, next week, so i will try that first stage mount flag way as soon as i get back to it.
[Nexus 4 Android Development] nitin.chobhe:
Looks like you can get Magisk to work (whenever you get time) :fingers-crossed:

Nitin
[Nexus 4 Android Development] myxal:
Hello. Revived my mako (mainboard failed) from a backup taken with the last official version (LOS 15.1). Thinking I'd save time by just repartitioning, restoring, and upgrading, instead of fresh install, I'm encountering a lot of showstopper issues (phone app doesn't work, wifi keeps disconnecting, etc.).

What's the recommended way to transfer data from the old installation to the new one (at least installed apps)? TitaniumBackup, as in the old days? (Sorry - I'm not keeping up to date with the latest android changes)