[ROM][9.0][UNOFFICIAL] [G800F/M/Y] LineageOS 16.0 [Beta] [16-12-2020]

Cynic_Custodian · Jun 17, 2019 3 0 0

Caller can't hear me

First of all thanks for this amazing rom, I absolutely love it.
My wife is less happy though, since she can't hear me when she calls. I would prefer the other way around too, but alas.
I googled it and posted a question on reddit but no solutions yet. I have it at random moments, not always and restarting doesn't always work.
Does anyone have any ideas? Hardware checks succeed every time.

spookcity138 · Aug 10, 2019 at 3:21 PM

Cynic_Custodian said:
First of all thanks for this amazing rom, I absolutely love it.

My wife is less happy though, since she can't hear me when she calls. I would prefer the other way around too, but alas.

I googled it and posted a question on reddit but no solutions yet. I have it at random moments, not always and restarting doesn't always work.

Does anyone have any ideas? Hardware checks succeed every time.

I actually saw your post on reddit and meant to reply but apparently got distracted or something. I have never had this problem, so its hard for me to say. I have however had issues with low volume in calls in every version of Android I've ever used on this phone. Where the other person says they don't hear me well and I need to speak a lot louder to be heard. I've been meaning to look into perhaps adjusting the mic gain,but if your wife can't hear you at all this will not fix anything for you.
I'd be curious to know if when this happens if your mic still works at all. Are you able to record via a voice recorder app?
I know its not the easiest,but if you are somehow able to grab and post a log of this happening it may be helpful. You could use an app like Matlog if you're rooted.

Sent from my SM-G800F using Tapatalk

Cynic_Custodian · Aug 10, 2019

spookcity138 said:
I actually saw your post on reddit and meant to reply but apparently got distracted or something. I have never had this problem, so its hard for me to say. I have however had issues with low volume in calls in every version of Android I've ever used on this phone. Where the other person says they don't hear me well and I need to speak a lot louder to be heard. I've been meaning to look into perhaps adjusting the mic gain,but if your wife can't hear you at all this will not fix anything for you.
I'd be curious to know if when this happens if your mic still works at all. Are you able to record via a voice recorder app?
I know its not the easiest,but if you are somehow able to grab and post a log of this happening it may be helpful. You could use an app like Matlog if you're rooted.

Sent from my SM-G800F using Tapatalk

