[OFFICIAL][a3xelte][SM-A310F]Lineage OS 17.1 for A3 2016 - Galaxy A3, A5, A7, A8, A9 Original Android Develop

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
LineageOS 17.1 is a free, community built, aftermarket firmware distribution of Android 10.0, which is designed to increase performance and reliability over stock Android for your device. The port for the Exynos7580 based devices was created by @Stricted and I along with many contributions from other people in the Android community.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What worksCalls, SMS, Mobile Data
Camera
NFC
WiFi
Bluetooth
Torch
Sensors
GPS
SELinux Enforcing
HWC​What doesn't work
IMS services (VoLTE, VoWiFi, etc). Samsung has their own proprietary implementation. It is not really possible to easily port that to LineageOS.
WiFi tether (hotspot) not functional (fixed in 21/01/2020 release)
HD headsets in call not working (fixed in 21/01/2020 release)
NFC HCE (GooglePay etc) fixed in 07/03/2020 release
You tell me!​There are still quite a few features that are not yet completed for LineageOS 17.1, these are not bugs this is a beta release.
Any hardware related issues will be ignored if you do not provide:
a) Logcat
b) proc/last_kmsg
c) data/tombstones
d) dmesg
Also do not under any circumstances post bug reports if you are using substratum themes or unsupported magisk modules or you have performed any system modifications
Installation
Install the latest TWRP (Available Here)
Make a full backup (just in case something goes wrong)
Do a full wipe (Cache, Data, System)
If this is your first time on a LineageOS ROM format data
Download the latest LOS build and transfer it to your phone
Install LOS
If you are installing GApps do it at the same time (preferably in the same install queue)
And finally boot, the first boot can take several minutes as it optimises all the apps
Do NOT install the TWRP app when prompted, this will cause a bootloop​ Downloads
Latest official releases HERE
Latest unofficial releases HERE
OpenGapps HERE
Flashable recoveries: HERE
TWRP is availableHERE
Magisk is available HERE​Thanks
@Stricted
@l-0-w
@sekil
@alexax66
@macs18max (BT call audio fix)
@Borduni
All the testers on the Discord group (https://discord.gg/8fp9cr7)
And all others who have contributed to the Exynos projects past and present​A special thanks to my donorsMarkus Anders
@D4ND310
@epicwilmo
@tyson
@thebinf
@Herti
@pixelou
@xavier66
And any that I missed ​
XDA:DevDB Information
Lineage OS 17.1 for A3 2016, ROM for the Samsung Galaxy A Series
Contributors
danwood76, stricted
Source Code: https://github.com/LineageOS
ROM OS Version: Android 10
Based On: LineageOS
Version Information
Status: Beta
Created 2020-01-17
Last Updated 2020-05-29​

Unofficial change log below:
Code:
Changes in the LineageOS 16/05/2020 release:
[INDENT]-Fixed mediaserver shim to solve boot crash introduced by last update
- Synced to latest LOS[/INDENT]
Changes in the LineageOS 13/05/2020 release:
[INDENT]- Fixed ringtone routing when headset is plugged in (thanks @stricted)
- Synced to latest LOS (including May security patch)
[/INDENT]Changes in the LineageOS Recovery 13/05/2020 release:
[INDENT]- Synced to latest source
- Added my signing keys to the zip verification function
[/INDENT]Changes in the twrp-a3xelte-3.3.1-0-danwood76 release:
[INDENT]- Synced to latest TWRP 8.1 source
- Added selinux labelling to system_root to fix broken backup restore
[/INDENT]
Older changes listed below:
Code:
Changes in the 12/04/2020 release:
[INDENT]- Disable rounded corner animations (thanks @dariotr)
- Cleanup overlays (thanks @dariotr)
- Switched to new BSP to solve licensing issues (thanks @stricted)
- Synced to latest LOS (including April security patch)
- Uploaded LineageOS recovery
[/INDENT]
Code:
Changes in the 12/03/2020 release:
[INDENT]-Added mounting of ext4 formatted SD cards
-Synced to latest LOS (including March security patch)
[/INDENT]
Code:
Changes in the 07/03/2020 release:
[INDENT]-Fixed NFC HCE (Google Pay should now work)
-Synced to latest LOS
[/INDENT]
Code:
Changes in the 29/02/2020 release:
[INDENT]-Disabled WiFi MAC randomisation
-Synced to latest LOS
[/INDENT]
Code:
Changes in the 16/02/2020 release:
[INDENT]-Switched to new HIDL power HAL
-Synced to latest LOS (including February security patch)
[/INDENT]
Code:
Changes in the 10/02/2020 release:
[INDENT]-Fixed Bluetooth audio config
[/INDENT]
Code:
Changes in the 08/02/2020 release:
[INDENT]-Re-enabled SELinux (had it disabled during testing)
-Fixed some of the bitrates in the audio config (fixes the robot voice in whatsapp messages)
[/INDENT]
Code:
Changes in the 07/02/2020 release:
[INDENT]-Fixed GPSD location in RIL blobs (thanks @alexax66)
-Synced to latest LOS
[/INDENT]
Code:
Changes in the 21/01/2020 release:
[INDENT]- WBS BT calling is fixed
- WiFi hotspot fixed
LOS Updates including:
- Ambient display settings now visible
- System profiles
- Dark mode fixes
[/INDENT]
Code:
Changes in the 17/01/2020 release:
[INDENT]
[*]Initial release
[/INDENT]

Reserved

Well done! I'll probably try it out too.

Hi danwood76,
thank you for LOS17!
I´ve just installed installed it but it doesn´t start. i can only the see the boot animation and nothing more happens.
I´m waiting now about 1 hour ....
What can I do now?
Thank you for your work so far!!!!
Regards
Toemmel

Hello Dan,
Just installed this rom with Opengapps 10 BETA pico and Magisk 20.3. Got it up and running within 5 minutes, clean flash.
Haven't found any error on installation, running very nice.

Hi!
Just tested it. Everything I tested worked fine so far. Switched back to my backup of LOS 16, as I am still waiting for the official release which should arrive soon I hope. Don't want to setup my phone from scratch several times.
Thanks for all your efforts!

Congratulations Dany just installed and everything works for me is perfect, the problem I found was only in the gapps, he does not install the error. but LOS17 is perfect. my model is a310m

Toemmel said:
Hi danwood76,
thank you for LOS17!
I´ve just installed installed it but it doesn´t start. i can only the see the boot animation and nothing more happens.
I´m waiting now about 1 hour ....
What can I do now?
Thank you for your work so far!!!!
Regards
Toemmel
Click to expand...
Click to collapse
How did you install?
You won't be able to update from official builds (without a resigning script and some luck)

Wiltoncandido said:
Congratulations Dany just installed and everything works for me is perfect, the problem I found was only in the gapps, he does not install the error. but LOS17 is perfect. my model is a310m
Click to expand...
Click to collapse
I tested the latest Pico and nano opengapps beta from the link in the OP and both work fine.

The mistake was mine, I was installing the gapps along with LOS17 I did the separate installation and everything worked out. thanks

Wiltoncandido said:
The mistake was mine, I was installing the gapps along with LOS17 I did the separate installation and everything worked out. thanks
Click to expand...
Click to collapse
Ok, The order is important.
1st ROM
2nd Gapps
3rd Magisk
Good that it is now working!

Thanks thanks man I thought my a3 was abondond in 2020

danwood76 said:
How did you install?
You won't be able to update from official builds (without a resigning script and some luck)
Click to expand...
Click to collapse
I was in your official LOS16. So I can't update to unofficial LOS17?
Or did I misunderstood something?
Thank you for yozr work that you did so far!!!!!
Regards
Toemmel

Toemmel said:
I was in your official LOS16. So I can't update to unofficial LOS17?
Or did I misunderstood something?
Thank you for yozr work that you did so far!!!!!
Regards
Toemmel
Click to expand...
Click to collapse
When lineageos 17.1 is finally released you can go official 16.0 to official 17.1 but this is an unofficial release.
In the install instructions I said to make a backup, erase, and install. That is what you need to do to run this build.

Hi, I noticed that 1 beta does not work hotspot, + Russian is not fully translated. thanks.

danwood76 said:
XDA:DevDB Information
Lineage OS 17.1 for A3 2016, ROM for the Samsung Galaxy A Series
Contributors
danwood76, stricted
Source Code: https://github.com/LineageOS
ROM OS Version: Android 10
Based On: LineageOS
Version Information
Status: Beta
Created 2020-01-17
Last Updated 2020-01-17
Click to expand...
Click to collapse
Dima464473 said:
Hi, I noticed that 1 beta does not work hotspot, + Russian is not fully translated. thanks.
Click to expand...
Click to collapse
logcat with this bug:
Code:
01-20 02:04:25.627 2637 2753 D WifiActiveModeWarden: Starting SoftApModeManager
01-20 02:04:25.629 2637 2753 I android_os_HwBinder: HwBinder: Starting thread pool for getting: [email protected]::IWifi/default
01-20 02:04:25.632 2418 2418 W libc : Unable to set property "wifi.active.interface" to "": error code: 0x18
01-20 02:04:25.632 2418 2418 E [email protected]: Failed to set active wlan iface name property: Success
01-20 02:04:25.632 2418 2418 I [email protected]: Wifi HAL started
01-20 02:04:25.632 2637 2753 I WifiVendorHal: Vendor Hal started successfully
01-20 02:04:25.633 2276 2276 I hwservicemanager: getTransport: Cannot find entry [email protected]::IHostapd/default in either framework or device manifest.
01-20 02:04:25.635 2637 2753 D HostapdHal: Successfully triggered start of hostapd using HIDL
01-20 02:04:25.635 2637 2754 I WifiP2pNative: Registering for interface available listener
01-20 02:04:25.639 2637 2754 I WifiP2pNative: Registering for interface available listener
01-20 02:04:25.639 2637 2754 D WifiP2pNative: P2P InterfaceAvailableListener true
01-20 02:04:25.640 2637 2754 D WifiP2pService: Wifi enabled=false, P2P Interface availability=true, Number of clients=0
01-20 02:04:25.640 2637 2754 D WifiP2pService: Wifi enabled=false, P2P Interface availability=true
01-20 02:04:25.691 6430 6430 I hostapd : Processing hidl events on FD 3
01-20 02:04:25.693 2276 2276 I hwservicemanager: getTransport: Cannot find entry [email protected]::IHostapd/default in either framework or device manifest.
01-20 02:04:25.694 2637 6428 I android_os_HwBinder: HwBinder: Starting thread pool for getting: [email protected]::IHostapd/default
01-20 02:04:25.695 2276 2276 I hwservicemanager: getTransport: Cannot find entry [email protected]::IHostapd/default in either framework or device manifest.
01-20 02:04:25.695 2637 6428 I HostapdHal: Completed initialization of IHostapd.
01-20 02:04:26.255 2637 2655 I EthernetTracker: interfaceLinkStateChanged, iface: wlan0, up: true
01-20 02:04:26.260 2418 2418 I WifiHAL : Initializing wifi
01-20 02:04:26.260 2418 2418 I WifiHAL : Creating socket
01-20 02:04:26.266 2418 2418 I WifiHAL : Initialized Wifi HAL Successfully; vendor cmd = 103
01-20 02:04:26.267 2418 2418 I [email protected]: Adding interface handle for p2p0
01-20 02:04:26.267 2418 2418 I [email protected]: Adding interface handle for wlan0
01-20 02:04:26.267 2418 2418 W [email protected]: No active wlan interfaces in use! Using default
01-20 02:04:26.267 2418 2418 E [email protected]: Failed to register radio mode change callback
01-20 02:04:26.267 2418 2418 W [email protected]: No active wlan interfaces in use! Using default
01-20 02:04:26.267 2418 2418 E WifiHAL : Failed to register debug response; result = -95
01-20 02:04:26.267 2418 2418 E [email protected]: Failed to get driver version: SUCCESS
01-20 02:04:26.268 2418 2418 I [email protected]: Configured chip in mode 1
01-20 02:04:26.268 2418 2418 W [email protected]: No active wlan interfaces in use! Using default
01-20 02:04:26.271 2418 2418 W libc : Unable to set property "wifi.active.interface" to "wlan0": error code: 0x18
01-20 02:04:26.272 2418 2418 E [email protected]: Failed to set active wlan iface name property: Success
01-20 02:04:26.272 2637 2753 D HalDevMgr: updateRttController: no one is interested in RTT controllers
01-20 02:04:26.273 2418 2418 I [email protected]: AP MAC randomization enabled
01-20 02:04:26.959 2637 2655 I EthernetTracker: interfaceLinkStateChanged, iface: wlan0, up: false
01-20 02:04:26.961 2637 2655 I EthernetTracker: interfaceLinkStateChanged, iface: wlan0, up: false
01-20 02:04:27.487 2637 2655 I EthernetTracker: interfaceLinkStateChanged, iface: wlan0, up: true
01-20 02:04:27.489 2418 2418 W libc : Unable to set property "wifi.active.interface" to "wlan0": error code: 0x18
01-20 02:04:27.489 2418 2418 E [email protected]: Failed to set active wlan iface name property: Success
01-20 02:04:27.497 2637 2754 D WifiP2pNative: P2P InterfaceAvailableListener false
01-20 02:04:27.497 2637 2754 D WifiP2pService: Wifi enabled=false, P2P Interface availability=false
01-20 02:04:27.500 2637 2753 D WificondControl: Setting up interface for soft ap mode
01-20 02:04:27.503 2402 2402 I netd : interfaceGetCfg("wlan0") <0.54ms>
01-20 02:04:27.504 2637 2753 I WifiNative: Interface state changed on Iface:{Name=wlan0,Id=4,Type=AP}, isUp=true
01-20 02:04:27.504 2637 2753 I WifiNative: Successfully setup Iface:{Name=wlan0,Id=4,Type=AP}
01-20 02:04:27.505 2276 2276 I hwservicemanager: getTransport: Cannot find entry [email protected]::ISupplicant/default in either framework or device manifest.
01-20 02:04:27.505 2637 2753 E SupplicantStaIfaceHal: Method getKeyMgmtCapabilities is not supported in existing HAL
01-20 02:04:27.506 2418 2418 E WifiHAL : Failed to register debug response; result = -95
01-20 02:04:27.511 2637 2637 D WifiService: handleWifiApStateChange: currentState=12 previousState=11 errorCode= -1 ifaceName=wlan0 mode=1
01-20 02:04:27.533 2476 2476 W wificond: Failed to get NL80211_ATTR_EXT_FEATURES
01-20 02:04:27.536 2276 2276 I hwservicemanager: getTransport: Cannot find entry [email protected]::IHostapd/default in either framework or device manifest.
01-20 02:04:27.537 2637 2753 E HostapdHal: IHostapd.addAccessPoint failed: 1,
01-20 02:04:27.537 2637 2753 E WifiNative: Failed to add acccess point
01-20 02:04:27.537 2637 2753 E SoftApManager: Soft AP start failed
01-20 02:04:27.538 2800 2800 I ConnectivityManager: stopTethering caller:com.android.systemui
01-20 02:04:27.539 2637 2637 D WifiService: handleWifiApStateChange: currentState=14 previousState=12 errorCode= 0 ifaceName=wlan0 mode=1
01-20 02:04:27.539 2637 2753 W WifiDiags: ifaceName: wlan0 is not in the start log user list
01-20 02:04:27.539 2637 2637 D WifiService: updateInterfaceIpState: ifaceName=null mode=-1 previous mode= -1
01-20 02:04:27.539 2637 2637 E WifiController: SoftAP start failed
01-20 02:04:27.539 2637 5326 I WifiService: stopSoftAp uid=1000
01-20 02:04:27.540 2637 2657 I Tethering: [EntitlementManager] removeDownstreamMapping: 0
01-20 02:04:27.542 2418 2418 W [email protected]: No active wlan interfaces in use! Using default
01-20 02:04:27.544 2418 2418 W libc : Unable to set property "wifi.active.interface" to "wlan0": error code: 0x18
01-20 02:04:27.544 2418 2418 E [email protected]: Failed to set active wlan iface name property: Success
01-20 02:04:27.545 6430 6430 E hostapd : Removing interface wlan0 failed
01-20 02:04:27.545 2637 2753 E HostapdHal: IHostapd.removeAccessPoint failed: 1,
01-20 02:04:27.546 2637 2753 E WifiNative: Failed to remove access point on Iface:{Name=wlan0,Id=4,Type=AP}
01-20 02:04:28.199 2637 2655 I EthernetTracker: interfaceLinkStateChanged, iface: wlan0, up: false
01-20 02:04:28.200 6430 6430 I hostapd : Terminating...
01-20 02:04:28.200 6430 6430 W hw-IPCThreadState: Calling IPCThreadState::self() during shutdown is dangerous, expect a crash.
01-20 02:04:28.200 6430 6430 W hw-IPCThreadState: Calling IPCThreadState::self() during shutdown is dangerous, expect a crash.
01-20 02:04:28.250 2637 2753 W HostapdHal: Timed out waiting for confirmation of hostapd death
01-20 02:04:28.250 2637 2753 D WificondControl: tearing down interfaces in wificond
01-20 02:04:28.253 2418 2418 W libc : Unable to set property "wifi.active.interface" to "": error code: 0x18
01-20 02:04:28.254 2418 6432 E WifiHAL : wifi_event_loop: Read after POLL returned 4, error no = 0 (Success)
01-20 02:04:28.254 2418 6432 D WifiHAL : Got a signal to exit!!!
01-20 02:04:28.254 2418 6432 I WifiHAL : Exit wifi_event_loop
01-20 02:04:28.254 2418 2418 E WifiHAL : wifi_cleanup: Read after POLL returned 4, error no = 0 (Success)
01-20 02:04:28.254 2418 2418 E WifiHAL : Event processing terminated
01-20 02:04:28.254 2418 2418 E [email protected]: Failed to set active wlan iface name property: Success
01-20 02:04:28.254 2418 2418 I [email protected]: Legacy HAL stop complete callback received
01-20 02:04:28.255 2418 2418 I WifiHAL : Internal cleanup completed
01-20 02:04:28.258 2637 2673 D HostapdHal: IHostapd died: cookie=-4625717533501100423
01-20 02:04:28.259 2418 2418 I [email protected]: Wifi HAL stopped
01-20 02:04:28.260 2637 2753 I WifiVendorHal: Vendor Hal stopped
01-20 02:04:28.260 2637 2753 I WifiNative: Successfully torn down Iface:{Name=wlan0,Id=4,Type=AP}
01-20 02:04:28.260 2637 2753 E HalDevMgr: getAllChipInfo: called but mWifi is null!?
01-20 02:04:28.260 2637 2753 E HalDevMgr: dispatchAvailableForRequestListeners: no chip info found
01-20 02:04:28.260 2637 2753 W HalDevMgr: stopWifi called but mWifi is null!?
01-20 02:04:28.260 2637 2753 I WifiNative: Successfully initiated teardown for iface=wlan0
01-20 02:04:28.260 2637 2753 D SoftApManager: Soft AP is stopped
01-20 02:04:28.260 2637 2754 W HalDevMgr: isWifiStarted called but mWifi is null!?
01-20 02:04:28.261 2637 2753 E WifiNative: Could not get Iface object for interface null
01-20 02:04:28.261 2637 2753 W HalDevMgr: isWifiStarted called but mWifi is null!?
01-20 02:04:28.261 2637 2753 W HalDevMgr: isWifiStarted called but mWifi is null!?
01-20 02:04:28.269 2637 2753 W HostapdHal: IHostapd/IHostapd died: cookie=4
01-20 02:04:28.269 2637 2753 W HalDevMgr: isWifiStarted called but mWifi is null!?

Thanks @alexax66 I will look into it tomorrow, I obviously can't do anything about Russian translation but I would urge you to submit correct translations via gerrit.
Regards,
Danny

Hi,
I tried to install the ROM with OpenGapps Pico (version January 16th, 2020) but after a couple of minutes into the initial booting process it returned to the recovery. The problem seems to be Gapps-related since the system booted just fine without Gapps installed. I wiped cache, data and system prior to the installation and am on the latest TWRP 3.3.0. I first installed the ROM and then OpenGapps in the same install queue (no Magisk). My models is a A310F.
Am I missing something essential?
Best regards,
thebinf

thebinf said:
Hi,
I tried to install the ROM with OpenGapps Pico (version January 16th, 2020) but after a couple of minutes into the initial booting process it returned to the recovery. The problem seems to be Gapps-related since the system booted just fine without Gapps installed. I wiped cache, data and system prior to the installation and am on the latest TWRP 3.3.0. I first installed the ROM and then OpenGapps in the same install queue (no Magisk). My models is a A310F.
Am I missing something essential?
Best regards,
thebinf
Click to expand...
Click to collapse
Odd, that is the same version OpenGapps I tested with and it worked fine. Try re-downloading it, maybe the download is corrupted?

Related

WiFi Issue - Not Turning On

Okay, so I've had this problem for a while now and for a while, I just used 3G, but then moved to using a different phone. But now I'm fed up of using my other phone, as it's no where near as good as the DNA, I'm looking to see if I can fix the problem.
Anyway, the problem is that I can't turn WiFi on. I flick the switch and it gets stuck at "Turning on Wi-Fi...".
(It's definitely a problem device side because I can't even see a list of networks or anything)
I'm currently unlocked, S-OFF. I've tried flashing different ROMs/kernels and even flashed back to complete stock. I've tried WiFi Fixer and WFix Manager with no luck.
I also opened the thing up to see if the cable was loose, but seems to be okay - could it be a board issue or something? If it even is a hardware issue?
Anyway, I thought a logcat may turn up some useful information, but I don't really know what I'm doing when it comes to understanding logcats. So perhaps there is someone that can make more of it:
Code:
--------- beginning of /dev/log/main
W/HtcNativeFlag( 8525): Fail to get flag string for type 'customer', use default value
W/HtcNativeFlag( 8525): Fail to get flag for type 'customer', use default value: -1
W/HtcNativeFlag( 8525): Fail to get flag string for type 'language', use default value
W/HtcNativeFlag( 8525): Fail to get flag for type 'language', use default value: -1
V/HtcDLNAServiceManager( 706): Settings:Agentname: wifi_on
V/HtcDLNAServiceManager( 706): Settings:Agentvalue: 1
V/Settings:Agent( 706): >> traceCallingStack()
V/Settings:Agent( 706): Process.myPid(): 706
V/Settings:Agent( 706): Process.myTid(): 1926
V/Settings:Agent( 706): Process.myUid(): 1000
V/Settings:Agent( 706):
V/Settings:Agent( 706):
W/System.err( 706): java.lang.Throwable: stack dump
W/System.err( 706): at java.lang.Thread.dumpStack(Thread.java:497)
W/System.err( 706): at android.provider.Settings$HtcISettings$Agent.traceCallingStack(Settings$HtcISettings.java:56)
W/System.err( 706): at android.provider.Settings$HtcIGlobal$Agent.monitorKey(Settings$HtcIGlobal.java:62)
W/System.err( 706): at android.provider.Settings$Global.putStringForUser(Settings.java:5673)
W/System.err( 706): at android.provider.Settings$Global.putString(Settings.java:5660)
W/System.err( 706): at android.provider.Settings$Global.putInt(Settings.java:5754)
W/System.err( 706): at com.android.server.wifi.WifiSettingsStore.persistWifiState(WifiSettingsStore.java:155)
W/System.err( 706): at com.android.server.wifi.WifiSettingsStore.handleWifiToggled(WifiSettingsStore.java:106)
W/System.err( 706): at com.android.server.wifi.WifiService.setWifiEnabled(WifiService.java:893)
W/System.err( 706): at android.net.wifi.IWifiManager$Stub.onTransact(IWifiManager.java:170)
W/System.err( 706): at android.os.Binder.execTransact(Binder.java:388)
W/System.err( 706): at dalvik.system.NativeStart.run(Native Method)
V/Settings:Agent( 706):
V/Settings:Agent( 706): << traceCallingStack(): 2(ms)
--------- beginning of /dev/log/system
D/WifiService( 706): setWifiEnabled: true pid=8525, uid=0
E/WifiService( 706): Invoking mWifiStateMachine.setWifiEnabled
I/WifiService( 706): isSprintWifiRestricted(): false
I/WifiService( 706): isMdmWifiRestricted(): false
D/WifiSettingsStore( 706): [SetWifiStatePersist] IsWifiStatePersist: true, persist : true
E/WifiHW ( 225): Failed to open wlan fw path param (No such file or directory)
E/SoftapController( 225): Softap fwReload failed
E/WifiStateMachine( 706): Failed to reload STA firmware java.lang.IllegalStateException: command '14 softap fwreload wlan0 STA' failed with '400 14 SoftAP command has failed'
D/PMS ( 706): acquireWL(48e3edf0): PARTIAL_WAKE_LOCK WifiStateMachine 0x1 706 1000
D/PMS ( 706): releaseWL(48e3edf0): PARTIAL_WAKE_LOCK WifiStateMachine 0x1
W/CommandListener( 225): Failed to retrieve HW addr for wlan0 (No such device)
D/libc ( 706): [NET] getaddrinfo+,hn 7(0x302e302e302e30),sn(),family 0,flags 4
D/libc ( 706): [NET] getaddrinfo-, SUCCESS
E/WifiStateMachine( 706): Unable to change interface settings: java.lang.IllegalStateException: command '16 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 16 Failed to set address (No such device)'
D/WirelessDisplayService( 706): WifiReceiver: action:android.net.wifi.WIFI_STATE_CHANGEDstate1
I/QuickSettingWifi( 1518): receive.wifiState:WIFI_STATE_ENABLING setEnable:false
D/WIFI_ICON( 1518): updateWifiState: WIFI_STATE_CHANGED disabled
D/StatusBar.NetworkController( 1518): dumpIcon[(gone) stat_sys_5signal_null|null (gone) stat_sys_no_sim F (gone)]
D/WifiNative-wlan0( 706): connectToSupplicant, iface=wlan0
I/wpa_supplicant( 8557): Successfully initialized wpa_supplicant
I/wpa_supplicant( 8557): NetworkSelection(WPA_SUPPLICANT) version: 1.b.2
I/wpa_supplicant( 8557): rfkill: Cannot open RFKILL control device
E/wpa_supplicant( 8557): nl80211: Could not configure driver to use managed mode
E/wpa_supplicant( 8557): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 8557): wlan0: Failed to initialize driver interface
E/wpa_supplicant( 8557): wlan0: BLACKLIST CLEAR
E/wpa_supplicant( 8557): wlan0: BLACKLIST REMOVE 00:00:00:00:00:00
I/battery-calibration( 8576): *** LEVEL: 87 CUR: -4500 ***: sleeping for 120 s...
Is there anything in there that would suggest it's a hardware issue, or a software issue?
If you think you need more information from me to help solve, just ask! And any help would be greatly appreciated!
What's your current radio/baseband version?
Have you updated the radio and/or firmware so that they match the software version you are trying to run?
If you have updated, are you just updating the radio or the firmware too?
Thanks for the quick reply,
My current radio is: 1.01.01.1112
I'm running: ~NuSenseONE~ Max Dlx RC1.8
They should work together, right?
But I still have the problem when I'm running stock Sense 4 and stock radio with or without unlock/s-off/etc.
I've been messing around all day, flashing different ROMs, kernels, radios, recoveries... Just everything I can think of.
I've attached the output of dmesg from boot. With that and the logcat, is it possible to determine if this is a software issue, or a hardware issue. Because if it's a hardware issue, I can stop fussing over this thing.
Why don't you post this in the rom thread?
thayl0 said:
Why don't you post this in the rom thread?
Click to expand...
Click to collapse
According to his posts, it happens on any rom, so it's not rom specific.
Sounds like hardware failure.
Out of interest, which part of the hardware is responsible for the WiFi?
Would it be possible to replace this myself?
If not, it's not the end of the world. I'm just interested to know.
jcsawyer said:
Out of interest, which part of the hardware is responsible for the WiFi?
Would it be possible to replace this myself?
If not, it's not the end of the world. I'm just interested to know.
Click to expand...
Click to collapse
Try putting the device back to stock config. At that point it may take several factory resets to trip the wi fi
Did you ever find a fix? I have the same problem, with the same stack trace.

[CM13] No WiFi after reboot

Hi,
a have a very strange problem with my Wifi. I cant switch it on.
When I install a new nightly build of CM via TWRP wifi is working like a charm. But after a reboot the toggle WLAN doesnt work. Hotspot creation isnt working either.
I already tried:
- setting wifi_display_on on settings.db to 1 --> no effect at all
I tried to get more info from logcat with "adb logcat". When I type "su \ svc wifi enable" the log is showing:
08-23 08:59:46.177 8067 8067 D AndroidRuntime: Calling main entry com.android.commands.svc.Svc
08-23 08:59:46.177 1982 1982 E SELinux : avc: denied { find } for service=wifi scontext=u:r:sudaemon:s0 tcontext=ubject_r:wifi_service:s0 tclass=service_manager
08-23 08:59:46.182 2374 2686 D WifiService: setWifiEnabled: true pid=8067, uid=0
08-23 08:59:46.182 2374 2686 E WifiService: Invoking mWifiStateMachine.setWifiEnabled
08-23 08:59:46.182 2374 2513 E WifiMonitor: killSupplicant p2ptrue init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown
08-23 08:59:46.182 8067 8067 D AndroidRuntime: Shutting down VM
08-23 08:59:46.232 2374 2513 E WifiStateMachine: Failed to load driver
08-23 08:59:46.232 2374 2374 E WifiService: Wi-Fi state is failed
08-23 08:59:46.232 2374 2374 D WifiService: setWifiEnabled: false pid=2374, uid=1000
08-23 08:59:46.232 2374 2374 E WifiService: Invoking mWifiStateMachine.setWifiEnabled
08-23 08:59:46.237 2374 2513 E WifiMonitor: killSupplicant p2ptrue init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown
08-23 08:59:46.282 2374 2513 E WifiStateMachine: Failed to load driver
08-23 08:59:46.287 2374 2374 E WifiService: Wi-Fi state is failed
08-23 08:59:46.287 2374 2374 D WifiService: setWifiEnabled: false pid=2374, uid=1000
08-23 08:59:46.287 2374 2374 E WifiService: Invoking mWifiStateMachine.setWifiEnabled
Click to expand...
Click to collapse
MOD: 13.0-20160821-NIGHTLY-i9300
Kernel: 3.0.101-CM-g6112c4d
I am pretty stuck here. Please help me getting my Wifi working again. Thx in adavance.
factory reset ?
exe98123q said:
factory reset ?
Click to expand...
Click to collapse
I would like to avoid that.
from snapshot work for you ? nightly are not stabile
backup system and test imo
Facing the same issue though in all cm based ROMs.
However it gets fixed in s6 experience ROM. It did for me at least. But after flashing cm it again gets back to the same error. Let me know if you get a solution.
Sent from my GT-I9300 using XDA-Developers mobile app
magically fixed
Hi,
2 Days ago I installed the latest Nightly on my S3 and Wifi keeps working even after Repoot. I have no idea why but I am happy.
KR
HaVonTe
I encountered the problem some months back but it was fixed automatically when I flashed a tw ROM. But it occurred again,finally changed the modem to the latest version and it works now. After changing the modem tried cm13,cm14.1,miui8,two,aosp.
In all of em it works. Though I was in cm13 only for like a day. Mostly use AOSP and wifi, hotspot,bt all works fine now.
Sent from my GT-I9300 using XDA-Developers mobile app

