[ROM][UNOFFICIAL][P][F500,LS991,H81x,US991,VS986] LineageOS 16.0

[LukeSlovian]

Hello Plese Help Me.

I don't have a microphone icon in - despite the Voice Type option enabled. I have been granted microphone permissions in the Gboard application menu - please support. I post screenshots.

 

[LukeSlovian]

1. Type "Gboard" or "Google Keyboard" on the playstore.
2. Open it, and the app itself will guide through the configuration process.

I don't have a microphone icon in - despite the Voice Type option enabled. I have been granted microphone permissions in the Gboard application menu - please support. I post screenshots.

https://photos.app.goo.gl/GUxd5Ha5vyEVXMWS9

 

[EWBG29]

I don't have a microphone icon in - despite the Voice Type option enabled. I have been granted microphone permissions in the Gboard application menu - please support. I post screenshots.

https://photos.app.goo.gl/GUxd5Ha5vyEVXMWS9

First:

Do you have Google App installed?
If not please install it and check again.

Second:

If you have Google App and the microphone icon is still missing try the following

1. Go to "text correction" on Gboard and enable "sugestion strips".
2. Make sure "Voice input key" is enable in the preferences section on Gboard (You said it was).
3. Make sure "Google Voice typing is enabled" in Managed Keyboard. (To get here go to setting and search for "language" and click "languages", in laguages click on "virtual keyboards" below keyboards & Inputs, then click on "+ Manage Keyboard" and make sure it is enabled

Those things should work

 

[Bruno M]

@steadfasterX can you release a new version with the Android october security patch. Thanks

 

[steadfasterX]

@steadfasterX can you release a new version with the Android october security patch. Thanks

I will when the patches I'm working on are ready.



Sent from my OnePlus 6T using XDA Labs

 

[steadfasterX]

The proximity sensor during calls is way to sensitive.

With holding it normally to my ear it often happens that i press buttons with my skin.
I cant't say exactly if the touchscreen is still on with the screen turned off in some cases during a call, or if the screen intermittently turns on to register touch input.

Either way it is way to sensitive and I have to resort to turning the screen off with the power button in order not to register unwannted button presses.

Is that how it always was or a new thing?

It is quite a hindrance ;(

do you have a screen protector applied? if so try without. Other then that your sensor might be defective (try another ROM to find out)

.-

 

[I-Immortal]

Hi sfx, thanks for your work and the hosting, very appreciated ! It's really incredible to have Pie running on such an old device that is unsupported by its manufacturer

I want to report an issue, I have random kernel panics and UI reboots sometimes. I think my phone (or UI) always reboot by itself after, no need to take out the battery. The last one (kernel panic) happened when I was browsing Discord, so nothing specific really.

You'll find the pstore/'s content attached to this message.

Wish you a nice day !

 

[steadfasterX]

Hi sfx, thanks for your work and the hosting, very appreciated ! It's really incredible to have Pie running on such an old device that is unsupported by its manufacturer

I want to report an issue, I have random kernel panics and UI reboots sometimes. I think my phone (or UI) always reboot by itself after, no need to take out the battery. The last one (kernel panic) happened when I was browsing Discord, so nothing specific really.

You'll find the pstore/'s content attached to this message.

Wish you a nice day !

The panic occurs because of:

[518629.743629 / 10-31 06:30:26.929][0] SMSM: Modem SMSM state changed to SMSM_RESET.
[518629.743877 / 10-31 06:30:26.929][0] Fatal error on the modem.
[518629.743991 / 10-31 06:30:26.929][0] modem subsystem failure reason: lte_ml1_dlm_rx_cfg.c:12560:Assert (rx_cfg_data_ptr->cur_rx_mask[scc_start_idx].
[518629.744129 / 10-31 06:30:26.929][0] [LGE] MSM Chip info : MSM Chip version 10000 ID fb FML 39.
[518629.744260 / 10-31 06:30:26.929][0] subsys-restart: subsystem_restart_dev(): Restart sequence requested for modem, restart_level = SYSTEM.
[518629.746633 / 10-31 06:30:26.933][0] M-Notify: General: 8
[518629.746780 / 10-31 06:30:26.933][0] lge_disable_watchdog
[518629.747099 / 10-31 06:30:26.933][0] panic in suspend: 0
[518629.747275 / 10-31 06:30:26.933][0] Kernel panic - not syncing: subsys-restart: Resetting the SoC - modem crashed.

This is part of the modem blobs (which I cannot fix).
What is your model and bootloader stack version and your modem partition version?

.-

 

[masemoel]

Just as a curiosity...

@steadfasterX is better to have v29a or v20p bootloader?

 

[ClassicRed]

a big thank you from a French man who thanks to you resurrected his LG G4 h815

So you do a great job

 

[I-Immortal]

The panic occurs because of:



This is part of the modem blobs (which I cannot fix).
What is your model and bootloader stack version and your modem partition version?

.-

Sorry, was away on a trip for the weekend. Thanks for your answer but sadly I don't know how to check the bootloader and modem versions installed on my device

I have a H815.

 

[steadfasterX]

Sorry, was away on a trip for the weekend. Thanks for your answer but sadly I don't know how to check the bootloader and modem versions installed on my device

I have a H815.

Official unlocked or UsU'd?

Sent from my OnePlus 6T using XDA Labs

 

[Heraku]

hey SteadfasterX,

I have two Problems:


1) There is still an echo while using the loudspeaker for the person on the other line


2) When I plug my headset in I get "noises" almost always. only way to solve that is to replug or skip a track. It happens with the music app (GPM) opened/closed/having a song selected or not - doesnt matter
The sound sounds either like a lower frequency white noise or like a lower frequency "sine swipe" <- which is realy wired. So in that case it get louder and also more intense. THe sounds do not exceed a certain volume but I think that they are louder than the set volume and I also cant change the loudness of these sounds wonce they appear with the volume rocker.

 

[steadfasterX]

hey SteadfasterX,

I have two Problems:


1) There is still an echo while using the loudspeaker for the person on the other line


