[ROM][13.0][UNOFFICIAL][OCE] LineageOS 20.0 [BETA] - HTC U Ultra ROMs, Kernels, Recoveries, & Other Dev

{
"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:
* 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.
*
*/
Introduction
LineageOS is a free, community built, aftermarket firmware distribution of Android 13 (T), which is designed to increase performance and reliability over stock Android for your device.
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. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Bugs
What's working:
Boot
Camera / Camcorder
RIL (LTE/Dual SIM/SMS)
VoLTE
Fingerprint Sensor
WiFi
Hotspot (2.4Ghz / 5Ghz)
Bluetooth
Secondary Screen (now it's working as a "Notch/Cutout" like other devices!, this area is now status bar)
GNSS GPS
Audio (Top speaker, Stereo speaker)
Type-C Headphone Audio
Video Playback
NFC
Sensors
USB (ADB/MTP/PTP)
Touch
What's not working:
VoWiFi
USB (MTP/PTP)
Hardware Encryption
SELinux is permissive
You tell me.
Installation instructions
Upgrade to Stock Oreo Rom!
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions and FORMAT DATA from TWRP of your device (required when coming from stock!).
Flash ROM.
Optional: Install the Google Apps addon package.
Optional: Install Magisk for Root.
Supported models:
ocedugl, ocedtwl, oceuhl
Downloads
Recovery : Unofficial TWRP - Support decrypt < USE THIS TO FLASH!
Gapps : NikGApps 13 ARM64
Rom : Download
Sources
oce device tree: oce
oce kernel tree: oce kernel
htc vendor tree: vendor tree
Donate
DONATE To Me
Big Thanks
LineageOS Team.
all PME (HTC 10) contributors.

Changelogs
2023/05/27
Properly fixed RIL and In-call audio.
2023/05/24
Updated to Android 13.0.0_r43 with May security patches.
Upstream updates and fixes.
Fixed RIL.
Added Aperture camera app.
Minor tweaks.
2022/09/09
Initial release of LineageOS 20.0 for HTC U Ultra.

Screenshots

Duuude u r great dude !

Hi Tarekzim, if possible, add face unlock in this custom ROM

Hello brother, thank you very much
You have revived our phone again
And you made Android 13 for it

I can't install any app from google play ( always pending)
And I tied to use app gallery but it can't read WiFi internet connection
And I can't attach screen shots to this reply

I need help!

Thx for your work, vm!

The rum is nice works beautifully but no google gapps work

Hi
First, I wanna thank you for building ROMs for HTC U Ultra.
Second, I have some suggestions for you in building this ROM. as you know HTC U Ultra has a very weak battery so it would be better if you put your main goal on battery optimization and its life.
Third, it would be nice if you can boost its microphone and speakers for calling.
Forth, lowering the charging time by changing some software stuff is a good idea.

tarkzim said:
Screenshots
Click to expand...
Click to collapse
Great work but Sim toolkit app not working

Jaceksgal said:
The rum is nice works beautifully but no google gapps work
Click to expand...
Click to collapse
Is your sim toolkit working

teraz nie sprawdzę bo mam inny pokój ale dzwonił i otwierał połączenia i smsy bez problemów

Jaceksgal said:
teraz nie sprawdzę bo mam inny pokój ale dzwonił i otwierał połączenia i smsy bez problemów
Click to expand...
Click to collapse
Which ROM do you have

Great work give us update version

joe-58 said:
Hi
First, I wanna thank you for building ROMs for HTC U Ultra.
Second, I have some suggestions for you in building this ROM. as you know HTC U Ultra has a very weak battery so it would be better if you put your main goal on battery optimization and its life.
Third, it would be nice if you can boost its microphone and speakers for calling.
Forth, lowering the charging time by changing some software stuff is a good idea.
Click to expand...
Click to collapse
@tarkzim

tarkzim said:
Screenshots
Click to expand...
Click to collapse
Hello Ta
tarkzim said:
Changelogs
2022/09/09
Initial release of LineageOS 20.0 for HTC U Ultra.
Click to expand...
Click to collapse
Hello tarkzim,
I was compiling the room and got stuck on this HELP
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=13
LINEAGE_VERSION=20.0-20230101-UNOFFICIAL-oce
TARGET_PRODUCT=lineage_oce
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=generic
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv8-a
TARGET_2ND_CPU_VARIANT=generic
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-5.4.0-135-generic-x86_64-Ubuntu-18.04.6-LTS
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=TQ1A.221205.011
OUT_DIR=out
PRODUCT_SOONG_NAMESPACES=vendor/htc/oce device/htc/oce hardware/qcom-caf/msm8996 vendor/qcom/opensource/data-ipa-cfg-mgr-legacy-um vendor/qcom/opensource/dataservices
============================================
<b>[100% 1/1] analyzing Android.bp files and generating ninja file at out/soong/build</b>
FAILED: out/soong/build.ninja
cd "$(dirname "out/host/linux-x86/bin/soong_build&quot" && BUILDER="$PWD/$(basename "out/host/linux-x86/bin/soong_build&quot" && cd / && env -i "$BUILDER" --top "$TOP" --soong_out "out/soong" --out "out" -o out/soong/build.ninja --globListDir build --globFile out/soong/globs-build.ninja -t -l out/.module_paths/Android.bp.list --available_env out/soong/soong.environment.available --used_env out/soong/soong.environment.used.build Android.bp
Killed
04:45:55 soong bootstrap failed with: exit status 1
FAILED: ninja fifo didn&apos;t finish after 5s
<font color="#CC0000">#### failed to build some targets (24:54 (mm:ss)) ####</font></pre>

dommies said:
<b>[100% 1/1] analyzing Android.bp files and generating ninja file at out/soong/build</b>
FAILED: out/soong/build.ninja
cd "$(dirname "out/host/linux-x86/bin/soong_build&quot" && BUILDER="$PWD/$(basename "out/host/linux-x86/bin/soong_build&quot" && cd / && env -i "$BUILDER" --top "$TOP" --soong_out "out/soong" --out "out" -o out/soong/build.ninja --globListDir build --globFile out/soong/globs-build.ninja -t -l out/.module_paths/Android.bp.list --available_env out/soong/soong.environment.available --used_env out/soong/soong.environment.used.build Android.bp
Killed
04:45:55 soong bootstrap failed with: exit status 1
FAILED: ninja fifo didn&apos;t finish after 5s
Click to expand...
Click to collapse
I've run into a similar situation trying to build 20. I'll share what I learned.
How much DRAM and swap do you have?
Recent updated LineageOS build guides for official devices says you should have 32GB DRAM to build 18.1 and higher. For example,
https://wiki.lineageos.org/devices/chagallwifi/build
"A reasonable amount of RAM (16 GB to build up to lineage-17.1, 32 GB or more for lineage-18.1 and up). The less RAM you have, the longer the build will take. Enabling ZRAM can be helpful.''
I'm able to build 20 on 18GB DRAM + no swap for arm architectures, but I suspect arm64 bit builds require at least 20GB DRAM starting with 20 so the above soong phase passes without error. I have no problems building 18.1 and 19.1 on 18GB DRAM building arm64.
You can verify by opening a terminal split into 2 panes. On the top, run brunch. On the bottom, run htop and watch your DRAM memory consumption during the above soong phase. If DRAM maxes out, then it's likely the problem.
So either add more DRAM and/or make a swap partition (probably 16GB).

retiredtab said:
I've run into a similar situati
retiredtab said:
I've run into a similar situation trying to build 20. I'll share what I learned.
How much DRAM and swap do you have?
Recent updated LineageOS build guides for official devices says you should have 32GB DRAM to build 18.1 and higher. For example,
https://wiki.lineageos.org/devices/chagallwifi/build
"A reasonable amount of RAM (16 GB to build up to lineage-17.1, 32 GB or more for lineage-18.1 and up). The less RAM you have, the longer the build will take. Enabling ZRAM can be helpful.''
I'm able to build 20 on 18GB DRAM + no swap for arm architectures, but I suspect arm64 bit builds require at least 20GB DRAM starting with 20 so the above soong phase passes without error. I have no problems building 18.1 and 19.1 on 18GB DRAM building arm64.
You can verify by opening a terminal split into 2 panes. On the top, run brunch. On the bottom, run htop and watch your DRAM memory consumption during the above soong phase. If DRAM maxes out, then it's likely the problem.
So either add more DRAM and/or make a swap partition (probably 16GB).
Click to expand...
Click to collapse
Thank you the issue was the RAM which I sorted but ROM did not run after installing it
on trying to build 20. I'll share what I learned.
How much DRAM and swap do you have?
Recent updated LineageOS build guides for official devices says you should have 32GB DRAM to build 18.1 and higher. For example,
https://wiki.lineageos.org/devices/chagallwifi/build
"A reasonable amount of RAM (16 GB to build up to lineage-17.1, 32 GB or more for lineage-18.1 and up). The less RAM you have, the longer the build will take. Enabling ZRAM can be helpful.''
I'm able to build 20 on 18GB DRAM + no swap for arm architectures, but I suspect arm64 bit builds require at least 20GB DRAM starting with 20 so the above soong phase passes without error. I have no problems building 18.1 and 19.1 on 18GB DRAM building arm64.
You can verify by opening a terminal split into 2 panes. On the top, run brunch. On the bottom, run htop and watch your DRAM memory consumption during the above soong phase. If DRAM maxes out, then it's likely the problem.
So either add more DRAM and/or make a swap partition (probably 16GB).
Click to expand...
Click to collapse

Related

[ROM][6.0.1][XT1622][UNOFFICIAL] CyanogenMod 13.0 for Moto G4 [BETA]

{
"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 ROM is in testing stage and not ready for daily use at the moment​
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community
First I would like to thank the following developers :
@ashwin007
@Shreps
@elandoido
@vache
I used the sources from @ashwin007 as a starting point and combined them with Motorola's stock kernel sources to base this cm 13.0 build on.
Before you start
THIS ROM IS TESTED ON XT1622 UNTESTED BY DEVELOPER ON ANY OTHER MOTO G4
Code:
*
* Your warranty will be voided !
*
* 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.
*
About the ROM
Current state of ROM : BETA
What works/is Fixed
Boots
Sound (excl ringtones)
Mic
GSM (ril)
Dualsim detection XT1622
Wifi
Camera
GPS
Ringtones (no wav/mp3 support)
What is not working
Important
Single sim support not working.
Minor
Flashing red border around screen. (seems sound related)
Instructions
How to install CM13.0
If you don't have TWRP yet, get it from here : TWRP by bender1987 (Use the flash option, not just boot)
Download the ROM and the Gapps that are located below to your device
Reboot into TWRP by holding VOL UP + POWER + HOME on boot (Needs to be tested)
In case things go wrong make a backup
After the backup has completed return to home and select Wipe and then Advanced Wipe
Now ONLY tick Dalvik Cache, System, Data and Cache
After ticking those, Swipe below to wipe
Once the wipe has completed return to home and select the ROM
After you selected the ROM swipe below to install it
After the ROM has installed flash the Gapps
When all of this is done, reboot into system, wait, and enjoy CM12.1
How to ROOT
In CM 13.0 Enable the developer options
Select Root access
Select Apps Only
Done
Questions and bug reporting
The following questions will be ignored
Inappropriate questions
Forced orders, EX. : "PLS FIX!!!!!!"
ETA's
Often repeated questions usually by the same user
Requests that are out of CM's framework (Ex. Adding Samsung Apps)
How to report a bug/issue
Explain exactly what happens
Mention a log if you can (Please use hastebin or any other paste site to keep the thread clean)
If you can't mention a log, explain as precise as possible when, why and where it occurs!
Changelog
Code:
**********
29/08/2016 - Extra prop settings in init for non dualsim XT1622 models, based on work from [user=68428475]@vache[/user].
**********
26/08/2016 - Slight prop changes in single/dual sim support. Maybe enough to get it to work on single sim. (dual works)
**********
25/08/2016 - Rild and libril build from source.
**********
24/08/2016 - Recompile, camera works again.
**********
23/08/2016 - Single sim settings (prop only) taken from XT1622 single sim and included. Build with detection. (Dual sim mode tested)
- Camera not working (something broke it)
**********
21/08/2016 - Disabled single/dual sim detection, limited 1 build to single sim for those who want to test if this could work. (20160821 build)
**********
20/08/2016 - Switched single/dual back to sim detection. (20160820 build)
- Changed default CPU governor from performance to Interactive to limit heat buildup.
**********
19/08/2016 - Switched single/dual sim check to hwrev based. Needs to be tested. (dualsim XT1622 works)
**********
18/08/2016 - Single sim needs to be tested, 2 'method' builds uploaded to test
- Enabled several decoding codecs, including aac and flac. (ringtones work better now)
- Did something not nice with sound, flashing red border around screen.
**********
17/08/2016 - Dual sim detection works (single sim detection working, sim not working)
- Memory option detection added. Settings split up between low mem (2G) and high mem (>2G) devices.
- Full cm phone support included
**********
15/08/2016 - [user=5426059]@ashwin007[/user] git a working build, cloned his device and vendor tree to learn where I went wrong and to see if I had some minor changes done correctly.
**********
05/08/2016 - First bootable image using Motorola kernel (permissive)
**********
06/07/2016 - First compile (I hope)
**********
Downloads
Latest CM 13.0 build : https://www.androidfilehost.com/?fid=24591000424960822
All CM 13.0 releases can be found here :
All CM 13.0 testing releases can be found here : https://www.androidfilehost.com/?w=files&flid=90423
All CM 13.0 beta releases can be found here :
Recommended GAPPS by opengapps.org : http://opengapps.org/ (I use pico)
Source
All our sources can be found here : https://github.com/Moto-G4
Screenshots
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
XDA:DevDB Information
CyanogenMod 13.0 for Moto G4, ROM for the Moto G4
Contributors
T_I, ashwin007, shreps, elandroido
Source Code: https://github.com/Moto-G4
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: CyanogenMod
Version Information
Status: Beta
Created 2016-07-06
Last Updated 2016-08-29
Ok, build failed. Used osprey (Moro G 2015) as starting point, maybe not the wisest choice. Merlin (Moto G 2015 Turbo) looks more similar. However, both based on msm8916 board. The only msm8952 basesd image I can find in cm sources is htc One A9 (hiaue), but that device is arm64, the Moto G4 (at least the one I have) only has the 32 bit libs. Uploaded current state to the git location in OP. I've build with android_device_motorola_athene, android_device_motorola_mcm8952-common and kernel-msm. (All cm-13.0 branch)
When someone has the time and experience to help, that would be nice. I'll try again day after tomorrow.
Edit: missing headers for f2fs in motorola kernel tree... those are split off in another git repo... joined them with the msm kernel and compiling again.
I find this device interesting but only if a working CM ROM exists (possibly also for Moto G4 Plus), so I plan to follow this thread. I hope in a growing community for G4/XT1622 and G4 Plus/XT1642. Interesting that I just searched for this when the ROM is not even a day old
Thanks @T_I
Waiting for beta version, so we can try it
Will this will work well on Indian Moto g4 plus variant (XT1643)
Moto G3 (?) lel is Moto G4 , any screenshots?
XT1641?
Enviado desde mi Moto G (4) mediante Tapatalk
Haven't got a clue, I've almost got the sources in a state that it'll build, we will have to wait and see if it'll boot after the build. (and after that if anything works)
can someone post a direct link to the cm13 rom i cant find it thanks
Just out of interest: how does compiling a build usually take, the way you say it, it seems like it takes quite a while (1+ hours).
[ROM][6.0.1][XT1622][UNOFFICIAL] CyanogenMod 13.0 for Moto G3 [building]
Florensie said:
Just out of interest: how does compiling a build usually take, the way you say it, it seems like it takes quite a while (1+ hours).
Click to expand...
Click to collapse
On this computer, it'll take about 2-3 hours, when it's done. I'm at the point where the kernel builds without errors, but the image itself gives some issues. Switched from osprey (Moto G3) to merlin (Moto G3 turbo) as starting point. Mainly because the turbo version is dual sim. It also has some thermal settings that re included in the tree, so I can take a peak and see how to include the thermal settings from the athene in the build. (and later how to correct them, the device is getting a bit warmer then I expected while using)
xtermmin said:
[ROM][6.0.1][XT1622][UNOFFICIAL] CyanogenMod 13.0 for Moto G3 [building]
Click to expand...
Click to collapse
1 typo found, corrected. Wouldn't be to surprised if there are more in OP.
Drat, almost there, but the build fails on the install-recovery.sh script.
Code:
Installing recovery patch to system partition
Warning: could not find SYSTEM/build.prop in <built-in function zip>
using prebuilt recovery.img from BOOTABLE_IMAGES...
using prebuilt boot.img from BOOTABLE_IMAGES...
cp: cannot stat '/usr/local/src/cm/android/system/out/target/product/athene/ota_temp/SYSTEM/bin/install-recovery.sh': No such file or directory
build/core/Makefile:1074: recipe for target '/usr/local/src/cm/android/system/out/target/product/athene/system/bin/install-recovery.sh' failed
make: *** [/usr/local/src/cm/android/system/out/target/product/athene/system/bin/install-recovery.sh] Error 1
make: Leaving directory '/usr/local/src/cm/android/system'
I'm currently look into the sources to see what should provide this script, as I can't find any references for this in my other builds. (which don't have this issue)
Edit: drat, stupid error in my sources. When you include build tree, it's nice the Android.mk will accept the device to include it... Rebuilding. With some luck this was the issue.
If that didn't work, try wih the moto x play sources...
waiting,will try it on Moto G4 plus XT1643(Indian)....
dhk.- said:
If that didn't work, try wih the moto x play sources...
Click to expand...
Click to collapse
Good one, as the merlin tree is a fork of lux, maybe a clean start is better. Last attempt for merlin, will try lux tomorrow.
Ok, switched angle of approach. Instead of rewriting an existing device, started with the twrp sources as starting point and working my way up to a setup similar to the osprey/lux/merlin setup. (separate board and device setup) First try will be compiling with the twrp sources for athene in the cm source tree. Pre build kernel and dt, nothing else.
Edit: Yes, this is the way to go. Just build the first bootable recovery from CM source. With both pre-build kernel and dt. Trying a build with kernel from sources, then dt from sources as well.
Edit 2: And broke it again. but I pin-pointed the section that breaks the build. The kernel and partitioning at least are OK, it's one of the extra modules/settings that make the mess. Will try again Thursday.
Any news?
My CM 13 - https://yadi.sk/d/-WvJyaqqtNJ2P
much does not work
is this works for g4 plus also?
is kernel 64-bit?
thx a lot
I have a G4 plus - x32 firmware
wizard-dima said:
Any news?
My CM 13 - https://yadi.sk/d/-WvJyaqqtNJ2P
much does not work
Click to expand...
Click to collapse
bugs??

[OFFICIAL][a5xelte][SM-A510F]Lineage OS 16.0 for A5 2016

{
"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"
}
Introduction
LineageOS 16.0 is a free, community built, aftermarket firmware distribution of Android 9.0 (Pie), which is designed to increase performance and reliability over stock Android for your device. The port for the Exynos7580 based devices was created by @Stricted and I along with many contributions from other people in the Android community.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What worksCalls, SMS, Mobile Data
Camera
NFC
WiFi
Bluetooth
Torch
Sensors
GPS
SELinux Enforcing
HWC​What doesn't work
IMS services (VoLTE, VoWiFi, etc). Samsung has their own proprietary implementation. It is not really possible to easily port that to LineageOS.​ Installation
Install the latest TWRP (Available Here)
Make a full backup (just in case something goes wrong)
Do a full wipe (Cache, Dalvik Cache, Data, System)
Download the latest LOS build and transfer it to your phone
Install LOS
If you are installing GApps do it at the same time (preferably in the same install queue)
And finally boot, the first boot can take several minutes as it optimises all the apps​ Downloads
Latest official releases HERE
Latest unoficial releases are uploaded HERE
OpenGapps HERE
TWRP is availableHERE
Magisk is available HERE​Thanks
@Stricted
@l-0-w
@sekil
@alexax66
@macs18max (BT call audio fix)
@Borduni
All the testers on the Discord group (https://discord.gg/8fp9cr7)
And all others who have contributed to the Exynos projects past and present​A special thanks to my donorsMarkus Anders
@D4ND310
@epicwilmo
@tyson
@thebinf
@Herti
@pixelou
@xavier66​
XDA:DevDB Information
Lineage OS 16.0 for A5 2016, ROM for the Samsung Galaxy A Series
Contributors
danwood76, stricted
Source Code: https://github.com/LineageOS
ROM OS Version: 9.x Pie
Based On: LineageOS
Version Information
Status: Stable
Created 2019-06-25
Last Updated 2019-08-22
Changelog
Code:
Changes in the 18/08/19 release:
[INDENT]Fixed GPS SEPolicy (thanks @stricted)
[/INDENT]
Older changes listed below:
Code:
Chaages in the 16/08/19 release:
[INDENT]Revert one HWC change to correct slight UI lag
LOS updates[/INDENT]
Code:
Chaages in the 11/08/19 release:
[INDENT]More HWC improvements (thanks @Stricted)
Added volume keys as a wakeup source (now visible in button settings)
Corrected fingerprint sensor location on the "add fingerprint" GUI
Synced WiFi config with stock (now same as A3)
August security patches[/INDENT]
Code:
Changes in the 23/07/19 release:
[INDENT]Fixed remaining HWC issues (we now build with no hacks to upstream LOS)
Added buildprop to skip waiting for buffer fences to signal (thanks @stricted and @ivan_meler)
Build new HIDL lights HAL
[/INDENT]
Code:
Changes in the 19/07/19 release:
[INDENT]Fixed TWRP device list so it will now install correctly on variants other than A510F (thanks @dariotr)
Fixed SSWAP
Synced with latest LOS sources[/INDENT]
Code:
Changes in the 07/07/2019 release:
[INDENT]Fixed HWC (Improves UI fluidity and power usage)
SELinux cleanup (thanks @Stricted)
Migrate to new HIDL LiveDisplay and Touch HALs (thanks @Stricted)
July Android Security Patch
LOS updates[/INDENT]
Code:
Changes in the 27/06/2019 release:
[INDENT]SEPolicy: Fixed SELinux denial that broke fingerprint on some variants
kernel: added config option to fix WiFi hotspot
[/INDENT]
Code:
Changes in the 25/06/2019 release:
[INDENT]
Initial release
[/INDENT]
Build Instructions
1. Setup a LineageOS build environment based on one of the supported LineageOS 16.0 devices: https://wiki.lineageos.org/index.html
Note: All commands below are executed from the LineageOS root directory
2. Initialise the LineageOS repositories
repo init -u git://github.com/LineageOS/android.git -b lineage-16.0
3. Sync the repos (can take a log time, around 30GB of downloads)
repo sync
4. Create the .repo/local_manifests directory and add the a5xelte manifest (attached)
mkdir .repo/local_manifests/
cp ~/Downloads/a5xelte.xml .repo/local_manifests/
5. Sync our device trees in
repo sync
6. Setup the build environment
source build/envsetup.sh
7. Finally start the build:
brunch lineage_a5xelte-userdebug
To pull in new changes it is usually only necessary to repeat steps 5 - 7.
thank you so much for bringing Los Pie to our little device
Downloading it right away
Can I dirty flash it over Bunny's Los 16 build ?
MBechirM said:
Can I dirty flash it over Bunny's Los 16 build ?
Click to expand...
Click to collapse
No, I wouldn't try that.
Our device tree is very different so a clean flash is the only way.
Great ROM
Runs smoothly on my phone everything seems to work just fine, only problem is the system seems to read the fingerprint scanner as an on display scanner.
Lungss said:
Runs smoothly on my phone everything seems to work just fine, only problem is the system seems to read the fingerprint scanner as an on display scanner.
Click to expand...
Click to collapse
How do you mean?
The fingerprint scanner location variable can only be front/back/left/right and I configured it for the front. It is working fine for me.
Regards,
Danny
danwood76 said:
How do you mean?
The fingerprint scanner location variable can only be front/back/left/right and I configured it for the front. It is working fine for me.
Regards,
Danny
Click to expand...
Click to collapse
The thumbnail under the instruction to locate fingerprint scanner shows the scanner location on the screen, while the scanner itself doesn't respond to any input.
This is what I see:
danwood76 said:
No, I wouldn't try that.
Our device tree is very different so a clean flash is the only way.
Click to expand...
Click to collapse
Ok then I'll clean flash it thanks for keeping this phone alive
Lungss said:
The thumbnail under the instruction to locate fingerprint scanner shows the scanner location on the screen, while the scanner itself doesn't respond to any input.
This is what I see:
--snip--
Click to expand...
Click to collapse
I think you are taking that image too literally .
The fingerprint scanner is the home button and it doesn't work whilst the charger is plugged in (not tested that on stock but it doesn't work whilst plugged in for me on LOS).
If you are having issues with the scanner then please dump a full logcat in matlog or via ADB which should help me debug.
Fingerprint scanner don't work like on the first builds of 15.1 los
Wow, that was fast ! :good:
Thank you for bringing Pie on our A510F !
I try your ROM asap.
Guigui
skaptes said:
Fingerprint scanner don't work like on the first builds of 15.1 los
Click to expand...
Click to collapse
Ah, I have missed the additional SEPolicy rule for the FP scanner on some variants.
I will correct this later.
I've tried your ROM, and everything is working fine for me exept the firgerprint scanner, but I understand that this will be solved soon.
Very happy with this ROM, thanks for the job !
Guigui
@danwood76, I am trying to build lineageos for microg 16.0 based on your rom, but failing evertime due to the following error :-
Syncing branch repository
sed: can't read build/core/version_defaults.mk: No such file or directory
sed: can't read build/core/version_defaults.mk: No such file or directory
sed: can't read build/core/version_defaults.mk: No such file or directory
[Wed Jun 26 10:23:17 UTC 2019] Can't detect the android version
the error log, suggests this :-
"Host key verification failed.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists"
I know this has got to do something with the ssh thing and I even tried to generate a ssh key for my local device but nothing happened.
Could you possibly suggest a solution to this.
Thanks.
The local manifest is the same that you have posted in this forum.
ashwini215 said:
@danwood76, I am trying to build lineageos for microg 16.0 based on your rom, but failing evertime due to the following error :-
Syncing branch repository
sed: can't read build/core/version_defaults.mk: No such file or directory
sed: can't read build/core/version_defaults.mk: No such file or directory
sed: can't read build/core/version_defaults.mk: No such file or directory
[Wed Jun 26 10:23:17 UTC 2019] Can't detect the android version
the error log, suggests this :-
"Host key verification failed.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists"
I know this has got to do something with the ssh thing and I even tried to generate a ssh key for my local device but nothing happened.
Could you possibly suggest a solution to this.
Thanks.
The local manifest is the same that you have posted in this forum.
Click to expand...
Click to collapse
I have changed the manifest in the build post to https so it should work if you update yours.
Regards,
Danny
I have a few questions, mini review and bugs report. (and sorry for my English, i'm from Poland)
1. HWC is a Hardware Composer? Why is disabled?
2. WiFi hotspot doesn't work.
3. I saw glitches when I switched to Youtube Vanced from playback in background for a few seconds (but this is probably a problem with this app)
4. ROM is a bit faster compared to Lineage 15.1 build by danwood76, but it still having a 2D animation stuttering sometimes.
KaroloBC said:
I have a few questions, mini review and bugs report. (and sorry for my English, i'm from Poland)
KaroloBC said:
1. HWC is a Hardware Composer? Why is disabled?
Click to expand...
Click to collapse
HWC is buggy on Pie so you get black screens / lockups. We use the graphics hardware acceleration instead and it works well.
KaroloBC said:
2. WiFi hotspot doesn't work.
Click to expand...
Click to collapse
Looks like I was missing a config option for Pie, I have added this and it will work in the next build (uploading now).
KaroloBC said:
3. I saw glitches when I switched to Youtube Vanced from playback in background for a few seconds (but this is probably a problem with this app)
Click to expand...
Click to collapse
I am not the author of YouTube Vanced.
KaroloBC said:
4. ROM is a bit faster compared to Lineage 15.1 build by danwood76, but it still having a 2D animation stuttering sometimes.
Click to expand...
Click to collapse
The phones hardware isn't the quickest, when I had stock on the A5 it ran very slow. We may see slight improvements if we ever manage to fix HWC.
Click to expand...
Click to collapse
Hi,
I'm currently uploading a quick bug fix release.
Code:
Changes in the 27/06/2019 release:
[INDENT]SEPolicy: Fixed SELinux denial that broke fingerprint on some variants
kernel: added config option to fix WiFi hotspot
[/INDENT]
Regards,
Danny

[ROM][UNOFFICIAL][R]LineageOS 18.0 for Galaxy J5 [J500H/FN/F/G/M/Y/8]

{
"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"
}
LineageOS is a free, community-built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.
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. Linked below is a package that has come from another Android project that restores the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
ROM Information
ROM Target Device: Samsung Galaxy J5 SM-J5008 | SM-J500H | SM-J500F/G/M/Y | SM-J500FN
ROM Status: Testing
ROM OS: LineageOS 18.0 (Android R)
Click to expand...
Click to collapse
What works
* Boots
* Basic functionality
* Wi-Fi
* Audio (music, etc)
* Camera (including video recording)
* Flash
* Sensors
* etc
What doesn't work
* RIL (in-call audio, messaging, data)
* Bluetooth
* GPS (may partially work, not tested)
* Miracast
* VoLTE, this will never work on AOSP as it's not easy to implement Samsung's proprietary implementation.
* Test and report other bugs
Device Names
Verify your device codename before downloading any firmware or recovery images!
Code:
[B]SM-J500F/G/M/Y[/B] - [COLOR="DarkSlateBlue"][B]j5lte[/B][/COLOR]
[B]SM-J5008[/B] - [COLOR="DarkSlateBlue"][B]j5ltechn[/B][/COLOR]
[B]SM-J500FN[/B] - [COLOR="DarkSlateBlue"][B]j5nlte[/B][/COLOR]
[B]SM-J500H[/B] - [COLOR="DarkSlateBlue"][B]j53gxx[/B][/COLOR]
Click to expand...
Click to collapse
Downloads
ROM Download: here
GApps Download (BitGapps): here
Installation
Install the latest OrangeFox(recommended, available here) or TWRP 3.3.1 or later
Make a full backup (just in case something goes wrong)
Make a full wipe(System, Data, Cache)
* Dirty flash may work, try and tell me.
Download the latest build and transfer it to your phone
Flash the zip
If you are installing GApps do it before booting to the ROM. Make sure to flash the correct architecture and version(arm 11.0)
And finally boot, the first boot can take several minutes as it optimizes all the apps
There are still quite a few features that are not yet completed for LineageOS 18.0, these are not bugs, this is a beta release.
You should provide logs when reporting any hardware-related issue.
How to provide logcats
Under Windows:
Code:
[B]* Install Samsung device drivers and then
the ADB utils from here:[/B]
[url]https://forum.xda-developers.com/showthread.php?t=2588979[/url]
[b]* Then enable developer mode, connect your phone to usb,
and from [B]cmd[/B] paste this command:[/b]
[I]adb logcat > %userprofile%/Desktop/logcat.txt[/I]
[b]then try to reproduce the bug.[/b]
[b]* The logcat file will be on your desktop.[/b]
Under Linux:
Code:
[b]* Install the ADB utils from your distribution's
package manager and execute the command:[/b]
[I]adb logcat > ~/logcat.txt[/I]
[b]then try to reproduce the bug.[/b]
[b]* The logcat file will be in your home directory.[/b]
* Submit the logcat here on the forums, or on the Telegram group.
* If you can't connect the device through ADB on Windows because of the drivers, connect the device over wifi, enable ADB over Network in developer options, and type:
Code:
adb connect [ip address here]
And then the adb logcat command for windows.
Click to expand...
Click to collapse
[/HIDE]
Also do not under any circumstances post bug reports if you are using substratum themes or unsupported Magisk modules or you have performed any system modifications.
Credits
I would like to everyone who has helped me throughout the whole process of making Q for J5, included but not limited to those people.
Galaxy-MSM8916 team for our base trees.
jenslody, SebaUbuntu, Soft-Bullet, and others for the Q bringup and other contributions!
itexpert.120 (Zeeshan Ahmad) for providing a server for building!
And everyone else who has done even the slightest for the project.
Source Code
Kernel source code: https://github.com/Galaxy-MSM8916/an...amsung_msm8916
ROM Source code: https://github.com/LineageOS
XDA:DevDB Information
LineageOS 18.0 for Galaxy J5 (2015), ROM for the Samsung Galaxy J5
Contributors
Zakaryan2004
ROM OS Version: Android 10
ROM Kernel: Linux 3.10.x
ROM Firmware Required: 6.0 Marshmallow Bootloader/Modem
Based On: LineageOS
Version Information
Status: Testing
Created 2020-11-17
Last Updated 2020-11-17
Reserved
Screenshots
Reserved
As some of you may know, Google has been recently making AOSP build system require more and more RAM, to the point that building with 8GB of RAM is more or less impossible (dirty builds with no changes take 5-6 hours with lots of hacks and modifications). Clean builds take days and sometimes weeks to build. My PC currently has 8GB RAM, and I have used it to build most of my ROMs. I have got a server from itexpert.120 (Zeeshan Ahmad) today, and I am very thankful to him for it, but I would prefer to have a more permanent solution. Building locally is easier for testing, but it is very tedious and time-consuming, so I am planning to upgrade my RAM.
I have never asked for any kind of donations for any of my work before, but right now I think it's time I do so, most probably for the only time. My country is in a bit of a tight situation right now, and I also don't have the 'usual' means of asking for donations (a la PayPal and such). As I am going to buy RAM from Amazon, I have decided to accept donations in form of Amazon.com Gift Cards. I am planning to buy 16GB DDR4 RAM from Amazon, which is currently $59.99 USD. I will be paying the remaining cost myself after the donation. Every amount will help! Remember, the Gift Card needs to be for Amazon.com. If you are interested in donating, please drop a PM on XDA or Telegram (@Zakaryan2004). I will help you through the process if there are any doubts. Thank you so much for reading and understanding.
Thanks for make j5 still alive
Congratulations sir :good:
Congratulations!!!!!!!
Sent from my j5xnlte using XDA Labs
As some of you may know, Google has been recently making AOSP build system require more and more RAM, to the point that building with 8GB of RAM is more or less impossible (dirty builds with no changes take 5-6 hours with lots of hacks and modifications). Clean builds take days and sometimes weeks to build. My PC currently has 8GB RAM, and I have used it to build most of my ROMs. I have got a server from itexpert.120 (Zeeshan Ahmad) today, and I am very thankful to him for it, but I would prefer to have a more permanent solution. Building locally is easier for testing, but it is very tedious and time-consuming, so I am planning to upgrade my RAM.
I have never asked for any kind of donations for any of my work before, but right now I think it's time I do so, most probably for the only time. My country is in a bit of a tight situation right now, and I also don't have the 'usual' means of asking for donations (a la PayPal and such). As I am going to buy RAM from Amazon, I have decided to accept donations in form of Amazon.com Gift Cards. I am planning to buy 16GB DDR4 RAM from Amazon, which is currently $59.99 USD. I will be paying the remaining cost myself after the donation. Every amount will help! Remember, the Gift Card needs to be for Amazon.com. If you are interested in donating, please drop a PM on XDA or Telegram (@Zakaryan2004). I will help you through the process if there are any doubts. Thank you so much for reading and understanding.
Awesome........ Thanks a bunch for your hard work,sir
@Zakaryan2004 Congratulations on making a rom with the latest Android for our dear and beloved j5 2015 thanks for not making him die, keep improving this custom rom and fixing bugs, Thank you so much :highfive:
This ROM is awesome having even close to android 11 is just mindblowing for our beloved device but after installing it I would like to report some problems/ bugs :
1). The battery life is so little with this ROM
2). After logging in to a Google account in the setup and after opening chrome it again asks for login and takes to the same setup but I have found it is okay with play store and YouTube
3). It is also a little bit laggy not severe but little bit
At last I would like to say that the developers are so amazing to put android 11 in this device. God bless you and keep the fantastic work going
I try to root using magisk few times but always fail, am i missing something? My device is SM-J500G thanks for help. I did flash using OrangeFox 10.1
groovybanana21 said:
I try to root using magisk few times but always fail, am i missing something? My device is SM-J500G thanks for help. I did flash using OrangeFox 10.1
Click to expand...
Click to collapse
Typically anything over 20.422 should work. Which magisk package are you using?
groovybanana21 said:
I try to root using magisk few times but always fail, am i missing something? My device is SM-J500G thanks for help. I did flash using OrangeFox 10.1
Click to expand...
Click to collapse
Use Magisk 21, that's the version which will work on Android 11. I have been using Magisk and it works just fine
Zakaryan2004 said:
Use Magisk 21, that's the version which will work on Android 11. I have been using Magisk and it works just fine
Click to expand...
Click to collapse
I see now, thats the prob. I use magisk 20.4(20400)
Thanks a lot for ur time.
---------- Post added at 05:19 PM ---------- Previous post was at 05:17 PM ----------
palmbeach05 said:
Typically anything over 20.422 should work. Which magisk package are you using?
Click to expand...
Click to collapse
I use magisk 20.4(20400), i'll try again. Thanks a lot for ur help
My phone keeps restarting. I am using the galaxy j500h
There is another probl, my simcard can't detected, i did switch to another slot and try to restart few times but still no luck:crying:
It's SM-J500G
Thanks for your help
groovybanana21 said:
There is another probl, my simcard can't detected, i did switch to another slot and try to restart few times but still no luck:crying:
It's SM-J500G
Thanks for your help
Click to expand...
Click to collapse
read:
Zakaryan2004 said:
What doesn't work
* RIL (in-call audio, messaging, data)
* Bluetooth
* GPS (may partially work, not tested)
* Miracast
* VoLTE, this will never work on AOSP as it's not easy to implement Samsung's proprietary implementation.
* Test and report other bugs
Click to expand...
Click to collapse
r0mushii said:
read:
Click to expand...
Click to collapse
I see.. :good:
FYI
Unofficial OpenGapps: https://sourceforge.net/projects/althafvly/files/gapps/
still in testing state...
btw, awesome work man!
thanks for keeping our J5 sound & alive

[ROM][OFFICIAL][cedric][11] LineageOS 18.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"
}
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. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
Instructions:
Download the latest build, recovery image and GApps (if you need them)
Flash the downloaded recovery image via fastboot
Boot to recovery
Format system and perform a factory reset
Reboot to recovery
Flash the latest build
Flash GApps and any other necessary add-ons
What's working:
WiFi
Camera and Camcorder
Bluetooth
NFC
Fingerprint - Oreo firmware required
GPS
OTG
Video Playback
Audio
RIL
VoLTE/VoWiFi
USB tethering/audio
SELinux: Enforcing
Known issues:
You tell me
Downloads:
Official builds: Here
Recovery: Here
Google Apps: Here
Reporting Bugs
All bugs should be reported here: Issue Tracker
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Thanks to:
@GivFNZ for testing my builds
@wiktorek140, @karthick mostwanted, @wh0dat, @KalilDev, @AsD Monio, @GoldeneyeS2, @Steve Mathew Joy and @rajatgupta1998 for their hard work on our device sources
LineageOS team
Changelogs:
Code:
2021-04-08:
Initial build.
Source code:
Common device tree: https://github.com/LineageOS/android_device_motorola_msm8937-common
Device tree: https://github.com/LineageOS/android_device_motorola_cedric
Kernel: https://github.com/LineageOS/android_kernel_motorola_msm8953
Nice, now on xda too
Already flashed build, its the same as in TG ig.
you can compile a completely android version go
rtd4 said:
you can compile a completely android version go
Click to expand...
Click to collapse
There is an A10 Go build on TG by Elite.
家Elite channel家
Android GO A10 📅: 05/04/21 👤: @eliteG5 🧩Cambios: - Optimkernel 356 - optimización autonomía de batería - optimización de rendimiento en general ❌NOTA: está build viene con gapps incluídas. ⚠BUGS: ninguno? ⬇Descarga...
t.me
thank you for your efforts, jarlpenguin - this is much appreciated. will this become an officially supported los-build at some point in the future?
SirRGB said:
There is an A10 Go build on TG by Elite.
家Elite channel家
Android GO A10 📅: 05/04/21 👤: @eliteG5 🧩Cambios: - Optimkernel 356 - optimización autonomía de batería - optimización de rendimiento en general ❌NOTA: está build viene con gapps incluídas. ⚠BUGS: ninguno? ⬇Descarga...
t.me
Click to expand...
Click to collapse
The rom is good but I can't load it off, only the lightning appears
Hi
First, TWRP wiped data from / system and / data partitions Then I installed the image lineage-18.1-20210406-UNOFFICIAL-cedric.zip and Magisk-v22.1.zip Usually, after such an operation, the Android installer starts, and here the system asks me for PIN, when I enter the correct PIN of the previous system, I have a message that the PIN is incorrect.
The phone is locked.
Is there any way to get around this problem via TWRP?
EDIT:
OK,
I formatted / data in TWRP and started the installer.
But I have a problem with the SD card (it was also in LineageOS 17):
cedric / # mount | grep dm-1
/dev/block/dm-1 on /mnt/expand/8be4d77f-6c9d-4b13-bbac-804c592fc0b3 type f2fs (ro,dirsync,seclabel,nosuid,nodev,noatime,background_gc=off,user_xattr,acl,inline_data,extent_cache,active_logs=6)
/dev/block/dm-1 on /data_mirror/data_ce/8be4d77f-6c9d-4b13-bbac-804c592fc0b3 type f2fs (ro,dirsync,seclabel,nosuid,nodev,noatime,background_gc=off,user_xattr,acl,inline_data,extent_cache,active_logs=6)
/dev/block/dm-1 on /data_mirror/data_de/8be4d77f-6c9d-4b13-bbac-804c592fc0b3 type f2fs (ro,dirsync,seclabel,nosuid,nodev,noatime,background_gc=off,user_xattr,acl,inline_data,extent_cache,active_logs=6)
cedric / # mount -o remount,rw /dev/block/dm-1
mount: '/dev/block/dm-1'->'/data_mirror/data_de/8be4d77f-6c9d-4b13-bbac-804c592fc0b3': Invalid argument
cedric / # mount -o remount,rw /mnt/expand/8be4d77f-6c9d-4b13-bbac-804c592fc0b3
mount: '/dev/block/dm-1'->'/mnt/expand/8be4d77f-6c9d-4b13-bbac-804c592fc0b3': Invalid argument
cedric / # mount -o remount,rw /mnt/expand/8be4d77f-6c9d-4b13-bbac-804c592fc0b3
mount: '/dev/block/dm-1'->'/mnt/expand/8be4d77f-6c9d-4b13-bbac-804c592fc0b3': Invalid argument
cedric / #
EDIT 2:
Where is in Lineage-18.1 configurations:
"Developer options > Kill app back button"
Cheers
Does LineageOS 18.1 work fine on the Moto G5? If that is the case, I am considering to install it as well.
Does anyone here know what I can do to avoid Google apps altogether? How can I install a good alternative play store on my device without using the Google Play Store first? Is APKPure a good alternative?
Nemgathos said:
Does LineageOS 18.1 work fine on the Moto G5? If that is the case, I am considering to install it as well.
Does anyone here know what I can do to avoid Google apps altogether? How can I install a good alternative play store on my device without using the Google Play Store first? Is APKPure a good alternative?
Click to expand...
Click to collapse
index - powered by h5ai v0.30.0 (https://larsjung.de/h5ai/)
index - powered by h5ai v0.30.0 (https://larsjung.de/h5ai/)
files.auroraoss.com
No need to sign in. You can also install aurora store via fdroid.
Nemgathos said:
Does LineageOS 18.1 work fine on the Moto G5? If that is the case, I am considering to install it as well.
Does anyone here know what I can do to avoid Google apps altogether? How can I install a good alternative play store on my device without using the Google Play Store first? Is APKPure a good alternative?
Click to expand...
Click to collapse
In my lineage-18.1-20210406-UNOFFICIAL-cedric.zip SELinux blocked Magisk (from image Magisk-v22.1.zip), log:
04-16 22:25:01.406 2794 2821 I ActivityManager: Start proc 5959:com.topjohnwu.magisk/u0a158 for service {com.topjohnwu.magisk/com.topjohnwu.magisk.core.download.DownloadService}
04-16 22:25:01.596 5959 5959 W opjohnwu.magisk: type=1400 audit(0.0:52): avc: denied { read } for uid=10158 name="u:object_r:virtual_ab_prop:s0" dev="tmpfs" ino=343 scontext=u:r:untrusted_app:s0:c158,c256,c512,c768 tcontext=u:object_r:virtual_ab_prop:s0 tclass=file permissive=0 app=com.topjohnwu.magisk
04-16 22:25:01.612 5959 5959 I TetheringManager: registerTetheringEventCallback:com.topjohnwu.magisk
04-16 22:25:01.625 457 511 E vold : Failed to find mounted volume for /storage/emulated/0/Android/data/com.topjohnwu.magisk/files/
04-16 22:25:01.626 5959 5959 W ContextImpl: Failed to ensure /storage/emulated/0/Android/data/com.topjohnwu.magisk/files: android.os.ServiceSpecificException: (code -22)
04-16 22:25:01.629 457 511 E vold : Failed to find mounted volume for /storage/emulated/0/Android/data/com.topjohnwu.magisk/cache/
04-16 22:25:01.630 5959 5959 W ContextImpl: Failed to ensure /storage/emulated/0/Android/data/com.topjohnwu.magisk/cache: android.os.ServiceSpecificException: (code -22)
04-16 22:25:01.634 457 511 E vold : Failed to find mounted volume for /storage/emulated/0/Android/media/com.topjohnwu.magisk/
Also advise you to wait for the new, improved versions of Lineage and Magisk.
I am currently using: lineage-17.1-20210414-microG-cedric.zip
works corrected.
Microg instead of Google-apps.
Instead of Google-play, I use the Aurora Store installed with Fdroid.
Cheers
Hello, I'm glad that my terminal still has life thanks to people like you, I had no problems installing the ROM, although the detail that I can detect is that when making a call I have no return audio or speaker, some idea?, even so many thanks for the support
JarlPenguin said:
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. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
Instructions:
Download the latest build, recovery image and GApps (if you need them)
Flash the downloaded recovery image via fastboot
Boot to recovery
Format system and perform a factory reset
Reboot to recovery
Flash the latest build
Flash GApps and any other necessary add-ons
What's working:
WiFi
Camera and Camcorder
Bluetooth
NFC
Fingerprint - Oreo firmware required
GPS
OTG
Video Playback
Audio
RIL
VoLTE/VoWiFi
USB tethering/audio
SELinux: Enforcing
Known issues:
You tell me
Downloads:
Unofficial build: GitHub
Recovery: GitHub
Google Apps: MindTheGApps
Reporting Bugs
All bugs should be reported here: Issue Tracker
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Thanks to:
@GivFNZ for testing my builds
@wiktorek140, @karthick mostwanted, @wh0dat, @KalilDev, @AsD Monio, @GoldeneyeS2, @Steve Mathew Joy and @rajatgupta1998 for their hard work on our device sources
LineageOS team
Changelogs:
Code:
2021-04-08:
Initial build.
Source code:
Common device tree: https://github.com/moto-msm8937/android_device_motorola_msm8937-common
Device tree: https://github.com/moto-msm8937/android_device_motorola_cedric
Kernel: https://github.com/JarlPenguin/android_kernel_motorola_msm8953
Click to expand...
Click to collapse
Hey Jarl, I know that you like copy-paste, but please modify the credits section to include cedric ones. Soham did the inital bringup, Lemony did testing, etc.
Thank you for this! I've been trying it for a few days now and It is working pretty good, no problems for now.
Jarl, please also update the thread to reflect it's official now.
Is this a 32-bit or 64-bit ROM?
hayaban said:
Is this a 32-bit or 64-bit ROM?
Click to expand...
Click to collapse
It is a 64bit treble compatible rom.
xattus:3 said:
Hello, I'm glad that my terminal still has life thanks to people like you, I had no problems installing the ROM, although the detail that I can detect is that when making a call I have no return audio or speaker, some idea?, even so many thanks for the support
Click to expand...
Click to collapse
I have the same problem
For those that want to know how to fully pass safety net
Install official version of rom from lineage os site
Install bitgapps https://bitgapps.ga/arm64
Install magisk (at time of writing I'm using version 23.0)
Hide magisk with random package name
Enable magisk hide
Install MagiskHide Props Config module
Install Terminal emulator from playstore
In terminal emulator type props then enter
Select option 1
Select option f
Choose Google (option 7)
Choose pixel 4 (option 22)
Choose android version 11 (option 2)
Restart
Official build, wow crazy.
LineageOS Downloads
download.lineageos.org
Hello everyone!
I just updated to the latest version (lineage-18.1-20210624-nightly-cedric-signed.zip - don't remember what before) and get a "Encryption unsuccessful" error.
How can I fix this without formatting or wiping anything?
EDIT: downgrade to 16 or 17 didn't fix it

[UNOFFICIAL] crDroid R Mod //crDRom11

crDroid 7.16
Your warranty is now void!
We're 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​
crDRom 11 is a project which based on crDroid 7.x with @AndyYan's and @phhusson's Treble GSI patches. Built with some Andy's patches & recommendations, also even without "ALLOW_MISSING_DEPENDENCIES=true" flag. And system can run with SELinux enforced state, as original Phh AOSP GSI. Fully compatible with PHH-Treble patches. Has dynamic root which can be activated/deactivated without reboot - 'su' binary and SuperUser app (can works on all devices even with system read-only). Also has dynamic SafetyNet helper (but it compatible not with all devices), users have four ways to pass SafetyNet: a. just enable SafetyNet option (recommended) b. disable SafetyNet and enable "Spoof Pixel 5" then reboot c. enable both options and reboot d. mount system as RW and create empty file /system/phh/secure (legacy method) and in the Recovery do Wipe Data
UPDATE VERSION
base: crDroid 7.16
latest build: 2022.03.30
treble patches: v316
SPL: 5 Mar 2022
FEATURES/CHANGES
see Project page changelog
DOWNLOAD (CLICK H3RE)
vanilla, gapps, go-gapps: all possible architectures
NAMING
Some information you should know about knowing what type of gsi it is
<ARCH>_xyZ
<ARCH> can either be arm, a64 (arm32_binder64) or arm64
x can either be a or b
y can either be v, o, g or f
Z can be N or S
b = a/b
a = a-only
g = gapps
o = gapps-go
v = vanilla (no gapps included)
f = floss (free & open source apps instead gapps)
N = no superuser
S = superuser included
Z = dynamic superuser included
-lite = for VNDK Lite vendors (also can help with broken camera even on normal VNDK vendors)
so in most common example "arm64_avZ" is ARM64 A-only vanilla with dynamic superuser
CONTACTS
> telegram group
> project page
KN0WN BUGS
• excluding fixes, the same as on all R GSI (in some cases doesn't work: broadcasting on TV, calls via BT; offline charging does not work normally; problems with GPS etc etc)
NOTE: always test ROM first without Magisk (with clean boot.img). and don't send me bug reports if you have:
a) Magisk installed
b) modified/custom vendor or kernel
c) dirty flashing rom without wiping data
d) modified props values (another device fingerprint and so on)
CREDITS
persons: @phhusson, @AndyYan
projects: TrebleGSI • BlissROMs • LineageOS • Havoc-OS • PixelExperience • ABC Rom • GrapheneOS • SyberiaOS • ProtonAOSP
#include_one
#include_two
Great stuffs - glad to see these threads coming out. Good - crDroid 7.5
Quite simply the best ROM ever. Lean, fast, no bugs, customizable to the last item.
I might hit 35h SOT on the BV9100 with this, the WP6 is heading for 25h
Thanks for a very battery friendly ROM. Standby battery drain is about 1% during 4 hours (in deep sleep 96%) on my device (a half of the drain of Bless 12.12 on the same device).
Great rom, thank you. Unfortunately wired headphone (3.5mm jack) does not work on my SD660 device.
retora said:
Great rom, thank you. Unfortunately wired headphone (3.5mm jack) does not work on my SD660 device.
Click to expand...
Click to collapse
Phh settings > Misc > Disable audio effects
or Force enable headphone jack
Hi, thanks a lot for the rom. Works fine on Poco X3 Pro. So far have noticed only some small cosmetic issues, like charging info on the lockscreen seems incorrect, although it charges fast, under 2h to full. Widevine is reported as L3 in Netflix, thus only SD playback is available.
{
"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"
}
crDRom R 2021.05.13
download /// changelog
pryggi said:
Hi, thanks a lot for the rom. Works fine on Poco X3 Pro. So far have noticed only some small cosmetic issues, like charging info on the lockscreen seems incorrect, although it charges fast, under 2h to full. Widevine is reported as L3 in Netflix, thus only SD playback is available. View attachment 5301523
Click to expand...
Click to collapse
for Netflix try to find "ro.netflix.bsp_rev" from your stock rom and add this prop to gsi
Hey, thanks for this release! I have been using crDroid 6 on Redmi Note 9 (Merlin) with very few issues. I updated today, but I am getting low fps and small stuttering in the UI. Is there any settings I can check to fix this?
Thanks
Edit: I have tried arm64-bgZ and arm64-bvZ-lite with no change.
UpperCenter said:
Hey, thanks for this release! I have been using crDroid 6 on Redmi Note 9 (Merlin) with very few issues. I updated today, but I am getting low fps and small stuttering in the UI. Is there any settings I can check to fix this?
Thanks
Edit: I have tried arm64-bgZ and arm64-bvZ-lite with no change.
Click to expand...
Click to collapse
hi, yes i guess you need check option Display > Blur (should be disabled) and also try to add in the /system/build.prop new line "debug.sf.latch_unsignaled=1"
say me, which treble base (kernel & vendor) used and if suggestions helped you
eremitein said:
/system/build.prop new line "debug.sf.latch_unsignaled=1"
Click to expand...
Click to collapse
Thanks for your comments, do I need to be root for this? How can I find which treble base I am using?
Edit: I added the line to /system/build.prop, it didn't seem to improve performance. Blur is also disabled.
crDRom R 2021.05.21
download /// changelog
So have a galaxy A705mn and can't mso e or receive phone calls ,is there any way possible for me to rectify this ?
Hi, tell me how to set up a call recording, I can't hear the interlocutor,
guest210 said:
Hi, tell me how to set up a call recording, I can't hear the interlocutor,
Click to expand...
Click to collapse
call recording in vanilla Dialer can rec only from microphone, so you need set volume higher or even enable loud speaker
Hi folks, as you maybe know all my GSI works suspended
Build server damaged and now for maintenance, I haven't information about his further fate
So... I don't know when I can resume my GSI building
By the way, this is not my server, literally I can't do anything to help
I can't even send money, my country is not supported in many payment systems
If you want to help, you can send donations to https://www.paypal.com/paypalme/electrikjesus
(he is the owner of the server, and he long gives me his server - I made a lot of GSI builds on it)
fast,easy and good gsi rom

Categories

Resources