Thanks for your quick reply. I've read about others having the exact same problem (with LineageOS I think, but not sure).
I am able to hear myself speak via the diagnose app for fairphones, so the mic(s) are working.
Here is the log from the call I made this afternoon:
08-10 13:07:36.345 I/TelecomFramework(1146): UserCallIntentProcessor: sendIntentToDestination: trampoline to Telecom.: [email protected]
08-10 13:07:36.350 I/TelecomFramework(1146): UserCallActivity: onCreate done
08-10 13:07:36.514 V/chatty (2378): uid=1000(system) CallAudioModeSt expire 4 lines
08-10 13:07:36.515 V/chatty (2378): uid=1000(system) uteStateMachine expire 15 lines
08-10 13:07:36.560 V/chatty (2378): uid=1000(system) Binder:2378_7 expire 1 line
08-10 13:07:37.650 I/Telephony(2719): TelephonyConnectionService: onCreateOutgoingConnection, request: ConnectionRequest xxxxxxxxxxxxxxxxxx Bundle[{touchPoint=Point(372, 1030), android.telecom.extra.START_CALL_WITH_VIDEO_STATE=0, android.telecom.extra.CALL_TELECOM_ROUTING_END_TIME_MILLIS=441335214, android.telecom.extra.CALL_TELECOM_ROUTING_START_TIME_MILLIS=441335214}]: (SBC.oSC)->CS.crCo->H.CS.crCo->[email protected]
08-10 13:07:38.074 I/Telephony(2719): TelephonyConnectionService: notifyCreateConnectionComplete [email protected]_1: (...->CSW.hCCC)->CS.crCoC->[email protected]
08-10 13:07:38.077 V/chatty (2378): uid=1000(system) Binder:2378_6 expire 4 lines
08-10 13:07:38.608 I/Telephony(2719): : onDisconnect: [email protected]_1, cause=LOCAL
08-10 13:07:38.635 V/chatty (2378): uid=1000(system) Binder:2378_D expire 9 lines
08-10 13:07:38.665 V/chatty (2378): uid=1000(system) ActivityManager expire 10 lines
08-10 13:07:38.738 V/chatty (2378): uid=1000(system) Binder:2378_D expire 19 lines
08-10 13:07:38.811 V/chatty (2378): uid=1000(system) CallAudioModeSt expire 10 lines
08-10 13:07:38.812 V/chatty (2378): uid=1000(system) uteStateMachine expire 27 lines
08-10 13:07:38.816 V/chatty (2378): uid=1000(system) BluetoothRouteM expire 2 lines
08-10 13:07:39.022 V/chatty (2378): uid=1000(system) ConnectivitySer expire 4 lines
08-10 13:07:39.081 V/chatty (2378): uid=1000 system_server expire 47 lines
08-10 13:07:39.398 V/chatty (2378): uid=1000(system) ActivityManager expire 2 lines
08-10 13:07:39.562 V/chatty (2378): uid=1000(system) android.ui expire 10 lines
08-10 13:07:41.116 V/chatty (2378): uid=1000(system) android.display expire 10 lines
08-10 13:07:41.866 V/chatty (2378): uid=1000(system) android.anim expire 6 lines
08-10 13:07:42.735 V/chatty (2378): uid=1000(system) Binder:2378_4 expire 1 line
08-10 13:07:42.882 W/wificond(2222): Copy constructor is only used for unit tests
08-10 13:07:42.883 W/wificond(2222): Failed to get NL80211_ATTR_EXT_FEATURES
08-10 13:07:42.886 W/wificond(2222): Copy constructor is only used for unit tests
08-10 13:07:42.892 W/wificond(2222): Failed to get NL80211_ATTR_EXT_FEATURES
08-10 13:07:42.895 W/wificond(2222): Copy constructor is only used for unit tests
08-10 13:07:42.896 W/wificond(2222): Failed to get NL80211_ATTR_EXT_FEATURES
08-10 13:07:43.110 V/chatty (2378): uid=1000(system) Binder:2378_1 expire 27 lines
08-10 13:07:43.503 V/chatty (2378): uid=1000(system) Binder:2378_7 expire 1 line
08-10 13:07:45.300 V/chatty (2378): uid=1000(system) Binder:2378_9 expire 1 line
08-10 13:07:45.475 I/TelecomFramework(1146): UserCallIntentProcessor: sendIntentToDestination: trampoline to Telecom.: [email protected]
08-10 13:07:45.480 I/TelecomFramework(1146): UserCallActivity: onCreate done
08-10 13:07:45.678 V/chatty (2378): uid=1000(system) Binder:2378_6 expire 1 line
08-10 13:07:46.482 V/chatty (2378): uid=1000(system) Binder:2378_13 expire 3 lines
08-10 13:07:46.636 V/chatty (2378): uid=1000(system) Binder:2378_11 expire 2 lines
08-10 13:07:46.662 I/Telephony(2719): TelephonyConnectionService: onCreateOutgoingConnection, request: ConnectionRequest xxxxxxxxxxxxxxxxxx Bundle[{touchPoint=Point(269, 717), android.telecom.extra.START_CALL_WITH_VIDEO_STATE=0, android.telecom.extra.CALL_TELECOM_ROUTING_END_TIME_MILLIS=441344723, android.telecom.extra.CALL_TELECOM_ROUTING_START_TIME_MILLIS=441344723}]: (SBC.oSC)->CS.crCo->H.CS.crCo->[email protected]
08-10 13:07:46.938 V/chatty (2378): uid=1000(system) Binder:2378_2 expire 23 lines
08-10 13:07:46.970 V/chatty (2378): uid=1000(system) Binder:2378_F expire 27 lines
08-10 13:07:47.089 I/Telephony(2719): TelephonyConnectionService: notifyCreateConnectionComplete [email protected]_1: (...->CSW.hCCC)->CS.crCoC->[email protected]
08-10 13:07:47.740 I/Telephony(2719): GsmConnection: handleSuppServiceNotification: type=0, code=1
08-10 13:08:00.219 V/chatty (2378): uid=1000(system) Binder:2378_3 expire 2 lines
08-10 13:08:00.319 I/Telephony(2719): : onDisconnect: [email protected]_1, cause=LOCAL