2) When I plug my headset in I get "noises" almost always. only way to solve that is to replug or skip a track. It happens with the music app (GPM) opened/closed/having a song selected or not - doesnt matter
The sound sounds either like a lower frequency white noise or like a lower frequency "sine swipe" <- which is realy wired. So in that case it get louder and also more intense. THe sounds do not exceed a certain volume but I think that they are louder than the set volume and I also cant change the loudness of these sounds wonce they appear with the volume rocker.

I have only one problem: I need logs. Read FAQ #1, follow the guide "specific issue". Ensure you set the life time of the paste to the longest period possible.

.-

 

[Heraku]

I have only one problem: I need logs. Read FAQ #1, follow the guide "specific issue". Ensure you set the life time of the paste to the longest period possible.

.-

sadly my pc stopped recognizing my phone. it will only charge.

ON THIS NOTE: why cant I use a mouse with an OTG adapter on this ROM?

 

[masemoel]

sadly my pc stopped recognizing my phone. it will only charge.

ON THIS NOTE: why cant I use a mouse with an OTG adapter on this ROM?

Driver issue is what you had. I also had that and I solved it by uninstalling a driver that was making a conflict.
Have you tried in another pc??

 

[steadfasterX]

New builds are cooking...

I have added a test in my jenkins build process to ensure that the unified device tree is working as it should.
Unifying our device tree makes it much easier to maintain and to add other not-yet added models - while it comes with the risk something goes wrong when it comes to blobs.

Nevertheless:
I would highly recommend doing the following (I have done that in my manual builds but you get it from jenkins - so there is a tiny little chance of bad luck .. ):

Pre-Cautions | Flashing instructions

1. Recommended: Backup (system, userdata in TWRP, your internal storage which contains your photos etc elsewhere)
2. Required: Do a "REGULAR CLEAN FLASH" (see bottom of this post)
3. Flash LOS - DO NOT choose to reboot afterwards - stay in TWRP.
4. TWRP menu: "Mount" --> choose "System"
5. From a terminal execute:

   adb shell md5sum /system/etc/firmware/venus.mbn

6. Compare the value (last 4 characters is fully enough) with these:
   If you flash:
   h815, f500, h818, h819 it should be: d1f6fe863643b1e8d1e597762474928c
   h810, h811, h812, ls991, us991, vs986 it should be: 78e5cf520d0de4a413ef1cfa7bbbe713
   WARNING: If that checksum is NOT as it should be: DO NOT PANIC! simply FLASH the PREVIOUS LOS version BEFORE booting!. This will ensure you will not blow a fuse.
   While the above test should be considered safe: If you are unsure about this procedure: WAIT before flashing until someone (or I) had done the above quick test from the builds jenkins is providing at my leech server.
