[UNOFFICIAL][ROM]BETA LineageOS 18.1 GO for Galaxy Tab A [SM-T350] Sept 12, 2022

Search This thread

breversa

Senior Member
Mar 21, 2012
528
163
LG G4
Fairphone 2
I guess my issue is now solved :)

Here's what I did:
0. Install the latest TWRP
1. Clean-wipe the tablet
2. Install this latest ROM
3. BOOT IT ONCE
4. Reboot to TWRP
5. Install BiTGApps (the download site is quite confusing: be sure to get the latest ARM version for Android 11, *not* the most downloaded one)
6. Boot the tablet
7. Notice no UI crash, no real slowdown, etc. :)
8. Install Magisk, Aurora Droid/Store (useful when preparing the device for someone else whose Google credentials you don't have), etc.

Happy. :)
 
  • Like
Reactions: lpedia

breversa

Senior Member
Mar 21, 2012
528
163
LG G4
Fairphone 2
As a Magisk module, there's no need. But I'd rather have MicroG not depend on Magisk, especially on the rare case when I need an unrooted device.

As a system app, I can't tell, I don't remember. But what I remember is that *with* signature spoofing, there's no issue. ;)
 
As a Magisk module, there's no need. But I'd rather have MicroG not depend on Magisk, especially on the rare case when I need an unrooted device.

As a system app, I can't tell, I don't remember. But what I remember is that *with* signature spoofing, there's no issue. ;)
Well, the module just uses magisk's layeredfs to pretend it's in system/priv-app (or just system/app, I can't remember) app so they have the same result. Except it gets deleted with a system update, so yeah sig spoof would be the way to go there. If smali patcher still works on R you can just replace the files instead of using it as a module.
 

retiredtab

Senior Member
Nov 16, 2017
1,239
813
New build called lineage-18.1-20220708-UNOFFICIAL-gt58wifi.zip

NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.

July 8, 2022 release notes
1. July 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-07
2. Whatever LiineageOS changed since last June release (about 1,500 files had to be recompiled).
 
  • Like
Reactions: breversa

breversa

Senior Member
Mar 21, 2012
528
163
LG G4
Fairphone 2
I guess my issue is now solved :)

Here's what I did:
0. Install the latest TWRP
1. Clean-wipe the tablet
2. Install this latest ROM
3. BOOT IT ONCE
4. Reboot to TWRP
5. Install BiTGApps (the download site is quite confusing: be sure to get the latest ARM version for Android 11, *not* the most downloaded one)
6. Boot the tablet
7. Notice no UI crash, no real slowdown, etc. :)
8. Install Magisk, Aurora Droid/Store (useful when preparing the device for someone else whose Google credentials you don't have), etc.

Happy. :)
I take this back:

The tablet experiences frequent (up to several times per hour) and sudden UI slowdowns/freezes once GApps are installed.

I did not notice such slowdowns on another tab of the same model withouth GApps.

I'll try to replicate the issue and provide logcat.
 

retiredtab

Senior Member
Nov 16, 2017
1,239
813
New build called lineage-18.1-20220805-UNOFFICIAL-gt58wifi.zip

NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.

Aug 5, 2022 release notes
1. Aug 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-08
2. Whatever LiineageOS changed since last July release (about 4,000 files had to be recompiled).
 
Last edited:
  • Like
Reactions: bluenote73

lmore377

Member
Jul 2, 2016
35
6
Not sure if anyone else has reported this issue, but when I try to enable any sort of tethering (hotspot, bluetooth, usb, etc.) I get this error in logcat:

Failed to open /proc/sys/net/ipv4/ip_forward: No such file or directory

The whole directory exists it's just ip_forward that's missing
 

retiredtab

Senior Member
Nov 16, 2017
1,239
813
Not sure if anyone else has reported this issue, but when I try to enable any sort of tethering (hotspot, bluetooth, usb, etc.) I get this error in logcat:

Failed to open /proc/sys/net/ipv4/ip_forward: No such file or directory

The whole directory exists it's just ip_forward that's missing
@lmore377

Follow the instructions in post #2 FAQ9 and then ZIP the file and send to me via PM or attach here.

I haven't done any tethering testing, but I suspect this might be selinux enforcing related. That is, some process wants to create that file and I may not have the rule written to allow it to happen.

In the adb logcat, it would look something like avc denied some_process { write }.

If you're running a linux distro, you can run

Bash:
adb pull /sys/fs/selinux/policy && adb logcat -b all -d | audit2allow -p policy

and it will show the rule(s) that's being enforced.
 

lmore377

Member
Jul 2, 2016
35
6
@lmore377

Follow the instructions in post #2 FAQ9 and then ZIP the file and send to me via PM or attach here.

I haven't done any tethering testing, but I suspect this might be selinux enforcing related. That is, some process wants to create that file and I may not have the rule written to allow it to happen.

In the adb logcat, it would look something like avc denied some_process { write }.

If you're running a linux distro, you can run