spookcity138 · Aug 11, 2019 at 10:39 AM

Cynic_Custodian said:
Thanks for your quick reply. I've read about others having the exact same problem (with LineageOS I think, but not sure).
I am able to hear myself speak via the diagnose app for fairphones, so the mic(s) are working.
Here is the log from the call I made this afternoon:
08-10 13:07:36.345 I/TelecomFramework(1146): UserCallIntentProcessor: sendIntentToDestination: trampoline to Telecom.: [email protected]
08-10 13:07:36.350 I/TelecomFramework(1146): UserCallActivity: onCreate done
08-10 13:07:36.514 V/chatty (2378): uid=1000(system) CallAudioModeSt expire 4 lines
08-10 13:07:36.515 V/chatty (2378): uid=1000(system) uteStateMachine expire 15 lines
08-10 13:07:36.560 V/chatty (2378): uid=1000(system) Binder:2378_7 expire 1 line
08-10 13:07:37.650 I/Telephony(2719): TelephonyConnectionService: onCreateOutgoingConnection, request: ConnectionRequest xxxxxxxxxxxxxxxxxx Bundle[{touchPoint=Point(372, 1030), android.telecom.extra.START_CALL_WITH_VIDEO_STATE=0, android.telecom.extra.CALL_TELECOM_ROUTING_END_TIME_MILLIS=441335214, android.telecom.extra.CALL_TELECOM_ROUTING_START_TIME_MILLIS=441335214}]: (SBC.oSC)->CS.crCo->H.CS.crCo->[email protected]
08-10 13:07:38.074 I/Telephony(2719): TelephonyConnectionService: notifyCreateConnectionComplete [email protected]_1: (...->CSW.hCCC)->CS.crCoC->[email protected]
08-10 13:07:38.077 V/chatty (2378): uid=1000(system) Binder:2378_6 expire 4 lines
08-10 13:07:38.608 I/Telephony(2719): : onDisconnect: [email protected]_1, cause=LOCAL
08-10 13:07:38.635 V/chatty (2378): uid=1000(system) Binder:2378_D expire 9 lines
08-10 13:07:38.665 V/chatty (2378): uid=1000(system) ActivityManager expire 10 lines
08-10 13:07:38.738 V/chatty (2378): uid=1000(system) Binder:2378_D expire 19 lines
08-10 13:07:38.811 V/chatty (2378): uid=1000(system) CallAudioModeSt expire 10 lines
08-10 13:07:38.812 V/chatty (2378): uid=1000(system) uteStateMachine expire 27 lines
08-10 13:07:38.816 V/chatty (2378): uid=1000(system) BluetoothRouteM expire 2 lines
08-10 13:07:39.022 V/chatty (2378): uid=1000(system) ConnectivitySer expire 4 lines
08-10 13:07:39.081 V/chatty (2378): uid=1000 system_server expire 47 lines
08-10 13:07:39.398 V/chatty (2378): uid=1000(system) ActivityManager expire 2 lines
08-10 13:07:39.562 V/chatty (2378): uid=1000(system) android.ui expire 10 lines
08-10 13:07:41.116 V/chatty (2378): uid=1000(system) android.display expire 10 lines
08-10 13:07:41.866 V/chatty (2378): uid=1000(system) android.anim expire 6 lines
08-10 13:07:42.735 V/chatty (2378): uid=1000(system) Binder:2378_4 expire 1 line
08-10 13:07:42.882 W/wificond(2222): Copy constructor is only used for unit tests
08-10 13:07:42.883 W/wificond(2222): Failed to get NL80211_ATTR_EXT_FEATURES
08-10 13:07:42.886 W/wificond(2222): Copy constructor is only used for unit tests
08-10 13:07:42.892 W/wificond(2222): Failed to get NL80211_ATTR_EXT_FEATURES
08-10 13:07:42.895 W/wificond(2222): Copy constructor is only used for unit tests
08-10 13:07:42.896 W/wificond(2222): Failed to get NL80211_ATTR_EXT_FEATURES
08-10 13:07:43.110 V/chatty (2378): uid=1000(system) Binder:2378_1 expire 27 lines
08-10 13:07:43.503 V/chatty (2378): uid=1000(system) Binder:2378_7 expire 1 line
08-10 13:07:45.300 V/chatty (2378): uid=1000(system) Binder:2378_9 expire 1 line
08-10 13:07:45.475 I/TelecomFramework(1146): UserCallIntentProcessor: sendIntentToDestination: trampoline to Telecom.: [email protected]
08-10 13:07:45.480 I/TelecomFramework(1146): UserCallActivity: onCreate done
08-10 13:07:45.678 V/chatty (2378): uid=1000(system) Binder:2378_6 expire 1 line
08-10 13:07:46.482 V/chatty (2378): uid=1000(system) Binder:2378_13 expire 3 lines
08-10 13:07:46.636 V/chatty (2378): uid=1000(system) Binder:2378_11 expire 2 lines
08-10 13:07:46.662 I/Telephony(2719): TelephonyConnectionService: onCreateOutgoingConnection, request: ConnectionRequest xxxxxxxxxxxxxxxxxx Bundle[{touchPoint=Point(269, 717), android.telecom.extra.START_CALL_WITH_VIDEO_STATE=0, android.telecom.extra.CALL_TELECOM_ROUTING_END_TIME_MILLIS=441344723, android.telecom.extra.CALL_TELECOM_ROUTING_START_TIME_MILLIS=441344723}]: (SBC.oSC)->CS.crCo->H.CS.crCo->[email protected]
08-10 13:07:46.938 V/chatty (2378): uid=1000(system) Binder:2378_2 expire 23 lines
08-10 13:07:46.970 V/chatty (2378): uid=1000(system) Binder:2378_F expire 27 lines
08-10 13:07:47.089 I/Telephony(2719): TelephonyConnectionService: notifyCreateConnectionComplete [email protected]_1: (...->CSW.hCCC)->CS.crCoC->[email protected]
08-10 13:07:47.740 I/Telephony(2719): GsmConnection: handleSuppServiceNotification: type=0, code=1
08-10 13:08:00.219 V/chatty (2378): uid=1000(system) Binder:2378_3 expire 2 lines
08-10 13:08:00.319 I/Telephony(2719): : onDisconnect: [email protected]_1, cause=LOCAL

