How To Guide [CLOSED][ISO] [19H2]Win10.0.18363.2158 Fine-tuning - Windows 10, 8, 7, XP etc.

Most people agree that the 1909 version has good stability and performance. It was updated not long ago, and Microsoft has a long time to support and maintain 19H2. So, I made a streamlined and optimized wim, suitable for people who are looking for stability.
Click to expand...
Click to collapse
Take 18363.2158 downloaded by UUP as the original image, including three branches: Professional Edition, Professional for Workstation Edition, and ioT Enterprise Edition​
While being lightly streamlined, try to maintain image integrity, support WinRE recovery, support WinBoot native installation, WTG, subsystems and other functions, and can also be updated~​
The actual test allocates 4GB RAM and occupies about 1GB. The main optimization and streamlining items are as follows​
[*][B]0. This system was never packaged! Simplified with MSMG Toolkit as the main tool (including NTLite and DISM++, etc. The configuration file of the NTLite streamlined project has been released, please check it yourself for DISM++)
1. Remove some applications and components, such as Edge, Cortana, Voice, and various accessories that have not been updated for a long time and have a bad experience. You can find a way to restore it yourself or replace it with a stronger software of the same type.
2. Remove or close applications or experience programs that collect user privacy and occupy performance
3. Uninstall and turn off Defender, Firewall and its automatic updates
4. Disable MPO to prevent foreground applications from being stuck due to busy GPU
5. The desktop displays IE browser, etc.[/B]
[*]
Download Links:
{Mod edit: Link removed}
OneDrive:https://liuxiane5-my.sharepoint.com...NNrmY9yD4i1qoBou-wpu3FpsjBc-s7Y0R3zg?e=tQ2wR1
File Name:AllLite18363.2158_3in1wim.iso​4.06 GB (4,367,056,896 Bits)
MD5: CC711ADE83D750D562835B87AC247DF7
SHA1: 0E7260EA651FD5C87992D312B5B931E469F0B6F0
2022.03.18,13:01:05
SHA256: 5C82C2739FD7A65B47D416EC55FA96DAACB2DD28758744F3C7902DD29B086DC5
SHA512: 64C3C41CA62F6C55D704F440F847986806878C078E6195C1BF58EF5CB0C0A1392376A7FBB1C9B91CFB81219BD739BB5EEA13979ADFBFD542CD95081C2B3E5DFB
CRC32: BF6D51D2
Formula file for NTLite: {Mod edit: Link removed}​
XML:
<?xml version="1.0" encoding="utf-8"?><Preset xmlns="urn:schemas-nliteos-com:pn.v1">
<Date>03/18/2022 12:25:35</Date>
<AppInfo>
<Version>1.8.0.6790</Version>
<Licensed>Yes</Licensed>
<Protections>Yes</Protections>
<Host>Windows 10 Pro for Workstations (2009) x64 - Client 10.0.22572.201 (zh-CN)</Host>
</AppInfo>
<ImageInfo>
<Version mode="offline">Windows 10 IoTEnterprise (1909) x64 - Client 10.0.18362.2158 (zh-CN)</Version>
<GUID>{031AC7B0-E28E-49BE-BF7A-75F24972E0CB}</GUID>
</ImageInfo>
<RemoveComponents></RemoveComponents>
<Compatibility protectHidden="true">
<ComponentFeatures>
<Feature enabled="yes">OOBE</Feature>
<Feature enabled="no">Hyper-V</Feature>
<Feature enabled="yes">OfficeSupport</Feature>
<Feature enabled="yes">NvidiaSetup</Feature>
<Feature enabled="yes">SafeMode</Feature>
<Feature enabled="no">SamsungSwitch</Feature>
<Feature enabled="yes">ShellSearchSupport</Feature>
<Feature enabled="yes">Spotify</Feature>
<Feature enabled="yes">USBModem</Feature>
<Feature enabled="yes">USB</Feature>
<Feature enabled="no">VisualStudio</Feature>
<Feature enabled="no">VPN</Feature>
<Feature enabled="yes">AppxSupport</Feature>
<Feature enabled="yes">WindowsUpdate</Feature>
<Feature enabled="yes">ActivationKMS</Feature>
<Feature enabled="yes">Activation</Feature>
<Feature enabled="yes">WLAN</Feature>
<Feature enabled="yes">Printing</Feature>
<Feature enabled="no">Recommended-All</Feature>
<Feature enabled="yes">ServicingStack</Feature>
<Feature enabled="no">NetworkDiscovery</Feature>
<Feature enabled="yes">VideoPlayback</Feature>
<Feature enabled="no">Recommended-Tablet</Feature>
<Feature enabled="yes">DefaultFonts</Feature>
</ComponentFeatures>
<MachineDrivers>
<Machine enabled="no">Hyper-V VM</Machine>
<Machine enabled="no">Parallels VM</Machine>
<Machine enabled="no">Virtual Box VM</Machine>
<Machine enabled="no">VMware VM</Machine>
<Machine enabled="yes">HostMachine</Machine>
</MachineDrivers>
</Compatibility>
<Features></Features>
<AddPackages></AddPackages>
<Drivers showHidden="true">
<AddDrivers></AddDrivers>
</Drivers>
<Unattended mode="0">
<OEMSetupComplete>false</OEMSetupComplete>
<AnswerFileLocationPanther>false</AnswerFileLocationPanther>
<AnswerFileLocationBoot>false</AnswerFileLocationBoot>
<SaveBothArch>false</SaveBothArch>
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup">
<OOBE>
<HideEULAPage>true</HideEULAPage>
<ProtectYourPC>3</ProtectYourPC>
<SkipMachineOOBE>true</SkipMachineOOBE>
<SkipUserOOBE>true</SkipUserOOBE>
</OOBE>
</component>
</settings>
<settings pass="windowsPE">
<component name="Microsoft-Windows-Setup">
<Diagnostics>
<OptIn>false</OptIn>
</Diagnostics>
<DynamicUpdate>
<Enable>false</Enable>
<WillShowUI>OnError</WillShowUI>
</DynamicUpdate>
<ImageInstall>
<OSImage>
<WillShowUI>OnError</WillShowUI>
<InstallFrom>
<MetaData>
<Key>/IMAGE/NAME</Key>
<Value>Windows 10 IoT Enterprise</Value>
</MetaData>
</InstallFrom>
</OSImage>
</ImageInstall>
<UserData>
<ProductKey>
<Key>[KEY]</Key>
<WillShowUI>OnError</WillShowUI>
</ProductKey>
</UserData>
</component>
</settings>
</Unattended>
<Tweaks>
<Settings>
<TweakGroup name="WindowsUpdate">
<Tweak name="AU\AUOptions">2</Tweak>
</TweakGroup>
<TweakGroup name="CrashControl">
<Tweak name="CrashControl\CrashDumpEnabled">3</Tweak>
</TweakGroup>
</Settings>
<Services></Services>
<ExtraServices></ExtraServices>
</Tweaks>
<ApplyOptions>
<ImageTasks>
<Task>imageSaveRebuild</Task>
<Task>imageFormatWim</Task>
</ImageTasks>
<AutoIsoFile>NTLite.iso</AutoIsoFile>
<AutoIsoLabel>NTLite</AutoIsoLabel>
<AutoSplitSize>4000</AutoSplitSize>
<CleanHotfixedLeftovers>0</CleanHotfixedLeftovers>
<ReuseDriverCache>false</ReuseDriverCache>
</ApplyOptions>
<Execution>
<Remove></Remove>
<Change></Change>
<Add>
<Item type="Placeholder">
<Index>0</Index>
</Item>
</Add>
</Execution>
<Registry>
<Item>D:\Users\Downloads\mpo_disable.reg</Item>
</Registry>
</Preset>
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Derivative version: The extreme reduction is performed on WinSxS, and the system update cannot be performed normally​
{Mod edit: Link removed}
{Mod edit: Link removed}
OneDrive:
https://liuxiane5-my.sharepoint.com/:u:/g/personal/zxgu183_e5_liuxianl_com/Eep5Akuay3xMubCgd6vw7hABgMHPPCxr_U2EKSdQLgwlug?e=UWow41
SxSLite18363.2158.esd
1.86 GB (2,005,212,336 Bits)
2022.03.23,21:25:11
MD5: A509EAB4458589F7DAD2E3148A136EB0
SHA1: 5476379B23B3862C4A62519026D13BC37DE5DF95
SHA256: 84DA97C2FDEB0DE9E79AADC923C1BC60D7D10D8A82E4B00A89E35469E612696A
SHA512: F4F54D2A39286FCAF5FEBC55F3E4C8E1A254A2CFE0D502CB150C93B86E7AB8A7E1F93ACAA14F21B51E6BA26AE43ACD29AF1E933F56ADFB80DB9421CFD95041EF
CRC32: 934033F1

@ZXGU Thread closed and 4 links removed. Please refer to your private messages.
Regards
Oswald Boelcke
Senior Moderator

Related

[HOWTO] Add ICS 'Recent Apps' button (or other softkeys) to Status bar

Preview :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
this mod is originally posted in nexus s forum.
[MOD] Add ICS 'Recent Apps' button to Status bar
i added just 'recent apps' button only but you can add other buttons what you want. like this :
anyway, if you want to add 'recent apps' button..
1) fix "APP_SWITCH" keycode to call ICS Recent Apps dialog.
- basically, same process to this mod : [HOWTO] Remap hardware button to ICS recent apps
platform/frameworks/base/policy/src/com/android/internal/policy/impl/PhoneWindowManager.java
from :
Code:
} else if (keyCode == KeyEvent.KEYCODE_APP_SWITCH) {
if (down && repeatCount == 0) {
showOrHideRecentAppsDialog(RECENT_APPS_BEHAVIOR_SHOW_OR_DISMISS);
}
return -1;
}
to :
Code:
} else if (keyCode == KeyEvent.KEYCODE_APP_SWITCH) {
if (down && repeatCount == 0 && !keyguardOn) {
try {
mStatusBarService.toggleRecentApps();
} catch (RemoteException e) {
Slog.e(TAG, "RemoteException when showing recent apps", e);
}
}
return -1;
}
2) modifiy Expanded Status bar layout
- decompile SystemUI.apk -> /res/layout/status_bar_expanded.xml
..or..
- platform/frameworks/base/packages/SystemUI/res/layout/status_bar_expanded.xml
from :
Code:
<RelativeLayout android:background="@drawable/notification_header_bg" android:paddingTop="3.0dip" android:paddingRight="3.0dip" android:paddingBottom="5.0dip" android:layout_width="fill_parent" android:layout_height="52.0dip">
<com.android.systemui.statusbar.policy.DateView android:textAppearance="@style/TextAppearance.StatusBar.Date" android:gravity="left|center" android:id="@id/date" android:paddingLeft="16.0dip" android:layout_width="wrap_content" android:layout_height="fill_parent" android:singleLine="true" android:layout_alignParentLeft="true" />
<ImageView android:id="@id/settings_button" android:paddingLeft="8.0dip" android:paddingRight="8.0dip" android:layout_width="wrap_content" android:layout_height="fill_parent" android:src="@drawable/ic_notify_quicksettings" android:layout_toRightOf="@id/date" android:contentDescription="@string/accessibility_settings_button" />
<ImageView android:id="@id/clear_all_button" android:paddingLeft="8.0dip" android:paddingRight="8.0dip" android:layout_width="wrap_content" android:layout_height="fill_parent" android:src="@drawable/ic_notify_clear" android:layout_alignParentRight="true" android:contentDescription="@string/accessibility_clear_all" />
</RelativeLayout>
to :
Code:
<RelativeLayout android:background="@drawable/notification_header_bg" android:paddingTop="3.0dip" android:paddingRight="3.0dip" android:paddingBottom="5.0dip" android:layout_width="fill_parent" android:layout_height="52.0dip">
<com.android.systemui.statusbar.policy.DateView android:textAppearance="@style/TextAppearance.StatusBar.Date" android:gravity="left|center" android:id="@id/date" android:paddingLeft="16.0dip" android:layout_width="wrap_content" android:layout_height="fill_parent" android:singleLine="true" android:layout_alignParentLeft="true" />
<ImageView android:id="@id/settings_button" android:paddingLeft="8.0dip" android:paddingRight="4.0dip" android:layout_width="wrap_content" android:layout_height="fill_parent" android:src="@drawable/ic_notify_quicksettings" android:layout_toRightOf="@id/date" android:contentDescription="@string/accessibility_settings_button" />
[COLOR="Blue"]<com.android.systemui.statusbar.policy.KeyButtonView android:paddingLeft="4.0dip" android:paddingRight="4.0dip" android:id="@id/recent_apps" android:layout_width="wrap_content" android:layout_height="fill_parent" android:src="@drawable/ic_sysbar_recent" android:layout_toRightOf="@id/settings_button" android:contentDescription="@string/accessibility_recent" systemui:keyCode="187" systemui:glowBackground="@drawable/ic_sysbar_highlight" />[/COLOR]
<ImageView android:id="@id/clear_all_button" android:paddingLeft="8.0dip" android:paddingRight="8.0dip" android:layout_width="wrap_content" android:layout_height="fill_parent" android:src="@drawable/ic_notify_clear" android:layout_alignParentRight="true" android:contentDescription="@string/accessibility_clear_all" />
</RelativeLayout>
3) you'd better replace /res/drawable-****/ic_sysbar_recent.png with smaller one...
mine(in above preview - for hdpi) is here : http://www.mediafire.com/?qxy9l1emmeofa4s
-----------------------------------------------------------------------------
and caution
- when i tested this on stock rom, search button works only when long pressed (=voice search).
- adding some kind of button like menu or back is meaningless.. (surely)
- and at least on my phone(nexus s), ICS blue(#33b1e1) doesn't look same color to date and quick settings button.. (don't know why)
- and do not use this mod with tablet ui or onscreen softkeys mod.
- and if you cannot compile android.policy.jar for some reason, try with my files instead.
you can find my files in these thread :
[MOD] Search key to ICS recent apps
[MOD] Add ICS 'Recent Apps' button to Status bar
and be careful. you should use suitable version to your rom. so if your cm9 rom was built few weeks ago, do not try with latest version of my mod.
I've been looking for this quite a while because my homebutton doesn't work that good anymore.
I'm running a Samsung galaxy s with teamhacksung ICS build 17.
Is there any chance you could make a flashable zip for this because I have absolutely no clue in coding. I'm just consuming these incredible things here on xda
It is very beautiful, thank you for your doing!
Sent from my MotoA953
I read all post from nexus because I'm using cm9 and they have made wonderful mod for it,but no guide at all,but you're really awesome because you made a guide and was really helping me port it to my phone,thanks!!!
from the ARC
Just flashed this and it seems to be working fine on the LG optimus v.
Where can I find the .java file in SystemUI.apk?
I want to include that in my own update.zip
F.West98 said:
Where can I find the .java file in SystemUI.apk?
I want to include that in my own update.zip
Click to expand...
Click to collapse
sorry but you have to compile from source code..
https://github.com/android/platform.../internal/policy/impl/PhoneWindowManager.java
What to do with that file?
I don't know exactly, it's my first own mod
F.West98 said:
What to do with that file?
I don't know exactly, it's my first own mod
Click to expand...
Click to collapse
apply above fix related to "APP_SWITCH" keycode and compile android.policy.jar.
you have to download entire ics source code to compile this..
maybe same thing can be done simply by smali editing but sorry, i don't know how..
But then it isn't CM9 anymore, is it?
Can't I download only the needed files from Github? And how to make it flashable?
Ah I understand something
I can place the .jar file (compiled) into the folder 'frameworks' in my flashable zip, there is also an apk (framework-res)
I have to download the complete source code and I only have to change the file (.java), which I compile as the .jar
Correct?
(but why do I need the whole source code, I'm on Windows...)
chucksaysblah said:
Just flashed this and it seems to be working fine on the LG optimus v.
Click to expand...
Click to collapse
How did you flash it on your LG? Did you recompile from source or something else?
F.West98 said:
But then it isn't CM9 anymore, is it?
Can't I download only the needed files from Github? And how to make it flashable?
Ah I understand something
I can place the .jar file (compiled) into the folder 'frameworks' in my flashable zip, there is also an apk (framework-res)
I have to download the complete source code and I only have to change the file (.java), which I compile as the .jar
Correct?
(but why do I need the whole source code, I'm on Windows...)
Click to expand...
Click to collapse
firstly, i recommend you read this : How to compile ICS
and if you want to use this on CM9, download CM source instead of AOSP.
https://github.com/CyanogenMod
download single framework file's source code and compile that one file is impossible. so you have to download entire ics source code..
and if you want to use what you made personally, you don't have to make flashable zip. just push modified files to your system using adb or (easily) android commander.
http://androidcommander.com/
So I have to wait 4 hours and only pick 1 file of evrything?
Flashable ZIP is easy for me
edit: and I have to restart my PC, save everything, check the x64-option in the BIOS, install virtualbox, download linux and install it?
Can't anyone compile for me? :S
Here are the edits as a github commit for devs coming along wanting to integrate this into existing source: https://github.com/ThePlayground/an...mmit/0377e4b83e616a68395a82ba902d2757a16627d5
Thanks for the mod. It's a great idea
twistedumbrella said:
Here are the edits as a github commit for devs coming along wanting to integrate this into existing source: https://github.com/ThePlayground/an...mmit/0377e4b83e616a68395a82ba902d2757a16627d5
Thanks for the mod. It's a great idea
Click to expand...
Click to collapse
wow.. I guess I should thank you. it would be great pleasure to me if this mod is useful for many users
good work! but just a question: whye dont anyone add that downstears like the original ics for nexus?
Good job OP. BTW, ICS color code in hex is 33b5e5 I believe.
Sent from my Galaxy Nexus using xda premium
awesome!!!
it's very convenient on Galaxy S
rugal28 said:
awesome!!!
it's very convenient on Galaxy S
Click to expand...
Click to collapse
Can you post it as flashable zip?
Great will compile later
Thx.

[solved] [Q] PAC kk build help...!!! (10-02-2014)

EDIT : Error solved
i am facing an error while building PAC 4.4 Alpha Update for my Xperia LWW...i googled around for the exact same error and got to know that it might be caused due to low memory...but i hav a Swap Partition of 15 GB (i know its a lot of SWAP but its to b on the safer side:fingers-crossed and i hav built successfully last week with the same PC config....
Heres the log :
Code:
PRODUCT_COPY_FILES vendor/cm/prebuilt/common/bootanimation/320.zip:system/media/bootanimation.zip ignored.
No private recovery resources for TARGET_DEVICE coconut
make -C kernel/semc/msm7x30 O=/home/admin01/1packk/out/target/product/coconut/obj/KERNEL_OBJ ARCH=arm CROSS_COMPILE="/home/admin01/1packk/prebuilts/misc/linux-x86/ccache/ccache /home/admin01/1packk/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7/bin/arm-eabi-" VARIANT_DEFCONFIG= SELINUX_DEFCONFIG= nAa_coconut_defconfig
make[1]: Entering directory `/home/admin01/1packk/kernel/semc/msm7x30'
GEN /home/admin01/1packk/out/target/product/coconut/obj/KERNEL_OBJ/Makefile
host Executable: clang (/home/admin01/1packk/out/host/linux-x86/obj/EXECUTABLES/clang_intermediates/clang)
#
# configuration written to .config
#
make[1]: Leaving directory `/home/admin01/1packk/kernel/semc/msm7x30'
Target buildinfo: /home/admin01/1packk/out/target/product/coconut/system/build.prop
make: Circular /home/admin01/1packk/out/target/common/obj/APPS/framework-res_intermediates/package-export.apk <- /home/admin01/1packk/out/target/common/obj/APPS/framework-res_intermediates/src/R.stamp dependency dropped.
target Java: bouncycastle (/home/admin01/1packk/out/target/common/obj/JAVA_LIBRARIES/bouncycastle_intermediates/classes)
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
JarJar: /home/admin01/1packk/out/target/common/obj/JAVA_LIBRARIES/okhttp_intermediates/classes-jarjar.jar
/home/admin01/1packk/prebuilts/gcc/linux-x86/host/i686-linux-glibc2.7-4.6/bin/../lib/gcc/i686-linux/4.6.x-google/../../../../i686-linux/bin/ld: BFD (GNU Binutils) 2.21 internal error, aborting at /i/toolchain-src//binutils/binutils-2.21/bfd/merge.c line 873 in _bfd_merged_section_offset
/home/admin01/1packk/prebuilts/gcc/linux-x86/host/i686-linux-glibc2.7-4.6/bin/../lib/gcc/i686-linux/4.6.x-google/../../../../i686-linux/bin/ld: Please report this bug.
collect2: ld returned 1 exit status
make: *** [/home/admin01/1packk/out/host/linux-x86/obj/EXECUTABLES/clang_intermediates/clang] Error 1
make: *** Waiting for unfinished jobs....
/home/admin01/1packk/out/target/product/coconut/pac_coconut-ota-eng.admin01.zip doesn't exist!
Total time elapsed: 9 minutes 20 seconds
********************************************************************************
*******************************PLEASE READ THIS!!*******************************
Please remember that this source is currently for private builds ONLY!
Public builds are NOT ALLOWED, all public builds will be removed.
It will be welcomed after nightlies begin. Thank you, the Developers.
*******************************PLEASE READ THIS!!*******************************
********************************************************************************
[email protected]:~/1packk$
so pls help me:crying: out if u can...cos i dont understand why i am getting the mentioned error when my previous builds were successful??...is my VERY Large SWAP partition creating the problem??or something else??
OLD post:
hello everyone i am again building (as i want to update) PAC 4.4 alpha for my SE LWW but now my PAC kk build seems to fail again nd again ...
heres what i did...
i tried to cherry-pick quicksettings 2.0 from PA from here and the build failed...
so i repo synced again to revert the changes from cherry pick nd built again but still failed...
tried many things nd got several errors nd builds failed..
then i deleted the whole of the frameworks folders (as the above commit affects it) both from the working dir as well as .repo/projects and repo synced again to download the source for it again...
but even after all this the build failed...so pls tel me what to do???
the error pic is here :silly: or below...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EDIT :
I did a clean build and it finished successfully ....
skull47 said:
hello everyone i am again building (as i want to update) PAC 4.4 alpha for my SE LWW but now my PAC kk build seems to fail again nd again ...
heres what i did...
i tried to cherry-pick quicksettings 2.0 from PA from here and the build failed...
so i repo synced again to revert the changes from cherry pick nd built again but still failed...
tried many things nd got several errors nd builds failed..
then i deleted the whole of the frameworks folders (as the above commit affects it) both from the working dir as well as .repo/projects and repo synced again to download the source for it again...
but even after all this the build failed...so pls tel me what to do???
the error pic is here :silly: or below...
pls help me out if possible:fingers-crossed:...it would be much appreciated as I AM TRYING TO LEARN:silly: NEW THINGS
thanks:good::highfive:
Click to expand...
Click to collapse
Post the contents of ~/1packk/.repo/local_manifests.xml
Also, do you have any other .xml files in that folder? If so, post them also.
Langes said:
Post the contents of ~/1packk/.repo/local_manifests.xml
Also, do you have any other .xml files in that folder? If so, post them also.
Click to expand...
Click to collapse
thnks a ton for replyin here...sorry to disturb u thru PM...but after i PMed u i remembered about this forum so posted here too...
nywys the code:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LegacyXperia/android_device_semc_coconut" path="device/semc/coconut" remote="github" revision="cm-11.0" />
<project name="LegacyXperia/android_device_semc_mogami-common" path="device/semc/mogami-common" remote="github" revision="cm-11.0" />
<project name="LegacyXperia/android_device_semc_msm7x30-common" path="device/semc/msm7x30-common" remote="github" revision="cm-11.0" />
<project name="LegacyXperia/msm7x30-3.4.x-nAa" path="kernel/semc/msm7x30" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_hardware_sony_DASH" path="hardware/sony/DASH" remote="github" revision="cm-11.0" />
<project name="LegacyXperia/proprietary_vendor_semc" path="vendor/semc" remote="github" revision="cm-11.0" />
<remove-project name="androidarmv6/android_hardware_qcom_display-legacy" path="hardware/qcom/display-legacy" revision="cm-10.2" />
<remove-project name="androidarmv6/android_hardware_qcom_media_legacy" path="hardware/qcom/media-legacy" revision="cm-10.2" />
<project name="LegacyXperia/android_hardware_qcom_audio-legacy" path="hardware/qcom/audio-legacy" />
<project name="LegacyXperia/android_hardware_qcom_display-legacy" path="hardware/qcom/display-legacy" revision="cm-11.0_old" />
<project name="LegacyXperia/android_hardware_qcom_media-legacy" path="hardware/qcom/media-legacy" revision="cm-11.0_old" />
<project name="CyanogenMod/android_external_wpa_supplicant_8_ti" path="external/wpa_supplicant_8_ti" revision="cm-10.2" />
<project name="Pinky-Inky-and-Clyde/proprietary_vendor_semc" path="vendor/semc" remote="github" revision="cm-11.0" />
</manifest>
EDIT: just noticed the vendor_semc conflict...removing LEGACYXPERIA's vendor/semc nd trying out again...
EDIT 2: no change...error still remains...nd noo there is no other .xml file here...
skull47 said:
thnks a ton for replyin here...sorry to disturb u thru PM...but after i PMed u i remembered about this forum so posted here too...
nywys the code:
EDIT: just noticed the vendor_semc conflict...removing LEGACYXPERIA's vendor/semc nd trying out again...
Click to expand...
Click to collapse
Was just about to point that out
It is also good practice to put your "remove-project" lines at the top. Other than that, everything looks good.
Are you cherry-picking anything before building?
You need only 55805 from CM, the others that are in LX updates.sh are not needed for PAC or already merged in PAC frameworks/av
Langes said:
Was just about to point that out
It is also good practice to put your "remove-project" lines at the top. Other than that, everything looks good.
Are you cherry-picking anything before building?
You need only 55805 from CM, the others that are in LX updates.sh are not needed for PAC or already merged in PAC frameworks/av
Click to expand...
Click to collapse
yes i am cherry picking only 55805 b4 building...
EDIT 2: no change...error still remains...nd noo there is no other .xml file here...
repo sync stuck at 99%
Langes said:
Was just about to point that out
It is also good practice to put your "remove-project" lines at the top. Other than that, everything looks good.
Are you cherry-picking anything before building?
You need only 55805 from CM, the others that are in LX updates.sh are not needed for PAC or already merged in PAC frameworks/av
Click to expand...
Click to collapse
the above mentioned error still occurs and not able to build...what shud i do???
and now another problem i am facing is that the repo sync command gets stuck at 99%..and ya i checked my network connections and they are all right...i even tried repo sync -f and left it for the whole night but still it is stuck at 99%...so pls help me out here...atached screenshot below...
skull47 said:
the above mentioned error still occurs and not able to build...what shud i do???
and now another problem i am facing is that the repo sync command gets stuck at 99%..and ya i checked my network connections and they are all right...i even tried repo sync -f and left it for the whole night but still it is stuck at 99%...so pls help me out here...atached screenshot below...
Click to expand...
Click to collapse
For the repo sync error, you should remove LegacyXperia/android_hardware_qcom_adio-legacy from roomsevice
file contect required
Langes said:
For the repo sync error, you should remove LegacyXperia/android_hardware_qcom_adio-legacy from roomsevice
Click to expand...
Click to collapse
thanks for the tip it worked...
can u or any one building PAC 4.4 pls tell me the contents of the file SkPDFDevice.P after the line 232 ( file location :
/your-working-directory/out/target/product/coconut/obj/SHARED_LIBRARIES/libskia_intermediates/src/pdf )
@3andala @Micha_Btz (sry to disturb u both but since u both hav built pac 4.4 u could help:fingers-crossed: me out)
thanks
skull47 said:
@3andala @Micha_Btz (sry to disturb u both but since u both hav built pac 4.4 u could help:fingers-crossed: me out)
thanks
Click to expand...
Click to collapse
i don't have build pac 4.4.x yet.
sry..my bad..
Micha_Btz said:
i don't have build pac 4.4.x yet.
Click to expand...
Click to collapse
oh sry my bad...but still could u tell me the file content of the 4.3 sources..they might help me out...
thanks for ur reply...
New Error
OP updated...
skull47 said:
OP updated...
Click to expand...
Click to collapse
Are you still having build errors?
Sent from my SCH-I605 using Tapatalk
gchild320 said:
Are you still having build errors?
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
nope built successfully...the problem was tat the swap partition was not active...i did swapon and rebuilt...it worked...
nywyz thanks for replyin

[DISCUSSION THREAD] CM12 for v500

Project deprecated, CM12 for v500 became official.
Code:
#include
/*
* 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 this ROM
* 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.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
Known Issues:
Permissive SELinux only
Rear camera is not working on some devices
How to install:
Download the ROM
Download GApps
Put the zip files on your SDCard
Reboot in Recovery
Wipe Data / Factory Reset
Select "Install zip from SDCard"
Choose CM12 zip file
Choose GApps zip file
Reboot system
Download ROM​
Download GApps​
Kernel source: https://github.com/victormlourenco/red_kernel_lge_v500/tree/cm-12.0
Device source:https://github.com/victormlourenco/android_device_lge_v500
XDA:DevDB Information
CM12 for v500, ROM for the LG G Pad 8.3
Contributors
Rick Roll
Source Code: http://ttps://github.com/victormlourenco/
ROM OS Version: 5.0.x Lollipop
Version Information
Status: Testing
Created 2014-12-04
Last Updated 2014-12-03
Rick Roll said:
Know Issues:
Permissive SELinux only
Click to expand...
Click to collapse
What does this mean? Is it a Problem?
And why do you post this in the 'General' section?
edisso10018 said:
What does this mean? Is it a Problem?
And why do you post this in the 'General' section?
Click to expand...
Click to collapse
The goal is to have a fully working sepolicy for our device like v510 and Nexus devices. This thread is only for general discussion about CM12 builds, I will make a dev thread later.
You rock, Rick Roll.
This thread seems more like a development thread, than a discussion. The rear camera issue must be just for those with a different camera module and it shouldn't work in CM 11 either.
I'm excited to see the first CM 12 thread for the v500. Awesome. I will help you any way I can to get this official like CM 11 is.
Thanks!
Is GPS working?
Yes, GPS works.
Very good for a not-even-nightly.
Thanks to Rick Roll and CM.
@Rick Roll, are you testing this with 4.4 base?
No, needs the 4.2.2 base.
Because the stock CM kernel requires 4.2 base or else there are brightness issues. Same as stock CM 11. Thanks, that implies that the kernel is stock CM.
Uploaded 20141204 build that fixes secure video (Netflix, Hulu, Google Play Movies, etc...).
CM11
edisso10018 said:
No, needs the 4.2.2 base.
Click to expand...
Click to collapse
Hey im coming from CM11 M12, can i install this? no problem?
Sure, just do a factory reset first.
slow wifi
Firat of all thanks for this amazing job , the ROM its perfect . but i havê the same problemas in the custom ROMs i havê slow WiFi download speed , i havê 100mbs but download its kbts. If anyone could help i wanna thanks please. Onde more time thanks rick roll
Hey there, would you mind sharing your local_manifest.xml for this? Im curious to see what you are using for vendor and common and cm dependencies. I was wanting to build a LP ROM as well for v500
Thanks!
timmytim said:
Hey there, would you mind sharing your local_manifest.xml for this? Im curious to see what you are using for vendor and common and cm dependencies. I was wanting to build a LP ROM as well for v500
Thanks!
Click to expand...
Click to collapse
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="victormlourenco/android_device_lge_v500" path="device/lge/v500" remote="github" />
<project name="victormlourenco/red_kernel_lge_v500" path="kernel/lge/v500" remote="github" />
<project name="victormlourenco/proprietary_vendor_lge" path="vendor/lge/" remote="github" />
</manifest>
Have fun
timmytim said:
Hey there, would you mind sharing your local_manifest.xml for this? Im curious to see what you are using for vendor and common and cm dependencies. I was wanting to build a LP ROM as well for v500
Thanks!
Click to expand...
Click to collapse
Timmytim, never seen you in here or don't remember, but heck yeah! I've been running your candy rom on my d850 for a couple of days now. Would love to have some candy5 on my v500!
Rick Roll said:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="victormlourenco/android_device_lge_v500" path="device/lge/v500" remote="github" />
<project name="victormlourenco/red_kernel_lge_v500" path="kernel/lge/v500" remote="github" />
<project name="victormlourenco/vendor_v500" path="vendor/lge/" remote="github" />
</manifest>
Have fun
Click to expand...
Click to collapse
Thank you!
---------- Post added at 02:10 PM ---------- Previous post was at 02:09 PM ----------
xallinvaynex said:
Timmytim, never seen you in here or don't remember, but heck yeah! I've been running your candy rom on my d850 for a couple of days now. Would love to have some candy5 on my v500!
Click to expand...
Click to collapse
I've been lurking in the shadows, lol. I am gonna try a build and see what happens :good:
timmytim said:
Thank you!
---------- Post added at 02:10 PM ---------- Previous post was at 02:09 PM ----------
I've been lurking in the shadows, lol. I am gonna try a build and see what happens :good:
Click to expand...
Click to collapse
Sweet! If you need a tester, let me know!
Rick Roll said:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="victormlourenco/android_device_lge_v500" path="device/lge/v500" remote="github" />
<project name="victormlourenco/red_kernel_lge_v500" path="kernel/lge/v500" remote="github" />
<project name="victormlourenco/vendor_v500" path="vendor/lge/" remote="github" />
</manifest>
Have fun
Click to expand...
Click to collapse
Have you ever received this while syncning your repos?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
timmytim said:
Have you ever received this while syncning your repos?
Click to expand...
Click to collapse
Are you building for another lge device? My vendor repo may be conflicting with yours since they are in the same folder.

[TEST][trltetmo] LineageOS 14.1

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Lineage OS Android Distribution
CyanogenMod LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Code:
/* 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 this ROM
* 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.
*/
-----------------------------------------------------------------------------------------------------​
After the usual introduction..
Hi there! We are trying to bring up trltexx and trltetmo to official nightly builds of LineageOS. We would like to know from whoever flash this build if there are major issues.. if you find something, please, report it (with a logcat would be great).
Download:
- test#1 lineage-14.1-20170202-UNOFFICIAL-trltetmo.zip
- test#2 lineage-14.1-20170224-UNOFFICIAL-trltetmo.zip
- GApps
Please try to be on N910TUVS2EPK2 bootloader/modem and perform a clean install
Installation Instruction:
Backup > Move your backup somewhere save > Perform a full wipe, factory reset > Flash ROM > Flash GApps > Wipe Cache & Dalvik Cache > Reboot
If you want to build it yourself use this roomservice.xml:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="fat-tire/android_device_samsung_trltetmo" path="device/samsung/trltetmo" remote="github" revision="cm-14.1" />
<project name="underscoremone/android_kernel_samsung_trlte" path="kernel/samsung/trlte" remote="github" revision="cm-14.1" />
<project name="underscoremone/android_device_samsung_trlte-common" path="device/samsung/trlte-common" remote="github" revision="cm-14.1" />
<project name="underscoremone/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_external_stlport" path="external/stlport" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-14.1" />
</manifest>
Thanks! :angel:
@_mone
From jef's thread
https://forum.xda-developers.com/showpost.php?p=70844978&postcount=438
I can't try right now.
Thanks for your work!
Screenshots?
Sent from my SM-N910T using Tapatalk
Downloading it
I tested the rom lineage-14.1-20170202-UNOFFICIAL-trltetmo.zip on my Note 4 trltetmo.
I can confirm
SIM IS WORKING
FINGERPRINT DOES NOT UNLOCK PHONE
CAMERA TAKES PICTURES
So far... So far... I haven't experienced any bugs
This is sorta stable
One big problem is Snapchat root detection. I can't log in on Snapchat because it says my phone rooted but root toggle is off
I appreciate you keeping note 4 alive!
Sent from my SM-N9200 using Tapatalk
This is an excellent start. An additional issue is the GPS issue that is common in the 7.1.1 ROMs. Once that is fix, it could be a daily driver for me. Keep up the good work
Anyone knows how to use Snapchat with LineageOS because everytime I try to log-in I get this error:
Oh no! Your login temporarily failed, so please try again later. If your login continues to fail, please visit https://support.snapchat.com/a/failed-login
What its basically saying is that while signing in, the app searches for SuperSU and root directories on your phone and if it finds them, the app blocks the process.
Any Fix? I haven't turned on ROOT on LineageOS
viewsfromthepi said:
Anyone knows how to use Snapchat with LineageOS because everytime I try to log-in I get this error:
Oh no! Your login temporarily failed, so please try again later. If your login continues to fail, please visit https://support.snapchat.com/a/failed-login
What its basically saying is that while signing in, the app searches for SuperSU and root directories on your phone and if it finds them, the app blocks the process.
Any Fix? I haven't turned on ROOT on LineageOS
Click to expand...
Click to collapse
How do yo turn on Root? Settings somewhere? Or do we need to flash SU?
SiNJiN76 said:
How do yo turn on Root? Settings somewhere? Or do we need to flash SU?
Click to expand...
Click to collapse
Turn on developer options in settings by tapping on build number repeatedly...go to developer options and enable root.
how is battery life?
SiNJiN76 said:
How do yo turn on Root? Settings somewhere? Or do we need to flash SU?
Click to expand...
Click to collapse
http://wccftech.com/enable-developer-options-android-nougat/
There should be a root option
Works & is stable enough for usage keep the updates coming.
I'm excited to keep getting updates for this phone! it's faster than marshmallow or lollipop!
viewsfromthepi said:
Anyone knows how to use Snapchat with LineageOS because everytime I try to log-in I get this error:
Oh no! Your login temporarily failed, so please try again later. If your login continues to fail, please visit https://support.snapchat.com/a/failed-login
What its basically saying is that while signing in, the app searches for SuperSU and root directories on your phone and if it finds them, the app blocks the process.
Any Fix? I haven't turned on ROOT on LineageOS
Click to expand...
Click to collapse
GPS is working for me hmmm
---------- Post added at 02:44 AM ---------- Previous post was at 01:56 AM ----------
how do we build this? willing to learn have not tried before.
....
viewsfromthepi said:
Anyone knows how to use Snapchat with LineageOS because everytime I try to log-in I get this error:
Oh no! Your login temporarily failed, so please try again later. If your login continues to fail, please visit https://support.snapchat.com/a/failed-login
What its basically saying is that while signing in, the app searches for SuperSU and root directories on your phone and if it finds them, the app blocks the process.
Any Fix? I haven't turned on ROOT on LineageOS
Click to expand...
Click to collapse
Snapchat checks for xposed, not root.
Hi, I found a bug which seems to be common on all 7.1 roms on my 910t3. When using vr apps there is no way to move the screen, as if the gyroscope is not working correctly. Screen rotation in general works however on web pages, etc. I've tested with several vr apps to no avail. This is the only thing preventing this from being a daily driver for me.
odj1041 said:
Snapchat checks for xposed, not root.
Click to expand...
Click to collapse
I dont have xposed and i have never installed it
viewsfromthepi said:
I dont have xposed and i have never installed it
Click to expand...
Click to collapse
I find that strange. I've used Snapchat with root on numerous roms
---------- Post added at 10:57 AM ---------- Previous post was at 10:53 AM ----------
viewsfromthepi said:
I tested the rom lineage-14.1-20170202-UNOFFICIAL-trltetmo.zip on my Note 4 trltetmo.
I can confirm
SIM IS WORKING
FINGERPRINT DOES NOT UNLOCK PHONE
CAMERA TAKES PICTURES
So far... So far... I haven't experienced any bugs
This is sorta stable
One big problem is Snapchat root detection. I can't log in on Snapchat because it says my phone rooted but root toggle is off
Click to expand...
Click to collapse
I can unlock with Fingerprint.
When registering swipe an extra time even though it says done. Also works for all AOSP trltetmo ROMs that use Fingerprint

[ROM][platina][UNOFFICIAL][R / 11] LineageOS 18.1 for Mi 8 Lite [microG]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
About
This thread is for continuous builds of LineageOS 18.1 on a monthly base, after the security patches got merged.
Disclaimer
I am not an Android experienced developer, so I CAN NOT fix non-working stuff. I'm just doing an upstream sync, brew a build and upload it for those, not ready to switch to LOS-20.
I AM NOT RESPONSIBLE FOR ANYTHING HAPPENING IF YOU USE/DO ANYTHING FROM/MENTIONED IN THIS THREAD BY EITHER ME OR OTHERS
Included in this ROM
LOS-18.1 upstream sync
MicroG Signature Spoof patches
Android 13 updated emoji font
When will updates be compiled?
I can't/won't give any guarantees. Normally I check the state of the monthly security patches from time to time and run a build once I remembered to check and they got merged. If the security fixes got already merged can be checked by everyone by a quick look into the LineageOS Gerrit with the fitting filter. For my head such a system isn't available, sorry^^
Requirements
unlocked Bootloader
Recommended Firmware: V12.0.3.0.QDTMIXM
Recovery capable to flash ROM. Examples:
LOS-20.0-platina-recovery
OrangeFox R11.1 (Can decrypt /data) (TBD)
Downloads
LOS18.1 unofficial builds
Flashing Instructions
official LOS instructions, follow the ones for unlocking and flashing a recovery.
Please don't ask for support on unlocking/flashing recovery on this thread!
Sources (Links include the specific branch used!)
Kernel
Mi 8 Lite Device Tree
Xiaomi SDM660 Common Device Tree
Xiaomi Proprietary Vendor
Xiaomi Hardware
Spoiler: ready to use roomservice.xml
For the listed sources this is a ready to use configuration to be placed under ".repo/local_manifests/" of an own build environment
XML:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="los" fetch="https://github.com/LineageOS/" revision="lineage-18.1" />
<remote name="muppets" fetch="https://gitlab.com/the-muppets/" revision="lineage-18.1" />
<!-- platina -->
<project name="android_device_xiaomi_sdm660-common" path="device/xiaomi/sdm660-common" remote="los" />
<project name="android_device_xiaomi_platina" path="device/xiaomi/platina" remote="los" />
<project name="android_kernel_xiaomi_sdm660" path="kernel/xiaomi/sdm660" remote="los" />
<project name="android_hardware_xiaomi" path="hardware/xiaomi" remote="los" />
<project name="proprietary_vendor_xiaomi" path="vendor/xiaomi" remote="muppets" />
</manifest>
Thank you!
BTW, install this will not delete my data, isn't it? Will sideload from official LOS 18.1 recovery.
roldev said:
BTW, install this will not delete my data, isn't it? Will sideload from official LOS 18.1 recovery.
Click to expand...
Click to collapse
Should be fine with an existing LOS18.1 installation.
Only thing possible: If currently an official LOS18.1 build is installed it will refuse to flash because of the mismatching signing keys between official <-> unofficial builds.
If that's the case you first have to do some adjustments to be able to flash unofficial builds over the existing installation.
Signing Builds | LineageOS Wiki
wiki.lineageos.org
9Lukas5 said:
Should be fine with an existing LOS18.1 installation.
Only thing possible: If currently an official LOS18.1 build is installed it will refuse to flash because of the mismatching signing keys between official <-> unofficial builds.
If that's the case you first have to do some adjustments to be able to flash unofficial builds over the existing installation.
Signing Builds | LineageOS Wiki
wiki.lineageos.org
Click to expand...
Click to collapse
Thank you. Installs well with warning about the keys. Because of lack of time didn't sign the build. Will do it on the next update. Best!
Hey, March Security update is only.
Upstream LineageOS Changelog
L
Hey, April Security update is only.
Upstream LineageOS Changelog
L
nice
is this the procedure, how you do the LOS 18.1 Build by yourself?
Build for platina | LineageOS Wiki
wiki.lineageos.org
mapausch said:
is this the procedure, how you do the LOS 18.1 Build by yourself?
Build for platina | LineageOS Wiki
wiki.lineageos.org
Click to expand...
Click to collapse
Yup, pretty much. Before the repo sync you'll have to include the needed device specific repo's into your build environment in order for them to be downloaded from a sync as well. Otherwise the build environment wouldn't know the device^^
Mine looks like this atm:
path in the build-environment: .repo/local_manifests/<some-name>.xml
XML:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="los" fetch="https://github.com/LineageOS/" revision="lineage-18.1" />
<remote name="muppets" fetch="https://gitlab.com/the-muppets/" revision="lineage-18.1" />
<project name="android_device_xiaomi_sdm660-common" path="device/xiaomi/sdm660-common" remote="los" />
<project name="android_device_xiaomi_platina" path="device/xiaomi/platina" remote="los" />
<project name="android_kernel_xiaomi_sdm660" path="kernel/xiaomi/sdm660" remote="los" />
<project name="android_hardware_xiaomi" path="hardware/xiaomi" remote="los" />
<project name="proprietary_vendor_xiaomi" path="vendor/xiaomi" remote="muppets" />
</manifest>
May security update online
Upstream Lineage changelog
cts failed for me (why?)
Also if you know please tell me why autofill doesnt work system wide (it dont in browser too)
Although its enabled ,nothing
gripbox said:
cts failed for me (why?)
Also if you know please tell me why autofill doesnt work system wide (it dont in browser too)
Although its enabled ,nothing
Click to expand...
Click to collapse
Im using opengapps pico btw
gripbox said:
cts failed for me (why?)
Click to expand...
Click to collapse
Don't know, can't really tell from here.
You have installed all the build dependencies, initialized the repo with the LineageOS 18.1 synced?
If you do a clean build and it fails, did you try to call the build command again without cleaning once or twice?
What are your system resources (Ram/Swap) doing throughout the build?
If you want to further help getting your own environment up running write a private message and maybe include a build log of the error.
gripbox said:
Also if you know please tell me why autofill doesnt work system wide (it dont in browser too)
Although its enabled ,nothing
Click to expand...
Click to collapse
Oof, no idea. I tried KeepassDX as autofill provider, which isn't that amazing for me. Don't know how good other providers normally work or why it doesn't work as good as you'd expect it to do, sorry :/
June security update online
Upstream Lineage changelog
what makes this version different from the official one?
PINO :) said:
what makes this version different from the official one?
Click to expand...
Click to collapse
Where do you see an official LOS18.1 atm?
The vanilla LOS doesn't list our device at all anymore, and official MicroG LOS for our device got it's last update mid October last year. Did I miss anything?
L
Just wanted to say THANKS again for keeping this alive. Really appreciated.
Same from me.
I use lineageOS 0612 version , and boot failed in lineageOS boot logo, can I debug it ?

Categories

Resources