KRACK and LineageOS 13.0 - LineageOS News & Discussion

Hello,
Is the fix for the KRACK vulnerability backportable to LineageOS 13.0? For those of us still on 13.0 that would be great.
If it is backportable, what steps are required?
Thanks,
-Mark

voidzero said:
Hello,
Is the fix for the KRACK vulnerability backportable to LineageOS 13.0? For those of us still on 13.0 that would be great.
If it is backportable, what steps are required?
Thanks,
-Mark
Click to expand...
Click to collapse
I found a great dev who made an app to mitigate the vulnerability.
https://forum.xda-developers.com/android/general/app-anti-krack-vulnerability-mitigation-t3690211
It's the best there is for now.

this rom v14 really heatup my lg g4 h815 dont know why

Related

[ROM][UNOFFICIAL][natrium][7.1] Resurrection Remix

Hi guys,
For all of you wanting to try out Resurrection Remix on their beloved Xiaomi mi5s Plus, I have made a build.
I think I do not need to introduce Resurrection Remix.
You probably all know about that fantastic ROM.
I just would like to stress that I take absolutely no credit for this.
All the credit goes to the magnificent work of Luk1337 : I bow down to him for his work on closed sources !
Of course the rest of the credit goes to the wonderful Resurrection Remix team... The number of features they've included and still managed to offer a stable and smooth ROM is amazing !
Of course, as I am just a compiler, but not a developer : I can offer no real support for this.
So take it as it is...
I don't even have time to check those builds.
So they're basically blind builds that may not even boot
But without further ado : here's the link...
Enjoy !
LATEST BUILD 2017-04-09 : https://drive.google.com/open?id=0Bz7S7jFQDiz8NXpLeEg2emY5ZGM
Of course, to comply with XDA rules about sources :
- ROM Source : https://github.com/ResurrectionRemix
- Device tree : https://github.com/LineageOS/android_device_xiaomi_natrium
- Gerrit to include the latest add-ons from Luk1337 : https://review.lineageos.org/#/q/status:open+topic:natrium
- Proprietary blobs : https://github.com/Mi5Devs/proprietary_vendor_xiaomi/tree/cm-14.1-natrium
- loca_manifests.xml file : https://github.com/NexusPenguin/local_manifests/blob/natrium_laos/natrium
With all this you get all you need to compile.
If you're feeling like it, do it yourself
Regards.
NexusPenguin
Amazing friend its the buil 20170324?? The same that you share me?
fiskersc said:
Amazing friend its the buil 20170324?? The same that you share me?
Click to expand...
Click to collapse
Hi,
Yes. So far it is.
I think there are 1 or 2 commits that I can add that haven't been merged by Luk so far.
I'll try to build today and upload.
I'll keep you posted.
Regards.
NexusPenguin said:
Hi,
Yes. So far it is.
I think there are 1 or 2 commits that I can add that haven't been merged by Luk so far.
I'll try to build today and upload.
I'll keep you posted.
Regards.
Click to expand...
Click to collapse
Thank for your work
How is this build working? Same issues from the source ROM? THX!
Good job.
This ROM I love me. Only I have seen a bug in the camera, this when record not save in the gallery. Is bug in ROM Lineage buid 24th the March is same.
Battery drain.
I whould me official build for this device. But little to little this develop is more big.
Very good, thank you for your work, RR is top
coco19821961 said:
This ROM I love me. Only I have seen a bug in the camera, this when record not save in the gallery. Is bug in ROM Lineage buid 24th the March is same.
Click to expand...
Click to collapse
Yes its the same bug on LineageOS
I'm waiting your build and latest lineageos has fixed record bug.
Thankyouforyourbuild
wolfwork said:
I'm waiting your build and latest lineageos has fixed record bug.
Thankyouforyourbuild
Click to expand...
Click to collapse
Yes in the build at 25th March is fixed
Hi guys,
New build is up. Link is in OP
Includes all the latest commits from Luk1337 (it's him you got to thank for making this possible).
Please report if it boots.
Bugs should be the same as the ones in Lineage.
Hope Xiaomi releases source code for this device some day... but it seems that will never happen
NexusPenguin said:
Hi guys,
New build is up. Link is in OP
Includes all the latest commits from Luk1337 (it's him you got to thank for making this possible).
Please report if it boots.
Bugs should be the same as the ones in Lineage.
Hope Xiaomi releases source code for this device some day... but it seems that will never happen
Click to expand...
Click to collapse
Where is the link for the new build??
fiskersc said:
Where is the link for the new build??
Click to expand...
Click to collapse
Hi,
Look at my post
It says "Link is in OP"
Thought it was obvious that it was under "Here goes Mark II"
Regards.
It boots correctly, the bug was solved. I done a dirty installation over the old rom.
Faster, smooth, substratum works well.
Amazing man thanks.
Hi guys,
Are you able to change the launcher in RR on Natrium ?
Me, it seems I've lost that feature
Or maybe I have overlooked it...
Any hint ?
Regards.
NexusPenguin said:
Hi guys,
Are you able to change the launcher in RR on Natrium ?
Me, it seems I've lost that feature
Or maybe I have overlooked it...
Any hint ?
Regards.
Click to expand...
Click to collapse
As in actually the launcher? Try home switcher in the app store, downloading another launcher or "clear default" under your current launcher app in all your apps.
Edit: I forgot, you can also go to your apps, touch the cogwheel and change your home app.
Hi,
Yeah... I found it ! Thanks a lot...
Man, it's there but they've hidden it really well !
Why didn't they left it with the "Home" in the settings is a mystery...
Now I have to confirm that with Resurrection Remix I've managed to fix (or almost fix) my GPS problems.
Regards.
NexusPenguin said:
Hi guys,
New build is up. Link is in OP
Includes all the latest commits from Luk1337 (it's him you got to thank for making this possible).
Please report if it boots.
Bugs should be the same as the ones in Lineage.
Hope Xiaomi releases source code for this device some day... but it seems that will never happen
Click to expand...
Click to collapse
Every works fine except led notofication. In version of lineage 26th,27th and toda y 28th works fine.
What happened in Resurrection Remix?
Is possible make a flasheable zip or new build for fix it?
Thanks in advance and good work friend.
isaakmg said:
Every works fine except led notofication. In version of lineage 26th,27th and toda y 28th works fine.
What happened in Resurrection Remix?
Is possible make a flasheable zip or new build for fix it?
Thanks in advance and good work friend.
Click to expand...
Click to collapse
Hi,
It seems that when building the MkII version, I forgot to include one of the commits on the gerrit.
And that is the one that enables notifications
Will include it and rebuild.
Stay put, I'll tell you when it's done

[UPDATE] LineageOS 13 STABLE with june security patch

lineage 13.0 with sources updated and camera reboots fixed!
Download > https://androidfilehost.com/?fid=889764386195910570
enjoy :fingers-crossed:
did you make any specific changes on this rom?
chepui said:
did you make any specific changes on this rom?
Click to expand...
Click to collapse
No

[VK810] [Altev] [Recovery] TWRP 3.3.0-0 Unofficial

Here's a build of TWRP Recovery 3.3.0-0 for the VK810: twrp-3.3.0-0-vk810.img
To install for the first time, follow the same instructions as for the other LG G Pad 8.3 models here: https://twrp.me/lg/lggpad83.html
If already rooted, just download the file and from a local terminal window type:
Code:
su
dd if=/sdcard/Download/twrp-3.3.0-0-vk810.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Or on a device that already has an older version of TWRP installed, select Install, tap Install Image, pick the .img file, select Recovery partition, and swipe to install.
I built this from the official TWRP project for the V500, but used the kernel from the unofficial LineageOS 14.1 build available here.
If you want to make modifications or updates, my device configuration project for the VK810 (and V500) are available here: https://github.com/Magendanz/android_device_lge
Note that I just updated the build to TWRP 3.2.1-0. I've also switched to the LineageOS 14.1 prebuilt kernel.
Just updated the build to TWRP v3.2.2-0. Release notes are here.
Magendanz said:
Just updated the build to TWRP v3.2.2-0. Release notes are here.
Click to expand...
Click to collapse
Do you have any custom roms planned? Or do you know of any good ones available now? Thanks for the new TWRP btw!
JTruj1ll0923 said:
Do you have any custom roms planned? Or do you know of any good ones available now? Thanks for the new TWRP btw!
Click to expand...
Click to collapse
I've been using the LineageOS 14.1 builds from @invisiblek (Dan) available here. However, it does have a problem accessing the device sensors, so you can't rotate the screen to change orientation or play many games. I'm anxiously awaiting a LOS 15.1 build.
Magendanz said:
I've been using the LineageOS 14.1 builds from @invisiblek (Dan) available here. However, it does have a problem accessing the device sensors, so you can't rotate the screen to change orientation or play many games. I'm anxiously awaiting a LOS 15.1 build.
Click to expand...
Click to collapse
I tried it and i kept having the screen flicker. Do you have that? I know there is a 8.1 rom for v500... Wonder if there is a way to build off of that? I just barely got this device working again after losing it from a move.
JTruj1ll0923 said:
I tried it and i kept having the screen flicker. Do you have that? I know there is a 8.1 rom for v500.. Wonder if there is a way to build off of that?
Click to expand...
Click to collapse
No, I haven't had a problem with screen flicker. The only OREO 8.1 build for v500 that I've seen is this crDroid one from @beroid. If we can find a nice clean LineageOS 15.1 project for v500 like we have for LineageOS 14.1, I can make the modifications to build for vk810. I did it for LineageOS 14.1 using these instructions, but ran into the same problem with the device sensors.
Magendanz said:
No, I haven't had a problem with screen flicker. The only OREO 8.1 build for v500 that I've seen is this crDroid one from @beroid. If we can find a nice clean LineageOS 15.1 project for v500 like we have for LineageOS 14.1, I can make the modifications to build for vk810. I did it for LineageOS 14.1 using these instructions, but ran into the same problem with the device sensors.
Click to expand...
Click to collapse
If I had a computer I could try and be of use, but sadly mine is out of service until I start my new job here soon.
Just updated the build to TWRP v3.2.3-0. Release notes are here. We're now building using the twrp-6.0 branch, just like the official v500 device tree.
Thanks for the updates!

Would we get anymore RR, AEX & HavoC Builds?

Will be any dev to work on RR,AEX & HavoC?
Those were all by our beloved Nfound, who has unfortunately moved on from the Axon 7.
Looks like the only options for updated builds are going to be the Lineage builds (14.1, 15.1, 16.0) , OR you could use generic treble GSIs which should almost be stable.(but won't be specific to our device.)
But for that we have to wait long time to get a stable treble
alwynjoshy said:
But for that we have to wait long time to get a stable treble
Click to expand...
Click to collapse
For me treble is very stable, I'm running pixelexperience and is great
J0nhy said:
For me treble is very stable, I'm running pixelexperience and is great
Click to expand...
Click to collapse
you have a link?
alwynjoshy said:
Will be any dev to work on RR,AEX & HavoC?
Click to expand...
Click to collapse
Who knows.
We've got Treble, but we still need some kind of universal patch for GSI roms to fix audio.
Everything else should work. (Personally, I didn't tried, staying with LOS 15 because of DAC)
Try latest AEX 5.8 from Nfound and Swifty R4 kernel.
xerocopy said:
Who knows.
We've got Treble, but we still need some kind of universal patch for GSI roms to fix audio.
Everything else should work. (Personally, I didn't tried, staying with LOS 15 because of DAC)
Try latest AEX 5.8 from Nfound and Swifty R4 kernel.
Click to expand...
Click to collapse
LOS 16 is the problem, and at least it hasn't got the crippling audio bug present in all B12 base builds. Of course having the DAC would be awesome, but I guess it all depends on getting the blobs from somewhere (though i have no idea of course)
I think 15.1 uses the DAC and hasn't got the audio bug but i'm not sure. Maybe the devs will end up fixing it if it does have it.
Zobat said:
you have a link?
Click to expand...
Click to collapse
Sure man,
https://forum.xda-developers.com/pr...ce-development/9-0-pixelexperience-p-t3833294
J0nhy said:
Sure man,
https://forum.xda-developers.com/pr...ce-development/9-0-pixelexperience-p-t3833294
Click to expand...
Click to collapse
Would you care to write how did you install image?
Only format System / Data and then flashing?
I'm currently on AEX 5.8 TREBLE with TWRP_3.2.1-8-TREBLE
And did you have any sound call isues with PixelExperience?
Thanks a lot
Choose an username... said:
LOS 16 is the problem, and at least it hasn't got the crippling audio bug present in all B12 base builds. Of course having the DAC would be awesome, but I guess it all depends on getting the blobs from somewhere (though i have no idea of course)
I think 15.1 uses the DAC and hasn't got the audio bug but i'm not sure. Maybe the devs will end up fixing it if it does have it.
Click to expand...
Click to collapse
AFAIK DAC works in LOS 16.
15.1 has the audio bug, even on the latest build. Orden didn't patch it, just for LOS 16.
LOS16 is the best choice right now. Smooth, NFC, Hotspot, DAC, no audio bug, etc. GSI are too problematic and laggy.
xerocopy said:
Who knows.
We've got Treble, but we still need some kind of universal patch for GSI roms to fix audio.
Everything else should work. (Personally, I didn't tried, staying with LOS 15 because of DAC)
Try latest AEX 5.8 from Nfound and Swifty R4 kernel.
Click to expand...
Click to collapse
Don't you have call bug on last treble AEX?
alwynjoshy said:
Don't you have call bug on last treble AEX?
Click to expand...
Click to collapse
Oh, you remind me something. I didn't have 'that' call bug.
Some people got problem on AEX 5.7/5.8 and other roms with call bug, it was caused LTE itself or Volte.
Try to change your APNs or Preffered Network Type to Global from LTE.
Edit: Check this thread.
I'm on A2017G LOS 15.1 (Schwifty R4 Kernel + LXT Glassfish profile), but I didn't get that bug when I was on AEX 5.8.
AEX 5.8 (with newer LOS 15.1 vendor and Schwifty R4) should be brillant. I will go back when new version of LOS 15.1 will comeout.
xerocopy said:
Oh, you remind me something. I didn't have 'that' call bug.
Some people got problem on AEX 5.7/5.8 and other roms with call bug, it was caused LTE itself or Volte.
Try to change your APNs or Preffered Network Type to Global from LTE.
Edit: Check this thread.
I'm on A2017G LOS 15.1 (Schwifty R4 Kernel + LXT Glassfish profile), but I didn't get that bug when I was on AEX 5.8.
AEX 5.8 (with newer LOS 15.1 vendor and Schwifty R4) should be brillant. I will go back when new version of LOS 15.1 will comeout.
Click to expand...
Click to collapse
My device is U model. I tried that way, changed to global but no improvement. But i noticed one thing that while ringing if i change the network mode or put the phone to flight mode tyen the calls went to voicemail so that we can identify that is the problem with rom. So far i got only one treble rom that has no call Error. ?️RR TREBLE ROM
alwynjoshy said:
My device is U model. I tried that way, changed to global but no improvement. But i noticed one thing that while ringing if i change the network mode or put the phone to flight mode tyen the calls went to voicemail so that we can identify that is the problem with rom. So far i got only one treble rom that has no call Error. ️RR TREBLE ROM
Click to expand...
Click to collapse
Whoa, NFound update his rom for Axon 7 yesterday!
AospExtended-v5.8-axon7-20180906-TREBLE.zip
Maybe he fixed that bug, I can't find anything on 4pda.ru. Sadly, he closed his own thread ona XDA.
Edit: Probably Sept. Security patches, nothing else.
xerocopy said:
Whoa, NFound update his rom for Axon 7 yesterday!
AospExtended-v5.8-axon7-20180906-TREBLE.zip
Maybe he fixed that bug, I can't find anything on 4pda.ru. Sadly, he closed his own thread ona XDA.
Edit: Probably Sept. Security patches, nothing else.
Click to expand...
Click to collapse
New AEX 8.1 build security patches are based on the OPM6.171019.030.K1 Nexus and has the latest sept.05 fixes (as the sept.01 fixes)
Code:
ro.build.id=OPM6.171019.030.K1
ro.build.version.security_patch=2018-09-05
xerocopy said:
Whoa, NFound update his rom for Axon 7 yesterday!
AospExtended-v5.8-axon7-20180906-TREBLE.zip
Maybe he fixed that bug, I can't find anything on 4pda.ru. Sadly, he closed his own thread ona XDA.
Edit: Probably Sept. Security patches, nothing else.
Click to expand...
Click to collapse
raystef66 said:
New AEX 8.1 build security patches are based on the OPM6.171019.030.K1 Nexus and has the latest sept.05 fixes (as the sept.01 fixes)
Code:
ro.build.id=OPM6.171019.030.K1
ro.build.version.security_patch=2018-09-05
Click to expand...
Click to collapse
Sadly this Rom also have the Call bug, the problems starts from second reboot, after clean install there were no issues but after from second reboot the problem starts, tried the global settings also
alwynjoshy said:
New AEX 8.1 build security patches are based on the OPM6.171019.030.K1 Nexus and has the latest sept.05 fixes (as the sept.01 fixes)
Sadly this Rom also have the Call bug, the problems starts from second reboot, after clean install there were no issues but after from second reboot the problem starts, tried the global settings also
Click to expand...
Click to collapse
Also AEX v6 GSI seems to be in the making (per NFound on telegram). We need a thread to exchange info & experience about these roms.
piet8stevens said:
Also AEX v6 GSI seems to be in the making (per NFound on telegram). We need a thread to exchange info & experience about these roms.
Click to expand...
Click to collapse
I tested the new AEX 9 build but it's almost the same as the AospExtended-v6.0-chiron-20180902-1012-ALPHA build from a couple of days ago floating on the MiMix2 net. I made a flashable zip of the build and as this one, it has a call bug, no NFC, not to many customs (as it is alpha...) (the Benzo rom or PE have way more customs atm and calls are working flawless...)
raystef66 said:
I tested the 'new' AEX 9 build but it's almost the same as the AospExtended-v6.0-chiron-20180902-1012-ALPHA build from a couple of days ago floating on the MiMix2 net. I made a flashable zip of the build and as this one, it has a call bug, no NFC, not to many customs (as it is alpha...) as the Benzo rom or PE who have way more customs atm...
Click to expand...
Click to collapse
Which /vendor do you use?
If I treblerize with LOS15. 1, can I flash any treble rom (GSI) ? Will encryption and restrictive selinux work?
What do you use currently as daily driver?
Have you tested latest NFound AEX5. 8 (from telegram - 20180906)? If so, with which /vendor?
piet8stevens said:
Which /vendor do you use?
If I treblerize with LOS15. 1, can I flash any treble rom (GSI) ? Will encryption and restrictive selinux work?
What do you use currently as daily driver?
Have you tested latest NFound AEX5. 8 (from telegram - 20180906)? If so, with which /vendor?
Click to expand...
Click to collapse
I'll always recommend the v1.1 NFounds way.
Benzo and PixelExperience are imo the best to use even as a daily driver. My focus is on Benzo as everything works beside the Hotspot (NFC is working with the @kountry83 NFC- fix ). Rest is flawless and a bunch of customization as I dont find that on other Pie's (only on PE). Even a 5hSOT with average use.
BenzoPie
PixelExperience
credits to them

Magisk: Some problem with the last LAOS update.

Hi, the latest LAOS releases on my Willow (Redmi Note 8T) have some problems with Magisk Plugins but not only Magisk itself has some problems. This summer I was using LAOS 18.1 with Magisk and the plugins without any problems and they worked. Now with the latest releases they don't work anymore. Since the only thing that has been updated is the LAOS updates I am thinking that the problem comes from some modification of them. Screenshots of the problem are visible on: https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-85784831
Anyone know about this issue? Thank you.

Categories

Resources