Bash:
adb pull /sys/fs/selinux/policy && adb logcat -b all -d | audit2allow -p policy

and it will show the rule(s) that's being enforced.
I think it's something more than just selinux (maybe some kernel build option?). There aren't any selinux errors in logcat and setting selinux to permissive didnt help. I also tried running `sysctl -w net.ipv4.ip_forward=1` which is supposed to be an alternative way of enabling forwarding but it just gives this error `sysctl: unknown key 'net.ipv4.ip_forward'`.

I also tried tethering in this crdroid rom and it worked there so i flashed the boot partition from that rom over this one. Not only did it boot but both tethering and the above command work now. I also included a logcat for this.

Code:
--------- beginning of main
08-11 19:16:21.291   655  3624 I chatty  : uid=1000(system) IpClient.eth0 expire 1 line
08-11 19:16:23.139   655  3624 D DhcpClient: Broadcasting DHCPDISCOVER
08-11 19:16:24.921   655   721 E LightsService: Light requested not available on this device. 2
08-11 19:16:24.958  1031  1031 I TetheringManager: startTethering caller:com.android.settings    ---Tried turning on tethering here
08-11 19:16:24.960   655   767 D EthernetTracker: Setting default interface mode to 2
08-11 19:16:24.961   655  3624 D DhcpClient: doQuit
08-11 19:16:25.036   655  3624 D DhcpClient: DHCP Packet Handler stopped
08-11 19:16:25.037   655  3624 D DhcpClient: onQuitting
08-11 19:16:25.051   655   767 D EthernetNetworkFactory: updateCapabilityFilter: [ AdministratorUids: [] RequestorUid: -1 RequestorPackageName: null]
08-11 19:16:25.058   655   767 D EthernetTracker: Tracking interface in server mode: eth0
08-11 19:16:25.105   292   292 E TetherController: Failed to open /proc/sys/net/ipv4/ip_forward: No such file or directory
08-11 19:16:25.107   655  1185 E Tethering: ERROR android.os.ServiceSpecificException: Remote I/O error (code 121)
08-11 19:16:25.108   655  1185 E Tethering: Error in setIpForwardingEnabled
08-11 19:16:25.447   655   665 I system_server: Background concurrent copying GC freed 72262(3170KB) AllocSpace objects, 8(384KB) LOS objects, 24% free, 10MB/14MB, paused 292us total 393.459ms
08-11 19:16:25.456   655   667 W System  : A resource failed to call release.
08-11 19:16:25.456   655   667 I chatty  : uid=1000(system) FinalizerDaemon identical 1 line
08-11 19:16:25.456   655   667 W System  : A resource failed to call release.
08-11 19:16:25.458   655   667 W MediaPlayer-JNI: MediaPlayer finalized without being released
08-11 19:16:25.458   413  2157 D NuPlayerDriver: reset(0xb60ef220) at state 6
08-11 19:16:25.463   655  1708 I system_server: oneway function results will be dropped but finished with status OK and parcel size 4
08-11 19:16:25.465   655  1708 I system_server: oneway function results will be dropped but finished with status OK and parcel size 4
08-11 19:16:25.468   413  3503 D NuPlayerDriver: notifyResetComplete(0xb60ef220)
08-11 19:16:25.469   413  2157 W AMessage: failed to post message as target looper for handler 0 is gone.
08-11 19:16:25.470   655   667 V MediaPlayer: resetDrmState:  mDrmInfo=null mDrmProvisioningThread=null mPrepareDrmInProgress=false mActiveDrmScheme=false
08-11 19:16:25.470   655   667 V MediaPlayer: cleanDrmObj: mDrmObj=null mDrmSessionId=null
08-11 19:16:25.471   655   667 W MediaPlayer-JNI: MediaPlayer finalized without being released
08-11 19:16:25.471   413  2203 D NuPlayerDriver: reset(0xb60ee780) at state 6
08-11 19:16:25.479   413  3423 D NuPlayerDriver: notifyResetComplete(0xb60ee780)
08-11 19:16:25.480   413  2203 W AMessage: failed to post message as target looper for handler 0 is gone.
08-11 19:16:25.484   655   667 V MediaPlayer: resetDrmState:  mDrmInfo=null mDrmProvisioningThread=null mPrepareDrmInProgress=false mActiveDrmScheme=false
08-11 19:16:25.484   655   667 V MediaPlayer: cleanDrmObj: mDrmObj=null mDrmSessionId=null
08-11 19:16:28.477   655  1060 I system_server: oneway function results will be dropped but finished with status OK and parcel size 4
08-11 19:16:33.482   655   693 E LightsService: Light requested not available on this device. 2

