• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[OFFICIAL] LineageOS 18.1 for the LG V20

Search This thread

Aethera

Senior Member
Feb 18, 2012
176
43
Bay Area
My H918 is still crashing. Please let me know if anyone has suggestions for a fix. Prior to crashing this is what the log shows:

10-13 19:43:34.554 0 0 E rmt_storage: INFO:rmt_storage_rw_iovec_cb: Write iovec request received for /boot/modem_fs1
10-13 19:43:34.555 0 0 E rmt_storage: INFO:rmt_storage_client_thread: Calling Write [offset=0, size=2097152]for /boot/modem_fs1!
10-13 19:43:34.623 0 0 E rmt_storage: INFO:rmt_storage_client_thread: Done Write (bytes = 2097152) for /boot/modem_fs1!
10-13 19:43:35.638 0 0 E : LGE charging scenario : state 0 -> 0(0-0), temp=294, volt=3941, fl_volt=4400 BTM=0, charger=1, cur_set=1000/0, chg_cur = 344
10-13 19:43:35.638 0 0 E [LGE-CC] lge_monitor_batt_temp_work: (alarm)->(alarm)
10-13 19:43:35.638 0 0 E vote : name[BATT_FCC], client[LGE_POWER_CLASS_FCC_VOTER,1], enabled[1], val[1000]
10-13 19:43:35.638 0 0 E vote : name[BATTCHG_SUSPEND], client[LGCC_EN_VOTER,1], enabled[0], val[0]
10-13 19:43:35.638 0 0 E vote : name[BATTCHG_SUSPEND], client[STORE_MODE_EN_VOTER,2], enabled[0], val[0]
10-13 19:43:35.638 0 0 E vote : name[USB_SUSPEND], client[STORE_MODE_USB_EN_VOTER,2], enabled[0], val[0]
10-13 19:43:35.667 0 0 W healthd : battery l=76 v=3941 t=29.4 h=2 st=2 c=344999 chg=u
10-13 19:43:36.505 2994 7829 E MtpServer: request read returned -1, errno: 5
10-13 19:43:36.510 2889 7827 E adbd : failed to send interruption signal to worker: No such process
10-13 19:43:36.543 0 0 E dwc3 6a00000.dwc3: request 0000000000000000 was not queued to ep0out
10-13 19:43:37.056 1195 1258 E LightsService: Light requested not available on this device. 2
10-13 19:43:37.206 7644 7679 E GH.PermissionChecker: Permission is not granted: android.permission.CALL_PHONE
10-13 19:43:37.237 7644 7679 E GH.PermissionChecker: Permission is not granted: android.permission.CALL_PHONE
10-13 19:43:37.287 7644 7644 E GH.PermissionChecker: Permission is not granted: android.permission.CALL_PHONE
10-13 19:43:37.381 7644 7679 E GH.PermissionChecker: Permission is not granted: android.permission.CALL_PHONE
10-13 19:43:37.537 963 998 E ANDR-PERF-MPCTL: Invalid profile no. 0, total profiles 0 only
10-13 19:43:48.813 8129 8129 W app_process: JNI RegisterNativeMethods: attempt to register 0 native methods for android.media.AudioAttributes
10-13 19:43:49.020 963 998 E ANDR-PERF-MPCTL: Invalid profile no. 0, total profiles 0 only
10-13 19:43:50.966 963 998 E ANDR-PERF-MPCTL: Invalid profile no. 0, total profiles 0 only
10-13 19:43:50.980 1195 2117 W NotificationService: Toast already killed. pkg=com.topjohnwu.magisk [email protected]
10-13 19:43:52.449 1195 1233 W WindowManager: Unable to start animation, surface is null or no children.
10-13 19:44:01.980 1195 1195 W WindowManager: removeWindowToken: Attempted to remove non-existing token: [email protected]
10-13 19:44:14.255 0 0 W healthd : battery l=76 v=3944 t=29.4 h=2 st=2 c=319974 chg=u
10-13 19:44:29.984 0 0 E vote : name[BATTCHG_SUSPEND], client[BATTCHG_UNKNOWN_BATTERY_EN_VOTER,0], enabled[0], val[0]
10-13 19:44:29.984 0 0 E SMBCHG : smbchg_config_chg_battery_type: BATTERY FULL NAME : LGE_BL44E1F_LGC_3200mAh
10-13 19:44:29.984 0 0 E vote : name[USB_ICL], client[PSY_ICL_VOTER,0], enabled[1], val[0]
10-13 19:44:30.000 0 0 W healthd : battery l=76 v=3944 t=29.4 h=2 st=2 c=319974 chg=u
10-13 19:44:30.062 0 0 W healthd : battery l=76 v=3944 t=29.4 h=2 st=2 c=319974 chg=u
10-13 19:44:35.690 0 0 E : LGE charging scenario : state 0 -> 0(0-0), temp=294, volt=3944, fl_volt=4400 BTM=0, charger=1, cur_set=1000/0, chg_cur = 319
10-13 19:44:35.690 0 0 E [LGE-CC] lge_monitor_batt_temp_work: (alarm)->(alarm)
10-13 19:44:35.829 0 0 E : Fatal error on the modem.
10-13 19:44:35.829 0 0 E : modem subsystem failure reason: sleep_target.c:305:.
10-13 19:44:35.840 0 0 E M-Notify: General: 8
 