7. Whenever an error occurs while flashing in TWRP (e.g "E1001: Failed to update system image.Updater process ended with ERROR: 7")
   or if the above checksum does not match:
   provide the recovery.log (FAQ #4 A)!!
   ... then flash the previous LOS version to get back to life - without harming your device.
8. if instead (as we all expect) all went well and you had opengapps before - ensure you reflash gapps

Cooking order & LIVE cooking view

• H815
• H811
• H815 UsU
• VS986
• H812
• H810

Live - View:

• Normal view: https://shebang.binbash.rocks:8800/...0/job/Build all LGE-G4 models/workflow-stage/
• Blue Ocean: https://shebang.binbash.rocks:8800/...-G4/LOS-16.0/Build all LGE-G4 models/activity (click at the top line )

Noteworthy Changes:

Flashing method: "REGULAR CLEAN FLASH" is REQUIRED!
(See the FAQ #2 of this thread how to do this)

• fixed: video call issue with facebook messenger, google duo, snapchat
  
• fixed: increased sample rate for audio-record (e.g. in use by google duo etc)
  
• new: switching to NFC 1.1 hidl
  
• new: complete re-work of GPS settings (optimizing and fixing several issues)
  
• fixed: crash due to qualcomm iZat crap
  
• new: added signature spoofing for microG support (disabled by default). all details here ( requested by @kinuris )
  
• platform security patch: 2019-10-05
  
  
• reminder: system apps permissions are enforced, too.
  If you convert (e.g by titanium backup) an app to be a system app it may not allow it to boot anymore!
  Apps & tools which provide TWRP flashable zip's should come with proper permissions already but if not LOS will not boot anymore. Good examples are OpenGapps or Magisk which both come with proper privapp permission confs.
  If you (really!) need to convert an app checkout the current integrated permissions before.
  If your app does not come with a flashable TWRP installer you can request to add your app by providing a log (FAQ 1 - option specific issue before starting that app) and I might add it.
  
  
• Full details:
  kernel: commits
  g4-common tree: commits
  g4 unified tree: commits
  closed issues (if any): github issue tracker
  LOS: all merged changes since last build
  

IMPORTANT:

• If you encounter issues try this first:
  

  adb shell
  su
  (or adb root when enabled)
  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)
  
  
• Taking a backup before is recommended - always
  

Keep in mind that almost all pie ROM's sharing the same common device tree (or main parts of it), same model device trees and for sure the same kernel - so you can enjoy most fixes for any pie ROM available.. :victory:

ok enough of words, just one more thing:
flash and enjoy this Google-independent, location aware and simply beautiful new LOS version - ever




Sent from my OnePlus 6T using XDA Labs

 

[breversa]

A big THANK YOU*for your awesome work, @steadfasterX !

Also, I've noticed that though my H815 running lineage-16.0-20190917-UNOFFICIAL-h815 has a flash (don't they all…), apps that require

android.hardware.camera.flash

(such as https://f-droid.org/packages/fr.jnda.android.flashalert/) will complain that it doesn't have it ! However, other apps that use the flash, such as Open Camera (https://f-droid.org/fr/packages/net.sourceforge.opencamera/) or Search Light (https://f-droid.org/fr/packages/com.scottmain.android.searchlight/), work perfectly fine.

Not sure if that's new or not though.

 

[steadfasterX]

sadly my pc stopped recognizing my phone. it will only charge.

ON THIS NOTE: why cant I use a mouse with an OTG adapter on this ROM?

Use FWUL if you have driver issues. That's why it exists ..

Mouse over otg has been disabled months ago in the kernel as no one needed it. If you need it back let me know.

A big THANK YOU*for your awesome work, @steadfasterX !

Also, I've noticed that though my H815 running lineage-16.0-20190917-UNOFFICIAL-h815 has a flash (don't they all…), apps that require (such as https://f-droid.org/packages/fr.jnda.android.flashalert/) will complain that it doesn't have it ! However, other apps that use the flash, such as Open Camera (https://f-droid.org/fr/packages/net.sourceforge.opencamera/) or Search Light (https://f-droid.org/fr/packages/com.scottmain.android.searchlight/), work perfectly fine.

Not sure if that's new or not though.

That's not known but not that surprisingly . We cannot use the flash in some cases (e.g. long press for torch) and so I disabled the faulty part of it. might be related but that might a log show.


Sent from my OnePlus 6T using XDA Labs

 

[jjcdennis]

Thanks steadfasterX, 2 beers on the way (at least in the US).