Thanks for the log. Sadly there is nothing there that jumps out at me as an issue really. I will do a little searching when I have some time and see if I can find anyone who has perhaps had and solved this issue. Maybe with some luck I will stumble upon something useful.

spookcity138 · Aug 11, 2019 at 4:33 PM

Updated

Changelog

Code:

* Synced LOS sources
* Latest security patches (August 2019)
* Merged latest lineageos/hardware/samsung sources into our hardware/samsung repo
* Dozen or so kernel commits
* Updated a bunch of proprietary vendor blobs to latest stock marshmallow
* Updated GPS config (Thanks to @mongo0 for the tip)
* Fixed called forwarding setup crashing/issues (Thanks to @rodman01)
* Added an encryption board flag and overlay ( This is a step towards hopefully solving the encryption issue. However it is highly unlikely that this is fixed. It is just all I could find on the matter. I will continue to look into it)
* Removed patches to keep LiveDisplay - So no more LiveDisplay (Lineage is going with Night Light instead)
* Added "ro.config.small_battery" (This will trigger device-idle in 15
minutes instead of 30 minutes)

Enjoy!

scheichxda · Aug 12, 2009 51 2 8

a-dead-trousers said:
Try it with the latest version. AFAIK there was a bug in the kernel that prevented the sdcard from working properly which should be fixed by now.

