Database Users

What happened to all the yoga 2 threads from ionioni and workdowg??

Hey guys, today after a long time i came back around to this subforum to see if there are any news for my yoga 2 380f but all i found were closed threads?! wtf happened?
after so many months of waiting one could finally unlock the bootloader and install a custom recovery - but now even the posts in these threads are empty.... why?

I am in the mids of gathering all the files that I did manage to get before they were removed. My tab is 1050f. Have all the stuff somewhere fore it
Sent from my SM-G901F using Tapatalk

I suspect a New dedicated forum

New TWRP 2.8.7.0 for YT2 1050 soon !
Hello !
Was CLOSED because not respected XDA rules about GPL !
Almost all work here on XDA require open source code ... he preferred to erase everything he did here instead to provide source code
About TWRP :
A recovery image does contain a Linux kernel which is under GPLv2, and the TWRP source code is under GPLv3 (see the license header in https://github.com/omnirom/android_b...d-6.0/twrp.cpp)
Click to expand...
Click to collapse
On the other hand, tomorrow I'll provide a new TWRP 2.8.7.0 UI 6.0 for Yoga Tablet 2 1050 !
I already managed to fix kernel issue on Stock Lenovo Kernel Android L .
I already pushed all my work on my github : twrp-yt2 for TWRP 2.8.7.0 and also for kernel ! I'll update kernel very soon , because right now is stock one .
Also in a short time I'll try to make a cm-13.0 for our device .
Best regards !

surdu_petru said:
Hello !
Was CLOSED because not respected XDA rules about GPL !
Almost all work here on XDA require open source code ... he preferred to erase everything he did here instead to provide source code
About TWRP :
On the other hand, tomorrow I'll provide a new TWRP 2.8.7.0 UI 6.0 for Yoga Tablet 2 1050 !
I already managed to fix kernel issue on Stock Lenovo Kernel Android L .
I already pushed all my work on my github : twrp-yt2 for TWRP 2.8.7.0 and also for kernel ! I'll update kernel very soon , because right now is stock one .
Also in a short time I'll try to make a cm-13.0 for our device .
Best regards !
Click to expand...
Click to collapse
Can I ask what device you are using as a Base or are you building a vendor folder from scratch
Thanks for your work. Looks like you have implemented pixel finger, I will try this later

pug1 said:
Can I ask what device you are using as a Base or are you building a vendor folder from scratch
Thanks for your work. Looks like you have implemented pixel finger, I will try this later
Click to expand...
Click to collapse
Yes, was started from scratch... should be OK for all YT2.
Also pixelflinger for _X86 are implemented, twrp works fine. ... and sure will work on stock Lenovo kernel for Android L.
Best regards.

I take it you will solve the vendor blobs as you build to find them out?
I have twrp 3.0.0-0 source so will try with that.
You said the kernel is solved? It will build if I sync your github? Have you built a kernel yet? If so what toolchain are you using? I couldn't get it to build as it could find my toolchain.
From the branch 5.1 on your github, it won't work with cm13 source?
Again thanks for your work matey

pug1 said:
I take it you will solve the vendor blobs as you build to find them out?
I have twrp 3.0.0-0 source so will try with that.
You said the kernel is solved? It will build if I sync your github? Have you built a kernel yet? If so what toolchain are you using? I couldn't get it to build as it could find my toolchain.
From the branch 5.1 on your github, it won't work with cm13 source?
Again thanks for your work matey
Click to expand...
Click to collapse
Kernel and also twrp must be compiled along with cm-12.1.
As I already said , my kernel source cannot be compiled ...( Lenovo do not provide a complete one ), but I'll update today later in order to fix all Lenovo issues.
Best regards.

New TWRP 2.8.7.0 for YT2 - 1050 ! Source code already available !

[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

LineageOS for microG

Android experience relies heavily on Google's Play Services. The microG project creates an alternative to installing Gapps, which install and execute closed-source blobs on our phones. MicroG however requires a patch called "signature spoofing", which allows microG's apps to spoof themselves as Google Apps. LineageOS currently does not include the patch due to different opinions among the developers. (further information can be found here)
This makes microG installation difficult on LineageOS and other ROMs. Our ROM is a fork of LineageOS with just the necessary changes to have microG built-in. We ship weekly builds for all the LineageOS supported devices..
You can find us on https://lineage.microg.org
XDA:DevDB Information
LineageOS for microG, ROM for all devices (see above for details)
Contributors
Simon94, ncorna, n1zzo, LineageOS, MaR-V-iN
Source Code: https://github.com/lineageos4microg
ROM OS Version: Android 10
Based On: LineageOS
Version Information
Status: Nightly
Created 2017-11-06
Last Updated 2020-08-28

Would like to have build for Nexus 9 aka flounder
Awesome start! Good luck with that! Cheers! :fingers-crossed:

Is this the thread mentioned in the FAQ where one can request builds for other devices supported by LineageOS?
If so, I'd love to see a build for the LG G5 (aka h850), which is currently the only high-end device by a known manufacturer with a removable battery and high repairability (8/10 from Ifixit).
It's fully supported by LineageOS (https://wiki.lineageos.org/devices/h850) and I'd be willing to report any possible problems and help debug it if necessary.
Thanks in advance and awesome project!

Can you please add support for LG G4 (H815) as well?

The LineageOS for microG OTA infrastructure is based on https://github.com/julianxhokaxhiu/LineageOTA?
I'm mounting my own infrastructure and I want to know how to build it. Thanks.

Current device list which will be built tomorrow:
Code:
a6020,angler,armani,athene,bacon,bullhead,cancro,capricorn,cheeseburger,clark,condor,crackling,d855,
deb,dragon,falcon,flo,flounder,gemini,h815,h850,hammerhead,harpia,herolte,here2lte,hlte,i9100,
i9300,jfltexx,kenzo,klte,libra,lux,m8,mako,mido,oneplus2,oneplus3,onyx,osprey,otus,paella,pme,
serranoltexx,shamu,thea,titan,victara,wt88047,yuga,Z00L

Simon94 said:
Current device list which will be built tomorrow:
Code:
a6020,angler,armani,athene,bacon,bullhead,cancro,capricorn,cheeseburger,clark,condor,crackling,d855,
deb,dragon,falcon,flo,flounder,gemini,h815,h850,hammerhead,harpia,herolte,here2lte,hlte,i9100,
i9300,jfltexx,kenzo,klte,libra,lux,m8,mako,mido,oneplus2,oneplus3,onyx,osprey,otus,paella,pme,
serranoltexx,shamu,thea,titan,victara,wt88047,yuga,Z00L
Click to expand...
Click to collapse
Please, include piccolo!

DaniPhii said:
Please, include piccolo!
Click to expand...
Click to collapse
Done!

@Simon94 does it supports substratum ? and thanks for the modded lineage .

Microg.me is a really wonderful project , I have been using it for 3 days, but there are some things that annoy me. In particular, is it really necessary to implement it in every single build ?? I use an application with the same signature, so at each ota it is replaced by the fakestore and that's annoying . Also one ota per day is pretty excessive I think, especially for daily usage. Why not release an update at the same time as the official lineage ?
Please excuse me if the answers to my questions are obvious, I'm a bit new on microg.

Would it be possible to built a pac which could be used for an unofficial LOS-Release to install it e.g. via twrp? I would to love to test the microg-package onto my satsuki (E6833) Sony Xperia Z5 Premium Dual

sandeep_7 said:
@Simon94 does it supports substratum ? and thanks for the modded lineage .
Click to expand...
Click to collapse
Same feature-set as LineageOS. If LOS supports substratum, we are supporting this aswell.
Silver_Defender said:
Microg.me is a really wonderful project , I have been using it for 3 days, but there are some things that annoy me. In particular, is it really necessary to implement it in every single build ?? I use an application with the same signature, so at each ota it is replaced by the fakestore and that's annoying . Also one ota per day is pretty excessive I think, especially for daily usage. Why not release an update at the same time as the official lineage ?
Please excuse me if the answers to my questions are obvious, I'm a bit new on microg.
Click to expand...
Click to collapse
Unfortunately we wont remove FakeStore since our goal is to provide a Google free ROM with a fully working ecosystem which requires having FakeStore installed. Sorry for that. What you could do is to write a script for OTA survival / - or removal and put it in the /system/addon.d directory. But we're not going to support this in any way.
Otherwise we can invite you to not use Play Store, but a replacement like Yalp Store.
We like to build as often as we can. Its up to you and your free choice. If you dont want to update on a daily basis, just dont do it
Best, Simon

MaStErB_1984 said:
Would it be possible to built a pac which could be used for an unofficial LOS-Release to install it e.g. via twrp? I would to love to test the microg-package onto my satsuki (E6833) Sony Xperia Z5 Premium Dual
Click to expand...
Click to collapse
..
https://lineage.microg.org/#faq said:
Can you add support for my device? It is not supported by LineageOS though...
No, I'm sorry.
Click to expand...
Click to collapse

MaStErB_1984 said:
Would it be possible to built a pac which could be used for an unofficial LOS-Release to install it e.g. via twrp? I would to love to test the microg-package onto my satsuki (E6833) Sony Xperia Z5 Premium Dual
Click to expand...
Click to collapse
There are several methods to get microg. Maybe you should start reading there https://forum.xda-developers.com/android/general/index-list-custom-roms-offering-t3557047
My preferred method have been nanomod patcher and shadow53's zip.

I can't find my device in the download section!! Yu yunique (jalebi). As the site says that all the devices with official linegae os support will get this rom?? Pls provide for my device jalebi. Thanks in advance.

Shashank Varma said:
I can't find my device in the download section!! Yu yunique (jalebi). As the site says that all the devices with official linegae os support will get this rom?? Pls provide for my device jalebi. Thanks in advance.
Click to expand...
Click to collapse
Added in next build.

Simon94 said:
Added in next build.
Click to expand...
Click to collapse
Thank you!! Waiting for it

Hey there! I have an old first-gen Moto X as my main android device (ghost) and I'd love to take advantage of your awesome project! I tried to get the docker image up and running myself, but I keep getting random DNS failures in docker, which seem to get silently passed, which results in the build claiming to be successful, yet no builds show up in my "zips" folder when it completes. Only thing that I think needs changed from the default is the lineageOS branch (cm-13.0). Would it be too much trouble to add 'ghost' to your list of builds?
Thank you,
neutral

Can you add support for taoshan (Sony Xperia L)?
Has LOS support.
Thanks!

Moto g5 cedric?

[TREBLE] Project treble for natrium

Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in it
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
What is Project Treble
Project Treble basically partitions your device into two separate partitions, a system and a vendor: system contains your generic system image, while vendor partition has your device specific files required for booting and running your phone. This way we can easily change the system image and be able to run our device on different system images with the same kernel and vendor partition.
About
Weijianism did not build any verdor image of new version because he does not own this device. Although I am not familiar with android source and android build, I am very happy to learn it so that we natrium owners can use project treble.
So I message to Weijianism to know how to do it and have learnt it for a few weeks. Now I am trying to build vendors. Cause I still know a few about it, It is really very hard for me to solve problems in myself. So if you have any advice, please tell me or push you code in github. THANK YOU!
What is NOT WORKING
Camera
Let's test it together.
Download
ALPHA 0815 (boot.img + vendor.img)
How to
1. wipe everything using TWRP
2. flash boot.img + vendor.img
3. flash system.img
4. reboot to system
Sources
Kernel for msm8996 (lineage-15.1)
Configuration for natrium (lineage-15.1)
Configuration for msm8996 (lineage-15.1) (Minor patches)
Proprietary vendor (lineage-15.1) (Minor patches, forked from Weijianism , credits MZO)
XDA: DevDB Information
Project Treble for Mi 5s Plus
Contributors
Justin_hill
Weijianism
Thanks to
LineageOS
Mi 5s Plus devs
@Weijianism
ROM OS Version: 8.x Oreo
Rom Kernel: Linux 3.x
Version Information
Status: Testing
Created: 2018-08-13
Last Updated: 2018-08-16

Anyone try ?

Well, Bluetooth & Camera won't work on any gsi. Bluetooth service has been stopped. Can't connect to camera.
:c

Bluetooth working, but wifi is always dropping. did you take the drivers from los? also very laggy compared to old treble.

1. bootloop problem solved when using rr gsi. (code from hacker1024)
2. bluetooth service stoped problem solved.
QuiseShampe said:
Well, Bluetooth & Camera won't work on any gsi. Bluetooth service has been stopped. Can't connect to camera.
:c
Click to expand...
Click to collapse
The camera's problem seems very hard, I will try to use GCam later. Now I do have no idea about how to solve it.
You may help me solve it if you like!
pote2639 said:
Bluetooth working, but wifi is always dropping. did you take the drivers from los? also very laggy compared to old treble.
Click to expand...
Click to collapse
Yes, I used code and drivers from los totally.
And I really don't know what happened on your device cause you didn't tell me any useful information (such as what gsi and which version). I only find this kind of problem when using gsi of Android P Developer Preview.

justin_hill said:
Yes, I used code and drivers from los totally.
And I really don't know what happened on your device cause you didn't tell me any useful information (such as what gsi and which version). I only find this kind of problem when using gsi of Android P Developer Preview.
Click to expand...
Click to collapse
I used this version sgsi ones. Build PR1.
https://forum.xda-developers.com/pr...ment/rom-android-p-developer-preview-t3816659

pote2639 said:
I used this version sgsi ones. Build PR1.
https://forum.xda-developers.com/pr...ment/rom-android-p-developer-preview-t3816659
Click to expand...
Click to collapse
emm, maybe you should not use version of developer preview there is an experimental build of Android pie.
And I am so sorry that I would not like to spend time on version of developer preview.

justin_hill said:
emm, maybe you should not use version of developer preview there is an experimental build of Android pie.
And I am so sorry that I would not like to spend time on version of developer preview.
Click to expand...
Click to collapse
I guess I'll wait for android p stable sgsi build then.

Good day sir!
Is there any chance that this rom will be available to Mi 5s (Capricorn) soon?

rhp_engcoy said:
Good day sir!
Is there any chance that this rom will be available to Mi 5s (Capricorn) soon?
Click to expand...
Click to collapse
Hope for me get a new natrium and I'll do for capricorn and natrium too.
Ofc, as justin did for natrium already, I'm gonna just ship it on my custom ROMs projects, not separated things like capricorn should get it too.

@justin_hill
This is interesting, thanks for taking this up!
I'd like to mention that my last RR build has more recent vendor files than @Weijianism's treble builds.
I'm not sure why bluetooth only works with an RR GSI... That's weird. We need logs, of course.
I've never ported Project Treble to a device before, but I'm happy to help.
With the camera - I think this old branch of the kernel may work. I have no idea why, though.
P.S. I'm hacker1024 on GitHub.

theOriginalSuperl2 said:
@justin_hill
This is interesting, thanks for taking this up!
I'd like to mention that my last RR build has more recent vendor files than @Weijianism's treble builds.
I'm not sure why bluetooth only works with an RR GSI... That's weird. We need logs, of course.
I've never ported Project Treble to a device before, but I'm happy to help.
With the camera - I think this old branch of the kernel may work. I have no idea why, though.
P.S. I'm hacker1024 on GitHub.
Click to expand...
Click to collapse
Yeah, your code have inspired me a lot when I saw your repositories.
Maybe I fixed the bluetooth problem when I add back the libbtnv.so to /vendor/lib/ since it was deleted in this commit.
For the camera problem, I don't know how vendor module relates to kernel. But I will try it afterwards.
Actually I almost know nothing about lineage source code, system build skills and things like this. If you can help, it will be grateful!

any news on the development?

Crescendo Xenomorph said:
any news on the development?
Click to expand...
Click to collapse
About treble support I can tell that I'm gonna include in my ROMs, and maybe I'll give some vendor zips too, if @justin_hill doesn't care about that.

Crescendo Xenomorph said:
any news on the development?
Click to expand...
Click to collapse
Sorry, I am trying to do something about Treble for Android Pie, But there are still several problems unsolved. Cause I'm not familiar with those code, so maybe I can't solve it by myself. It will be so grateful if anyone can contribute to it.
So we will expect @Hlcpereira WORK, Thank you so much!

Hey, is the camera problem solved?

It can't be booting on any sgsi so what should i
do

Build my own LOS / sources for LineageOS 15.1

Hello,
I want to compile my own LineageOS 15.1 ROM for G950F/dreamlte but i can't find sourcetrees device, kernel, vendor or manifest/roomservice.xml.
Can everyone help me ?
Thank you very much.
Cu Frank

8224Freak said:
Hello,
I want to compile my own LineageOS 15.1 ROM for G950F/dreamlte but i can't find sourcetrees device, kernel, vendor or manifest/roomservice.xml.
Can everyone help me ?
Thank you very much.
Cu Frank
Click to expand...
Click to collapse
Lineage 15.1/16 is already released by another developer, @Ivan_Meler, and he has not released the device tree as it's incomplete. (Fingerprint, hotspot, etc.) Hence, these source trees aren't uploaded yet. You can find the LOS threads in the Cross-Development section.

8224Freak said:
Hello,
I want to compile my own LineageOS 15.1 ROM for G950F/dreamlte but i can't find sourcetrees device, kernel, vendor or manifest/roomservice.xml.
Can everyone help me ?
Thank you very much.
Cu Frank
Click to expand...
Click to collapse
Try looking here https://github.com/travismills82?tab=repositories or PM-ing Ivan_Meler, you are welcome on the LOS fdev

Visera said:
Lineage 15.1/16 is already released by another developer, @Ivan_Meler, and he has not released the device tree as it's incomplete. (Fingerprint, hotspot, etc.) Hence, these source trees aren't uploaded yet. You can find the LOS threads in the Cross-Development section.
Click to expand...
Click to collapse
No, the reason behind why he hasn't released the device tree yet because it contains proprietary files that he can't release.