npjohnson

Recognized Developer
For other readers out there, its worth noting I've had zero issues with mobile/data settings for months up until during a brief vacation. I wouldn't call it a compatibility issue quite yet. Feels like it's fixable, I could go nuclear and start from scratch I suppose.

I've been daily driving LOS for several months, its been relatively stable as far as a 6 year old device goes. I'm quite pleased with it!

No offense A. Whit, but you seem to have mentioned great displeasure in the work of FOSS developers more than once in this post (and that you're an engineer?). Maybe its time you move on from the community or consider contributing back?
On your last comment: I can't agree more - for a guy that won't even file a dang bug report in the proper place with logs to help solve the issues, sure has a lot to say lol
 

npjohnson

Recognized Developer
My H918 is still crashing. Please let me know if anyone has suggestions for a fix. Prior to crashing this is what the log shows:

10-13 19:43:34.554 0 0 E rmt_storage: INFO:rmt_storage_rw_iovec_cb: Write iovec request received for /boot/modem_fs1
10-13 19:43:34.555 0 0 E rmt_storage: INFO:rmt_storage_client_thread: Calling Write [offset=0, size=2097152]for /boot/modem_fs1!
10-13 19:43:34.623 0 0 E rmt_storage: INFO:rmt_storage_client_thread: Done Write (bytes = 2097152) for /boot/modem_fs1!
10-13 19:43:35.638 0 0 E : LGE charging scenario : state 0 -> 0(0-0), temp=294, volt=3941, fl_volt=4400 BTM=0, charger=1, cur_set=1000/0, chg_cur = 344
10-13 19:43:35.638 0 0 E [LGE-CC] lge_monitor_batt_temp_work: (alarm)->(alarm)
10-13 19:43:35.638 0 0 E vote : name[BATT_FCC], client[LGE_POWER_CLASS_FCC_VOTER,1], enabled[1], val[1000]
10-13 19:43:35.638 0 0 E vote : name[BATTCHG_SUSPEND], client[LGCC_EN_VOTER,1], enabled[0], val[0]
10-13 19:43:35.638 0 0 E vote : name[BATTCHG_SUSPEND], client[STORE_MODE_EN_VOTER,2], enabled[0], val[0]
10-13 19:43:35.638 0 0 E vote : name[USB_SUSPEND], client[STORE_MODE_USB_EN_VOTER,2], enabled[0], val[0]
10-13 19:43:35.667 0 0 W healthd : battery l=76 v=3941 t=29.4 h=2 st=2 c=344999 chg=u
10-13 19:43:36.505 2994 7829 E MtpServer: request read returned -1, errno: 5
10-13 19:43:36.510 2889 7827 E adbd : failed to send interruption signal to worker: No such process
10-13 19:43:36.543 0 0 E dwc3 6a00000.dwc3: request 0000000000000000 was not queued to ep0out
10-13 19:43:37.056 1195 1258 E LightsService: Light requested not available on this device. 2
10-13 19:43:37.206 7644 7679 E GH.PermissionChecker: Permission is not granted: android.permission.CALL_PHONE
10-13 19:43:37.237 7644 7679 E GH.PermissionChecker: Permission is not granted: android.permission.CALL_PHONE
10-13 19:43:37.287 7644 7644 E GH.PermissionChecker: Permission is not granted: android.permission.CALL_PHONE
10-13 19:43:37.381 7644 7679 E GH.PermissionChecker: Permission is not granted: android.permission.CALL_PHONE
10-13 19:43:37.537 963 998 E ANDR-PERF-MPCTL: Invalid profile no. 0, total profiles 0 only
10-13 19:43:48.813 8129 8129 W app_process: JNI RegisterNativeMethods: attempt to register 0 native methods for android.media.AudioAttributes
10-13 19:43:49.020 963 998 E ANDR-PERF-MPCTL: Invalid profile no. 0, total profiles 0 only
10-13 19:43:50.966 963 998 E ANDR-PERF-MPCTL: Invalid profile no. 0, total profiles 0 only
10-13 19:43:50.980 1195 2117 W NotificationService: Toast already killed. pkg=com.topjohnwu.magisk [email protected]
10-13 19:43:52.449 1195 1233 W WindowManager: Unable to start animation, surface is null or no children.
10-13 19:44:01.980 1195 1195 W WindowManager: removeWindowToken: Attempted to remove non-existing token: [email protected]
10-13 19:44:14.255 0 0 W healthd : battery l=76 v=3944 t=29.4 h=2 st=2 c=319974 chg=u
10-13 19:44:29.984 0 0 E vote : name[BATTCHG_SUSPEND], client[BATTCHG_UNKNOWN_BATTERY_EN_VOTER,0], enabled[0], val[0]
10-13 19:44:29.984 0 0 E SMBCHG : smbchg_config_chg_battery_type: BATTERY FULL NAME : LGE_BL44E1F_LGC_3200mAh
10-13 19:44:29.984 0 0 E vote : name[USB_ICL], client[PSY_ICL_VOTER,0], enabled[1], val[0]
10-13 19:44:30.000 0 0 W healthd : battery l=76 v=3944 t=29.4 h=2 st=2 c=319974 chg=u
10-13 19:44:30.062 0 0 W healthd : battery l=76 v=3944 t=29.4 h=2 st=2 c=319974 chg=u
10-13 19:44:35.690 0 0 E : LGE charging scenario : state 0 -> 0(0-0), temp=294, volt=3944, fl_volt=4400 BTM=0, charger=1, cur_set=1000/0, chg_cur = 319
10-13 19:44:35.690 0 0 E [LGE-CC] lge_monitor_batt_temp_work: (alarm)->(alarm)
10-13 19:44:35.829 0 0 E : Fatal error on the modem.
10-13 19:44:35.829 0 0 E : modem subsystem failure reason: sleep_target.c:305:.
10-13 19:44:35.840 0 0 E M-Notify: General: 8
looks like whatever firmware you're on isn't new enough? What stock version did you come from?
 

npjohnson

Recognized Developer
Yes, I have had same issue on H910
and
- speakerphone not working
- phone getting too warm / hot
- phone reboots randomly (not often but once in a while)
- other issues

So I flashed stock US99620f_00_1120 on my H910 and now very happy with no ATT garbage apks and everything on phone works perfect.

LOS is not even close to being ready for daily use. Some Devs maintaining LOS for V20 phones are just not able to make BASIC features work. Some dont even own a H910. Its a hobby to play with. And I understand that some orrigional source code is not available which I being an engineer understand is a huge problem.

Only reason why I have 5 LG v20 phones (H910 and H918) is because I like the ability to change battery to larger size and I dont need or want the "newer phones".
1. It works on my h918, and on another developers h910 (yes, we do have one!) - not sure why you're hitting this - a bug report and logs (as I've said x^n times to you) would be helpful.
2. What are you doing with it? It's an old phone - thermal throttling is to be expected - it's like running Win10 on an XP built PC - can you? Yes, will it throttle and slow down? Also yes.
3. I haven't seen these - do you have any mods? If no - next time it happens pull /sys/fs/pstore and post the logs here - I'll solve it ASAP. Random reboots can and often are hardware related in one way or another.
4. "indescriptive" - file bugs if you want help, if not, please just go away.

You persistently insult the devs for lge-8996 and act high and mighty - either contribute, file proper bugs, or just go away tbh - it's a free time project that you seem to enjoy making not fun for the devs.
 
  • Like
Reactions: mangokm40

npjohnson

Recognized Developer
I'm not 100% sure that was the ROM. I bought the phone on eBay and flashed LOS from whatever ROM the phone was on. My understanding was it was better to not try to upgrade it prior to flashing because later stock ROM updates prevent flashing custom ROMs.
You should upgrade to the newest Nougat for your device - not sure what that is tbh.
 

Aethera

Senior Member
Feb 18, 2012
176
43
Bay Area

Attachments

  • Screenshot_20211013-222132_Settings.png
    Screenshot_20211013-222132_Settings.png
    207.4 KB · Views: 6
  • Like
Reactions: npjohnson

mangokm40

Senior Member
Jan 13, 2019
102
46
FYI this was the guide I used when rooting and installing bootloader on the phone: https://forum.xda-developers.com/t/...locking-downgrading-rooting-and-twrp.3808258/

This guide says to downgrade to H91810P before rooting. It also says that H91810P through H91810U are ARB1 so perhaps I can extract the modem from the H91810U KDZ and install it.
You can also look at this:
https://forum.xda-developers.com/t/...wrp-flashable-bootloaders-and-modems.3547268/

I should tell you. I downloaded the files, but never tried to flash them.
Read through the whole topic. I don't know enough and am scared I will do something to brick my phone. Since my h918 is serving its purpose well, I'm still on the 10p firmware I loaded in order to unlock it.
 
  • Like
Reactions: Aethera

Aethera

Senior Member
Feb 18, 2012
176
43
Bay Area
You can also look at this:
https://forum.xda-developers.com/t/...wrp-flashable-bootloaders-and-modems.3547268/

I should tell you. I downloaded the files, but never tried to flash them.
Read through the whole topic. I don't know enough and am scared I will do something to brick my phone. Since my h918 is serving its purpose well, I'm still on the 10p firmware I loaded in order to unlock it.
Thanks for the info. I flashed the 20h modem from that page and unfortunately the phone is bootlooping. According to what I researched the .2.0.1.c3-00045-M8996FAAAANAZM-1 baseband that was previously on the phone corresponds to 10u however the AndroidFileHost link for the 10u modem is now dead.

Luckily the phone still boots into TWRP.
 
  • Like
Reactions: mangokm40

Aethera

Senior Member
Feb 18, 2012
176
43
Bay Area
So it's still crashing:

10-15 03:07:08.692 0 0 E : LGE charging scenario : state 0 -> 0(0-0), temp=268, volt=3767, fl_volt=4400 BTM=0, charger=1, cur_set=3200/0, chg_cur = 1307
10-15 03:07:08.692 0 0 E [LGE-CC] lge_monitor_batt_temp_work: (alarm)->(alarm)
10-15 03:07:22.147 461 461 E lowmemorykiller: Error writing /proc/5071/oom_score_adj; errno=22
10-15 03:07:48.887 2450 3659 E NetworkScheduler.ATC: Error finding compatible intent-filter to handle SERVICE_ACTION_EXECUTE_TASK for com.google.android.gms/.chimera.GmsInternalBoundBrokerService [CONTEXT service_id=218 ]
10-15 03:07:48.887 2450 3659 E NetworkScheduler.TED: Invalid service definition provided: null [CONTEXT service_id=218 ]
10-15 03:08:04.061 0 0 E msm-dwc3 6a00000.ssusb: Abort PM suspend!! (USB is outside LPM)
10-15 03:08:04.061 0 0 E dpm_run_callback(): platform_pm_suspend+0x0/0x50 returns -16
10-15 03:08:04.061 0 0 E PM : Device 6a00000.ssusb failed to suspend: error -16
10-15 03:08:04.065 0 0 E PM : Some devices failed to suspend, or early wake event detected
10-15 03:08:04.342 0 0 E : Fatal error on the modem.
10-15 03:08:04.342 0 0 E : modem subsystem failure reason: sleep_target.c:305:.
10-15 03:08:04.351 0 0 E M-Notify: General: 8
 
  • Sad
Reactions: mangokm40

itt533

Member
Nov 12, 2020
24
1
chennai
The battery drain is not from third party apps. But from OS.
Made a backup with Migrate, clean flash of Lighthouse ROM, restored the migrate backup and I went from >30% drain over a night with LOS to 2% drain after 24 hours on Lighthouse.
Problem solved
i have a h990ds and the drain is sometimes only of 2 to 5 %. Most of the time, if i had to use the torch, or it went ringing alarm for minutes then the drain might reach 20%.
 
Moderator Announcement

Thread slightly cleaned!

This is a development site and people contribute work as a fun hobby, NOT A JOB! They don't owe you anything but you owe the developers respect!
If a ROM does not work for you, what did you do to contribute? Did you clean flash? More important, did you run a log of errors to help the developer? Just remember what you would expect in your profession. Or were you just too lazy to help and prefer to leech and complain?
This world will only get better if we all learn to give instead of always taking! Please do not comment on rude posts, please report and a moderator will help.
Thank you all for your cooperation.

Regards
Oswald Boelcke
Senior Moderator
 

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    Moderator Announcement

    Thread slightly cleaned!

    This is a development site and people contribute work as a fun hobby, NOT A JOB! They don't owe you anything but you owe the developers respect!
    If a ROM does not work for you, what did you do to contribute? Did you clean flash? More important, did you run a log of errors to help the developer? Just remember what you would expect in your profession. Or were you just too lazy to help and prefer to leech and complain?
    This world will only get better if we all learn to give instead of always taking! Please do not comment on rude posts, please report and a moderator will help.
    Thank you all for your cooperation.

    Regards
    Oswald Boelcke
    Senior Moderator
    1
    is there a way to get stereo while recording video?

    gamma kernel will allow IR blaster for both emitting and receiving? It should be mentioned that this device also records IR codes from other remote controls.

    Is there any feature that will be lost with gamma kernel? greater power draining?
    I'll say it again, if anyone just links me the changes needed, I can get them put into the official kernel.
    1
    Speakerphone mode while in a phone call:

    Solution for LOS ( it worked for camera audio apk )

    reference:
    reddit.com/r/lgv20/comments/dqfskw/i_finally_found_how_to_record_clean_stereo_audio/

    1) Verify speakerphone in LOS uses TOP MIC
    I just verified speakerphone is using all 3 MICs. Thats a problem = Lots of NOISE ! Make changes to use TOP MIC only.

    2) SET PHONE/DIALER apk to use UNPROCESSED mode for TOP MIC when using speakerphone mode. ALL Programs (in this case phone DIALER) "which use the UNPROCESSED mode (MIC input) give superior audio quality. Note that this mode is pretty quiet, as the other modes do some adjustable gain. Since the V20's mic has a wider dynamic range than usual, and it doesn't actually let you capture at 24-bit, you would get a higher noise floor than on another phone with 16-bit recording, assuming the same quality of mic, amp, etc. just a different gain before the ADC."
    Feel free to push up a patch, the wiki has great detail on how to do so.

    ButI was referring to the IR changes in Gamma kernel.
    1
    Yes, I have had same issue on H910
    and
    - speakerphone not working
    - phone getting too warm / hot
    - phone reboots randomly (not often but once in a while)
    - other issues

    So I flashed stock US99620f_00_1120 on my H910 and now very happy with no ATT garbage apks and everything on phone works perfect.

    LOS is not even close to being ready for daily use. Some Devs maintaining LOS for V20 phones are just not able to make BASIC features work. Some dont even own a H910. Its a hobby to play with. And I understand that some orrigional source code is not available which I being an engineer understand is a huge problem.

    Only reason why I have 5 LG v20 phones (H910 and H918) is because I like the ability to change battery to larger size and I dont need or want the "newer phones".
    1. It works on my h918, and on another developers h910 (yes, we do have one!) - not sure why you're hitting this - a bug report and logs (as I've said x^n times to you) would be helpful.
    2. What are you doing with it? It's an old phone - thermal throttling is to be expected - it's like running Win10 on an XP built PC - can you? Yes, will it throttle and slow down? Also yes.
    3. I haven't seen these - do you have any mods? If no - next time it happens pull /sys/fs/pstore and post the logs here - I'll solve it ASAP. Random reboots can and often are hardware related in one way or another.
    4. "indescriptive" - file bugs if you want help, if not, please just go away.

    You persistently insult the devs for lge-8996 and act high and mighty - either contribute, file proper bugs, or just go away tbh - it's a free time project that you seem to enjoy making not fun for the devs.
    1
    And the speakerphone sucks. Not usable

    THE LG V20 is my favorite phone
    Fun! The 20-something'th time you've said this?

    For the love of god then either fix it, provide logs on a a freaking bug ticket (which I'll say for the 8th time, but you refuse to do), or just don't post!
  • 19
    lineage-os-logo.png

    LG V20

    Code:
    - Your warranty is now void.
    - You have been warned.
    - Use at your own risk.

    Introduction:
    This is the Official Lineage OS 18.1 thread for the LG V20.

    Downloads:
    Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
    If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.

    Known Bugs:
    • IMS (VoLTE/Wi-Fi Calling) doesn't work due to framework tie-ins used by the LG proprietary binaries.
    • Find any? Report them according to this guide.
    Notes:
    • The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
    Kernel Source: https://github.com/LineageOS/android_kernel_lge_msm8996
    6
    On my LG v20 H910 with LOS 18.1 lineage-18.1-20210722-nightly-h910-signed.zip
    (nothing else installed, no gapps, no mods, no root, etc...) the "LOS SNAP CAMERA" VIDEO record sound volume is almost 0%

    SAME ISSUE ON Lg v20 H918 !!!!!!! I have that phone also.

    After days of research and playing with mixer_paths_tasha.xml settings I gave up..... PROBLEM VERIFIED: its a LOS snap camera apk issue.

    Then I installed ROM [android 11] UNOFFICIAL SuperiorOS-Xcalibur

    https://forum.xda-developers.com/t/...96-11-unofficial-superioros-xcalibur.4248255/

    COMING FROM LINEAGE/RR:

    1. Boot into twrp
    2. Do a regular wipe (not format)
    3. Flash Superior zip
    4. Flash magisk (optional but recommended)
    5. Wipe dalvik
    6. Reboot

    CAMERA VIEDO WORKS PERFECT !!!!
    PERFECT SOUND !!!



    To LOS maintainers: Fix the LOS SNAP CAMERA apk or quit screwing around with programming android ROMs. Simple as that. I am a MSEE engineering manager and if I cant do my job right I don't do it at all.


    The LOS snap camera has been broken for a very long time (years) and many people have had to use GCAM or Open Camera and all these people including myself are sick that LOS maintainers can't fix a simple but very important apk in LOS (CAMERA video sound issue). This is well documented all over LOS wiki and github etc.....

    FROM: bernardobas, Senior Member


    "Hi @npjohnson
    Open Camera (and BSG GCam 8.1) uses unprocessed-mic by default to get audio while recording video."


    I am done with LOS until this is fixed. YOU ARE WASTING MY TIME
    Yeah, considering h910/h918 are near identical, makes sense that they both suffer.

    By your own statement, you're an engineer, and should be able to discern based on the info you gave me that it is _not_ an issue with the "Snap Camera apk", instead that we are using compressed audio path, and clearly it isn't processing right (likely a codec issue like I mentioned several posts ago). We could swap it to unprocessed mic input, but that will be garbled and awful - only using that as a last resort as opposed to actually fixing the compressed audio route.

    As for the insults launched - k, stop using lineage then. I literally have not a care in the world whether you use it. I'm doing hard work for free, which, as an engineer, you should understand is often thankless, and your naggy/attacking comments only make me want to never touch the device again :)

    I'll be looking at it sometime this week, but for everyone else on this thread who has been kind and supportive lol.
    5
    On my LG v20 H910 with LOS 18.1 lineage-18.1-20210722-nightly-h910-signed.zip
    (nothing else installed, no gapps, no mods, no root, etc...) the "LOS SNAP CAMERA" VIDEO record sound volume is almost 0%

    SAME ISSUE ON Lg v20 H918 !!!!!!! I have that phone also.

    After days of research and playing with mixer_paths_tasha.xml settings I gave up..... PROBLEM VERIFIED: its a LOS snap camera apk issue.

    Then I installed ROM [android 11] UNOFFICIAL SuperiorOS-Xcalibur

    https://forum.xda-developers.com/t/...96-11-unofficial-superioros-xcalibur.4248255/

    COMING FROM LINEAGE/RR:

    1. Boot into twrp
    2. Do a regular wipe (not format)
    3. Flash Superior zip
    4. Flash magisk (optional but recommended)
    5. Wipe dalvik
    6. Reboot

    CAMERA VIEDO WORKS PERFECT !!!!
    PERFECT SOUND !!!



    To LOS maintainers: Fix the LOS SNAP CAMERA apk or quit screwing around with programming android ROMs. Simple as that. I am a MSEE engineering manager and if I cant do my job right I don't do it at all.


    The LOS snap camera has been broken for a very long time (years) and many people have had to use GCAM or Open Camera and all these people including myself are sick that LOS maintainers can't fix a simple but very important apk in LOS (CAMERA video sound issue). This is well documented all over LOS wiki and github etc.....

    FROM: bernardobas, Senior Member


    "Hi @npjohnson
    Open Camera (and BSG GCam 8.1) uses unprocessed-mic by default to get audio while recording video."


    I am done with LOS until this is fixed. YOU ARE WASTING MY TIME
    Maybe you should go back to stock? You do realize we do this for free and on our own time? If there are any issues we try to fix them ASAP but with your comments I doubt @npjohnson is going to want to support the device anymore. If there is any issue I would recommend reporting it in a less-hostile way and it might be a simple fix rather than insulting the primary dev for LOS on the device who may now not want to support the device anymore...
    4
    Moderator Announcement

    Thread slightly cleaned!

    This is a development site and people contribute work as a fun hobby, NOT A JOB! They don't owe you anything but you owe the developers respect!
    If a ROM does not work for you, what did you do to contribute? Did you clean flash? More important, did you run a log of errors to help the developer? Just remember what you would expect in your profession. Or were you just too lazy to help and prefer to leech and complain?
    This world will only get better if we all learn to give instead of always taking! Please do not comment on rude posts, please report and a moderator will help.
    Thank you all for your cooperation.

    Regards
    Oswald Boelcke
    Senior Moderator
    2
    On my LG v20 H910 with LOS 18.1 lineage-18.1-20210722-nightly-h910-signed.zip
    (nothing else installed, no gapps, no mods, no root, etc...) the "LOS SNAP CAMERA" VIDEO record sound volume is almost 0%

    SAME ISSUE ON Lg v20 H918 !!!!!!! I have that phone also.

    After days of research and playing with mixer_paths_tasha.xml settings I gave up..... PROBLEM VERIFIED: its a LOS snap camera apk issue.

    Then I installed ROM [android 11] UNOFFICIAL SuperiorOS-Xcalibur

    https://forum.xda-developers.com/t/...96-11-unofficial-superioros-xcalibur.4248255/

    COMING FROM LINEAGE/RR:

    1. Boot into twrp
    2. Do a regular wipe (not format)
    3. Flash Superior zip
    4. Flash magisk (optional but recommended)
    5. Wipe dalvik
    6. Reboot

    CAMERA VIEDO WORKS PERFECT !!!!
    PERFECT SOUND !!!



    To LOS maintainers: Fix the LOS SNAP CAMERA apk or quit screwing around with programming android ROMs. Simple as that. I am a MSEE engineering manager and if I cant do my job right I don't do it at all.


    The LOS snap camera has been broken for a very long time (years) and many people have had to use GCAM or Open Camera and all these people including myself are sick that LOS maintainers can't fix a simple but very important apk in LOS (CAMERA video sound issue). This is well documented all over LOS wiki and github etc.....

    FROM: bernardobas, Senior Member


    "Hi @npjohnson
    Open Camera (and BSG GCam 8.1) uses unprocessed-mic by default to get audio while recording video."


    I am done with LOS until this is fixed. YOU ARE WASTING MY TIME
    So, my girlfriend is at home, asked her to try it - and surprise surprise, Snap Camera's video recorded audio works just fine lol. Front and rear camera.

    I did pick the patchset we merged on g5-common though afterwards, and merged it - it sounds to loud to me tbh, but enough people seem to like it better, lets go with it.