Code:
--------- beginning of main
08-11 19:52:45.123   703  2500 D DhcpClient: Broadcasting DHCPDISCOVER
08-11 19:52:46.368   703   770 E LightsService: Light requested not available on this device. 2
08-11 19:52:46.399  1060  1060 I TetheringManager: startTethering caller:com.android.settings
08-11 19:52:46.406   703   819 D EthernetTracker: Setting default interface mode to 2
08-11 19:52:46.410   703  2500 D DhcpClient: doQuit
08-11 19:52:46.459   703  2500 D DhcpClient: DHCP Packet Handler stopped
08-11 19:52:46.459   703  2500 D DhcpClient: onQuitting
08-11 19:52:46.474   703   819 D EthernetNetworkFactory: updateCapabilityFilter: [ AdministratorUids: [] RequestorUid: -1 RequestorPackageName: null]
08-11 19:52:46.482   703   819 D EthernetTracker: Tracking interface in server mode: eth0
08-11 19:52:46.483   703   819 I EthernetNetworkFactory: networkForRequest, request: NetworkRequest [ REQUEST id=1, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN AdministratorUids: [] RequestorUid: 1000 RequestorPackageName: android] ], network: null
08-11 19:52:46.484   703   819 E EthernetNetworkFactory: releaseNetworkFor, failed to get a network for NetworkRequest [ REQUEST id=1, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN AdministratorUids: [] RequestorUid: 1000 RequestorPackageName: android] ]
08-11 19:52:46.484   703   819 I EthernetNetworkFactory: networkForRequest, request: NetworkRequest [ REQUEST id=16, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN AdministratorUids: [] RequestorUid: 1000 RequestorPackageName: android] ], network: null
08-11 19:52:46.485   703   819 E EthernetNetworkFactory: releaseNetworkFor, failed to get a network for NetworkRequest [ REQUEST id=16, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN AdministratorUids: [] RequestorUid: 1000 RequestorPackageName: android] ]
--------- beginning of system
08-11 19:52:24.964   509   509 I chatty  : uid=1010(wifi) /system/bin/wificond expire 2 lines
08-11 19:52:24.970   509   509 W wificond: Failed to get NL80211_ATTR_EXT_FEATURES
08-11 19:52:46.532   703   787 D ConnectivityService: NetReassign [no changes]
08-11 19:52:46.532   229   229 I hwservicemanager: getTransport: Cannot find entry [email protected]::IOffloadConfig/default in either framework or device manifest.
08-11 19:52:46.533   703  1240 E Tethering: ERROR getIOffloadConfig error java.util.NoSuchElementException
08-11 19:52:46.533   703  1240 E Tethering: [OffloadHardwareInterface] ERROR Could not find IOffloadConfig service
08-11 19:52:46.533   703  1240 I Tethering: [OffloadController] tethering offload config not supported
08-11 19:52:46.536   703  1240 I Tethering: [UpstreamNetworkMonitor] requesting mobile upstream network: NetworkRequest [ NONE id=0, [ Transports: CELLULAR Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN Uid: 1000 AdministratorUids: [] RequestorUid: -1 RequestorPackageName: null] ]
08-11 19:52:46.537   703  1240 D ConnectivityService: requestNetwork for uid/pid:1000/703 NetworkRequest [ REQUEST id=40, legacyType=5, [ Transports: CELLULAR Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN Uid: 1000 AdministratorUids: [] RequestorUid: 1000 RequestorPackageName: android] ]
08-11 19:52:46.537   703   787 D ConnectivityService: NetReassign [no changes]
08-11 19:52:46.537   703  1240 I Tethering: [BpfCoordinator] Polling started
08-11 19:52:46.540   703   783 D UntrustedWifiNetworkFactory: got request NetworkRequest [ REQUEST id=40, legacyType=5, [ Transports: CELLULAR Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN Uid: 1000 AdministratorUids: [] RequestorUid: 1000 RequestorPackageName: android] ] with score 0 and providerId 0
08-11 19:52:46.541   703   819 D Ethernet: got request NetworkRequest [ REQUEST id=40, legacyType=5, [ Transports: CELLULAR Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN Uid: 1000 AdministratorUids: [] RequestorUid: 1000 RequestorPackageName: android] ] with score 0 and providerId 0
08-11 19:52:46.542   703   783 D WifiNetworkFactory: got request NetworkRequest [ REQUEST id=40, legacyType=5, [ Transports: CELLULAR Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN Uid: 1000 AdministratorUids: [] RequestorUid: 1000 RequestorPackageName: android] ] with score 0 and providerId 0
08-11 19:52:46.542  1038  1038 D PhoneSwitcherNetworkRequstListener: got request NetworkRequest [ REQUEST id=40, legacyType=5, [ Transports: CELLULAR Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN Uid: 1000 AdministratorUids: [] RequestorUid: 1000 RequestorPackageName: android] ] with score 0 and providerId 0
08-11 19:52:46.545   703  1240 I Tethering: Looking for default routes on: {InterfaceName: wlan0 LinkAddresses: [ fe80::86b5:41ff:fe46:dd2e/64,192.168.1.246/24,2603:8080:8500:4181:86b5:41ff:fe46:dd2e/64,2603:8080:8500:4181:f8bb:e536:b1aa:1f17/64,fd86:d2a0:5404:0:86b5:41ff:fe46:dd2e/64,fd86:d2a0:5404:0:f8bb:e536:b1aa:1f17/64 ] DnsAddresses: [ /fd86:d2a0:5404::1,/192.168.1.1 ] Domains: lan MTU: 0 ServerAddress: /192.168.1.1 TcpBufferSizes: 524288,1048576,2097152,262144,524288,1048576 Routes: [ fe80::/64 -> :: wlan0 mtu 0,::/0 -> fe80::7a29:edff:fe33:7134 wlan0 mtu 0,2603:8080:8500:4181::/64 -> :: wlan0 mtu 0,fd86:d2a0:5404::/64 -> :: wlan0 mtu 0,192.168.1.0/24 -> 0.0.0.0 wlan0 mtu 0,0.0.0.0/0 -> 192.168.1.1 wlan0 mtu 0 ]}
08-11 19:52:46.546   703  1240 I Tethering: Found upstream interface(s): [wlan0]
08-11 19:52:46.551   703  1240 I Tethering: Looking for default routes on: {InterfaceName: wlan0 LinkAddresses: [ fe80::86b5:41ff:fe46:dd2e/64,192.168.1.246/24,2603:8080:8500:4181:86b5:41ff:fe46:dd2e/64,2603:8080:8500:4181:f8bb:e536:b1aa:1f17/64,fd86:d2a0:5404:0:86b5:41ff:fe46:dd2e/64,fd86:d2a0:5404:0:f8bb:e536:b1aa:1f17/64 ] DnsAddresses: [ /fd86:d2a0:5404::1,/192.168.1.1 ] Domains: lan MTU: 0 ServerAddress: /192.168.1.1 TcpBufferSizes: 524288,1048576,2097152,262144,524288,1048576 Routes: [ fe80::/64 -> :: wlan0 mtu 0,::/0 -> fe80::7a29:edff:fe33:7134 wlan0 mtu 0,2603:8080:8500:4181::/64 -> :: wlan0 mtu 0,fd86:d2a0:5404::/64 -> :: wlan0 mtu 0,192.168.1.0/24 -> 0.0.0.0 wlan0 mtu 0,0.0.0.0/0 -> 192.168.1.1 wlan0 mtu 0 ]}
08-11 19:52:46.553   860   860 V KeyguardUpdateMonitor: onSubscriptionInfoChanged()
08-11 19:52:46.554   703  1240 I Tethering: Found upstream interface(s): [wlan0]
08-11 19:52:46.562  1038  1038 D Telephony: isEmergencyPreferredAccount: subId=-1, activeData=-1
08-11 19:52:46.562  1038  1038 D Telephony: isEmergencyPreferredAccount: Device does not require preference.
08-11 19:52:46.577  2507  2507 I dnsmasq : started, version 2.51 cachesize 150
08-11 19:52:46.577  2507  2507 I dnsmasq : compile time options: IPv6 GNU-getopt no-I18N DHCP no-scripts
08-11 19:52:46.578  2507  2507 W dnsmasq : warning: no upstream servers configured
08-11 19:52:46.578  2507  2507 I dnsmasq : read /etc/hosts - 2 addresses
08-11 19:52:46.579  2507  2507 I dnsmasq : Closing wildcard listener family=2
08-11 19:52:46.579  2507  2507 I dnsmasq : Closing wildcard listener family=10
08-11 19:52:46.580  2507  2507 I dnsmasq : using nameserver 192.168.1.1#53
08-11 19:52:46.580  2507  2507 I dnsmasq : using nameserver fd86:d2a0:5404::1#53
08-11 19:52:46.581  2507  2507 I dnsmasq : using nameserver 192.168.1.1#53
08-11 19:52:46.581  2507  2507 I dnsmasq : using nameserver fd86:d2a0:5404::1#53
08-11 19:52:47.643   703   720 I EthernetTracker: interfaceLinkStateChanged, iface: eth0, up: false
08-11 19:52:47.652   703   819 D EthernetNetworkFactory: updateCapabilityFilter: [ AdministratorUids: [] RequestorUid: -1 RequestorPackageName: null]
08-11 19:52:47.653   703   819 D EthernetTracker: No longer tracking interface in server mode: eth0
08-11 19:52:47.666   703   819 D EthernetTracker: Setting default interface mode to 1
08-11 19:52:47.677  2507  2507 E dnsmasq : interface given in set_interfaces: 'eth0' has no ifindex; ignoring
08-11 19:52:47.677  2507  2507 I dnsmasq : Closing listener [fe80::250:b6ff:fef3:25d6%8]:53
08-11 19:52:47.677  2507  2507 I dnsmasq : Closing listener [::1]:53
08-11 19:52:47.677  2507  2507 I dnsmasq : Closing listener [192.168.59.114]:53
08-11 19:52:47.677  2507  2507 I dnsmasq : Closing listener [127.0.0.1]:53
08-11 19:52:47.678  2507  2507 I dnsmasq : using nameserver 192.168.1.1#53
08-11 19:52:47.678  2507  2507 I dnsmasq : using nameserver fd86:d2a0:5404::1#53
 

