[ROM][UNOFFICIAL] LineageOS-16.0 & 17.1 [mako]

woutercools

Member
Sep 12, 2012
22
9
23
Then I used OpenGapps from 20190929 and everything worked.
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 ----------

Try 0921 OpenGapps Nano. That solved the same issue for me.[/url]
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.
 

voron00

Senior Member
Mar 8, 2011
274
882
123
@voron00: 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/#
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.'
 

carsti77

Member
May 13, 2019
15
2
0
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.'
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?
 

voron00

Senior Member
Mar 8, 2011
274
882
123
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?
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.
 
Last edited:

carsti77

Member
May 13, 2019
15
2
0
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.
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?
 

voron00

Senior Member
Mar 8, 2011
274
882
123
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?
Because linux kernel is always updating, many things gets changed like headers, syscalls, api's, functions and more.
 

carsti77

Member
May 13, 2019
15
2
0
Because linux kernel is always updating, many things gets changed like headers, syscalls, api's, functions and more.
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:
 

Petlo_Lithi

Member
Dec 11, 2019
21
0
0
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
 

voron00

Senior Member
Mar 8, 2011
274
882
123

nitin.chobhe

Recognized Contributor
Jan 3, 2013
8,097
19,497
263
Pune
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
Read the OP before posting anything that's already covered there (and discussed many times in this very thread).

Nitin
 
  • Like
Reactions: dahawthorne

_yr

New member
Dec 12, 2019
1
1
0
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 :eek:
 
  • Like
Reactions: sule_krug

asdasd40

New member
Dec 14, 2019
2
1
0
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
 
Last edited: