LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
{
"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"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
This thread is for Unofficial LineageOS 14.1 builds for klimtlte (SM-T705). The following will not be supported here:
Custom kernels
Mods
Xposed
I don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files
First time flashing LineageOS 14.1 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash LineageOS
Install the Google Apps addon package (Optional)
Reboot
As the current ROM is starting to become quite stable, there's been progress made towards automated weekly builds for LineageOS 14.1.
The infrastructure is being set-up by @thompatry.
If this goes forward, this implies:
There will be a new build every week, probably build being completed late Friday.
The builds will no longer be personally tested by me before being uploaded (but everything will probably be fine)
Change logs will no longer be posted within every new build, but instead when the changes are uploaded to GitHub. I will try though to post changes for major bugs or fixes as they are released.
Some builds might feature only minor changes, ie. only updating the LineageOS source
Klimtlte Downloads
Google Apps:
http://opengapps.org/
Kernel
https://github.com/exynos5420/android_kernel_samsung_exynos5420
Device Tree
https://github.com/exynos5420/android_device_samsung_klimtlte
Aytex, who made all of the banners on this post.
@Barracuda77777 (For helping along the way)
@UpInTheAir for his kernel magic and misc fixes
@crpalmer (for picassowifi device and kernel gits - the base @Barracuda77777 and @nvertigo67 started of from)
@eousphoros (for his device git)
@nvertigo67 (for his work on chagallwifi)
@Nexorrr (for his work on chagalllte)
Fingerprint is disabled
Calling reboots the device
Other issues?
Before posting in this thread, make sure of a few things:
You used the search function of the forums.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread.
Logs! You can use this: https://play.google.com/store/apps/details?id=com.tortel.syslog
Wow, that looks awesome! I will download and report back.
Gesendet von meinem SM-T705 mit Tapatalk
@deadman96385 you mention 14.1 in the thread but 6.0.1 in the topic title
If it's 14.1, can I ask you a local_manifest for chagalllte ?
Thanks
Orphee said:
@deadman96385 you mention 14.1 in the thread but 6.0.1 in the topic title
If it's 14.1, can I ask you a local_manifest for chagalllte ?
Thanks
Click to expand...
Click to collapse
Oops i just fixed it thanks
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- DEVICES -->
<project name="exynos5420/android_device_samsung_klimtlte" path="device/samsung/klimtlte" remote="github" revision="cm-14.1" />
<project name="exynos5420/android_device_samsung_exynos5420-common" path="device/samsung/exynos5420-common" remote="github" revision="cm-14.1" />
<!-- KERNEL -->
<project name="exynos5420/android_kernel_samsung_exynos5420" path="kernel/samsung/exynos5420" remote="github" revision="cm-14.1" />
<!-- VENDOR -->
<project name="exynos5420/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-14.1" />
<!-- HARDWARE -->
<project name="exynos5420/android_hardware_samsung_slsi-cm_exynos5420" path="hardware/samsung_slsi-cm/exynos5420" remote="github" revision="cm-14.1" />
<project name="CyanogenMod/android_external_stlport" path="external/stlport" remote="github" revision="cm-14.1" />
<project name="exynos5420/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-14.1" />
<project name="lineageos/android_hardware_samsung_slsi-cm_exynos" path="hardware/samsung_slsi-cm/exynos" remote="github" revision="cm-14.1"/>
<project name="lineageos/android_hardware_samsung_slsi-cm_exynos5" path="hardware/samsung_slsi-cm/exynos5" remote="github" revision="cm-14.1"/>
<project name="lineageos/android_hardware_samsung_slsi-cm_openmax" path="hardware/samsung_slsi-cm/openmax" remote="github" revision="cm-14.1"/>
</manifest>
Nice! Thanks for this man. Looking forward to testing it out. Btw which would u recommend: liquid death OS or this ROM?
deadman96385 said:
Oops i just fixed it thanks
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- DEVICES -->
<project name="exynos5420/android_device_samsung_klimtlte" path="device/samsung/klimtlte" remote="github" revision="cm-14.1" />
<project name="exynos5420/android_device_samsung_exynos5420-common" path="device/samsung/exynos5420-common" remote="github" revision="cm-14.1" />
<!-- KERNEL -->
<project name="exynos5420/android_kernel_samsung_exynos5420" path="kernel/samsung/exynos5420" remote="github" revision="cm-14.1" />
<!-- VENDOR -->
<project name="exynos5420/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-14.1" />
<!-- HARDWARE -->
<project name="exynos5420/android_hardware_samsung_slsi-cm_exynos5420" path="hardware/samsung_slsi-cm/exynos5420" remote="github" revision="cm-14.1" />
<project name="CyanogenMod/android_external_stlport" path="external/stlport" remote="github" revision="cm-14.1" />
<project name="exynos5420/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-14.1" />
<project name="lineageos/android_hardware_samsung_slsi-cm_exynos" path="hardware/samsung_slsi-cm/exynos" remote="github" revision="cm-14.1"/>
<project name="lineageos/android_hardware_samsung_slsi-cm_exynos5" path="hardware/samsung_slsi-cm/exynos5" remote="github" revision="cm-14.1"/>
<project name="lineageos/android_hardware_samsung_slsi-cm_openmax" path="hardware/samsung_slsi-cm/openmax" remote="github" revision="cm-14.1"/>
</manifest>
Click to expand...
Click to collapse
Thank you !
about the following line : <project name="CyanogenMod/android_external_stlport" path="external/stlport" remote="github" revision="cm-14.1" />
It should be lineageos i guess!
Edit : Do you plan to add 14.1 branch to exynos5420/android_device_samsung_chagalllte or should i leave it as this for chagalllte ?
adil089 said:
Nice! Thanks for this man. Looking forward to testing it out. Btw which would u recommend: liquid death OS or this ROM?
Click to expand...
Click to collapse
LineageOS for now because LiquidDeath OS has to many bugs right now because it is AOSP based
Orphee said:
Thank you !
about the following line : <project name="CyanogenMod/android_external_stlport" path="external/stlport" remote="github" revision="cm-14.1" />
It should be lineageos i guess!
Click to expand...
Click to collapse
Yeah it should be but stlport isn't gonna be updated like at all anymore.
Can you please make this rom for t700 as well..?? Most people have T700
Roberttk said:
Can you please make this rom for t700 as well..?? Most people have T700
Click to expand...
Click to collapse
Doubtful i gave my t700 away for the time being. If someone would like to build it themselves it isn't hard.
deadman96385 said:
Doubtful i gave my t700 away for the time being. If someone would like to build it themselves it isn't hard.
Click to expand...
Click to collapse
I'm downloading the source tree right now, I should have a build and new thread up soon.
@deadman96385
I have removed first line in update_script file and flashed it on t700..
It is working fine.,. I have not yet noticed any bug... Camera , music , WiFi everything are working...
Does flashing by this method is safe?
Awesome work Deadman! Works perfectly. I found a bug with root access and the SD cards. It's only possible to allow root for adb.
About the SD issue, when I click on my SD card in the file manager it says "This operation requires elevated permissions. Try changing to Root Access Mode", which is not possible and I can't access my SD card.
Gesendet von meinem SM-T705 mit Tapatalk
haimann95 said:
Awesome work Deadman! Works perfectly. I found a bug with root access and the SD cards. It's only possible to allow root for adb.
About the SD issue, when I click on my SD card in the file manager it says "This operation requires elevated permissions. Try changing to Root Access Mode", which is not possible and I can't access my SD card.
Gesendet von meinem SM-T705 mit Tapatalk
Click to expand...
Click to collapse
Lineage has decided not to root the device by default, a method to allow native root is still being designed. For the time being i would recommend you use a third party root system, aka SuperSU, SuperUser, phh Superuser
Thank you for your hard work
I instaled on my t705 my problem is no data connection but for phone call and sms are fine
I flashed twice but the problem persist
I hope it will fixed in the next build
Best regard
hans william said:
Thank you for your hard work
I instaled on my t705 my problem is no data connection but for phone call and sms are fine
I flashed twice but the problem persist
I hope it will fixed in the next build
Best regard
Click to expand...
Click to collapse
Same problem here with clean install, latest OpenGapps Nano package, APN is correct, using latest Magisk and Phh Superuser.
- SMS/Calls send and receive fine
- no Mobile Data (wifi is fine)
- camera works (viewfinder has some banding, but photos are clean)
- couldn't get the rom to boot with DATA/Cache formated to F2FS
hans william said:
Thank you for your hard work
I instaled on my t705 my problem is no data connection but for phone call and sms are fine
I flashed twice but the problem persist
I hope it will fixed in the next build
Best regard
Click to expand...
Click to collapse
TASL said:
Same problem here with clean install, latest OpenGapps Nano package, APN is correct, using latest Magisk and Phh Superuser.
- SMS/Calls send and receive fine
- no Mobile Data (wifi is fine)
- camera works (viewfinder has some banding, but photos are clean)
- couldn't get the rom to boot with DATA/Cache formated to F2FS
Click to expand...
Click to collapse
Ok added Mobile Data to the bug list that is the one thing i can't test.
f2fs is not supported currently
Great work on the rom
I have a problem making calls with a bluetooth device though,on the line app it reports a mic problem and on skype it just crashes
starting five stars for this excellent ROM !!!! The only problem encountered so far is the telephone data connection does not appear (3g, 4g, etc.). I installed it last night, let's see if I can find other problems ...... do you know !!! Anyway congratulations ..... :good::good:
Mobile data bug isn't fixed yet?
How about battery life in this rom?
Related
after compile and succesfuly
then fllas to my device can't boot
this device tree my device
[
{
"remote": "yazidkucrit",
"repository": "android_device_samsung_msm7x27a-common",
"target_path": "device/samsung/msm7x27a-common",
"revision": "android-4.4"
},
{
"remote": "yazidkucrit",
"repository": "android_device_samsung_trebon",
"target_path": "device/samsung/trebon",
"revision": "android-4.4"
},
{
"remote": "TheWhisp",
"repository": "proprietary_vendor_samsung_msm7x27a",
"target_path": "vendor/samsung",
"revision": "cm-10.2"
},
{
"remote": "yazidkucrit",
"repository": "kernel_KeongBalap",
"target_path": "kernel/samsung/msm7x27a-common",
"revision": "master"
}
]
yazidkucrit said:
after compile and succesfuly
then fllas to my device can't boot
this device tree my device
[
{
"remote": "yazidkucrit",
"repository": "android_device_samsung_msm7x27a-common",
"target_path": "device/samsung/msm7x27a-common",
"revision": "android-4.4"
},
{
"remote": "yazidkucrit",
"repository": "android_device_samsung_trebon",
"target_path": "device/samsung/trebon",
"revision": "android-4.4"
},
{
"remote": "TheWhisp",
"repository": "proprietary_vendor_samsung_msm7x27a",
"target_path": "vendor/samsung",
"revision": "cm-10.2"
},
{
"remote": "yazidkucrit",
"repository": "kernel_KeongBalap",
"target_path": "kernel/samsung/msm7x27a-common",
"revision": "master"
}
]
Click to expand...
Click to collapse
Device can't boot is a little less of information...
Do you see the Omni-Logo ? If not than it's quite sure that even the kernel does not boot up. If yes than do a logcat during boot up.
Greetz
lagloose said:
Device can't boot is a little less of information...
Do you see the Omni-Logo ? If not than it's quite sure that even the kernel does not boot up. If yes than do a logcat during boot up.
Greetz
Click to expand...
Click to collapse
no omni the logo, but if the menu button and back in the press there are vibrations which indicates that it is alive
hi, can you help me with something?
yjosipy is trying to build cm11 as well but we have a problem,
when sync repo, it giver error at your manifest
can you plz tell us what is wrong?
<!-- Local projects -->
<project path="external/webkit" name="legaCyMod/android_external_webkit" revision="cm-11.0" />
<project path="hardware/atheros/wlan" name="TheWhisp/android_hardware_atheros_wlan" revision="cm-11.0" />
<project path="hardware/qcom/display-legacy" name="TheWhisp/android_hardware_qcom_display-legacy" revision="jellybean-mr2" />
<project path="hardware/qcom/media-legacy" name="Dazzozo/android_hardware_qcom_media-legacy" revision="jellybean-mr2" />
<project path="device/samsung/msm7x27a-common" name="yazidkucrit/android_device_samsung_msm7x27a-common" revision="cm-11.0" />
<project path="device/samsung/trebon" name="yazidkucrit/android_device_samsung_s7500" revision="cm-11" />
<project path="kernel/samsung/msm7x27a-common" name="yazidkucrit/kernel_KeongBalap" revision="master" />
<project path="vendor/samsung" name="yazidkucrit/proprietary_vendor_samsung_msm7x27a" revision="cm-10.2" />
The revision on your manifest and your branch on github for Samsung common are different, update manifest for this to android-4.4 and you will be fine. See you are using LegaCyMod for the WebKit. You know there are some patches that you need to apply before you build, you can find them on Legacymod github
Sent from my Blade III using Tapatalk
ShadowsDie said:
hi, can you help me with something?
yjosipy is trying to build cm11 as well but we have a problem,
when sync repo, it giver error at your manifest
can you plz tell us what is wrong?
<!-- Local projects -->
<project path="external/webkit" name="legaCyMod/android_external_webkit" revision="cm-11.0" />
<project path="hardware/atheros/wlan" name="TheWhisp/android_hardware_atheros_wlan" revision="cm-11.0" />
<project path="hardware/qcom/display-legacy" name="TheWhisp/android_hardware_qcom_display-legacy" revision="jellybean-mr2" />
<project path="hardware/qcom/media-legacy" name="Dazzozo/android_hardware_qcom_media-legacy" revision="jellybean-mr2" />
<project path="device/samsung/msm7x27a-common" name="yazidkucrit/android_device_samsung_msm7x27a-common" revision="cm-11.0" />
<project path="device/samsung/trebon" name="yazidkucrit/android_device_samsung_s7500" revision="cm-11" />
<project path="kernel/samsung/msm7x27a-common" name="yazidkucrit/kernel_KeongBalap" revision="master" />
<project path="vendor/samsung" name="yazidkucrit/proprietary_vendor_samsung_msm7x27a" revision="cm-10.2" />
Click to expand...
Click to collapse
<project path="device/samsung/trebon" name="yazidkucrit/android_device_samsung_s7500" revision="cm-11" /> where did u find this repo ? ...it looks like it doesn't exist..
B]<project path="device/samsung/msm7x27a-common" name="yazidkucrit/android_device_samsung_msm7x27a-common" revision="cm-11.0" />
branch error : or android-4.4 or master
ilpolpi65 said:
<project path="device/samsung/trebon" name="yazidkucrit/android_device_samsung_s7500" revision="cm-11" /> where did u find this repo ? ...it looks like it doesn't exist...
Click to expand...
Click to collapse
yes sry i saw that right after i posted this
so i guess i delete that and its done?
---------- Post added at 11:45 PM ---------- Previous post was at 11:31 PM ----------
robt77 said:
The revision on your manifest and your branch on github for Samsung common are different, update manifest for this to android-4.4 and you will be fine. See you are using LegaCyMod for the WebKit. You know there are some patches that you need to apply before you build, you can find them on Legacymod github
Sent from my Blade III using Tapatalk
Click to expand...
Click to collapse
i dont know what patches are you talking about, can you clarify me that?
or is the legacymod only for blade III?
ShadowsDie said:
yes sry i saw that right after i posted this
so i guess i delete that and its done?
---------- Post added at 11:45 PM ---------- Previous post was at 11:31 PM ----------
i dont know what patches are you talking about, can you clarify me that?
or is the legacymod only for blade III?
Click to expand...
Click to collapse
I only mentioned it as saw the legacymod/WebKit repo and thought I would mention it. Think our phones have similar chip sets so it might work. The patches are under local manifest on legacymod github. There are one under framework/base and two under framework/webview you may need to make an amendment to your boardconfig to allow use of that WebKit. Sorry still new to this Android development.
Sent from my Blade III using Tapatalk
fatal: remote error: Git repository not found
Hi,
I'm trying to build Omnirom for my gt-s7500 and I get "fatal: remote error: Git repository not found" errors when doing repo sync for all the "extra" repositories beside the Omnirom tree.
I use the sources from http://forum.xda-developers.com/showthread.php?t=2640855
Here's what I have in my local manifest :
Code:
<!-- Local projects -->
<manifest>
<project path="device/samsung/msm7x27a-common" name="yazidkucrit/android_device_samsung_msm7x27a-common" revision="android-4.4" />
<project path="device/samsung/trebon" name="yazidkucrit/android_device_samsung_trebon" revision="android-4.4" />
<project path="kernel/samsung/msm7x27a-common" name="yazidkucrit/kernel_bekicot" revision="master" />
<project path="vendor/samsung" name="TheWhisp/proprietary_vendor_samsung_msm7x27a" revision="cm-10.2" />
</manifest>
Any idea ? I'm a newbie in this area and I'm trying to learn.
Thanks in advance,
Jérôme
jdegreef said:
I'm trying to build Omnirom for my gt-s7500 and I get "fatal: remote error: Git repository not found" errors..
Click to expand...
Click to collapse
Look at what it says for which repositories it cannot find, then you try to manually find them on github.com. Check branches/revisions as well.
jdegreef said:
Here's what I have in my local manifest :
Click to expand...
Click to collapse
You need to specify where these yazidkucrit and TheWhisp repos are, so your local manifest should look like this:
Code:
<!-- Local projects -->
<manifest>
<remote fetch="git://github.com/yazidkucrit" name="yazidkucrit" />
<remote fetch="git://github.com/TheWhisp" name="TheWhisp" />
<project path="device/samsung/msm7x27a-common" name="yazidkucrit/android_device_samsung_msm7x27a-common" remote="github" revision="android-4.4" />
<project path="device/samsung/trebon" name="yazidkucrit/android_device_samsung_trebon" remote="github" revision="android-4.4" />
<project path="kernel/samsung/msm7x27a-common" name="yazidkucrit/kernel_bekicot" remote="github" revision="master" />
<project path="vendor/samsung" name="TheWhisp/proprietary_vendor_samsung_msm7x27a" remote="github" revision="cm-10.2" />
</manifest>
Also, I very much doubt that your kernel is called msm7x27a-common.
Thank You both of you.
It turned out that my local_manifest was corrupt probably because of a copy/paste from the web. I recreate it from scratch and everything synced without error.
But now when trying breakfast i get
Code:
[email protected]:~/android/omni$ breakfast
You're building on Linux
Lunch menu... pick a combo:
1. full-eng
Which would you like? [aosp_arm-eng]
you device can't be found in device sources..
Traceback (most recent call last):
File "build/tools/roomservice.py", line 297, in <module>
fetch_dependencies(device)
File "build/tools/roomservice.py", line 250, in fetch_dependencies
raise Exception("ERROR: could not find your device "
Exception: ERROR: could not find your device folder location, bailing out
I assume my knowledge is very limited and up until now I've only been able to build CM11 for officially supported devices.
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
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.
{
"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
{
"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 ?