So I did with the latest edition 11th August

Still the same

Regards

spookcity138 · Aug 13, 2019 at 3:59 PM

scheichxda said:
So I did with the latest edition 11th August

Still the same

Regards

This is very strange. As mentioned,there was an issue with writing to the externalSD,but this has long since been fixed. I am able to delete,rename,move and any other thing one would need to do with my external SD card. I have no idea why you are not. Is your card formatted to fat32?

ugeins · Aug 13, 2019 at 4:36 PM

For me everything works fine. Also RW access to the SD Card. Thanks.......

Gesendet von meinem SM-G800F mit Tapatalk

scheichxda · Aug 12, 2009 51 2 8

spookcity138 said:

Updated

Changelog

Code:

* Synced LOS sources
* Latest security patches (August 2019)
* Merged latest lineageos/hardware/samsung sources into our hardware/samsung repo
* Dozen or so kernel commits
* Updated a bunch of proprietary vendor blobs to latest stock marshmallow
* Updated GPS config (Thanks to @mongo0 for the tip)
* Fixed called forwarding setup crashing/issues (Thanks to @rodman01)
* Added an encryption board flag and overlay ( This is a step towards hopefully solving the encryption issue. However it is highly unlikely that this is fixed. It is just all I could find on the matter. I will continue to look into it)
* Removed patches to keep LiveDisplay - So no more LiveDisplay (Lineage is going with Night Light instead)
* Added "ro.config.small_battery" (This will trigger device-idle in 15
minutes instead of 30 minutes)

Enjoy!

If I try to encrypt the phone the phone ends up in a boot-loop
Any idea how to avoid this?

Regards

spookcity138 · Aug 14, 2019 at 11:10 AM

scheichxda said:
If I try to encrypt the phone the phone ends up in a boot-loop

Any idea how to avoid this?

Regards

This is a known issue. I added a few things as steps to try to fix this, but as I expected it is still broken. So yeah, encryption just doesn't work. This seems to be an issue with other devices on LOS 16 as well. I will continue to look into this when time permits.

Sent from my SM-G800F using Tapatalk

Nevelet · Aug 14, 2019 6 1 0

Hi, first of all I want to congratulate you on this work, I'm glad you're keeping this project alive. I wanted to know but without "HWC" (Hardware Composer) could I damage any component in my smartphone? Thanks so much!

Marteng69 · Sep 13, 2014 60 16 0

spookcity138 said:
This is a known issue. I added a few things as steps to try to fix this, but as I expected it is still broken. So yeah, encryption just doesn't work. This seems to be an issue with other devices on LOS 16 as well. I will continue to look into this when time permits.

I have installed the latest version with a clean install. Encryption is still not possible. The phone where I tried it still behaves the way I described some posts ago. I can start the process of encryption and it stops after a few seconds.

Kenitilas · Aug 16, 2019 5 1 0

Update & GPS

Hi everyone,

I am new to this forum. I tested the lineage os build from this thread on my old phone to use it as a GPS in my car.
After flashing i recogniced some anomalies. At first I don't have any update menu on this phone. Second the GPS is not working. I tried it on some navigation apps and with some sensor analysing apps. No GPS signal was found.
Can anyone help me? I tried to use the search function without any result.

TY Kenitilas

spookcity138 · Aug 17, 2019 at 3:48 PM

Nevelet said:
Hi, first of all I want to congratulate you on this work, I'm glad you're keeping this project alive. I wanted to know but without "HWC" (Hardware Composer) could I damage any component in my smartphone? Thanks so much!

Well, I am never going to say it is impossible because strange things happen. That said it is very unlikely and I don't personally see how. The only real effect of not having working hardware composition should be a slight battery hit and perhaps small performance hit. Although neither of these things I notice. Basically without the HWC we are just relying solely on the GPU for screen composition.

Marteng69 said:
I have installed the latest version with a clean install. Encryption is still not possible. The phone where I tried it still behaves the way I described some posts ago. I can start the process of encryption and it stops after a few seconds.