retiredtab

Senior Member
Nov 16, 2017
1,239
813
@lmore377 , I'll have to look at your logs sometime later. Right now, I'm releasing 19.1 for SM-T350 among other things. I noticed that ip_forward is there in 19.1. So you can try 19.1 at

https://forum.xda-developers.com/t/...19-1-galaxy-tab-a-sm-t350-aug-9-2022.4479287/

and let me know if tethering works in 19.1

Bash:
gt58wifi:/proc/sys/net/ipv4 # ls
conf                               ip_local_reserved_ports           tcp_challenge_ack_limit  tcp_max_orphans            tcp_stdurg
fwmark_reflect                     ip_no_pmtu_disc                   tcp_congestion_control   tcp_max_ssthresh           tcp_syn_retries
icmp_echo_ignore_all               ip_nonlocal_bind                  tcp_default_init_rwnd    tcp_max_syn_backlog        tcp_synack_retries
icmp_echo_ignore_broadcasts        ipfrag_high_thresh                tcp_delack_seg           tcp_max_tw_buckets         tcp_thin_dupack
icmp_errors_use_inbound_ifaddr     ipfrag_low_thresh                 tcp_dsack                tcp_mem                    tcp_thin_linear_timeouts
icmp_ignore_bogus_error_responses  ipfrag_max_dist                   tcp_early_retrans        tcp_min_tso_segs           tcp_timestamps
icmp_ratelimit                     ipfrag_secret_interval            tcp_ecn                  tcp_moderate_rcvbuf        tcp_tso_win_divisor
icmp_ratemask                      ipfrag_time                       tcp_fack                 tcp_mtu_probing            tcp_tw_recycle
igmp_max_memberships               neigh                             tcp_fastopen             tcp_no_metrics_save        tcp_tw_reuse
igmp_max_msf                       netfilter                         tcp_fastopen_key         tcp_orphan_retries         tcp_use_userconfig
inet_peer_maxttl                   ping_group_range                  tcp_fin_timeout          tcp_reordering             tcp_window_scaling
inet_peer_minttl                   route                             tcp_frto                 tcp_retrans_collapse       tcp_wmem
inet_peer_threshold                tcp_abort_on_overflow             tcp_fwmark_accept        tcp_retries1               tcp_workaround_signed_windows
ip_default_ttl                     tcp_adv_win_scale                 tcp_keepalive_intvl      tcp_retries2               udp_mem
ip_dynaddr                         tcp_allowed_congestion_control    tcp_keepalive_probes     tcp_rfc1337                udp_rmem_min
ip_early_demux                     tcp_app_win                       tcp_keepalive_time       tcp_rmem                   udp_wmem_min
ip_forward                         tcp_available_congestion_control  tcp_limit_output_bytes   tcp_sack                   xfrm4_gc_thresh
ip_local_port_range                tcp_base_mss                      tcp_low_latency          tcp_slow_start_after_idle
 
  • Like
