[ROM][Unofficial][markw][6.0.1]Lineage Os 13.0 for Redmi 4 Prime/Pro

[GuestD0714]

Add persist.debug.wfd.enable=1 to build.prop for enable Miracast

Inviato dal mio Redmi 4 Prime utilizzando Tapatalk

After reboot you have to enable this: (see picture)


Inviato dal mio Redmi 4 Prime utilizzando Tapatalk

 

[cimdrap]

Camera crash log

 

[BlaX72]

Check your bootloader status with "fastboot oem device-info". I think it is locked. If it's unlocked explain how you flash the recovery

I've already stated that i checked whether the bootloader is locked. Its unlocked. And I flashed recovery the same way i did it hundred times since i had Nexus 7: fastboot flash recovery *recovery_name*.img

 

[Alecotro]

Has it ever worked? If so, which build? Maybe it's the new blobs, does it work though Miracast?

With stock miui it worked, sorry, but I never tried with other ROM.
When I'm home I'll update this post with the answer to miracast.
Update:
-miracast confirmed
-with build.prop tweak by @Yoshi02 now it works

 

[asfethan]

People with logs, just host it somewhere and send me the link through pm, I'll look into BT issue.

Hi there again, I was testing MIUI ROM for some days and here are some my discoveries.
- probably there is no problem with BT pairing after all
- the only one difference I can see between MIUI and this LineageOS build is that MIUI will reconnect noticeably faster after connection loss

I enabled BT logging and disconnected remote device by disabling its bluetooth. Then I re-enabled it again and after some waiting I disabled logging and retrieved the file from phone. Remote device is still disconnected which is far longer than on MIUI ROM.

I'll send you link to that log via PM. I can also log whole time until remote device reconnects but sometime it's more than hour.

UPDATE: Probably I was wrong again. I couldn't pair with watches again using several attempts after first successful pairing. I tried to reboot the phone and then I could pair them on first try.

 

[Alezzander_]

I couldn't pair with watches again using several attempts after first successful pairing.

Try: Forget Paired device (watches) in Bluetooth menu (gear opposite the pairing device), then Paire your watch again. I use this method when try to connect to the Car Bluetooth. This help to me.

 

[baggino]

Sometimes I miss the call ringing, I go, in settings> sounds, and no ringtone is selected. Has it happened to some of you too? With miui, this did not happen

 

[rabin69x]

can anyone confirm me about HW decoder working for 1080p videos or not? And I don't like HW+ decoder

Sent from my Redmi 4 using Tapatalk

 

[Flynhx]

can anyone confirm me about HW decoder working for 1080p videos or not? And I don't like HW+ decoder

Sent from my Redmi 4 using Tapatalk

HW decoder works fine on my phone with this ROM, Played it with this type of video, 1080p/MP4 format/x264 video codec/aac audio codec

Sent from my Redmi 4 Prime using XDA-Developers Legacy app

 

[smaxlyb]

nice

 

[jacoghi]

Ok, people, update was posted, good changes are:

- Hopefully fixed the biggest deal breaker for selfie whiners, front camera, however, since there are 3 different front camera models for this device, let me know if there are problems, and if so, your specific camera model;
- New media encoding libraries, should be way faster to generate encoded multimedia files - this doesn't affect pictures, only videos and audio;
- New audio and BT libraries, let me know if the problem with the watch still persists;
- Applied patch as indicated by our great friend, Raziel. People with two SIMs, let me know if SIM settings are still being messed up after reboot;
- Miracast now should be working out of the box, let me know;

Bad same thing:
- A-GPS isn't as simple as I initially imagined, I'll leave it the way it is for now, so keep it in device only mode;

ROM won't be updated over next days, since I'll go back to MIUI looking to find out some things that are still bothering me related to AGPS and Power. Anyways, let me know if you have problems.

 

[jacoghi]

Ok, guys, I just had a shed of light brightening me up and found the reason for our AGPS not working, which is kind of an issue... So for this, I would like to get your opinions...

The AGPS module depends on the proprietary wifi module, which we don't have anymore. The reason for that being is that you can't use the proprietary wifi module using a kernel built from source... So, the two options are:
1) Go ahead the way we are, High accuracy and battery saving modes will NEVER work properly on CM13, but we can change our kernel at will and change things like fixing the front camera... (sure this is correct on stock camera, was messed up on sources released by Xiaomi)
2) Use the stock kernel from Xiaomi, which will work with AGPS perfectly, but we'll be stranded with that kernel for the rest of the days.