Thanks for the feedback. I kinda assumed this was going to be the case. I will add it as a non working feature in the main post and continue to try to figure out what the fix may be.

Kenitilas said:
Hi everyone,

I am new to this forum. I tested the lineage os build from this thread on my old phone to use it as a GPS in my car.
After flashing i recogniced some anomalies. At first I don't have any update menu on this phone. Second the GPS is not working. I tried it on some navigation apps and with some sensor analysing apps. No GPS signal was found.
Can anyone help me? I tried to use the search function without any result.

TY Kenitilas

Hmm,strange. While GPS is far from perfect in this ROM it does work for me. I will try to look into improving it some when I have some time.

Kenitilas · Aug 16, 2019 5 1 0

spookcity138 said:
Hmm,strange. While GPS is far from perfect in this ROM it does work for me. I will try to look into improving it some when I have some time.

It's possible that the GPS problem is based on my phone. Today I tried the LOS 14, LOS 15 and 2 stock roms. GPS never worked.. so I guess its something wrong with the antenna

spookcity138 · Aug 17, 2019 at 4:54 PM

Kenitilas said:
It's possible that the GPS problem is based on my phone. Today I tried the LOS 14, LOS 15 and 2 stock roms. GPS never worked.. so I guess its something wrong with the antenna

Thanks a lot for the follow up. I'm afraid it does sound like an issue with your device if you're having GPS issues with all of these different ROMS.

Sent from my SM-G800F using Tapatalk

Kenitilas · Aug 16, 2019 5 1 0

[/COLOR]

spookcity138 said:
Thanks a lot for the follow up. I'm afraid it does sound like an issue with your device if you're having GPS issues with all of these different ROMS.

After flashing all those ROMS I wanted to go back to your android 9 build just because its the latest, fastest and best (thank you!!), but now I am getting an ERROR 7 while flashing with TWRP. Any solutions?

fidoedidoe · Aug 18, 2019 at 2:55 PM

Kenitilas said:
[/COLOR]

After flashing all those ROMS I wanted to go back to your android 9 build just because its the latest, fastest and best (thank you!!), but now I am getting an ERROR 7 while flashing with TWRP. Any solutions?

I've seen this in the distant past. Check you're using the latest version or TWRP (3.3.1) and try again. Failing that maybe check md5 of ROM before installing.

Kenitilas · Aug 16, 2019 5 1 0

fidoedidoe said:
I've seen this in the distant past. Check you're using the latest version or TWRP (3.3.1) and try again. Failing that maybe check md5 of ROM before installing.

ok I did the following steps:

1. I installed the latest stock ROM to have the "latest" vendor
2. check MD5 (as always -> matched)
3. Flash TWRP (3.3.1) -> latest
4. wipe system
5. install LOS

--> Ending up again with an error 7

(I also tried a LOS 14 and LOS 15 version: both worked for my phone)

fidoedidoe · Aug 18, 2019 at 4:49 PM

Kenitilas said:
ok I did the following steps:

1. I installed the latest stock ROM to have the "latest" vendor
2. check MD5 (as always -> matched)
3. Flash TWRP (3.3.1) -> latest
4. wipe system
5. install LOS

--> Ending up again with an error 7

(I also tried a LOS 14 and LOS 15 version: both worked for my phone)

If memory serves me...error 7 has something to do with the "assert" in the updater script used by the rom installation. If you open the zip, and drill into the folder structure you'll see the updater script is checking you have the correct hardware to install on...you can edit the script to remove the check...but that carries a risk. Are you sure you have the right variant of TWRP for your hardware?..if you're confident everything is good then like I say update the script...but please do double/triple check first..as flashing into wrong hardware is dangerous (brick)

Edit:
Further reading: https://android-fix.com/android-errors/61-status-error-7-twrp.html

[ROM][9.0][UNOFFICIAL] [G800F/M/Y] LineageOS 16.0 [Beta] [16-12-2020]

New member

Senior Member

New member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Member

Senior Member

Member

Senior Member

Member

Senior Member

Member

Senior Member