Reactions: zpunout

retiredtab

Senior Member
Nov 16, 2017
1,239
813
New build called lineage-18.1-20220912-UNOFFICIAL-gt58wifi.zip

NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.

Sept 12, 2022 release notes
1. Sept 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-09
2. Whatever LiineageOS changed since last July release (about 12,500 files had to be recompiled).
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    New build called lineage-18.1-20220912-UNOFFICIAL-gt58wifi.zip

    NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.

    Sept 12, 2022 release notes
    1. Sept 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-09
    2. Whatever LiineageOS changed since last July release (about 12,500 files had to be recompiled).
    1
    Hey retiredtab, thanks for keeping this device alive :) much appreciated
  • 5
    PLEASE BEFORE YOU decide to try this rom, you MUST read all of post 1, 2, 3 and 4 (about 10 minute read). If you think this is an unreasonable request, then stop reading now and find another rom. Thank you.

    I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this rom.

    BACKUP YOUR DATA AND OLD rom BEFORE trying my rom.

    If you are NOT an expert in using fastboot, adb, odin, heimdall, twrp, DO NOT use this rom. You must know how to use these tools to revert back to your old rom.

    If you are new to flashing custom roms, do NOT attempt this.

    If you need your tablet for work and something important, do NOT flash this rom. This rom could result in a bricked device or boot loop or non booting device or you not being able to revert back to your old rom.

    What works

    1. bluetooth
    2. wifi
    3. brightness
    4. external audio
    5. GPS
    6. audio through headphone jack
    7. audio over bluetooth
    8. selinux enforcing
    9. camera

    Thanks
    1. LineageOS team for source code.
    2. Pre alpha testers for the Samsung Tab A/E roms who provided valuable feedback: lpedia, Schaagi, katochwa, Henrick Grimler
    3. nubianprince for helping fix audio over bluetooth on SM-T350 on 18.1.
    4. Huge thanks to Henrick Grimler https://github.com/Grimler91 for helping me reproduce a major bug in 18.1 which led me to find a solution. Henrick also helped fine tune some of the sepolicy as well.
    5. Sebastiano Barezzi https://github.com/SebaUbuntu for giving the msm8916 repo some 18.1 code updates in March 2021.
    6. Exynos5420 team for sharing it's knowledge in building roms.
    7. msm8916 team for their repos
    8. dylux for suggesting a fix for the front camera photo/record crashing by using stock SM-T350 media_profiles.xml.
    4
    New build called lineage-18.1-20220611-UNOFFICIAL-gt58wifi.zip

    NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.

    June 11, 2022 release notes
    1. June 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-06
    2. Whatever LiineageOS changed since last May release (about 9,500 files had to be recompiled).
    3
    FAQ - I spent hundreds of hours building this rom. It was frustrating process from Nov 2020 to March 2021 running into bug after bug. The least you can do is spend a few minutes reading everything before posting.

    Q1. Where are the source and kernel source files?
    A1. The kernel source files are at


    The device tree files are at


    The vendor tree files are at

    In addition, there is a repo diff file for device specific tweaks needed to work and a roomservice.xml (local manifest file) file so you can build this rom yourself.

    Q2. Is this BETA rom suitable as a daily driver?
    A2. It can be depending on your requirements. I can't test every app so you try it yourself to see if it's suitable. I've been using this rom myself since mid March 2021 with no major issues.

    Q3. What if my app, xyz, doesn't work?
    A3. I won't answer questions regarding why your app doesn't work. If your app, whatever it is, doesn't work, then go back to your old rom. It's difficult enough building and maintaining these roms. Remember, I'm an unpaid volunteer making a rom for free for your benefit.

    Q4. Your rom is laggy and buggy.
    A4. If you find the above, then go back to your old rom. There's only so much software can do on a 2015 budget level tablet. Remember a budget tablet will have the slower SoC/CPU and less DRAM than a top of the line model. Your tablet will also run slower when you use gapps (google apps). You can run a lot of software without using gapps. Research fdroid, newpipe, Aurora store etc.

    Q5. What TWRP should I use?
    A5. You MUST use TWRP 3.5.2_9. Get it from


    Q6. Why should I use this rom?
    A6. You don't. If you don't like this rom, then don't use it. Yes, it's that simple.

    Q7. Will you offer monthly updates with security patches?
    A7. I will try to offer monthly security patches, but that all depends on if I continue to have high speed Internet in the future.

    Q8. Can you help me? I'm a newbie. Can you provide step by step instructions?
    A8. Do your own research. There are lots of tutorials, videos, etc on how to flash roms. Newbie questions must be posted in the Questions and Answers forum, not here.

    Q9. Can I report a bug with respect to the rom?
    A9. Yes, but you need to supply the following information. If you don't, I won't look at it.

    You must provide an adb logcat of the problem and tell me how to reproduce it. Note I will not be downloading any apps that require money or an userid/password. For example, if you have problems with Netflix, I cannot help you since I don't have a paid subscription. If you use some app that requires an userid/password, I cannot help you as I'm not willing to create another userid/password even if it's free.

    To get a logcat, open up a terminal window.
    Code:
    # clear the logcat first
    adb logcat -c
    # start logcat trace
    adb logcat > problem.txt
    # reproduce problem
    # wait until problem has occured, then stop trace by hitting ctrl-c

    Q10. Will you still build 17.1 for this device?
    A10. Yes, for now, but I will probably discontinue building 17.1 at the end of 2021. I will likely be trying to build 19.0 once it's released so I don't want to maintain 3 releases.

    Q11. Do I need to erase everything and format my data?
    A11. Yes, you MUST erase all the partitions (system, data, dalvik/art cache, cache) using TWRP and MUST format your data before installing 18.1 when you are coming from stock or an earlier version of LineageOS or from another custom rom. If you get stuck at the boot animation for more than 5 minutes, it's likely because you didn't follow the instructions I just wrote. Dirty flashes from stock, other custom roms or older LineageOS versions are not supported and not likely to work.

    Q12. What gapps should I use?
    A12. I don't use gapps anymore. I use Aurora Store. As of Nov 6, 2021, I no longer make recommendations on which gapps to use as your mileage may vary. It's reported that opengapps does no testing on their daily builds and some version results in bootloops, bitgapps may run out of disk space will installing apps and Mindthegapps as causing overall slowdown of the system.

    The only recommendation I can make is to use the SMALLEST version of gapps which is PICO or equivalent naming convention. DO NOT use anything other than PICO. That is, do not use nano, mini, stock, etc.

    If you are going to install gapps, flash the rom first, reboot into system/OS, reboot to recovery, flash gapps, reboot into system/OS. That is, do not flash/install the rom and gapps at the same time.

    Q13. I'm having problems with gapps, can you answer why it's not working?
    A13. I will not answer any questions regarding gapps. This thread is about the rom, not gapps and I don't use gapps so I cannot help you. Android does not depend on gapps in order to work.

    Q14. Why isn't my post answered?
    A14. It's probably because it's answered in the FAQ or not relevant to the rom. Again, I do not run Windows OS or use gapps. Questions already answered in the FAQ will be completely ignored.

    Q15. Can I turn off the on screen navigation keys?
    A15. To turn off on screen navigation, go to settings, system, advanced, gestures, system navigation, gesture navigation. It's enabled by default because I find it useful. If you don't like it, you only need to disable once and your preference will be remembered. If you want to invert the onscreen keys, goto settings, system, buttons and enable invert layout

    Q16. What speed up/optimization tips do you suggest?
    A16.

    1. Turn off animations. Go into developer settings, scroll down to the drawing section, and set window, transition and animator scale all to "off".
    2. If you don't have a google account, don't install gapps. Use Aurora Store to get your apps as you can get all the same apps from the play store using an anonymous login.
    3. Dont' run more than 2 apps at the same time. You can probably listen to music in the background and use a web browser at the same time, but don't expect great performance from a 2015 entry level tablet.
    4. Use a web browser like Brave that has built in adblock and privacy features.
    5. Use newpipe to watch your streaming content. It has built in adblock so you don't have to watch forced ads.
    6. Look for apps that are open source, ad free and lightweight.

    Q17. Does this rom support Magisk?
    A17. I don't use Magisk myself so I don't know and Magisk is always being updated to fool Google's certification process. Others have reported Magisk as working, but I won't answer any questions regarding it.

    Q18. Will this rom ever become official?
    A18. Never. I don't want the responsibilities that come with being an official maintainer. In addition, I know my device trees, code organization and git commits will NOT meet LineageOS standards. Remember, I'm an unpaid volunteer doing this in my free time and sharing my work with you for free so you can get hundreds of hours of enjoyment from this tablet.

    Q19. What is the difference between this rom and others?
    A19. This rom tries to be pure LineageOS with little to no modifications. Other roms may have different UI, different bundled apps, etc. Use whatever meets your requirements.

    Q20. Will there be any major 18.1 code modifications in the future?
    A20. I don't anticipate any major modifications. There may be some slight tweaking to the sepolicy, small bug fixes and minor code cleanup, but all the hard work in getting the rom up and running and fixing all the major bugs have been done completed. This doesn't mean the code is perfect or well organized, but I won't be doing any major changes now that 18.1 is working. Any major changes will be done in 19.0.

    Q21. Why did you fork the device and vendor trees for 18.1?
    A21. The msm8916 repos seem geared towards phones and sometimes do not work or cause boot animation loops for tablets so I decided to fork their repos. In other words, what's deemed as msm8916-common code isn't common to all devices.

    In addition, since I'm building SM-T350, SM-T550, SM-P550 and SM-T560NU (all use the same msm8916 code), it seems easier to maintain all of them if I can control my own code repos and not worry if my changes affects the phones or not. I still have not figured out the best way to manage all my repos and it's a work in progress.

    Q22. Can you build a variant of this device? For example, a LTE or S-pen version.
    A22. If I don't physically have the device, I cannot and will not build it unless I can boot and test it myself. Even then, there's no guarantee that I can get those variant features working.

    Q23. Can I load this rom on a variant devivce like LTE or S-pen version?
    A23. The rom is built for the device explicitly listed. If you are an advanced user and understand TWRP, adb, odin, heimdall, you can try loading it on a LTE or S-pen variant by modifying the updater-script, but it may cause a bricked device, bootloops or non functionality of LTE/S-pen. You have been informed and warned!

    Q24. Will this run on the SM-T355 or SM-P355?
    A24. No. Someone has tried and it will result in a bootloop.

    Q25. How do I know if I have a BOE panel?
    A25. Some ST-350 tablets have a BOE display panel. In order for it to work with TWRP and any custom rom, you must have the correct bootloader installed on a BOE panel otherwise you will see a black/blank screen. To check to see if you have a BOE panel, open a terminal and

    Code:
    adb root
    adb shell cat /proc/cmdline

    The very last parameter will be mdss_mdp.panel. If you see BOE anywhere in that string, then you have a BOE panel. For example,

    mdss_mdp.panel=1:dsi:0:ss_dsi_panel_S6D7AA0_LSL080AL03_BOE_WXGA:1:none

    There is a fix as documented at


    Q26. What is a GO build?
    A26. A GO build uses less DRAM, disk space and supposed to be better suited for devices with 2GB DRAM or less. I have no idea whether it's true or not vs a NON GO build, but I figured I would try a GO build.

    Some of the features removed in a GO build are documented in post #46 in this thread in addition to work profiles. If you need these features, you can edit a property in the build.prop as documented in post #49.

    Q27. Okay, I understand the consequences and that this is BETA rom and willing to take the risks outlined, now where can I find the rom?
    A27. Downloads are at

    2
    NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.

    Sept 12, 2022 release notes
    1. Sept 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-09
    2. Whatever LiineageOS changed since last July release (about 12,500 files had to be recompiled).

    Aug 5, 2022 release notes
    1. Aug 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-08
    2. Whatever LiineageOS changed since last July release (about 4,000 files had to be recompiled).

    July 8, 2022 release notes
    1. July 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-07
    2. Whatever LiineageOS changed since last June release (about 1,500 files had to be recompiled).

    June 11, 2022 release notes
    1. June 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-06
    2. Whatever LiineageOS changed since last May release (about 9,500 files had to be recompiled).

    May 7, 2022 release notes
    1. May 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-05
    2. Whatever LiineageOS changed since last April release (about 11,000 files had to be recompiled).
    3. Selfie camera and video no longer crash with stock camera. Thanks to @dylux for suggesting these fixes which are commits

    https://github.com/retiredtab/devic...mmit/c9ac11147f83d611e006731aad7c14108f293d64

    and

    https://github.com/retiredtab/devic...mmit/cfa55e0478b59821f3d16501104b51ceeef8b010

    April 10, 2022 release notes
    1. Arpil 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-04
    2. Whatever LiineageOS changed since last March release (about 11,000 files had to be recompiled).

    Mar 12, 2022 release notes
    1. Mar 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-03
    2. Whatever LiineageOS changed since last Feb release (about 5,700 files had to be recompiled).

    Feb 12, 2022 release notes
    1. Feb 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-02
    2. Whatever LiineageOS changed since last January release (about 34,500 files had to be recompiled).

    Jan 20, 2022 release notes
    1. Jan 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-01
    2. Whatever LiineageOS changed since last December release (about 10,000 files had to be recompiled).

    Dec 10 release notes
    1. Dec 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2021-12
    2. Whatever LiineageOS changed since last November release (about 11,000 files had to be recompiled).

    Nov 7 release notes
    1. Nov 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/318560

    2. I enabled zram swap with size 512MB. I noticed that the last couple of months that Clash Royale would crash/close and logs showed

    Code:
    10-28 14:26:01.412    0    0 I [2:        kswapd0:  91] lowmemorykiller: Killing 'ell.clashroyale' (6730), adj 0,

    Hopefully, by enabling zram, that will stop Clash Royale from crashing/closing.

    Zswap is enabled on stock Nougat SM-T350 (part of the Samsung Tab A/E family that uses same msm8916 kernel code)

    https://github.com/retiredtab/andro...mmit/2a6bf385e6dfe6073fe328b7b1c563ccd60a5ede

    https://github.com/retiredtab/andro...mmit/438d5d3ad20cbc98f0f8c18eb610b6268de19395

    This code uses the in kernel low memory killer (lmk). I tried using the Android OS lmk, but it doesn't work very well and shows this in the log.

    Code:
    E lowmemorykiller: /proc/zoneinfo parse error
    E lowmemorykiller: Failed to get free memory!

    3. Whatever LineageOS changed since last Oct release (about 7,200 files had to be recompiled). One of these changes has removed the built in terminal program from LineageOS as AOSP deprecated this app as per

    https://review.lineageos.org/c/LineageOS/android_vendor_lineage/+/304043

    Oct 10 release notes
    1. Oct 1 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/317001
    2. Added https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/316839 to fix landscape mode system UI. This patch is not yet officially merged as of Oct 10 release.
    3. Whatever LiineageOS changed since last September release (about 6,100 files had to be recompiled).

    Sept 10 release notes
    1. Reverted the patch to https://github.com/retiredtab/andro...mmit/a32c7a0bed536281d20b7c1cf8d41c84a268cc80
    Removing systemUI from pinner services causes a 4 to 6 delay in bringing up the home screen. This is seen when loading or playing a game for about 20 minutes and then either hitting the recents or home button. By reverting this commit, pressing recents or home button brings up the systemUI right away.
    2. Sept 5 security patches as per https://review.lineageos.org/c/LineageOS/android/+/315661
    3. Whatever LiineageOS changed since last August release (about 6,200 files had to be recompiled).

    Aug 8 release notes
    1. Fix battery status icon. When you plug in AC adapter, settings, battery does not show it charging even though it is. This is due to the sepolicy being too restrictive. I added https://github.com/retiredtab/msm89...mmit/c1eca9f7740b6a384d4fab8a1e8d812f59c17a99
    2. Aug 5 security patches as per https://review.lineageos.org/c/LineageOS/android/+/314477
    3. Whatever LiineageOS changed since last July release (about 11,500 files had to be recompiled).
    4. 18.1 continues to be my daily driver since March 2021.

    July 10 release notes
    1. Initial public release to XDA. This is an ALPHA build.
    2. July 5 security patches as per https://review.lineageos.org/q/topic:"android-11.0.0_r39"+(status:eek:pen OR status:merged)
    2
    Thanks for the instructions!
    I updated the FAQ Q26/A26 to reflect what features are removed with the GO build and how to edit the build.prop file for users who want/need these features.