camera issues

I am having issues with custom rom that i built using lineage-15.1. My device is sanders. The camera is not working. The camera 2 app disappears soon after booting after installation. I installed open camera and it says camera is in use.
I got the logcats and i see this error -
02-12 10:46:44.252 760 760 F DEBUG : Abort message: 'CANNOT LINK EXECUTABLE "/system/vendor/bin/mm-qcamera-daemon": cannot locate symbol "_Z35eglQueryStringImplementationANDROIDPvi" referenced by "/system/vendor/lib/libguy.so"...'
I ran the nm command on the libguy.so and I find an undefined symbol there. I searched and found a shim that has this very symbol - libshim_camera_hal.so, I also found source files for this and found the function in device/motorola/sanders/libshims/camera_hal.cpp
I checked the shim file on the device, the shim file is present in /system/lib64 and /system/lib folders. libguy.so is in /system/vendor/lib and is 32bit.
Is this an LD_LIBRARY_PATH issue?
What can i do to fix this issue.
doors666 said:
I am having issues with custom rom that i built using lineage-15.1. My device is sanders. The camera is not working. The camera 2 app disappears soon after booting after installation. I installed open camera and it says camera is in use...
Click to expand...
Click to collapse
I don't have this device but, the following threads, that's device specific, may be helpful for what you are looking for and don't be afraid to ask for some member guidance within one of them.
https://forum.xda-developers.com/showthread.php?t=3722844
https://forum.xda-developers.com/showthread.php?t=3708082
https://forum.xda-developers.com/showthread.php?t=3708997
If all else fails, try posting your question within the following thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3593531
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
are you building that lib shims?
in libshims/Android.mk
and in device.mk
Refer to this tree: https://github.com/Keertesh19/device_motorola_sanders
yes I am building that. the files do have slight differences though as I took the device,vendor,kernel from validus links. I also downloaded the validus tree using the manifest and built it and i get the same issue there also. but its not there in the latest published rom.
I still have this issue, tried a lot of things, but still no fix.
I downloaded the latest validus published ROM build and that works fine, no issues with the camera.
I synced the validus repo using the manifest file and made a build, camera does not work.
Steps -
repo sync with validus manifest.
lunch validus_sanders-userdebug
brunch sanders
clean install.
Am I missing some step here? One thing that bothered me is that brunch works fine, but make fails. The error (I think it was about java doc, it asks me to run make update-api, that also fails.
I extracted both the ROMs and did a compare on both ramdisk and /system, no significant difference that could cause this.
I extracted the shims from good rom and copied it onto the phone which had my built rom and it still did not work.
I tried fedora (26 and 27) and ubuntu (17.10 and 16.04 LTS) to make build, no difference.
I modified the initrc and modified the LD_SHIM_LIBS to include the full path for the shims, still does not work.
This is the error that I get in the logs -
03-02 09:32:31.853 2558 2558 I init : type=1400 audit(0.0:520): avc: denied { execute_no_trans } for uid=1006 path="/system/vendor/bin/mm-qcamera-daemon" dev="mmcblk0p53" ino=2817 scontext=u:r:init:s0 tcontext=ubject_r:vendor_file:s0 tclass=file permissive=1
03-02 09:32:31.924 2558 2558 F libc : CANNOT LINK EXECUTABLE "/system/vendor/bin/mm-qcamera-daemon": cannot locate symbol "_Z35eglQueryStringImplementationANDROIDPvi" referenced by "/system/vendor/lib/libguy.so"...
03-02 09:32:31.924 2558 2558 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 2558 (mm-qcamera-daem), pid 2558 (mm-qcamera-daem)
03-02 09:32:31.939 2561 2561 E cutils-trace: Error opening trace file: No such file or directory (2)
03-02 09:32:31.936 2562 2562 I crash_dump32: type=1400 audit(0.0:521): avc: denied { ptrace } for uid=1006 scontext=u:r:crash_dump:s0 tcontext=u:r:init:s0 tclass=process permissive=1
03-02 09:32:31.945 2562 2562 I crash_dump32: obtaining output fd from tombstoned, type: kDebuggerdTombstone
03-02 09:32:31.946 691 691 I /system/bin/tombstoned: received crash request for pid 2558
03-02 09:32:31.947 2562 2562 I crash_dump32: performing dump of process 2558 (target tid = 2558)
03-02 09:32:31.947 2562 2562 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
03-02 09:32:31.947 2562 2562 F DEBUG : Build fingerprint: 'google/walleye/walleye:8.1.0/OPM1.171019.011/4448085:user/release-keys'
03-02 09:32:31.947 2562 2562 F DEBUG : Revision: '0'
03-02 09:32:31.947 2562 2562 F DEBUG : ABI: 'arm'
03-02 09:32:31.947 2562 2562 F DEBUG : pid: 2558, tid: 2558, name: mm-qcamera-daem >>> /system/vendor/bin/mm-qcamera-daemon <<<
03-02 09:32:31.947 2562 2562 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
03-02 09:32:31.948 2562 2562 F DEBUG : Abort message: 'CANNOT LINK EXECUTABLE "/system/vendor/bin/mm-qcamera-daemon": cannot locate symbol "_Z35eglQueryStringImplementationANDROIDPvi" referenced by "/system/vendor/lib/libguy.so"...'
03-02 09:32:31.948 2562 2562 F DEBUG : r0 00000000 r1 000009fe r2 00000006 r3 00000008
03-02 09:32:31.948 2562 2562 F DEBUG : r4 000009fe r5 000009fe r6 ff8a460c r7 0000010c
03-02 09:32:31.949 2562 2562 F DEBUG : r8 00000000 r9 ed86e010 sl 00000000 fp ff8a58a4
03-02 09:32:31.949 2562 2562 F DEBUG : ip ff8a4630 sp ff8a45f8 lr ed907309 pc ed905808 cpsr 200f0030
03-02 09:32:31.950 2562 2562 F DEBUG :
03-02 09:32:31.950 2562 2562 F DEBUG : backtrace:
03-02 09:32:31.950 2562 2562 F DEBUG : #00 pc 0005f808 /system/bin/linker (__dl_abort+63)
03-02 09:32:31.950 2562 2562 F DEBUG : #01 pc 00010931 /system/bin/linker (__dl___linker_init+2820)
03-02 09:32:31.950 2562 2562 F DEBUG : #02 pc 000156a4 /system/bin/linker (_start+4)
the latest changes to the device tree seems to have fixed this issue. thanx guys. though would love to know what was causing this issue.

service media.camera didn't start

cant open camera since my phone went flat once. (even installed camera2 on magisk)
logcat shows it trying to connect and does this cycle every couple of sections
Code:
03-05 16:57:25.911 5778 5858 I CameraManagerGlobal: Connecting to camera service
03-05 16:57:26.449 25035 25139 W ServiceManager: Service media.camera didn't start. Returning NULL
03-05 16:57:26.912 5778 5858 I CameraManagerGlobal: Connecting to camera service
03-05 16:57:27.912 5778 5858 I CameraManagerGlobal: Connecting to camera service
03-05 16:57:28.912 5778 5858 I CameraManagerGlobal: Connecting to camera service
03-05 16:57:29.725 2563 2595 W ServiceManager: Service media.camera didn't start. Returning NULL
03-05 16:57:29.913 5778 5858 I CameraManagerGlobal: Connecting to camera service
03-05 16:57:30.129 2742 2742 F linker : CANNOT LINK EXECUTABLE "/system/bin/cameraserver": library "libc++_shared.so" not found
found this when i launched the camera app
Code:
03-05 17:04:41.376 4793 5142 D FlashlightController: cameraId null
03-05 17:04:41.387 4793 11362 D ShortcutManager: th = 1 is camera package
and dumpsys returns
Code:
$ dumpsys media.camera
Can't find service: media.camera

[ROM][SM-T350][UNOFFICIAL][crDroidAndroid-11.0][v7.10][ANDROID 11] Galaxy Tab A 8.0

I am not responsible for bricked devices, or any other hardware malfunctions that comes as a result of flashing this ROM, Please do some research if you have any concerns about features included before flashing it, this ROM was built for the SM-T350 if you choose to flash this on any other device do so at your own risk!
Click to expand...
Click to collapse
>> crDroid Features <<​
-Installation instructions-
1. Download the ROM and GApps and transfer them to your device.
2. Boot to recovery (TWRP recommended).
3. Do a full backup of your device
4. Wipe the System, Cache, Data and ART/Dalvik cache. (Recommended)
5. Flash the ROM Zipfile.
6. Flash the GApps (optional, needed for e.g. Google Playstore to work).
7. Flash the root solution of your choice (optional).
8. Reboot your device.
TWRP 3.7.0 SM-T350 IMG DOWNLOAD​TWRP 3.7.0 SM-T350 ODIN DOWNLOAD​TWRP 3.3.1 SM-T350 DOWNLOAD​
Download crDroidAndroid-11.0 SM-T350 Build 2021-09-19​
Click to expand...
Click to collapse
MD5 FILE​
Click to expand...
Click to collapse
If you are having problems flashing this ROM you are most likely running into issues other members were having with the device most of which were already solved, please spend some time reading through this post of other posts related to this device.
-Backlight issues-
Read this post https://forum.xda-developers.com/showpost.php?p=83488241&postcount=41
Thanks
CrDroid Team
Evervolv Team
XDA:DevDB Information
crDroid Android, ROM for the Samsung Galaxy Tab A series
Contributors
nubianprince
ROM OS Version: Android 11
ROM Kernel: Linux 3.10.x
Based On: crDroidAndroid
Version Information
Status: Stable
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel
Grab a logcat right after the problem has occurred. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If it is a random reboot, grab /proc/last_kmsg.
What is the issue?
Attach or link the file.
Working
Audio (Tested)
Bluetooth (Tested)
Wifi (Tested)
Face Unlock (Tested)
Camera (Tested)
Netflix (Tested)
Not Working
You tell me
F.A.Q
1: Can I flash this on my SM-P355 tab
The ROM was built for the SM-T350 device (you can edit the updater script and flash at your own risk, a lot can go wrong)
2: Is this for Samsung Tab A 8.0 (2019)
The 2019 tablet is a SM-T290 device this ROM was built for the SM-T350
3: I get an error 7 when flashing this ROM
Install the TWRP image in the main post
4: Will you build for the SM-P355, SM-T290, SM-P350?
No I am only building for the devices that I own, feel free to use my device tree to build for your device
Changes
2021-06-18
- May Security Patches
2021-06-21
- June Security Patches
- DRM fixes
2021-06-24
- Overclocked Kernel & GPU
- Added missing vendor blobs to fix drm issues
2021-06-27
- Cleaned up sensor spamming
- Some sepolicy fixes
2021-07.07
- Fix for UI blur issues
- Some sepolicy fixes
2021-07.08
- Fix for live display
2021-09-19
- September Security Patches
Two bugs.
1) sensors not working
Code:
2557 12-16 15:23:13.580 372 372 E Sensors : couldn't find 'accelerometer_sensor' input device
2558 12-16 15:23:13.581 372 372 E Sensors : couldn't find 'accelerometer_sensor' input device
2559 12-16 15:23:13.581 372 372 E Sensors : Couldn't open accelerometer_sensor.
2560 12-16 15:23:13.581 372 372 E Sensors : AccelerometerSensor: undefined chip spec()
2561 12-16 15:23:13.581 372 372 E Sensors : couldn't find 'light_sensor' input device
2562 12-16 15:23:13.581 372 372 E Sensors : couldn't find 'light_sensor' input device
2563 12-16 15:23:13.581 372 372 E Sensors : Couldn't open light_sensor.
2564 12-16 15:23:13.581 372 372 E Sensors : LightSensor: undefined chip spec()
2565 12-16 15:23:13.582 372 372 E Sensors : couldn't find 'grip_sensor_wifi' input device
2566 12-16 15:23:13.582 372 372 E Sensors : couldn't find 'grip_sensor_wifi' input device
2567 12-16 15:23:13.582 372 372 E Sensors : Couldn't open grip_sensor_wifi.
For my build, I found that sensors have to be in passthrough mode and sensors.msm8916 has to be removed. That is, manifest.xml
Code:
<hal format="hidl">
<name>android.hardware.sensors</name>
<transport arch="32">passthrough</transport>
<version>1.0</version>
<interface>
<name>ISensors</name>
<instance>default</instance>
</interface>
</hal>
and msm8916.mk
Code:
# Sensor HAL
# RT sensor needs to be passthrough and sensors.msm8916 needs to be removed in order to work
PRODUCT_PACKAGES += \
[email protected]
# [email protected] \
# sensors.msm8916
2) drm not working
Code:
2527 12-16 15:23:13.530 364 364 E [email protected]: Failed to lookup symbol createDrmFactory in library /vendor/lib/mediadrm/libwvdrmengine.so: dlopen failed: cannot locate symbol "_ZN6google8protobuf8internal13empty_string_E" referenced by "/system/vendor/lib/mediadrm/libwvdrmengine.so"...
You are missing a commit like
https://review.lineageos.org/q/_ZN6google8protobuf8internal13empty_string_E
===
Since you are using evervolv's kernel code, I suggested to them that they consider overclocking the CPU/GPU and gave them the commits, but they haven't or decided not to implement them.
For overclock, see
[ROM][OFFICIAL][11.0] Evervolv for Galaxy Tab A 8.0 (SM-T350)
Evervolv is an AOSP (Android Open Source Project) rom that has roots dating back to 2011 with the Google Nexus One. Since then it has served as an open door for people of all kinds to contribute and experiment. The work put into this rom is...
forum.xda-developers.com
retiredtab said:
Two bugs.
1) sensors not working
Code:
2557 12-16 15:23:13.580 372 372 E Sensors : couldn't find 'accelerometer_sensor' input device
2558 12-16 15:23:13.581 372 372 E Sensors : couldn't find 'accelerometer_sensor' input device
2559 12-16 15:23:13.581 372 372 E Sensors : Couldn't open accelerometer_sensor.
2560 12-16 15:23:13.581 372 372 E Sensors : AccelerometerSensor: undefined chip spec()
2561 12-16 15:23:13.581 372 372 E Sensors : couldn't find 'light_sensor' input device
2562 12-16 15:23:13.581 372 372 E Sensors : couldn't find 'light_sensor' input device
2563 12-16 15:23:13.581 372 372 E Sensors : Couldn't open light_sensor.
2564 12-16 15:23:13.581 372 372 E Sensors : LightSensor: undefined chip spec()
2565 12-16 15:23:13.582 372 372 E Sensors : couldn't find 'grip_sensor_wifi' input device
2566 12-16 15:23:13.582 372 372 E Sensors : couldn't find 'grip_sensor_wifi' input device
2567 12-16 15:23:13.582 372 372 E Sensors : Couldn't open grip_sensor_wifi.
For my build, I found that sensors have to be in passthrough mode and sensors.msm8916 has to be removed. That is, manifest.xml
Code:
<hal format="hidl">
<name>android.hardware.sensors</name>
<transport arch="32">passthrough</transport>
<version>1.0</version>
<interface>
<name>ISensors</name>
<instance>default</instance>
</interface>
</hal>
and msm8916.mk
Code:
# Sensor HAL
# RT sensor needs to be passthrough and sensors.msm8916 needs to be removed in order to work
PRODUCT_PACKAGES += \
[email protected]
# [email protected] \
# sensors.msm8916
2) drm not working
Code:
2527 12-16 15:23:13.530 364 364 E [email protected]: Failed to lookup symbol createDrmFactory in library /vendor/lib/mediadrm/libwvdrmengine.so: dlopen failed: cannot locate symbol "_ZN6google8protobuf8internal13empty_string_E" referenced by "/system/vendor/lib/mediadrm/libwvdrmengine.so"...
You are missing a commit like
https://review.lineageos.org/q/_ZN6google8protobuf8internal13empty_string_E
===
Since you are using evervolv's kernel code, I suggested to them that they consider overclocking the CPU/GPU and gave them the commits, but they haven't or decided not to implement them.
Click to expand...
Click to collapse
I already started a new build to fix the sensors with June security patches... I will look into drm thought I had that fixed
I use devcheck by flar2 to check sensors and drm. When I click on the system menu in devcheck, my build with DRM shows Version 14.0.0, security L3 and clearkey 1.2. On your June 18 build, the same app shows nothing for DRM because of the error message that I included.
TCP/IP errors.
With Android 11, you also need a patch to fix TCP/IP errors. I found these in my build back in March 2021 and you have them too in your build.
Code:
03-24 08:08:09.674 1059 1653 E TcpInfo : parsing error.
03-24 08:08:09.674 1059 1653 E TcpInfo : java.lang.IllegalArgumentException: Length 104 is less than required.
03-24 08:08:09.674 1059 1653 E TcpInfo : at com.android.networkstack.netlink.TcpInfo.<init>(TcpInfo.java:118)
03-24 08:08:09.674 1059 1653 E TcpInfo : at com.android.networkstack.netlink.TcpInfo.parse(TcpInfo.java:143)
To fix, see
[ROM][UNOFFICIAL-ABANDONED][11] LineageOS 18.1 for Samsung Galaxy S5 (klte*)
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project with extra...
forum.xda-developers.com
and
[ROM][UNOFFICIAL-ABANDONED][11] LineageOS 18.1 for Samsung Galaxy S5 (klte*)
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project with extra...
forum.xda-developers.com
I opted for the DerpFest fix at
TcpSocketTracker: Opt-out for TCP info parsing on legacy kernels · DerpFest-AOSP/[email protected]
This feature requires netlink features that are unsupported on kernel versions lower than 4.4, therefore opt-out for it in such cases and avoid constantly crashing TcpSocketTracker. Change-Id: I12...
github.com
since I didn't want to touch the msm8916 kernel code.
Thanks to Henrik Grimler for pointing this out to me back in March 24, 2021.
Henrik Grimler submitted those kernel changes to msm8916 gerrit a while back after discovering it, but gerrit been down for days and I don't know when it will be up.
Again, I opted for the DerpFest fix, but I'm following the msm8916 kernel, not evervolv, so if Henrik's changes get merged into 18.1, I can revert the DerpFest fix.
Running a new build to include the patch for DRM, will do some testing when it is done, as for overclocking the kernel will take a look at that is weekend
New build uploaded (2021-06-21) with a few fixes @lividhen that app you couldn't get to work in the android 10 build should work in this build.
@nubianprince , the June 21 build still has problems with DRM and sensors.
1. DRM
Your DRM shows clearkey 1.2 now using devcheck by flar2, but is mssing the widevine other info as I wrote in post #7.
Code:
2434 12-19 09:31:43.905 0 0 I [1: init: 1] init: starting service 'vendor.drm-hal-1-0'...
2435 12-19 09:31:43.913 0 0 E [1: init: 1] init: File /vendor/bin/hw/[email protected] (labeled "u:object_r:vendor_file:s0") has incorrect label or no domain transition from u:r:init:s0 to another SELinux domain defined. Have you configured your service correctly? https://source.android.com/security/selinux/device-policy#label_new_services_and_address_denials
2474 12-19 09:31:44.041 363 363 E [email protected]: Failed to lookup symbol createDrmFactory in library /vendor/lib/mediadrm/libwvdrmengine.so: dlopen failed: cannot locate symbol "_ZN6google8protobuf8internal13empty_string_E" referenced by "/system/vendor/lib/mediadrm/libwvdrmengine.so"...
2. Sensors are still broken. As you can see in trace, it's starting and then dying (signal 9).
Code:
339 06-21 13:01:47.743 0 0 I [3: init: 1] init: starting service 'vendor.sensors-hal-1-0'...
340 06-21 13:01:47.761 2841 2841 E [email protected]: Couldn't load sensors module (Unknown error -2147483648)
341 06-21 13:01:47.761 2841 2841 D RefBase : RefBase: Explicit destruction, weak count = 0 (in 0xa6f00114)
342 06-21 13:01:47.761 2841 2841 W RefBase : CallStack::getCurrentInternal not linked, returning null
343 06-21 13:01:47.761 2841 2841 W RefBase : CallStack::logStackInternal not linked
344 06-21 13:01:47.762 2841 2841 E LegacySupport: Could not get passthrough implementation for [email protected]::ISensors/default.
345 06-21 13:01:47.790 0 0 I [0: init: 1] init: Service 'vendor.sensors-hal-1-0' (pid 2841) exited with status 1
346 06-21 13:01:47.790 0 0 I [0: init: 1] init: Sending signal 9 to service 'vendor.sensors-hal-1-0' (pid 2841) process group...
347 06-21 13:01:47.790 0 0 I [0: init: 1] libprocessgroup: Successfully killed process cgroup uid 1000 pid 2841 in 0ms
Pictures from devcheck to illustrate what I'm describing. The file names tell you which screenshot is what. You can see the difference between my build and yours. I didn't take a picture of crDroid sensors, but yours only has temperature whereas mine as 2 more.
So your June 21 build is completely missing the widevine information in the screenshot above. And yes, clearkey info is at the bottom of that crdroid screenshot. It cannot scroll any farther down in case you were wondering. The adb logcat error message I included also tells you that something is still wrong.
New build uploaded with overclocked kernel and some other fixes, still need to cleanup a few things
@nubianprince , June 24 has overclock for both CPU and GPU. DRM and sensors both are fixed as viewed by devcheck app.
While the sensors work in devcheck, adb logcat still shows something is not quite 100% as it continually spams
Code:
9184 06-24 14:27:53.969 0 0 I [1: init: 1] init: starting service 'vendor.sensors-hal-1-0'...
9185 06-24 14:27:54.000 2879 2879 I sensors_hal_wrapper: Initializing wrapper for Samsung Sensor-HAL
9186 06-24 14:27:54.002 2879 2879 E Sensors : couldn't find 'accelerometer_sensor' input device
9187 06-24 14:27:54.002 2879 2879 E Sensors : couldn't find 'accelerometer_sensor' input device
9188 06-24 14:27:54.003 2879 2879 E Sensors : Couldn't open accelerometer_sensor.
9189 06-24 14:27:54.003 2879 2879 E Sensors : AccelerometerSensor: undefined chip spec()
9190 06-24 14:27:54.003 2879 2879 E Sensors : couldn't find 'light_sensor' input device
9191 06-24 14:27:54.003 2879 2879 E Sensors : couldn't find 'light_sensor' input device
9192 06-24 14:27:54.003 2879 2879 E Sensors : Couldn't open light_sensor.
9193 06-24 14:27:54.003 2879 2879 E Sensors : LightSensor: undefined chip spec()
9194 06-24 14:27:54.003 2879 2879 E Sensors : couldn't find 'grip_sensor_wifi' input device
9195 06-24 14:27:54.003 2879 2879 E Sensors : couldn't find 'grip_sensor_wifi' input device
9196 06-24 14:27:54.003 2879 2879 E Sensors : Couldn't open grip_sensor_wifi.
9197 06-24 14:27:54.003 2879 2879 E Sensors : GripSensor_wifi: undefined chip spec()
9198 06-24 14:27:54.003 2879 2879 E Sensors : couldn't find 'meta_event' input device
9199 06-24 14:27:54.004 2879 2879 E Sensors : couldn't find 'meta_event' input device
9200 06-24 14:27:54.004 2879 2879 E Sensors : Couldn't open meta_event.
9201 06-24 14:27:54.004 2879 2879 D Sensors : sensors_poll_context_t: sensor list: 0
9202 06-24 14:27:54.006 2879 2879 E HidlServiceManagement: Service [email protected]::ISensors/default must be in VINTF manifest in order to register/get.
9203 06-24 14:27:54.006 2879 2879 E LegacySupport: Could not register service [email protected]::ISensors/default (-2147483648).
9204 06-24 14:27:54.033 0 0 I [2: init: 1] init: Service 'vendor.sensors-hal-1-0' (pid 2879) exited with status 0
9205 06-24 14:27:54.033 0 0 I [2: init: 1] init: Sending signal 9 to service 'vendor.sensors-hal-1-0' (pid 2879) process group...
Do a grep for "vendor.sensors-hal-1-0" in your device tree and/or vendor tree to what is calling it.
I am aware of the sensor spamming, I will see what is going on with that as soon as I can, I have to take a closer look at the vendor blobs.
There's no rush to fix. I'm just pointing out the bugs/errors that you may have missed.
Will this work if I have a Tab A with 7.1.1 installed? Also what variant of Gapps should I download?
batouttahell24 said:
Will this work if I have a Tab A with 7.1.1 installed? Also what variant of Gapps should I download?
Click to expand...
Click to collapse
Make sure you have TWRP recovery installed and follow the steps in the main post, you can google open_gapps-arm-11

Categories

Resources