{
"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"
}
WARNING: BETA BUILD. There are numerous issues still.
Disclaimer
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.
Nougat firmware needed for fingerprints to work correctly : https://forum.xda-developers.com/showpost.php?p=79342931&postcount=939
Introduction
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. More info.
These are my UNOFFICIAL builds of LineageOS-16.0 for LG V20 variants. I did NOT create this ROM. I am helping to contribute to this ROM. Thanks to all other coders who contributed to LineageOS.
IMPORTANT
BACKUP! These are UNTESTED builds. Please be ready to recover your previous ROM. If it kernel panic, boots into bootloader, etc... grab as much info as you can.
Builds are done periodically (see download below)
Do NOT be rude.
Respect all users.
Any and all users, please help each other. I have a us996 variant, so other variants might have some issues.
For broken issues see 2nd post
Issues:
us996 static on boot: Unlock bootload from LG, using dirty Santa causes static on boot, will not fix. (Flash the us996-DS version)
WiFi or Bluetooth MAC is "00:00:00:00:00:00" - You wiped the misc partition, you'll need to fix: https://forum.xda-developers.com/showpost.php?p=70474540&postcount=12 (Should be fixed by static hax thanks for @Blaises)
5Ghz tether not working due to "error"
H918 - ARB1 .. flash the 10p version, ARB0..flash the PRE10p. (10p is where the ARB got tripped to 1)
Install
You can upgrade from 15.1 (UNOFFICIAL) to 16.0. If you are not on my UNOFFICIAL yet, flash the to-x86cpu.zip first (and reboot recover before upgrade, not reboot into system).
I would suggest the TWRP from Phoenix591 (See Thanks section below)
Flash to-x86cpu.zip if needed. (See Downloads below)
Flash UNOFFICIAL ROM
Wipe cache, and dalvik cache
Magisk if you choose
Flash GAPPS (I use nano)
Reboot and wait....
(Copied from OFFICIAL thread)
To enable Developer Options go to Settings, About Phone and repeatedly press Build Number.
Bugs
If you encounter issues/bugs that are not known, please report. This is not the OFFICIAL ROM, but I can help to get any issues fixed. I use the us996 variant. If I can replicate your issue then I can track it down. If I cannot, please provide as much detail as possible. Logcats are great.
Please indicate what v20 variant you have (h910, h918/p, ls997 us996, vs995, h990/ds) athe dated version. Any mods (no judgment) as well.
I am aware people run mods or change things. I am not against it (as I do myself). However, if needed I may ask you to data wipe (you can say no), or remove a mod that might be interfering. I will do the best I can.
Thanks
Any and all users in this thread who contributed or will contribute to making this ROM as stable as possible
LineageOS Team
@Rashed97 for continued help
@Omar-Avelar for kernel help along the way
@Blaises for Bluetooth and WiFi static hax if all 00s.
@Phoenix591 for TWRP update that support OTA ( https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239 )
Downloads
ROM: UNOFFICIAL downloads (Note date)
Gapps: arm64 nano 9.0
Sourcesrs/0B51rjK5Hd_P5NmpwY1o4VmlyaUk
https://github.com/LineageOS
https://github.com/LineageOS/android_kernel_lge_msm8996
https://github.com/LineageOS/android_device_lge_msm8996-common
https://github.com/LineageOS/android_device_lge_v20-common
h910
h918
ls997
us996
vs995
h990
UNOFFICIAL downloads
Issues
WARNING: This build is running in permissive mode.
What is working:
Fingerprints (If they are not READ: https://forum.xda-developers.com/showpost.php?p=79342931&postcount=939 )
WiFi
Camera
NFC
Bluetooth ONLY IF you come from an upgraded 15.1 version only.
2.4 Ghz Hotspot
USB OTG
The v20 Second Screen! The upper left area is now a defined notch. This allows for the second screen area to be active now!
What is NOT working:
VoLTE and WiFi calling do not (and most likely never will).
5.0 Ghz Hotspot (still)
Bluetooth will fail if you wipe (clean flash).
NFC
IR
Encrpytion is untested, so it may fail.
Fingerprints will only work until a reboot. You can then enroll again. If you get an error in enrolling, the fpdata is "full", and you will need to do the following as root and reboot. You can then enroll again:
Code:
rm /data/system/users/0/fpdata/user.db
rm /data/system/users/0/settings_fingerprint.xml
Most likely safteynet will fail. This build is in permissive mode, unsure if anything can help to fake it (nor will I try).
Gamma Kernel will not work without updates to it. Camera will definitely break.
Anything else NOT listed above might or might not work. I will adjust as necessary and reports. If anyone has any knowledge and can troubleshoot and fix the NOT working items, let me know.
logcat capture
Here is how I capture logs. You need to ensure you can do this right at boot and will need to setup ahead of time.
You need to have root, either su, or "adb root". Verify you can get root quickly.
Here are the steps I do to accomplish this. This is a Linux system, so windows will vary slightly.
Reboot the phone while plugged into the computer.
At a shell, keep attempting to get root/shell:
Code:
adb root ; adb shell
Once connected, immediately paste the following (to capture logs).
Code:
cd /cache
dmesg -w > dm &
logcat -b all > lc &
If you have root installed via Magisk as "su":
Reboot the phone while plugged into the computer.
At a shell, keep attempting to get root/shell:
Code:
adb shell
Once connected, immediately paste the following (to capture logs).
Code:
su
cd /cache
dmesg -w > dm &
logcat -b all > lc &
Once Phone reboots, or boots up. The needed files are in /cache "lc" and "dm", and are available in TWRP even.
Holy crap x86!
8am here and I was just about to go to bed. Thought I better check the forums one last time and I saw this at the top and my brain went
"No."
Then I clicked and I was like
"YES!"
Well damn done I'll be getting on this for testing ASAP!
Whoa! whaaaaat!
Definitely will try this ASAP.
Out of curiosity tough, so the 2nd scree will be treated as a notch right?
What will happen to the screen on landscape mode? The statusbar will remain on the 2nd screen or moved to the top of screen as usual?
You the real mvp:crying:
So exciting .... I am still thinking what ROM to put on my H990DS - LOS 15.1, RR or rooted stock Oreo, and now - LOS 16 appeared! Amazing!
Thank you. Thank you. Thank you..
Quick & Dirty Testing
Okay, so.
I did a full TWRP backup, flashed the 16.0 build for my H990DS, the openGAPPS AROMA zip for 9.0 (importing all the same options I did when first installing 15.1) and the latest Magisk beta 17.3, following the installation instructions to the letter.
This was a "DIRTY" flash over 15.1 (it's not really dirty when doing it how Lineage does its patching but I digress).
No custom kernel, no Xposed (after flashing the xposed uninstaller). Just the ROM, GAPPS, Magisk and everything my phone already had on it.
I previously had Gamma kernel, Xposed & Magisk.
The device boots (takes about 10 mins the first time) and gets to the lock screen, and after a few seconds it shows "shutting down" when I'm in the middle of entering my PIN, turns off and boots back into recovery.
I flashed the Magisk uninstaller, rebooted and tried again with the same result. I can see on the second screen for a few seconds that WiFi/Cell and Bluetooth are all working, and my watch pops up that it's connected to my V20 before it shuts off.
I'm not willing to completely wipe and test in case something gets wiped that a TWRP backup has missed. Going to try to pull any logs I can and upload them.
Edit: After a few more attemps including a battery pull, it booted and is currently in the system updating apps.
Edit 2: Just did it again while I was taking screenshots. Was in the system for maybe 3-4 minutes. Going to try to install Magisk and get root for logs.
Edit 2.5: Formatted /system and flashed the ROM clean, same issue
Edit 3: @x86cpu I managed to get a couple straight "adb shell dmesg" in between the device booting to the lock-screen and the shut-down occuring. I also got a kmsg from TWRP in case it's of any use. There's a lot of failures for stuff to opening and in the dmesg logs you can see where the shutdown occurs so maybe you'll be able to tell what's causing it.
Logs are here and I'm going to revert to my 15.1 setup backup for now.
I hope this helps! Do let me know if you need me to do the process again and manually pull any specific log files using TWRP.
Up and running on h918p clean flash from RR
How to enable swipe gestures?
Got this on my H910 version and its working really good so far.. You're a BEAST
Redline said:
Okay, so.
I did a full TWRP backup, flashed the 16.0 build for my H990DS, the openGAPPS AROMA zip for 9.0 (importing all the same options I did when first installing 15.1) and the latest Magisk beta 17.3, following the installation instructions to the letter.
This was a "DIRTY" flash over 15.1 (it's not really dirty when doing it how Lineage does its patching but I digress).
No custom kernel, no Xposed (after flashing the xposed uninstaller). Just the ROM, GAPPS, Magisk and everything my phone already had on it.
I previously had Gamma kernel, Xposed & Magisk.
The device boots (takes about 10 mins the first time) and gets to the lock screen, and after a few seconds it shows "shutting down" when I'm in the middle of entering my PIN, turns off and boots back into recovery.
I flashed the Magisk uninstaller, rebooted and tried again with the same result. I can see on the second screen for a few seconds that WiFi/Cell and Bluetooth are all working, and my watch pops up that it's connected to my V20 before it shuts off.
I'm not willing to completely wipe and test in case something gets wiped that a TWRP backup has missed. Going to try to pull any logs I can and upload them.
Edit: After a few more attemps including a battery pull, it booted and is currently in the system updating apps.
Edit 2: Just did it again while I was taking screenshots. Was in the system for maybe 3-4 minutes. Going to try to install Magisk and get root for logs.
Edit 2.5: Formatted /system and flashed the ROM clean, same issue
Edit 3: @x86cpu I managed to get a couple straight "adb shell dmesg" in between the device booting to the lock-screen and the shut-down occuring. I also got a kmsg from TWRP in case it's of any use. There's a lot of failures for stuff to opening and in the dmesg logs you can see where the shutdown occurs so maybe you'll be able to tell what's causing it.
Logs are here and I'm going to revert to my 15.1 setup backup for now.
I hope this helps! Do let me know if you need me to do the process again and manually pull any specific log files using TWRP.
Click to expand...
Click to collapse
I checked logs, nothing out of the ordinary (for this beta build), most failures are ok. Obviously, something caused the shutdown. I had the same issue initially on my us996, but did get past it. I'm guessing something with the H990 is causing it, which might be the dual sim.
If you want to enable the loggy.sh, you need to remount system rw, then edit /vendor/bin/loggy.sh an uncomment the two logcat and dmesg lines. It'll then catch a dmesg and full logcat from boot. Those might help more so.
In twrp even...
mount /system
vi /system/vendor/bin/loggy.sh (You'll need to understand vi at this point).
It should look like this: (right now the logcat and dmesg are commented out).
Code:
#!/system/bin/sh
# loggy.sh.
#_date=`date +%F_%H-%M-%S`
logcat -b all -f /cache/logcat_${_date}.txt &
dmesg -w > /cache/kmsg_${_date}.txt &
Save..
umount /system
Then after boot check for the files in /cache in TWRP.
Are IR blaster/fm radio tested? and are there areas where lineage os 16 adds to 15.1 in terms of non-stock features?
aminjomaa13 said:
Are IR blaster/fm radio tested? and are there areas where lineage os 16 adds to 15.1 in terms of non-stock features?
Click to expand...
Click to collapse
This is a Beta build. I would imagine that FM tuner and IR blasters are not working yey
ki11aprime said:
Up and running on h918p clean flash from RR
How to enable swipe gestures?
Click to expand...
Click to collapse
It's under System -> Gestures.
So I flashed onto my H918-10p, was encrypted under 15.1 previously. Wasn't able to get past the password initially, just kept rebooting into recovery like Redline, and once I did it seems it also corrupted my data, I got a warning about my password being correct but the data being corrupt, and was prompted to reset my phone. I tried just about everything, but had to format my data and clear the encryption, as even TWRP was no longer able to mount system (unknown error 150). Reflashed after formatting, and now up and running, currently charging my phone to try and encrypt again. Can't thank you enough for getting this ROM out so quick, this is awesome!
Edit: Tried encrypting, unfortunately it failed. Rebooted to recovery while encrypting, and then had to reformat and reflash.
Wonderful! can't believe you got LineageOS 16 on beta this soon, great job.
Will flashing this ROM after being on stock Oreo breaks fingerprint scanner just how LineageOS 15.1 does it? or is it fine? if it does the same I should flash Stock nougat first before flashing this one.
x86cpu said:
I checked logs, nothing out of the ordinary (for this beta build), most failures are ok. Obviously, something caused the shutdown. I had the same issue initially on my us996, but did get past it. I'm guessing something with the H990 is causing it, which might be the dual sim.
If you want to enable the loggy.sh, you need to remount system rw, then edit /vendor/bin/loggy.sh an uncomment the two logcat and dmesg lines. It'll then catch a dmesg and full logcat from boot. Those might help more so.
In twrp even...
mount /system
vi /system/vendor/bin/loggy.sh (You'll need to understand vi at this point).
It should look like this: (right now the logcat and dmesg are commented out).
Code:
#!/system/bin/sh
# loggy.sh.
#_date=`date +%F_%H-%M-%S`
logcat -b all -f /cache/logcat_${_date}.txt &
dmesg -w > /cache/kmsg_${_date}.txt &
Save..
umount /system
Then after boot check for the files in /cache in TWRP.
Click to expand...
Click to collapse
Sounds exactly like Rescue Party.
Everything is working well. Had to use kernel adiutor for the screen retention. Phone was pretty hot so that didn't help. Anyways
It's working amazing so thank you I'll update with any bugs if I find any.
Update: SELinux is not enforcing, and I don't think I can use privacy guard without it. We don't have exposed so I can't use xprivacyula so anyone got any help on how to fix it?
Update 2: fingerprint issue is there but deletes itself completely after a reboot but isn't an issue that much, don't mind it.
Also, ambient display isn't working. On the up side it's basically stable enough to use as a daily driver and I plan to. So happy with this, just need a new screen now
Also the brightness slider could use some work. Doesn't turn up the brightness till about half way up
---------- Post added at 01:57 AM ---------- Previous post was at 01:54 AM ----------
aminjomaa13 said:
Are IR blaster/fm radio tested? and are there areas where lineage os 16 adds to 15.1 in terms of non-stock features?
Click to expand...
Click to collapse
The ir scanner works in gamma. I doubt the fm radio will ever work unless some dev can work it
Grin59 said:
Had to use kernel adiutor for the screen retention. Phone was pretty hot so that didn't help.
Click to expand...
Click to collapse
Doesn't it have the RGB sliders in the display settings like previous LineageOS versions?
Grin59 said:
Update: SELinux is not enforcing
Click to expand...
Click to collapse
That's what permissive mode is
Related
{
"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"
}
Disclaimer
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.
Introduction
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. More info.
These are my UNOFFICIAL builds of LineageOS-17.1 for LG V20 variants. I did NOT create this ROM. I am helping to contribute to this ROM. Thanks to all other coders who contributed to LineageOS.
IMPORTANT
BACKUP! These are UNTESTED builds. Please be ready to recover your previous ROM. If it kernel panic, boots into bootloader, etc... grab as much info as you can.
Builds are done periodically (see download below)
Do NOT be rude.
Respect all users.
Any and all users, please help each other. I have a us996 variant, so other variants might have some issues.
This now runs System-As-Root. Ie.. / and /system are merged, so /system is really /, and /system is /system/system.
There are currently no gapps yet for lineage-17.0. So Google GSM apps are pre-installed in this. Once they are available, I will discontinue adding them.
For broken issues see 2nd post
Issues:
us996 static on boot: Unlock bootload from LG, using dirty santa causes static on boot, will not fix. (Flash the us996-DS version)
WiFi or Bluetooth MAC is "00:00:00:00:00:00" - You wiped the misc partition, you'll need to fix: https://forum.xda-developers.com/showpost.php?p=70474540&postcount=12 (Should be fixed by static hax thanks for @Blaises)
5Ghz tether not working due to "error"
H918 - ARB1 .. flash the 10p version, ARB0..flash the PRE10p. (10p is where the ARB got tripped to 1)
Install
You can upgrade from 15.1 (UNOFFICIAL) to 16.0 to 17.1. If you are not on my UNOFFICIAL yet, flash the to-x86cpu.zip first (and reboot recovery before upgrade, not reboot into system).
You cannot upgrade from lineage-17.0 to lineage-17.1
I would suggest the TWRP from Phoenix591 (See Thanks section below)
Due to system-as-root, TWRP might indicate no o/s installed. I tested rebooting into recovery before flashing the two tested Gapps.
Flash to-x86cpu.zip if needed. (See Downloads below)
Flash UNOFFICIAL ROM
Wipe cache, and dalvik cache
Magisk if you choose
Flash GAPPS (I use nano)
FlameGapps (I tested Basic)
Reboot and wait....
Bugs
If you encounter issues/bugs that are not known, please report. This is not the OFFICIAL ROM, but I can help to get any issues fixed. I use the us996 variant. If I can replicate your issue then I can track it down. If I cannot, please provide as much detail as possible. Logcats are great.
Please indicate what v20 variant you have (h910, h918/p, ls997 us996, vs995, h990/ds) and the dated version. Any mods (no judgment) as well.
I am aware people run mods or change things. I am not against it (as I do myself). However, if needed I may ask you to data wipe (you can say no), or remove a mod that might be interfering. I will do the best I can.
Thanks
Any and all users in this thread who contributed or will contribute to making this ROM as stable as possible
LineageOS Team
@Rashed97 for continuing
@Blaises[/MENTION] for Bluetooth and WiFi static hax if all 00s.
@Phoenix591 for TWRP update that support OTA ( https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239 )
@npjohnson for help along the way.
Downloads
ROM: UNOFFICIAL downloads (Note date)
Gapps: arm64 nano 10.0
FlameGapps (I tested Basic)
Sources
https://github.com/LineageOS
https://github.com/LineageOS/android_kernel_lge_msm8996
https://github.com/LineageOS/android_device_lge_msm8996-common
https://github.com/LineageOS/android_device_lge_v20-common
h910
h918
ls997
us996
vs995
h990
What is working:
WiFi
Camera
GPS
NFC
2.4 Ghz Hotspot
USB OTG
The v20 Second Screen! The upper left area is now a defined notch. This allows for the second screen area to be active now!
What is NOT working:
VoLTE and WiFi calling do not (and most likely never will).
5.0 Ghz Hotspot
Encrpytion is untested, so it may fail.
Unsure if Gamma Kernel will not work.
Anything else NOT listed above might or might not work. I will adjust as necessary and reports. If anyone has any knowledge and can troubleshoot and fix the NOT working items, let me know.
logs
Here is how I capture logs. You need to ensure you can do this right at boot and will need to setup ahead of time.
You need to have root, either su, or "adb root". Verify you can get root quickly.
Here are the steps I do to accomplish this. This is a Linux system, so windows will vary slightly.
Reboot the phone while plugged into the computer.
At a shell, keep attempting to get root/shell:
Code:
adb root ; adb shell
Once connected, immediately paste the following (to capture logs).
Code:
cd /cache
nohup dmesg -w > dm &
nohup logcat -b all > lc &
If you have root installed via Magisk as "su":
Reboot the phone while plugged into the computer.
At a shell, keep attempting to get root/shell:
Code:
adb shell
Once connected, immediately paste the following (to capture logs).
Code:
su
cd /cache
nohup dmesg -w > dm &
nohup logcat -b all > lc &
Once Phone reboots, or boots up. The needed files are in /cache "lc" and "dm", and are available in TWRP even.
I have not had the time to fully test things. So please report back what might not be working correctly.
Thats great, thank you for builds. Its awasome. I waited lg g5 h850 los17 :victory:
Arda Süzen said:
Thats great, thank you for builds. Its awasome. I waited lg g5 h850 los17 :victory:
Click to expand...
Click to collapse
Those are next, haven't had a chance yet.
x86cpu said:
Those are next, haven't had a chance yet.
Click to expand...
Click to collapse
H918: 17 dirty flash over latest 16. Happy to report only minor issue with 17. Battery indicator on status bar won't show circle. I told you it was minor.
Please give 17 at least 12 hours to settle down after upgrade.
Thanks for this!!
scottyrick said:
H918: 17 dirty flash over latest 16. Happy to report only minor issue with 17. Battery indicator on status bar won't show circle. I told you it was minor.
Please give 17 at least 12 hours to settle down after upgrade.
Thanks for this!!
Click to expand...
Click to collapse
There are things in LineageOS that have not yet been completed. Battery circle is one of them. Once Lineage completes that part it will show up in a later build. There could be some others too. Gapps still does not have a release that can be used yet.
First I thanks @x86cpu for giving us the latest Android Rom lineage 17, I have a bug when calling. It's just with speaker mode and couldn't disable speaker mode.
Thank you so much @x86cpu !! I dind't see this coming!
I dirty flashed over LOS 16.1, everything works fine so far. I can confirm Gamma Kernel V13 can boot. But I can't confirm whether it's problematic or not, still testing.
Also, if I were to clean install from stock Nougat, can I skip flashing LOS 16.1 (LOS 15 then directly flash LOS 17)?
Thank you so much @x86cpu your work is greatly appreciated
If anyone needs an app store I strongly recommend Aurora, it's a FOSS play store client.
---------- Post added at 10:05 PM ---------- Previous post was at 10:02 PM ----------
sajadzare said:
First I thanks @x86cpu for giving us the latest Android Rom lineage 17, I have a bug when calling. It's just with speaker mode and couldn't disable speaker mode.
Click to expand...
Click to collapse
If you can, get a logcat, it'll show exactly what's wrong and x86cpu can fix it easily
Currently testing, clean flash with gamma v13 boots up. It can be really smooth but also really laggy. Brightness slider works like it should be mostly, but lags.
I don't know for sure if 90hz is actually enabled, I can't really see it, with gamma v13 but lineage 17 is being super smooth sometimes, like with the nav bar swiping up
I tried to install magisk, but the phone doesn't boot it just get a error screen, anyone knows how to root this rom.
Thanks
VS995 Boot Loop
VS995: I dirty flashed over LOS16. The phone boot looped into recovery on reboot. I then tried a factory wipe and a fresh install. The phone reboots and starts the setup. During the setup the phone app force closes, the phone reboots into recovery and is boot looped to recovery. Anyone having luck with the VS995? I will get logs if needed.
VoLTE and WiFi calling do not (and most likely never will).
What actually prevents this from working? I know I read something about the way LG implemented it but I can't seem to find that information now.
TripOG said:
VoLTE and WiFi calling do not (and most likely never will).
What actually prevents this from working? I know I read something about the way LG implemented it but I can't seem to find that information now.
Click to expand...
Click to collapse
They need to be remade from scratch since LG is using proprietary code. This also applies to the fm radio
@x86cpu Thanks for bringing LOS17 to the V20. I am a former v20 user. Was just passing through
A couple of general tips on los17(have been using it for some time on my v30):-
There are serveral gapps for Android 10: I like https://nikgapps.github.io/ the best. Opengapps test builds are on sourceforge(a big buggy), others like bitgapps, exlite gapps also exist for Q.
Older magisk version like 19.1, 19.3 etc. cause bootloop on los17, I recommend Magisk 20.1
Again thanks for maintaining LOS for v20, I enjoyed it a lot when I had the v20.
Audio devices aren't working. Bluetooth connects (active, batterylevel) but the audio plays through the device's speaker and 3.5mm devices aren't detected.
Occurs with both stock and Gamma kernel,
I dirty flashed 17 over 16
H990DS
x86cpu said:
Disclaimer
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.
Introduction
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. More info.
These are my UNOFFICIAL builds of LineageOS-17.0 for LG V20 variants. I did NOT create this ROM. I am helping to contribute to this ROM. Thanks to all other coders who contributed to LineageOS.
IMPORTANT
BACKUP! These are UNTESTED builds. Please be ready to recover your previous ROM. If it kernel panic, boots into bootloader, etc... grab as much info as you can.
Builds are done periodically (see download below)
Do NOT be rude.
Respect all users.
Any and all users, please help each other. I have a us996 variant, so other variants might have some issues.
This now runs System-As-Root. Ie.. / and /system are merged, so /system is really /, and /system is /system/system.
There are currently no gapps yet for lineage-17.0. So Google GSM apps are pre-installed in this. Once they are available, I will discontinue adding them.
For broken issues see 2nd post
Issues:
us996 static on boot: Unlock bootload from LG, using dirty santa causes static on boot, will not fix. (Flash the us996-DS version)
WiFi or Bluetooth MAC is "00:00:00:00:00:00" - You wiped the misc partition, you'll need to fix: https://forum.xda-developers.com/showpost.php?p=70474540&postcount=12 (Should be fixed by static hax thanks for @Blaises)
5Ghz tether not working due to "error"
H918 - ARB1 .. flash the 10p version, ARB0..flash the PRE10p. (10p is where the ARB got tripped to 1)
Install
You can upgrade from 15.1 (UNOFFICIAL) to 16.0 to 17.0. If you are not on my UNOFFICIAL yet, flash the to-x86cpu.zip first (and reboot recover before upgrade, not reboot into system).
I would suggest the TWRP from Phoenix591 (See Thanks section below)
Flash to-x86cpu.zip if needed. (See Downloads below)
Flash UNOFFICIAL ROM
Wipe cache, and dalvik cache
Magisk if you choose
Flash GAPPS (I use nano) (see above)
Reboot and wait....
Bugs
If you encounter issues/bugs that are not known, please report. This is not the OFFICIAL ROM, but I can help to get any issues fixed. I use the us996 variant. If I can replicate your issue then I can track it down. If I cannot, please provide as much detail as possible. Logcats are great.
Please indicate what v20 variant you have (h910, h918/p, ls997 us996, vs995, h990/ds) athe dated version. Any mods (no judgment) as well.
I am aware people run mods or change things. I am not against it (as I do myself). However, if needed I may ask you to data wipe (you can say no), or remove a mod that might be interfering. I will do the best I can.
Thanks
Any and all users in this thread who contributed or will contribute to making this ROM as stable as possible
LineageOS Team
@@Rashed97 for continuing
@Blaises[/MENTION] for Bluetooth and WiFi static hax if all 00s.
@@Phoenix591 for TWRP update that support OTA ( https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239 )
@@npjohnson for help along the way.
Downloads
ROM: UNOFFICIAL downloads (Note date)
Gapps: arm64 nano 10.0
Sources
https://github.com/LineageOS
https://github.com/LineageOS/android_kernel_lge_msm8996
https://github.com/LineageOS/android_device_lge_msm8996-common
https://github.com/LineageOS/android_device_lge_v20-common
h910
h918
ls997
us996
vs995
h990
Click to expand...
Click to collapse
OMG thank you so much!!
Grin59 said:
They need to be remade from scratch since LG is using proprietary code. This also applies to the fm radio
Click to expand...
Click to collapse
This is so disappointing, I know it's not a big deal for most people but those are some pretty big features especially with the looming shutdown of 3G. Is it the same way on newer LG phones?
{
"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"
}
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.
Click to expand...
Click to collapse
Features
FlokoROM v4 is based on crDroid 7.x , but there are some differences.
Floko-specific features:
OmniSwitch included
Trebuchet as a default Home Launcher
Bromite as a default Web Browser
Kawaii Easter Egg in Floko Settings
Remove Music Player (install what you like)
Remove Navbar design customization
Remove non-free LongScreenshot
Remove non-free FaceUnlock feature
Remove non-free font packages
crDroid and LineageOS features:
Battery bar
Lockscreen customization
Navigation bar customization
Network traffic monitor
QS columns
QS/Notifications opacity
Screenshot quality
Statusbar Quick/Smart pulldown
Style(Theming)
Switch 4G/LTE icon
Volume panel customization
VoLTE icon customization (if available on your device)
Known Issues
When the phone is powered off from Lineage and the battery is not removed, the battery charge will fall at an approximate rate of 2% per hour of time that the phone is powered off without the battery having been removed since it was powered off. This does not occcur when powering off from TWRP, having first powered up to TWRP or rebooted to TWRP from Lineage. It also does not occur if the battery is removed from the phone before being put back in, either after powering off from Lineage or being pulled out while Lineage is running. This bug has affected the apq8084 chipset since Oreo (as described by the S5 Plus community, which uses the same chipset). However, the S5 Plus had received official lineage-15.1 and 16.0 support despite being affected by this bug. Furthermore, we have deduced that it must be caused by one or more of the 652 commits that separate the Nougat and Oreo kernel branches. We will never have the time to go through each and every one of these commits to fix this bug outright, but we are always open to suggestions.
If NFC is turned off when the phone is booted up, the NFC toggle will freeze in the "off" position and remain off until the phone is rebooted. If NFC is turned on when the phone is booted up, the NFC toggle will function properly to turn NFC both on and off. However, if NFC is turned off and the phone is rebooted, this bug will reappear.
The 2nd SIM slot does not work in any trlteduos variant.
VoLTE is not supported, and will not be supported for the foreseeable future.
If you encountered other issues, please tell me
How to Install
MAKE A BACKUP OF ALL YOUR DATA.
(First time) Wipe Data, Cache, Dalvik
Flash ROM, GApps, Magisk(optional), ...
Reboot to System
Enjoy.
Thanks
love. respect. and love.
crDroid
LineageOS
OmniROM
Team
@1indwurm
Credits
ripee
Inkypen
IogosA
ghostwheel
ananjaser1211
khalvat
triplLr
lindwurm
Flominator
Downloads
FlokoROM Initial Release:
- SM-N910F/G/P/R4/T/T3/V/W8: trlte
- SM-N9100ZC/ZH/6W/9W: trlteduos (experimental)
- SM-N915F/G/P/R4/T/W8: tblte
FlokoROM September release:
- SM-N910F/G/P/R4/T/T3/V/W8: trlte
- SM-N9100ZC/ZH/6W/9W: trlteduos (experimental)
- SM-N915F/G/P/R4/T/W8: tblte
Changelog:
- fixed lag on bromite in certain videos
- fixed cpu performence settings
- selinux is enforced
- updated security patches
Reporting Bugs
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.
Source Codes
FlokoROM: github.com/FlokoROM
Device tree: apq8084
XDA: DevDB Information
FlokoROM v4, ROM for Samsung Galaxy Note 4
Contributors
Flominator, ripee, Inkypen, logosA, ghostwheel, ananjaser1211, khalvat, tripLr
ROM OS Version: Android 11
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock Marshmallow for your variant.
Version Information
Status: Beta
Current Stable Version: 11
Stable Release Date: 2021-06-04
Created 2021-06-04
Last Updated 2021-09-13
are u sure N9100 is a tblte and N915 is trlteduos ? not swapped ?
boy_venz21 said:
are u sure N9100 is a tblte and N915 is trlteduos ? not swapped ?
Click to expand...
Click to collapse
thanks for notice fixed now
Good job!
FlokoROM + BiTGApps
based on Android 11 (Lineage OS 18) (crDroid 7). Feels stable after 2 days' use. Does not crash.
SIM works.
fingerprint sensor (swipe) works.
Bank app works.
Have not tried installing Magisk. It is because the Bank app already works and I don't want to mess up.
crDroid 6.12 + opengapps
based on Android 10 (Lineage OS 17). Crash from time to time.
Sometimes the SIM card is not detected, and restart / reboot is needed.
fingerprint sensor does not work.
Bank app does not work. I have tried everything at Magisk.
Magisk can be installed (flash zip file).
Hope you like the above comparison. SM-N9100. TWRP 3.5.2. By the way, the 2nd SIM card slot not tested. GPS tested, but does not work. Google location service (Wifi) works
ROM RUNS VERY SMOOTH, I THINK THAT HAVE A BIT BETTER THAN CRDRID ROM 7.6, WELCOM TO DISCUSS TI IN HERE.
Best ROM I've ever used on this device. Bar none. Even better and more stable than the ROM it's based on (crDroid). So, hats off to you.
The problem I've had with it, however, is that there are a few apps that aren't allowed to function the way they are supposed to. These apps do function properly on crDroid 7.6, therefore it must be because of the adjustments made to that ROM.
The problems I've had are with apps that are supposed to have access to the system or root folders and are not afforded FULL access. I've noticed this with all the file managers I've used. But, my primary file managers are MiXplorer and X-plore.
I've been able to rename files in the system or root areas, but not copy anything to those areas. And, yes, I have given these programs all the permissions they have asked for (and then some). And I have uninstalled them, then reinstalled. Still, they don't function properly. MiXplorer doesn't even save it settings connsistantly (even though it did on crDroid 7.6). You make adjustments in settings and exit the program and immediately restart ... it may keep those settings changes on that restart, but after awhile, once you restart the program, sometime later it, reverts back to factory default settings. Strange. Never seen that before.
This also seems to be why a program like Elixr 2 does not function as intended (even though it does on crDroid 7.6). I can save a backup in the program, however, even though I can copy a backup of my older custom backup widgets, etc., to the programs backup location (something I've done for years - across multiple ROMS - and with crDroid 7.6), once you try to restore from backup it says "No permission to use this feature". Never see that before.
So, I appreciate all your work. I just hope this is a kink you can figure out and get adjusted.
Thanks, a lot!
This ROM looks great, thank you for making it. Been on crDroid 6.12 for quite a while and been very happy with it but need to update.
Does this ROM have signature spoofing built in? I want to run microG. Root with magisk no problem? Will wait for confirmation before I install.
BTW super cool to include OmniSwitch, by far my fave recents/switcher.
Apex Predator said:
This ROM looks great, thank you for making it. Been on crDroid 6.12 for quite a while and been very happy with it but need to update.
Does this ROM have signature spoofing built in? I want to run microG. Root with magisk no problem? Will wait for confirmation before I install.
BTW super cool to include OmniSwitch, by far my fave recents/switcher.
Click to expand...
Click to collapse
hello, In ternms of signature spoofing its the same as lineage 18.1. I personaly at testing had no problems with root espacialy magisk and micro G. Issues with read write in root I cant confirm.
It seems that trlteduos has a problem, how to fix this?
"assert failed: run_program("/tmp/install/bin/variant_blobs.sh")==0"
Do you have any other Android 11 ROMs for trlteduos?
VerdghXeljior said:
It seems that trlteduos has a problem, how to fix this?
"assert failed: run_program("/tmp/install/bin/variant_blobs.sh")==0"
Click to expand...
Click to collapse
seems to be an common issue with trlte duos roms. Idk why. Any help is welcome.
This is the first Snapdragon ROM on my N910V (Verizon model) that HAS NOT brought up the Maintenance Mode upon reboot. I've rebooted probably 50 times and haven't seen it even once!
This ROM seems to work very well on that device, but I have dropped Wifi a few times. No cellular card in this one, so can't verify that feature.
Since I mainly use these devices for watching TV and videos, I'd like to get Dolby working, or even viper, but no luck so far.
UPDATE: After 1 week, the wifi just stopped working. It just won't start, but everything else seems fine. I was able to install Dolby Atmos eventually and it works now, but without Wifi, it's useless to me. I reverted back to an Android 10 ROM and it's functioning just fine now, proving its not the device.
Tried this ROM. What i noticed is that the CPU speed never dips below 1958Mhz, and it never goes into deep sleep.
Other than that i've had no issues with this ROM. Used it in my spare phone without a SIM so it didn't get that thorough of a workout.
lowfatmilk said:
Tried this ROM. What i noticed is that the CPU speed never dips below 1958Mhz, and it never goes into deep sleep.
Other than that i've had no issues with this ROM. Used it in my spare phone without a SIM so it didn't get that thorough of a workout.
Click to expand...
Click to collapse
hi, this is intendet to get decent performence, to change that, use performence settings in the battery section.
Yeah, tried that. Doesn't seem to let me lower the base CPU speed below 1958Mhz tho.
I must be missing something.
-- Phone runs a little warm with the CPU set up like this, but it certainly is more fluid than it used to be.
any updates to floko or cr
hi everyone i have samsung note 4 910f and i flash many rom including this floko and cr, mostly of them work fine for few days, then i got random freeze from Ui, application start to not open, till some time the phone completely shutdown and i need the remove the battery.
i bought a brand new battery for see if the problem are the same, but nothing change, i roll back to the stock rom, and after few time the problem come back.
all my flashing are with the latest twrp except for the stock i use odin, in the twrp i use to wipe all of them (dalvik/ art cache, system , data, cache, internal storage). may i do something wrong? it is normal to have baseband and bootloader from the old stock samsung firmware (see attach file)
thanks in advance and sorry for my english
boss472 said:
hi everyone i have samsung note 4 910f and i flash many rom including this floko and cr, mostly of them work fine for few days, then i got random freeze from Ui, application start to not open, till some time the phone completely shutdown and i need the remove the battery.
i bought a brand new battery for see if the problem are the same, but nothing change, i roll back to the stock rom, and after few time the problem come back.
all my flashing are with the latest twrp except for the stock i use odin, in the twrp i use to wipe all of them (dalvik/ art cache, system , data, cache, internal storage). may i do something wrong? it is normal to have baseband and bootloader from the old stock samsung firmware (see attach file)
thanks in advance and sorry for my english
Click to expand...
Click to collapse
pls, try to log errors. you can is matlog for example, this my give you a hint whats wrong with your phone
{
"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 LineageOS:
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (pie), 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.
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
Features
Check out all the great stuff of LineageOS here
My builds are signed by a custom key for better security
F-Droid + priv ext + a bunch of additional repos included
AuroraStore included
My builds come with full OTA update support
... you know that thing which informs you that a new update is there and where you just click to download + install
Known issues
Keep in mind that this is brand new stuff so it may (still) contain unknown issues!
So back up regularly and frequently!
LineageOS Camera does not work -> install "Open Camera". I am NOT working on a fix sorry.
Open Camera does work but only for photo, i.e. video recording fails. I am NOT working on a fix sorry.
Bluetooth might crash/stop working when enable + disable afterwards (reboot to fix that)
If you find a bug not listed let me know and SHARE LOGS! -> READ FAQ#1 for how to provide proper logs.
Requirements
Latest TWRP or SHRP (recommended) build.
Do a full (i.e. Nandroid) backup before doing anything!
Samsung STOCK firmware should be on T285XXU0AQH1.
You can check your current firmware version in Android -> settings -> About / Phone info -> Baseband version
If you like try first without flashing this firmware but if you encounter any issues upgrade to this version first before reporting
Fast and (afaik) good site for downloading: https://sfirmware.com/samsung-sm-t285/
(scroll down and type T285XXU0AQH1 in the search box, choose the one for your country, download, flash as usual, flash TWRP/SHRP again, flash this ROM)
Installation
Full clean install as described here (FAQ #2) is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
Flash the ROM
Optional (if you want root): Flash Magisk
Optional (if you want to use google stuff): Flash GApps (ARM, 7.1)
Boot it (will take a bit on first boot!!! be patient!)
Enjoy
Download
Get your build from my leech server (new installs or re-installs)
https://leech.binbash.rocks:8008/lineage/nougat/gtexslte/
If you have a previous version of my(!) /e/ ROM installed already and just want to update to a newer release:
Android settings -> Updater (yes my builds have built-in OTA support!)
Note:
Builds are updated as soon as possible. There is no build cycle.
Information pertaining to your device is displayed accordingly.
The current build is the latest for your device.
Changelogs
Join my Telegram groups (see "Support" topic)
Support
Of course in this thread but also by Telegram.
I have created a generic group for all stuff around Android : here
and another one if you want to keep up2date whenever I build something (TWRP, SHRP, LOS, /e/, ...): here
Credits
jedld, really he did a great job and making this project possible at first!
LineageOS team, devs, contributors
and all I forgot to mention ....!
Sources
build manifest
Frequently Asked Questions (FAQ)
Q #01: I want to report an issue. What is the proper way to do so?
I'm glad that you are asking: before doing so check the KNOWN ISSUES topic in the OP and ofc the other FAQ's listed here!
If you encountered a kernel panic follow FAQ #6 in this post instead.
If you have issues with "just" the boot process follow FAQ #7 for a very easy way to grab the boot logs.
if you have an audio issue follow FAQ #10 instead.
If your issue is not listed there click here to proceed:
If your issue is not listed there follow the directions here briefly and I may can fix it.
Often selinux can cause issues so try that at very first:
Code:
adb shell
su
(or "adb root" when enabled in developer settings)
setenforce permissive
Try again and if the issue is gone when in permissive mode: provide me a logcat as described here -> on step 3 I need the SELINUX log (option D)
If that does not solve your issue follow the logcat GUIDE to provide a valid log depending on what your issue is.
Ensure you have done a full CLEAN install before doing so (refer to FAQ #2 for what that means).
Warning: NO SUPPORT when:
- magisk is installed (known to cause issues sometimes - regardless of the ROM or version)
- Xposed is installed (known to cause issues sometimes - regardless of the ROM or version)
If you have installed any of these UNINSTALL or better do a FULL CLEAN install (see FAQ #2) before doing anything else. Often enough these above causes several issues like battery draining, problems on booting and much more. Even when they may work properly you should re-produce your issue without them first and follow the above to grab the log.
Magisk is a great piece of software and besides that it is Open Source which SuperSu never was.
I just saying I do not "support" issues with LOS when you have Magisk installed. Why? It is (like Xposed) extendable with modules (made by whoever) and those can cause billions of issues.
Other then that magisk was sometimes the reason for battery drain etc. Magisk modifies the boot "process" and sits very deep in the system (which is needed to make it work ofc) but that has the potential to make a system/ROM unstable or result in strange behaviors.
so in order to support a specific issue I have to be sure the ROM is in a "clean" state, no magisk, no xposed. The LOS root-addon is tested with LOS and made for it so that is not an issue but for the rest there are so many things which can going wrong..
Q #02: I want to install clean, how? What is a clean install? What is the recommended way to flash a new ROM version?
A clean install ensures that there are no leftovers from any previous install. One can say that there are 2 phases of a clean flash:
1) regular
2) full - when you (still) encounter issues
Usually the regular one is fully ok when flashing a new ROM version but if you encounter strange issues nobody else is reporting or if a release post is recommending it you should do a full clean install instead.
A regular clean install can be done like this:
WIPE -> Advanced -> select: System + Cache
Flash the ROM
reflash root addon/magisk if you want root
reflash opengapps if you want to use Google crap
A full clean install needs 2 steps more then the regular:
follow the steps for regular clean
go back in WIPE -> touch the "FORMAT data" button and type "yes" to format the internal storage (you will LOOSE ALL YOUR DATA - obviously)
REBOOT -> Recovery
Flash the ROM
reflash root addon/magisk if you want root
reflash opengapps if you want to use Google crap
It is absolutely recommended to create a backup before and COPYING IT to your PC(!) before doing the above.
Q #03: Are there any plans or a chance of official LOS builds?
no.
Q #04: Google Play shows that my device is not "certified" - how can I fix that?
First of all you must be on the latest build.
If your issue persists click here to proceed:
The second thing is you must not be rooted by the LOS root addon (afaik). Magisk has its own protections to ensure you stay certified but I hadn't the time to test the LOS root-addon.
You also need to know that google play remembers your devices last state so if you are on the latest build and still having that issue do this and it will be certified again:
android settings -> apps -> find play store -> clear data (yes data, not cache) -> reboot -> open play store -> wait 2..5 minutes -> check certified state again
Q #5: A life without Google?! Read here how:
A life without Google ? Is that possible ? ...and why you should consider it ?
So why? That's easy to answer and if those are worth it depends totally on your personal needs:
1) BATTERY. Google services are draining a LOT of your battery, so to get the most out of your battery you should abandon Google gapps
2) PRIVACY. Almost all Google apps phoning home to Google! You don't care about that? You really should. You have nothing to hide? Oh dear believe me you have no idea how much of your private data you do NOT want to share. Keep also in mind that you give your private data not to a company only , there are always humans behind and what they do.. You do not believe me? Read on
BREAKING NEWS:
You can go on with the following steps or simply head-over to /e/ OS which is LOS but completely Google-Free + microG fully working pre-installed:
check it out here!
Q #6: issues with audio (e.g. echo's, silence on one or the other site, ..)? Read here how to provide a specific log for that:
Do the following steps:
1) Ensure you have adb set up on your PC, and have adb debugging and adb root enabled in developer options on your phone
2) Then perform the following (all one command)
On Linux:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver" && sleep 10 && adb logcat -b all |egrep -vi "(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)"
Click to expand...
Click to collapse
On windows:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver && sleep 10 && logcat -b all |egrep -vi '(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)' "
Click to expand...
Click to collapse
3) Then re-produce your audo issue and cancel the logcat from step 2 before hanging up!
4) Share the logcat output from the console screen using paste.omnirom.org
reserved
Finally new living for my old tablet, gonna review thing later after flashing it.
Smoothest rom ever performance better than stock or any other rom that i had tried. Except the bug u mention above but thats no big deal. Well finally can instal youtube and google map.
Really love it!
The most stable build for t285!would recommend to everyone who is looking for a custom ROM for t285.But the audio is really low can barely hear it any type of help will be appreciated using it with gapps mini package works as a charm
Gtexlte user said:
Really love it!
The most stable build for t285!would recommend to everyone who is looking for a custom ROM for t285.But the audio is really low can barely hear it any type of help will be appreciated using it with gapps mini package works as a charm
Click to expand...
Click to collapse
Are their any plains for adding oms support?
Gtexlte user said:
Really love it!
[..] the audio is really low can barely hear it any type of help will be appreciated
Click to expand...
Click to collapse
I guess you mean the speaker?
Gtexlte user said:
Are their any plains for adding oms support?
Click to expand...
Click to collapse
nope. oms is a deep hack in the sources and this will never be implemented by me
Yes I mean the speaker
Is there any way to increase it I can root the device.
Gtexlte user said:
Yes I mean the speaker
Is there any way to increase it I can root the device.
Click to expand...
Click to collapse
For me its loud enough, maybe try enable audio fx built in apps
kaishi12 said:
For me its loud enough, maybe try enable audio fx built in apps
Click to expand...
Click to collapse
Yes I enabled it and there was only a slight boost in audio about 10% boost.It was always a problem in steadfasterX builds could be because I upgraded from one LOS build to another.I could try by flashing the stock ROM and then flash the LOS build.In the stock ROM audio was really loud.If Any one else have this issue could you tell about how did you flash the ROM you upgraded from a previous ROM or were on stock and flashed Did you did a clean install or a regular?I flashed Dolby it seem to have increase a bit and had become more hearable.
Gtexlte user said:
Yes I enabled it and there was only a slight boost in audio about 10% boost.It was always a problem in steadfasterX builds could be because I upgraded from one LOS build to another.I could try by flashing the stock ROM and then flash the LOS build.In the stock ROM audio was really loud.If Any one else have this issue could you tell about how did you flash the ROM you upgraded from a previous ROM or were on stock and flashed Did you did a clean install or a regular?I flashed Dolby it seem to have increase a bit and had become more hearable.
Click to expand...
Click to collapse
I do clean instal from stock rom, well i forgot to mention i using max volume, but strangely theres no noise
kaishi12 said:
I do clean instal from stock rom, well i forgot to mention i using max volume, but strangely theres no noise
Click to expand...
Click to collapse
What do you mean by max volume you set the volume to the max or is it the name of an app or something.thanks for replying.
Gtexlte user said:
What do you mean by max volume you set the volume to the max or is it the name of an app or something.thanks for replying.
Click to expand...
Click to collapse
Set volumw to the max
Gtexlte user said:
Yes I enabled it and there was only a slight boost in audio about 10% boost.It was always a problem in steadfasterX builds could be because I upgraded from one LOS build to another.I could try by flashing the stock ROM and then flash the LOS build.In the stock ROM audio was really loud.If Any one else have this issue could you tell about how did you flash the ROM you upgraded from a previous ROM or were on stock and flashed Did you did a clean install or a regular?I flashed Dolby it seem to have increase a bit and had become more hearable.
Click to expand...
Click to collapse
You don't have that issue in jedlds build?
steadfasterX said:
You don't have that issue in jedlds build?
Click to expand...
Click to collapse
Yes I don't have it in jedld builds
Gtexlte user said:
Yes I don't have this issue in jedld builds
Click to expand...
Click to collapse
I switched to your LOS builds because some stuff was broken there.but the speaker was the same as stock over there
Is there any way to fix the camera recording issue.
I notice update but it say installation blocked, its for the device?
Clean installed your rom. Everything was smooth but i cant use face unlock in this rom. it keeps showing starting up.i think its because of the recording bug.i installed face unlock in jedld cm 13 build it worked in that rom but it didnt worked in yours. Other than that thi rom is perfect.
steadfasterX said:
You don't have that issue in jedlds build?
Click to expand...
Click to collapse
i Had this issue in jedld build too
{
"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:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/12.1/README.mkdn
Flashing Instructions:
Pre-installation:
Recovery (from download page, recovery button)
NikGapps core (Download from here - note that you may also need setup wizard addon if you rely on Google restore)
Magisk root (after first boot)
First time installation:
Backup your data to PC, OTG flash drive
Boot to fastboot and flash recovery
Code:
fastboot flash recovery recovery.img
Now boot to recovery by holding VOL UP + POWER
Navigate to Factory reset and format data, wipe cache and wipe system
Now reboot to recovery
Navigate to Apply update and choose from adb (if you have crDroid.zip on external sdcard, you may choose this option and navigate to where the zip is)
Now sideload crDroid zip
Code:
adb sideload crDroid.zip
If you are running with gapps, choose again to apply from adb and sideload gapps.zip
Reboot to system
Update installation:
Via recovery
Boot to recovery
Navigate to Apply update and choose from adb (if you have crDroid.zip on external sdcard, you may choose this option and navigate to where the zip is)
Now sideload crDroid zip
Code:
adb sideload crDroid.zip
Via OTA:
Go to Settings -> System -> Updater and download latest build
Choose install and let it finish
Reboot
Do note that crDroid 8 is encrypted by default, so if you want to run decrypted, you'll need to sideload dfe.zip
Sources:
ROM: https://github.com/crdroidandroid
Kernel source: https://github.com/crdroidandroid/android_kernel_xiaomi_sdm845
Download:
ROM https://crdroid.net/beryllium
Known isues:
- none critical
Visit official website @ crDroid.net
crDroid Poco Telegram
crDroid Community Telegram
If you like my work, consider a donation > My Paypal
The installation worked liked charm. Thank you so much!!
Thanks for your work Gabriel! Wonderful, I'm glad the ROM is finally encrypted by default
Bug: Bluetooth is trying to turn on and off, repeatedly.
Overall, it feels like a LOS developer build with unlocked features.
HI GWOLFU TNX IN ADVANCE
im not be able to root
flash latest magisk apk or zip no difrens beetwin apk and zip
Sia_scazy said:
HI GWOLFU TNX IN ADVANCE
im not be able to root
flash latest magisk apk or zip no difrens beetwin apk and zip
Click to expand...
Click to collapse
Needs magisk canary
That has support for A12
a9k1t said:
Bug: Bluetooth is trying to turn on and off, repeatedly.
Overall, it feels like a LOS developer build with unlocked features.
Click to expand...
Click to collapse
Aware from telegram chat
Will try to fix with next update
Thanks
Best rom.
Thanks gwolfu! I'd love to upgrade this week, but I've got a few questions first:
Is a dirty flash upgrade from crDroid 7 supported?
I had issues with nikgapps before, with the signal app not receiving any messages unless I open the app (nikgapps specific issue). I'd like to try bitgapps instead. your rom should also work well with that gapps pack, right?
I use encrypted f2fs data partition right now. is that also supported by this crdroid 8 build? or do I have to update the fstab again?
Does it pass safetynet (with/without magisk)?
Oehr said:
Thanks gwolfu! I'd love to upgrade this week, but I've got a few questions first:
Is a dirty flash upgrade from crDroid 7 supported?
I had issues with nikgapps before, with the signal app not receiving any messages unless I open the app (nikgapps specific issue). I'd like to try bitgapps instead. your rom should also work well with that gapps pack, right?
I use encrypted f2fs data partition right now. is that also supported by this crdroid 8 build? or do I have to update the fstab again?
Does it pass safetynet (with/without magisk)?
Click to expand...
Click to collapse
1. Not possible to dirty flash
2. Should work with other gapps (I just shared what I used, however not tested by me)
3. F2FS data is not added yet due to some bug I've noticed
4. Passed SN out of the box even without magisk
Build 20200124 is up
Changelog
- Fixed bluetooth issues
There is an issue with the recovery: it does not automount the micrsod card. manually mounting using adb shell works, but as I am not sure where to mount it, I have no means of applying the update from the microsd card.
P.S. I am using a 1TB microSD card with a single exfat partition
gwolfu said:
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/12.0/README.mkdn
Flashing Instructions:
Pre-installation:
Recovery (here)
NikGapps core (Download from here)
Magisk root (after first boot)
First time installation:
Backup your data to PC, OTG flash drive
Boot to fastboot and flash recovery
Code:
fastboot flash recovery recovery.img
Now boot to recovery by holding VOL UP + POWER
Navigate to Factory reset and format data, wipe cache and wipe system
Now reboot to recovery
Navigate to Apply update and choose from adb (if you have crDroid.zip on external sdcard, you may choose this option and navigate to where the zip is)
Now sideload crDroid zip
Code:
adb sideload crDroid.zip
If you are running with gapps, choose again to apply from adb and sideload gapps.zip
Reboot to system
Update installation:
Boot to recovery
Navigate to Apply update and choose from adb (if you have crDroid.zip on external sdcard, you may choose this option and navigate to where the zip is)
Now sideload crDroid zip
Code:
adb sideload crDroid.zip
Do note that crDroid 8 is encrypted by default, so if you want to run decrypted, you'll need to sideload dfe.zip
Sources:
ROM: https://github.com/crdroidandroid
Kernel source: https://github.com/crdroidandroid/android_kernel_xiaomi_sdm845
Download:
ROM https://crdroid.net/beryllium
Known isues:
- none critical
Visit official website @ crDroid.net
crDroid Poco Telegram
crDroid Community Telegram
If you like my work, consider a donation > My Paypal
Click to expand...
Click to collapse
Bug bluetooth.....not working
wladoom said:
Bug bluetooth.....not working
Click to expand...
Click to collapse
Works fine for me with Build 20200124:
gwolfu said:
Build 20200124 is up
Changelog
- Fixed bluetooth issues
Click to expand...
Click to collapse
gwolfu said:
1. Not possible to dirty flash
2. Should work with other gapps (I just shared what I used, however not tested by me)
3. F2FS data is not added yet due to some bug I've noticed
4. Passed SN out of the box even without magisk
Click to expand...
Click to collapse
as for bitgapps: doesn't work. It fails mounting the vendor partition. tried nikgapps now and receiving message in signal seems to work for now. only time will tell!
as for f2fs, the mounting parameters for encryption differ. I didn't check out the fstab yet, but for crdroid 7, I had to remove the ext4 mount for /data and leave only f2fs with the following permissions in there:
Code:
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/bootdevice/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,background_gc=off,fsync_mode=nobarrier latemount,wait,fileencryption=ice,quota
And even then it was wonky: it only worked when the data partition was COMPLETELY empty, so that encryption was enabled on first boot. encrypting afterwards failed. Maybe that helps you in troubleshooting f2fs support for data.
P.S. Unless it goes mainline again, I'll stick with the current ext4 variant, as I had to patch fstab every time I updated the rom back with crdroid 7...
Hey, huge thanks for crDroid, currently on 7.13, will flash 8 this weekend. I've noticed that when hiding nav bar, the back gesture doesn't work anymore and haven't find out how to fix this (7.13 version though). Did I miss something ?
Oehr said:
Works fine for me with Build 20200124:
as for bitgapps: doesn't work. It fails mounting the vendor partition. tried nikgapps now and receiving message in signal seems to work for now. only time will tell!
as for f2fs, the mounting parameters for encryption differ. I didn't check out the fstab yet, but for crdroid 7, I had to remove the ext4 mount for /data and leave only f2fs with the following permissions in there:
Code:
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/bootdevice/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,background_gc=off,fsync_mode=nobarrier latemount,wait,fileencryption=ice,quota
And even then it was wonky: it only worked when the data partition was COMPLETELY empty, so that encryption was enabled on first boot. encrypting afterwards failed. Maybe that helps you in troubleshooting f2fs support for data.
P.S. Unless it goes mainline again, I'll stick with the current ext4 variant, as I had to patch fstab every time I updated the rom back with crdroid 7...
Click to expand...
Click to collapse
you can't encrypt afterwards
you either do it at first boot (does that automatically in crDroid 8), or you flash DFE and no encryption from there on
also no real benefits in F2FS imo
gwolfu said:
you can't encrypt afterwards
you either do it at first boot (does that automatically in crDroid 8), or you flash DFE and no encryption from there on
also no real benefits in F2FS imo
Click to expand...
Click to collapse
f2fs has been specifically developed for flash memory. it comes with fs-based wear leveling which is great for flash memory without a proper flash controller (microsd cards, emmc, etc.). Some more recent android phones (e.g. pixel 6, poco x3) use f2fs as its default fs for the data (and cache) partition.
Makigo123 said:
Hey, huge thanks for crDroid, currently on 7.13, will flash 8 this weekend. I've noticed that when hiding nav bar, the back gesture doesn't work anymore and haven't find out how to fix this (7.13 version though). Did I miss something ?
Click to expand...
Click to collapse
do not disable nav bar. switch to gesture bar and set its size to compact and/or disable navigation hint instead. i stumbled into the same "issue" in crdroid 8, until i figured out that I was doing it wrong. It is confusing, as all these options are split between basically three different screens.
Oehr said:
do not disable nav bar. switch to gesture bar and set its size to compact and/or disable navigation hint instead. i stumbled into the same "issue" in crdroid 8, until i figured out that I was doing it wrong. It is confusing, as all these options are split between basically three different screens.
Click to expand...
Click to collapse
Thanks, you made my day brighter
Unfortunately, I have the issue with receiving message in the Signal app again: After a while, especially while not charging, signal stops receiving messages on the phone unless I specifically open the signal app again...
I checked the usual culprits, such as battery optimization and such, but everything checks out... I had the issue before with crdroid back when I also tried nikgapps... There was no issue when I later switched to opengapps, but that is not possible for now.
Any clue as to how to fix this? I really don't want to check my signal app all the time
Oehr said:
Unfortunately, I have the issue with receiving message in the Signal app again: After a while, especially while not charging, signal stops receiving messages on the phone unless I specifically open the signal app again...
I checked the usual culprits, such as battery optimization and such, but everything checks out... I had the issue before with crdroid back when I also tried nikgapps... There was no issue when I later switched to opengapps, but that is not possible for now.
Any clue as to how to fix this? I really don't want to check my signal app all the time
Click to expand...
Click to collapse
issue is with nikgapps
should be fixed in latest build released today
if dirty flashing new gapps on top, do also clear app data of Google Play Services app and reboot after dirty flash done and booted
{
"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 13, 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.
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. You can also view the Changelog for a full list of changes & features.
Basic requirements:
Unlock your bootloader, make sure you are on Android 13 firmware.
Make sure you can send and receive SMS and receive calls (also via WiFi and LTE, if possible). It would be better for you to get VoLTE/VoWiFi utilized once on stock to provision IMS
Currently tested on XQ-BC72. Expected to work on XQ-BC62, XQ-BC52 and XQ-BC42 (If it does not work, please report. See 5 in "Important Notes" section for more information)
Make sure you have gone through the installation guide once before proceed!
Installation:
Flash additional partitions and recovery.
Download the following files from the download link:
dtbo.img
vendor_boot.img
boot.img
Connect your device to your PC via USB if isn't already
If your device is not already in fastboot mode, on the computer, open a command prompt (on Windows) or terminal (on Linux or macOS) window, and type:
Code:
adb reboot bootloader
Flash the downloaded image files to your device by typing:
Code:
fastboot flash dtbo <dtbo>.img
fastboot flash vendor_boot <vendor_boot>.img
fastboot flash boot <boot>.img
Now reboot into recovery to verify the installation:
Code:
fastboot reboot recovery
Installing LineageOS from recovery
Download the lineageos installation package that you would like to install from the download link
If you are not in recovery, reboot into recovery
Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
Return to the main menu
Sideload the LineageOS package
On the device, select "Apply Update", then "Apply from ADB" to begin sideload
On the PC, sideload the package using:
Code:
adb sideload filename.zip
Return to the main menu
(Optionally) If you want to install any add-ons, click "Advanced", then "Reboot to Recovery", then when your device reboots, click "Apply Update", then "Apply from ADB", then "adb sideload filename.zip" those packages in sequence.
Once you have installed everything successfully, click the back arrow in the top left of the screen, then "Reboot system now"
Downloads:
https://androidfilehost.com/?w=files&flid=337547
Device Trees & Kernel Source:
https://github.com/hellobbn/android_device_sony_sm8350-common
https://github.com/hellobbn/android_device_sony_pdx215
https://github.com/hellobbn/android_kernel_sony_sm8350
Important Notes:
If you have no signal problem, debug in the following step:
Go to Settings > About phone > Tap Build number 7 times to enable Developer options
Go to Settings > System > Developer options, and enable "USB debugging" and "Rooted debugging"
Connect your device to your PC, and type in command prompt or terminal:
Code:
adb root
Type the following command:
Code:
adb shell getprop ro.vendor.product.rf.id
You should get the the following output based on your model (See table at the end of this section)
If you get the correct output, go to step 5, otherwise please go to step 6 to report bug
If you get correct output, type:
Code:
adb shell /vendor/bin/nv_updater -c 0
and check if you get signal. If you still can't get signal, please report with:
Type
Code:
adb logcat
and get the log during the execution of the above command.
If you get incorrect output, please report with the following information
Your model
Type
Code:
adb shell "strings /dev/block/by-name/LTALabel | grep <Your model name bere>"
and add the result to your bug report
ModelOutputXQ-BC72PDX215-C2XQ-BC62PDX215-A2USXQ-BC52PDX215-A2XQ-BC42PDX215-J2
Reporting Bugs:
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 /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (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
If you are facing issues like no signal
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:
Change Log:
Code:
2023-03-21
- Android 13 QPR2
- Update blobs to XQ-BC72_Customized HK_61.2.A.0.396
20223-03-15
- Added wip and upcoming lineage health feature (a8df2fa16, https://review.lineageos.org/q/topic:charging-control-hal-20) (This feature is not yet stable, only enable it if you want to test)
- Calibrate the speaker on boot (71265bc07)
- Fix problems on notification light (88df873ca)
- Fix codec profile to match stock (ea68c40b7)
- Fix OTG in recovery mode (c1e2d0417)
- Fix echo cancellation in loud speaker mode (96766b7ec)
- Other clean-ups
2023-0216
- Initial release
Nice Work! 前排支持大佬
Well done!
Installed this on my XQ-BC62, and everything appears to be working fine. Cameras, 5G, SMS, VoLTE, etc.
Any screenshots ?
Pandemic said:
Any screenshots ?
Click to expand...
Click to collapse
Eh screenshot of which part do you want?
Pandemic said:
Any screenshots ?
Click to expand...
Click to collapse
screenshots for weaklings, take and install a cat in a bag
And seriously, I would rather watch a short video with ROM settings, or an overview in general
Does Camera2Api work ok? More specifically the image stabilization? Would a GCam work too?
I know from experience unofficial LOS means something from the mandatory list is not working, or the developer doesn't want to publish it to become official, which if all works ok, doesn't make sense
So any chances this becomes LOS official?
(I'm a huge fan of LOS and will definitely use this if it has support and updates).
Thanks!
The camera 2 API level is the same as stock.
This will become official when I think it is stable enough.
Just installed this yesterday on my XQ-BC62 and everything seems to be working well. Haven't run into any issues, so far.
One thing I have noticed and I don't know if it's just me, but when I need to flash anything, including this rom, I need to be in FastbootD and not just regular fastboot mode in order for my computer to see the phone. Otherwise, I just get a message saying <waiting for device>. I don't know if that is just understood with this phone or if it's just my device.
Great work!
CCivale said:
Just installed this yesterday on my XQ-BC62 and everything seems to be working well. Haven't run into any issues, so far.
One thing I have noticed and I don't know if it's just me, but when I need to flash anything, including this rom, I need to be in FastbootD and not just regular fastboot mode in order for my computer to see the phone. Otherwise, I just get a message saying <waiting for device>. I don't know if that is just understood with this phone or if it's just my device.
Great work!
Click to expand...
Click to collapse
Thanks.
The problem that your device is not recognized in fastboot mode is more like a driver issue. If you are on windows, you may need to go to device manager and you may see a yellow triangle on your android device, and you need to manually install the driver for that (called something like Bootloader interface). You can find instructions online.
clfbbn said:
Thanks.
The problem that your device is not recognized in fastboot mode is more like a driver issue. If you are on windows, you may need to go to device manager and you may see a yellow triangle on your android device, and you need to manually install the driver for that (called something like Bootloader interface). You can find instructions online.
Click to expand...
Click to collapse
Oh, great, thanks for the tip. I'll have to take a look for that.
And again, great job on the rom. I've been silently hoping that LIneage would come out for this phone. It's pretty much my go to custom rom, going all the way back to CM.
which version of the 20th Lineage is this using? vS etc?
Is there any way for donations to support your work? LOL
DaVinci42 said:
Is there any way for donations to support your work? LOL
Click to expand...
Click to collapse
I personally don't accept donation
You can donate lineageos to support it instead .
How about the Camera, guys?
VO7T said:
How about the Camera, guys?
Click to expand...
Click to collapse
Should work perfectly
Will there be an effort to get pdx215 upstreamed to "official" status? Official ROMs come with the benefit of LineageOS for microG builds.
toastal said:
Will there be an effort to get pdx215 upstreamed to "official" status? Official ROMs come with the benefit of LineageOS for microG builds.
Click to expand...
Click to collapse
Related repositories have been forked to lineageos. So we are half way there.
Hey man, thanks for such a great rom. finally getting somehwere good for custom roms for our device! you're the best, maybe you could start accepting small donations
Edit: Is there a way to get the stock camera and video cam?
DrDrag0n said:
Hey man, thanks for such a great rom. finally getting somehwere good for custom roms for our device! you're the best, maybe you could start accepting small donations
Edit: Is there a way to get the stock camera and video cam?
Click to expand...
Click to collapse
https://drive.google.com/file/u/2/d/1M0kyWTTjr7p8d9hVyQG83O0ySJfzMOeT/view?usp=sharing just install these APKs and you should be ready to go!