I personally don't use high accuracy as I already said many times, anyways, I'd like to get your opinion on this.

 

[Razziell]

Ok, guys, I just had a shed of light brightening me up and found the reason for our AGPS not working, which is kind of an issue... So for this, I would like to get your opinions...

The AGPS module depends on the proprietary wifi module, which we don't have anymore. The reason for that being is that you can't use the proprietary wifi module using a kernel built from source... So, the two options are:
1) Go ahead the way we are, High accuracy and battery saving modes will NEVER work properly on CM13, but we can change our kernel at will and change things like fixing the front camera... (sure this is correct on stock camera, was messed up on sources released by Xiaomi)
2) Use the stock kernel from Xiaomi, which will work with AGPS perfectly, but we'll be stranded with that kernel for the rest of the days.

I personally don't use high accuracy as I already said many times, anyways, I'd like to get your opinion on this.

Maybe I do not understand something, but why not use it https://github.com/markw-dev/androi...mmit/3f441ef3f0ea1d66bd4a2a1b9a3cf91987154227 ?
P.S. Is it worth waiting for your current source at Github?

 

[jacoghi]

Maybe I do not understand something, but why not use it https://github.com/markw-dev/androi...mmit/3f441ef3f0ea1d66bd4a2a1b9a3cf91987154227 ?
P.S. Is it worth waiting for your current source at Github?

The open source wlan drivers don't contain instructions to communicate with the lowi server, my friend, it just will never work. The only module with those instructions is the one that comes from stock, which only works with the kernel it was compiled with. So an open source driver will never work.

I'm too lazy for git, my friend, find it attached. Kernel is stock, pronto drivers and fixes for cpusets (which is now completely disabled on my build, phone loses performance like hell).

 

[Razziell]

My ROM

 

[jacoghi]

My ROM

That's the hardware GPS, my friend. AGPS is the assisted one, that uses Wifi and RIL, nothing to do with that.

 

[Razziell]

If works so well, why suffer? Agps need for more initial quick search.

 

[jacoghi]

If works so well, why suffer? Agps need for more initial quick search.

There are some services that only work with Google Location History, which uses the assisted GPS. It's a matter of having a fully working rom just like MIUI with no bottlenecks and without the Chinese bloat.

 

[cimdrap]

2) Use the stock kernel from Xiaomi, which will work with AGPS perfectly, but we'll be stranded with that kernel for the rest of the days.

I personally don't use high accuracy as I already said many times, anyways, I'd like to get your opinion on this.

I think that this is the best option for now. We could still use the buil.prop line to get camera working... Am i right?

 

[asfethan]

Ok, guys, I just had a shed of light brightening me up and found the reason for our AGPS not working, which is kind of an issue... So for this, I would like to get your opinions...

The AGPS module depends on the proprietary wifi module, which we don't have anymore. The reason for that being is that you can't use the proprietary wifi module using a kernel built from source... So, the two options are:
1) Go ahead the way we are, High accuracy and battery saving modes will NEVER work properly on CM13, but we can change our kernel at will and change things like fixing the front camera... (sure this is correct on stock camera, was messed up on sources released by Xiaomi)
2) Use the stock kernel from Xiaomi, which will work with AGPS perfectly, but we'll be stranded with that kernel for the rest of the days.

I personally don't use high accuracy as I already said many times, anyways, I'd like to get your opinion on this.

If you are interested in my opinion, I think it's better to go with OSS with benefits like updates, fixes, customization.
Personaly I never use high accuracy mode and also I don't like to participiate in networks scanning.

BUT.

I don't know if is it related to kernel or libs, or whatever but I have lags when I'm taking photos.
This lag can be described as ability to shake-blur photo after you press shutter because photo isn't taken immediately (there is mentioned lag).
I have this issue with every camera application I can try. I had this issue also on Xiaomi Redmi Note 2 with CM13 and it wasn't present on MIUI ROM.
I was suspecting need of some proprietary stuff which stock ROM/kernel has and CM hasn't.
If msdx321's ROM has stock kernel then I assume it's some proprietary stuff again because I didn't have such issues (tried only with camera app present in that rom).

And well if we sum all of this, for me it's still about 50 : 50 - proprietary : oss, so I am pretty undecided.
If there is way to fix the camera without proprietary blob, I'll definitely vote for oss no matter in what state will be that location stuff.