[ROM][testing][suez] Lineage-16.0 [05 JULY 2022]

Search This thread

Kate6

Member
Mar 25, 2009
49
24
Vancouver, WA
I am unable to install LOS 16 though, due to the system partition sizing, and don't really have any experience with using Parted or any other command line partition methods. Would you please share even just a brief step series on how you were able to resize the system partition so that it would allow you to flash LOS 16, then use the "TWRP resize" option to make the necessary room to go back and flash GApps and Magisk?

I don't know that I'd recommend monkeying with the partitions if aren't reasonably comfortable with command line tools in general... And just to say again - I'm not actually running Lineage 16. WiFi was entirely too unstable for me with the July 5th Lineage 16 ROM... So I'm actually running Lineage 14 on mine for now.

But basically, what I did was -
  1. Grabbed the parted binary from https://github.com/edk2-porting/parted-android
  2. Booted into twrp, adb pushed the parted binary to /tmp, chmod a+x'ed it
  3. "unit b" tells parted to display partition start/end/size down to the byte
  4. remove the system, cache and data partitions... I wanna say they were partitions 12, 13 and 14? Something like that. Been a week or so since I did it. (Looks like it's actually 13, 14 and 15 now that I grabbed the actual tablet to make the screenshot I attached below...)
  5. Recreate system, cache and data so that they have the same partition numbers they did previously but with their sizes adjusted... Basically this means figure out how much you wanna increase the size of "system" by and then add that same number to the end sector of system, to both the start and end sectors of the new cache and to the start sector of the new data partition... Keeping the start sector of system and the end sector of data the same as they were before the modification.
  6. Make sure you rename your newly created partitions to system, cache and userdata to match their original names...
  7. Basically, when you're done, you want the output of parted's "print" command to look exactly the same as at the start except for the "end" number of system, the "start" and "end" numbers of cache and the "start" number of data.
  8. After that you need to get the kernel to register the new partition table... The simplest way to do that is probably just to reboot the recovery.
Now the system partition image that comes with the ROM is an image for a system partition of the original size... After flashing the image you want to use this to adjust the flashed filesystem to take up the full size of the partition. The Wipe -> Advanced Wipe -> (select System) Repair or Change Filesystem -> Resize File System option in the twrp UI appears to run resize2fs for you, if you'd prefer not to do it yourself from the adb shell.

Here's a screenshot showing the "end result"... This is what my suez' partition table currently looks like. Notice the size of my system partition is 3093299200... The original size of system was 1692925952.

suez.jpg
 

puffdank

Member
Apr 25, 2012
8
0
I don't know that I'd recommend monkeying with the partitions if aren't reasonably comfortable with command line tools in general... And just to say again - I'm not actually running Lineage 16. WiFi was entirely too unstable for me with the July 5th Lineage 16 ROM... So I'm actually running Lineage 14 on mine for now.

But basically, what I did was -
  1. Grabbed the parted binary from https://github.com/edk2-porting/parted-android
  2. Booted into twrp, adb pushed the parted binary to /tmp, chmod a+x'ed it
  3. "unit b" tells parted to display partition start/end/size down to the byte
  4. remove the system, cache and data partitions... I wanna say they were partitions 12, 13 and 14? Something like that. Been a week or so since I did it. (Looks like it's actually 13, 14 and 15 now that I grabbed the actual tablet to make the screenshot I attached below...)
  5. Recreate system, cache and data so that they have the same partition numbers they did previously but with their sizes adjusted... Basically this means figure out how much you wanna increase the size of "system" by and then add that same number to the end sector of system, to both the start and end sectors of the new cache and to the start sector of the new data partition... Keeping the start sector of system and the end sector of data the same as they were before the modification.
  6. Make sure you rename your newly created partitions to system, cache and userdata to match their original names...
  7. Basically, when you're done, you want the output of parted's "print" command to look exactly the same as at the start except for the "end" number of system, the "start" and "end" numbers of cache and the "start" number of data.
  8. After that you need to get the kernel to register the new partition table... The simplest way to do that is probably just to reboot the recovery.
Now the system partition image that comes with the ROM is an image for a system partition of the original size... After flashing the image you want to use this to adjust the flashed filesystem to take up the full size of the partition. The Wipe -> Advanced Wipe -> (select System) Repair or Change Filesystem -> Resize File System option in the twrp UI appears to run resize2fs for you, if you'd prefer not to do it yourself from the adb shell.

Here's a screenshot showing the "end result"... This is what my suez' partition table currently looks like. Notice the size of my system partition is 3093299200... The original size of system was 1692925952.

View attachment 5683061
Wow, thank you, very much APPRECIATED! :)
 

psi78

Senior Member
Feb 22, 2020
109
32
Respect @Kate6 that you did that system partition resizing endeavour👍🏻

For anyone having problems with installing gapps because of too small system partition and wants to debloat LineageOS and free up space on system partition:

I wrote a small shell script, which deletes lots of system apps (which most of us probably don't need).

See attached file and screenshots for cleaned up app directory and background apps.
It's just kinda quick and dirty. If you wanna keep some apps you may change the script with a text editor (nano in twrp for example) and comment the corresponding lines out with #

It requires a root shell and system partition mounted as writable.
An easy way to do both of that is from TWRP (mount the System partition, then use the built in terminal app in TWRP Advanced menu).


A clean install of the ROM and using the script from an external sd card would be like this:

1. Wipe all partitions besides Micro SD Card from TWRP, also format data partition even. Reboot into recovery/TWRP then to avoid mount problems.

2. Install the latest version of the ROM from TWRP. Don't start LineageOS yet.

3. Mount the system partition in the "Mount" section of TWRP again

4. Start Terminal from TWRP ("Advanced" section in TWRP menu) and execute the following commands:
cd /external_sd
chmod +x suezcleanapp2.sh
./suezcleanapp2.sh
The script should run without errors (if there's an error "file not found" or the like, you probably haven't mounted system partition properly)

5. Install opengapps 9 arm64 pico.

Optionally also remove Google Contacts and Calendar Sync Adapters then to keep Google from syncing your personal data to the tablet.
To do that mount System partition again (the opengapps installer script unmounts it after completion).
Then use the following shell command in TWRP Terminal:
rm -r /system/app/GoogleC*

Optionally also remove
/system/app/GoogleTTS (used for voice search in Playstore/other Google apps like Google Maps)
/system/priv-app/GoogleBackupTransport (backups your settings and data to Google servers, may cause unwanted background activity, i.e. if you don't want to backup these with a media tablet usage style)

Boot into LineagesOS then for the first time.

6. When the setup wizard asks for wlan connection: i'd skip this step, complete the setup wizard without internet connection. Then after the setup wizard, enable Power Saving mode, establish Wlan connection and enter your credentials in Playstore, let it do all updates (you can also manually update Playstore app itself when using Playstore Settings/About/Playstore Version). Then finalize the setup wizard installation process of LOS.


This worked for me with current version of the ROM and opengapps 9 arm64 pico.

And as already said before, in the current state of the ROM i'd advise to enable Power Saving in Quick settings and use an app like "CPU Info" (after startup) to check if CPU cores 2 and 3 are powering down normally in idle mode (at least like after 20-30 secs after booting if no more updates are due).
If they don't power down, do a cold boot (power off/ power on) or try reboot. Then if you have the tablet in a good state, try to avoid rebooting, just put it into flight mode over night or the like.

If you have any comments/additions let me know.


Edit: Built a slightly more sophisticated version 2 ("suezcleanapp2.sh") which backups all removed system apps to /sdcard/suezbackup/ and correspondig subdirectories. Tested it with TWRP Terminal. Not sure if this works with ADB.
Also preserved the LineageOS Dark and Black Theme to enable correct functioning of Dark mode.
Edit: Also added comments explaining the apps in version 2 of the script
 

Attachments

  • Screenshot_20220814-181507_Settings.png
    Screenshot_20220814-181507_Settings.png
    82.7 KB · Views: 66
  • Screenshot_20220814-183702_Settings.png
    Screenshot_20220814-183702_Settings.png
    61.8 KB · Views: 64
  • Screenshot_20220814-181518_Trebuchet.png
    Screenshot_20220814-181518_Trebuchet.png
    149.6 KB · Views: 59
  • Screenshot_20220814-184143_LineageOS_Settings.png
    Screenshot_20220814-184143_LineageOS_Settings.png
    39.9 KB · Views: 69
  • suezcleanapp2.sh
    3.5 KB · Views: 68
  • suezcleanapp.sh
    665 bytes · Views: 23
Last edited:

psi78

Senior Member
Feb 22, 2020
109
32
I don't know that I'd recommend monkeying with the partitions if aren't reasonably comfortable with command line tools in general... And just to say again - I'm not actually running Lineage 16. WiFi was entirely too unstable for me with the July 5th Lineage 16 ROM... So I'm actually running Lineage 14 on mine for now.

But basically, what I did was -
  1. Grabbed the parted binary from https://github.com/edk2-porting/parted-android
  2. Booted into twrp, adb pushed the parted binary to /tmp, chmod a+x'ed it
  3. "unit b" tells parted to display partition start/end/size down to the byte
  4. remove the system, cache and data partitions... I wanna say they were partitions 12, 13 and 14? Something like that. Been a week or so since I did it. (Looks like it's actually 13, 14 and 15 now that I grabbed the actual tablet to make the screenshot I attached below...)
  5. Recreate system, cache and data so that they have the same partition numbers they did previously but with their sizes adjusted... Basically this means figure out how much you wanna increase the size of "system" by and then add that same number to the end sector of system, to both the start and end sectors of the new cache and to the start sector of the new data partition... Keeping the start sector of system and the end sector of data the same as they were before the modification.
  6. Make sure you rename your newly created partitions to system, cache and userdata to match their original names...
  7. Basically, when you're done, you want the output of parted's "print" command to look exactly the same as at the start except for the "end" number of system, the "start" and "end" numbers of cache and the "start" number of data.
  8. After that you need to get the kernel to register the new partition table... The simplest way to do that is probably just to reboot the recovery.
Now the system partition image that comes with the ROM is an image for a system partition of the original size... After flashing the image you want to use this to adjust the flashed filesystem to take up the full size of the partition. The Wipe -> Advanced Wipe -> (select System) Repair or Change Filesystem -> Resize File System option in the twrp UI appears to run resize2fs for you, if you'd prefer not to do it yourself from the adb shell.

Here's a screenshot showing the "end result"... This is what my suez' partition table currently looks like. Notice the size of my system partition is 3093299200... The original size of system was 1692925952.

View attachment 5683061
Did you have heat problems on this ROM and unstable Wifi? The tablet feels really hot on the back in that case. If so enable Power Saving/Extreme Power Saver mode, should cool it down more.
 

Kate6

Member
Mar 25, 2009
49
24
Vancouver, WA
Did you have heat problems on this ROM and unstable Wifi? The tablet feels really hot on the back in that case. If so enable Power Saving/Extreme Power Saver mode, should cool it down more.

I can't say the tablet at any point felt physically hot to the touch, but I still went ahead and tested your theory. In addition to turning on Extreme Power Saver, I also left the tablet sitting on top of my air conditioner's exhaust vent for a nice long while, so that when I picked it up the chassis felt genuinely cool to the touch.

I also tried using a kernel tweaker app to underclock the CPU.

WiFi was still considerably less reliable in the July 5th build of the Lineage 16 ROM from this thread than in the Lineage 14 ROM I've been using. Which is this one, to be specific.
 

psi78

Senior Member
Feb 22, 2020
109
32
I can't say the tablet at any point felt physically hot to the touch, but I still went ahead and tested your theory. In addition to turning on Extreme Power Saver, I also left the tablet sitting on top of my air conditioner's exhaust vent for a nice long while, so that when I picked it up the chassis felt genuinely cool to the touch.

I also tried using a kernel tweaker app to underclock the CPU.

WiFi was still considerably less reliable in the July 5th build of the Lineage 16 ROM from this thread than in the Lineage 14 ROM I've been using. Which is this one, to be specific.
Mm alright. So it isn't the cpu thing.

Are you using 2.4 or 5 GHz Wlan?

Here someone already reported WLAN/packet loss problems with this suez LOS16 ROM on 5GHz WLAN:

I use 2.4 GHz WLAN (fritz!box Modem/german DSL) and it works fine for me.
https://www.speedtest.net/ showing stable 50Mbps downstream/10 Mbps upstream which is my DSL speed.
https://packetlosstest.com tests are reporting zero packet losses when i use suez with this LOS16 ROM.

So maybe 5GHz Wlan is bugged, @ggow what do you think?

@Kate6:
With Smartpack Kernel Manager you could also try out other settings for TCP but probably won't help much if it's a driver issue.
Or send a logcat/dmesg to ggow also.
 

Kate6

Member
Mar 25, 2009
49
24
Vancouver, WA
Mm alright. So it isn't the cpu thing.

Are you using 2.4 or 5 GHz Wlan?

Tried with both 2.4 GHz and 5 GHz. And tried both on two separate routers... A Netgear R7000 and a Linksys WRT1200AC. Both running the August 03 2022 build of DDWRT. Similar instability problems with all combos.

Or send a logcat/dmesg to ggow also.

I'm probably going to do that, but I'm thinking I want to set it up so it's just the ROM with no apps whatsoever (including no gapps) installed so the logcat will be as clean as possible. Should be able to get that done in the next few days.

... Or really, ggow's signature clearly says he won't answer questions over PM, so my plan was to post a logcat to this thread.
 
  • Like
Reactions: psi78

Kate6

Member
Mar 25, 2009
49
24
Vancouver, WA
Alright I sat down and captured a logcat...

This is just the lineage-16.0-20220705-UNOFFICIAL-suez.zip ROM installed. No gapps, no apps. The only things I tweaked was turning on developer mode for ADB access and gave it the passport to one of my 2.4 GHz access points (since you guys seem to say it's stable with 2.4 GHz for you)...

I let it make several attempts at connecting. At one point the list of SSID's it was seeing went blank so I toggled the wifi off and back on again, then let it try some more...

Edit: xda doesn't seem to want to let me attach the file to this post, so here it is as a gist...
 

psi78

Senior Member
Feb 22, 2020
109
32
Alright I sat down and captured a logcat...

This is just the lineage-16.0-20220705-UNOFFICIAL-suez.zip ROM installed. No gapps, no apps. The only things I tweaked was turning on developer mode for ADB access and gave it the passport to one of my 2.4 GHz access points (since you guys seem to say it's stable with 2.4 GHz for you)...

I let it make several attempts at connecting. At one point the list of SSID's it was seeing went blank so I toggled the wifi off and back on again, then let it try some more...

Edit: xda doesn't seem to want to let me attach the file to this post, so here it is as a gist...
Don't really have a clue of this, but this could maybe the relevant part in your logcat:

08-15 21:31:54.103 2126 2126 I wpa_supplicant: wlan0: GAS-QUERY-DONE addr=ae:4c:a5:bd:ea:31 dialog_token=13 freq=5785 status_code=0 result=TIMEOUT
08-15 21:31:54.104 2126 2126 I wpa_supplicant: wlan0: ANQP-QUERY-DONE addr=ae:4c:a5:bd:ea:31 result=FAILURE
08-15 21:31:55.012 488 2129 D DhcpClient: Broadcasting DHCPDISCOVER
08-15 21:31:56.145 2126 2126 I wpa_supplicant: wlan0: GAS-QUERY-DONE addr=ae:4c:a5:bd:ea:30 dialog_token=14 freq=5785 status_code=0 result=TIMEOUT
08-15 21:31:56.147 2126 2126 I wpa_supplicant: wlan0: ANQP-QUERY-DONE addr=ae:4c:a5:bd:ea:30 result=FAILURE
08-15 21:31:56.164 488 2203 D DhcpClient: Received packet: cc:f7:35:09:0f:25 OFFER, ip /10.0.6.182, mask /255.255.255.0, DNS servers: /10.0.6.1 , gateways [/10.0.6.1] lease time 86400, domain adultstore
08-15 21:31:56.165 488 2129 D DhcpClient: Got pending lease: IP address 10.0.6.182/24 Gateway 10.0.6.1 DNS servers: [ 10.0.6.1 ] Domains adultstore DHCP server /10.0.6.1 Vendor info null lease 86400 seconds
08-15 21:31:56.168 488 2129 D DhcpClient: Broadcasting DHCPREQUEST ciaddr=0.0.0.0 request=10.0.6.182 serverid=10.0.6.1
08-15 21:31:58.191 2126 2126 I wpa_supplicant: wlan0: GAS-QUERY-DONE addr=ae:4c:a5:bd:ea:32 dialog_token=15 freq=5785 status_code=0 result=TIMEOUT
08-15 21:31:58.192 2126 2126 I wpa_supplicant: wlan0: ANQP-QUERY-DONE addr=ae:4c:a5:bd:ea:32 result=FAILURE
08-15 21:32:00.233 2126 2126 I wpa_supplicant: wlan0: GAS-QUERY-DONE addr=ae:4c:a5:bd:ea:33 dialog_token=16 freq=5785 status_code=0 result=TIMEOUT
08-15 21:32:00.233 2126 2126 I wpa_supplicant: wlan0: ANQP-QUERY-DONE addr=ae:4c:a5:bd:ea:33 result=FAILURE
08-15 21:32:00.698 2126 2126 I wpa_supplicant: wlan0: GAS-QUERY-DONE addr=ae:4c:a5:b6:44:31 dialog_token=17 freq=2462 status_code=0 result=TIMEOUT
08-15 21:32:00.699 2126 2126 I wpa_supplicant: wlan0: ANQP-QUERY-DONE addr=ae:4c:a5:b6:44:31 result=FAILURE
08-15 21:32:01.176 488 2129 D DhcpClient: Broadcasting DHCPREQUEST ciaddr=0.0.0.0 request=10.0.6.182 serverid=10.0.6.1
08-15 21:32:01.217 2126 2126 I wpa_supplicant: wlan0: GAS-QUERY-DONE addr=ae:4c:a5:b6:44:35 dialog_token=18 freq=2462 status_code=0 result=TIMEOUT
08-15 21:32:01.222 2126 2126 I wpa_supplicant: wlan0: ANQP-QUERY-DONE addr=ae:4c:a5:b6:44:35 result=FAILURE
08-15 21:32:01.743 2126 2126 I wpa_supplicant: wlan0: GAS-QUERY-DONE addr=ae:4c:a5:b6:44:37 dialog_token=19 freq=2462 status_code=0 result=TIMEOUT
08-15 21:32:01.743 2126 2126 I wpa_supplicant: wlan0: ANQP-QUERY-DONE addr=ae:4c:a5:b6:44:37 result=FAILURE
08-15 21:32:03.803 2126 2126 I wpa_supplicant: wlan0: GAS-QUERY-DONE addr=ae:4c:a5:b6:ea:31 dialog_token=20 freq=2462 status_code=0 result=TIMEOUT
08-15 21:32:03.803 2126 2126 I wpa_supplicant: wlan0: ANQP-QUERY-DONE addr=ae:4c:a5:b6:ea:31 result=FAILURE
08-15 21:32:05.845 2126 2126 I wpa_supplicant: wlan0: GAS-QUERY-DONE addr=ae:4c:a5:b6:ea:32 dialog_token=21 freq=2462 status_code=0 result=TIMEOUT
08-15 21:32:05.845 2126 2126 I wpa_supplicant: wlan0: ANQP-QUERY-DONE addr=ae:4c:a5:b6:ea:32 result=FAILURE
08-15 21:32:06.190 488 2129 D DhcpClient: Broadcasting DHCPREQUEST ciaddr=0.0.0.0 request=10.0.6.182 serverid=10.0.6.1
08-15 21:32:07.909 2126 2126 I wpa_supplicant: wlan0: GAS-QUERY-DONE addr=ac:4c:a5:b5:ea:34 dialog_token=22 freq=2462 status_code=0 result=TIMEOUT
08-15 21:32:07.909 2126 2126 I wpa_supplicant: wlan0: ANQP-QUERY-DONE addr=ac:4c:a5:b5:ea:34 result=FAILURE
08-15 21:32:09.946 2126 2126 I wpa_supplicant: wlan0: GAS-QUERY-DONE addr=ae:4c:a5:b6:ea:35 dialog_token=23 freq=2462 status_code=0 result=TIMEOUT
08-15 21:32:09.946 2126 2126 I wpa_supplicant: wlan0: ANQP-QUERY-DONE addr=ae:4c:a5:b6:ea:35 result=FAILURE
08-15 21:32:11.989 2126 2126 I wpa_supplicant: wlan0: GAS-QUERY-DONE addr=ae:4c:a5:b6:ea:37 dialog_token=24 freq=2462 status_code=0 result=TIMEOUT
08-15 21:32:11.989 2126 2126 I wpa_supplicant: wlan0: ANQP-QUERY-DONE addr=ae:4c:a5:b6:ea:37 result=FAILURE
08-15 21:32:12.656 2126 2126 I wpa_supplicant: wlan0: GAS-QUERY-DONE addr=ac:4c:a5:b5:44:34 dialog_token=25 freq=2462 status_code=0 result=TIMEOUT
08-15 21:32:12.656 2126 2126 I wpa_supplicant: wlan0: ANQP-QUERY-DONE addr=ac:4c:a5:b5:44:34 result=FAILURE
08-15 21:32:14.166 488 2129 D DhcpClient: Broadcasting DHCPDISCOVER
08-15 21:32:14.569 488 573 I PowerManagerService: Waking up from sleep (uid=1000 reason=android.policy:pOWER)...
08-15 21:32:14.570 488 488 W UsageStatsService: Event reported without a package name
08-15 21:32:14.577 488 514 I DisplayPowerController: Blocking screen on until initial contents have been drawn.
08-15 21:32:14.579 488 507 W KernelCpuProcReader: File not exist: /proc/uid_cpupower/time_in_state
08-15 21:32:14.579 488 507 W KernelCpuProcReader: File not exist: /proc/uid_cpupower/concurrent_active_time
08-15 21:32:14.580 488 507 W KernelCpuProcReader: File not exist: /proc/uid_cpupower/concurrent_policy_time
08-15 21:32:14.590 272 272 D SurfaceFlinger: Set power mode=2, type=0 flinger=0x7f1c043000
08-15 21:32:14.590 257 449 I hwcomposer: [HWC] SetPowerMode(2) Display(0)
08-15 21:32:14.590 488 512 I DisplayManagerService: Display device changed state: "Built-in Screen", ON
08-15 21:32:14.604 488 573 I InputReader: Reconfiguring input devices. changes=0x00000004
08-15 21:32:14.642 272 476 D IMGSRV : gralloc_device_alloc:1039: hnd=0x7f1c138d20 ID=8910 fd=32 ref=0 1200(1216)x1920(1920)-0x1 usage=0xb00 size=9338880(9338880) cache=0
08-15 21:32:14.642 272 476 D IMGSRV : gralloc_register_buffer:1328: hnd=0x7f1c138e60 ID=8910 fd=53 ref=2
08-15 21:32:14.642 272 476 D IMGSRV : gralloc_device_free:1178: ID=8910 ref=1
08-15 21:32:14.644 660 928 D IMGSRV : gralloc_register_buffer:1328: hnd=0x7eda4f1960 ID=8910 fd=94 ref=1
08-15 21:32:14.658 2126 2126 E wpa_supplicant: wpa_driver_nl80211_driver_cmd: failed to issue private commands, error msg: Out of memory

Edit: Do your WLAN routers have IPV6 enabled? Maybe an IPV6 DHCP/ DNS request leading to delays there🤔🤔 (since it shows several timouts/failures in conjunction with an ipv6 address, also apparently leading to an out of memory error)
 
Last edited:

Kate6

Member
Mar 25, 2009
49
24
Vancouver, WA
Edit: Do your WLAN routers have IPV6 enabled? Maybe an IPV6 DHCP/ DNS request leading to delays there🤔🤔 (since it shows several timouts/failures in conjunction with an ipv6 address, also apparently leading to an out of memory error)

Sorry where do you see IPv6 related stuff? All I'm seeing is failed ANQP queries.

None of the MAC addresses on the failed ANQP queries appear to be in my router's ARP table though. My router's OUI prefix is C0:56:27 (Belkin) and the tablet's of course is cc:f7:35 (Amazon)...
 

Kate6

Member
Mar 25, 2009
49
24
Vancouver, WA
Okay they appear to be the SSID's of neighbors' routers.

Code:
[email protected]:~# nmcli d wifi list
IN-USE  BSSID              SSID                    MODE   CHAN  RATE        SIGNAL  BARS  SECURITY      
        14:CC:20:D1:DC:AC  TheJellyFox-2.4GHz      Infra  6     195 Mbit/s  100     ****  WPA2          
        C0:56:27:76:27:9A  RoyCircles-2.4GHz       Infra  9     130 Mbit/s  100     ****  WPA2 WPA3        <---- My router
        78:23:AE:85:AD:E3  Radish                  Infra  6     195 Mbit/s  92      ****  WPA2          
        7A:23:AE:85:AD:E3  --                      Infra  6     195 Mbit/s  90      ****  WPA1 WPA2    
        0E:C0:3E:35:E8:09  --                      Infra  11    130 Mbit/s  89      ****  WPA2          
        AE:4C:A5:B6:EA:31  --                      Infra  11    260 Mbit/s  87      ****  WPA2 802.1X     <--- failed ANQP query
        AC:4C:A5:B5:EA:34  Sassypants House        Infra  11    260 Mbit/s  85      ****  WPA2            <---- failed ANQP query
        AE:4C:A5:B6:EA:35  --                      Infra  11    260 Mbit/s  85      ****  WPA2 WPA3       <----- failed ANQP query
 
  • Like
Reactions: Kramar111

psi78

Senior Member
Feb 22, 2020
109
32
Sorry where do you see IPv6 related stuff? All I'm seeing is failed ANQP queries.

None of the MAC addresses on the failed ANQP queries appear to be in my router's ARP table though. My router's OUI prefix is C0:56:27 (Belkin) and the tablet's of course is cc:f7:35 (Amazon)...
yeah, right, my bad, thought at first glance those : separated numbers where ipv6 adresses. But like you found out, they were are mac addresses/BSSIDs of WLAn routers.

Well this ROM already had problems with hidden SSIDs in the past, but not sure if that's related to your problem.
But weird if other Wlan networks lead to such problems with potential out of memory error for the Wlan driver ("wpa_supplicant: wpa_driver_nl80211_driver_cmd: failed to issue private commands, error msg: Out of memory")

Didn't see errors like that in my logcat yet🤔, but in Germany on the other hand other Wlan DSL routers are common, the fritz!box is widely used and some Telekom routers.

Well, i'd say go to the utmost and tell your neighbours to throw out their hardware pieces of crap😆
 
Last edited:

Kate6

Member
Mar 25, 2009
49
24
Vancouver, WA
Well this ROM already had problems with hidden SSIDs in the past, but not sure if that's related to your problem.
But weird if other Wlan networks lead to such problems with potential out of memory error for the Wlan driver.
Didn't see errors like that in my logcat yet🤔

I tend to think it was making those queries because I had the tablet sitting on the "nearby WiFi AP's" activity screen... I can't imagine why else it would be querying neighbors' routers. I'm thinking they're just part of building that list.

This bit appears to be it successfully talking to my router... But the connection didn't actually stay up.


Code:
08-15 21:31:56.164 488 2203 D DhcpClient: Received packet: cc:f7:35:09:0f:25 OFFER, ip /10.0.6.182, mask /255.255.255.0, DNS servers: /10.0.6.1 , gateways [/10.0.6.1] lease time 86400, domain adultstore
08-15 21:31:56.165 488 2129 D DhcpClient: Got pending lease: IP address 10.0.6.182/24 Gateway 10.0.6.1 DNS servers: [ 10.0.6.1 ] Domains adultstore DHCP server /10.0.6.1 Vendor info null lease 86400 seconds
08-15 21:31:56.168 488 2129 D DhcpClient: Broadcasting DHCPREQUEST ciaddr=0.0.0.0 request=10.0.6.182 serverid=10.0.6.1
 

Jemus

Senior Member
Jun 5, 2012
105
15
I rooted my old fire 10 sues, than I did the softbrick and was able to install twrp.
As all files were deleted during the unlock process I then installed this LineageOS Rom and rebooted the device.

Only thing happening is, that I see the LineageOS Boot animation. But the tablet doesn't get past that.

Any ideas what might have run wrong?
 

psi78

Senior Member
Feb 22, 2020
109
32
I rooted my old fire 10 sues, than I did the softbrick and was able to install twrp.
As all files were deleted during the unlock process I then installed this LineageOS Rom and rebooted the device.

Only thing happening is, that I see the LineageOS Boot animation. But the tablet doesn't get past that.

Any ideas what might have run wrong?
If you haven't done already wipe all partitions besides micro sd card in TWRP and format data partition.
Then reboot to TWRP/recovery and install the ROM.
Should startup then, first startup takes a long time though, something like 1-2 mins where you only see the boot animation (during which apps are optimized)
 

Jemus

Senior Member
Jun 5, 2012
105
15
If you haven't done already wipe all partitions besides micro sd card in TWRP and format data partition.
Then reboot to TWRP/recovery and install the ROM.
Should startup then, first startup takes a long time though, something like 1-2 mins where you only see the boot animation (during which apps are optimized)
Already solved that Problem by repairing the Data Partition via twrp. I formatted it to ext4. Before this it wasn't mountable.
 
  • Like
Reactions: psi78

FirstEver

Senior Member
Jul 18, 2013
397
530
London
www.firstever.eu
Hi,
I am using the older LineageOS 12.1-20200505-UNOFFICIAL-suez on my FIre 10 with some older TWRP version.
What is the easiest way to upgrade it to LineageOS 16, without bricking this tablet?

1. Flash new TWRP image using old TWRP? [DONE]
2. Wipe Data, Cache, System partitions in TWRP and install new ROM? [DONE]
3. Does the latest Magisk works with this ROM? [DONE]
4. What GApps version I can use? (probably the system partition is very small). [ERROR 70]

Is is possible to install GApps on this ROM without changing the size of System partition size?
I tested PICO, NANO and MICRO and always see ERROR 70.

Thanks!
 
Last edited:

psi78

Senior Member
Feb 22, 2020
109
32
Hi,
I am using the older LineageOS 12.1-20200505-UNOFFICIAL-suez on my FIre 10 with some older TWRP version.
What is the easiest way to upgrade it to LineageOS 16, without bricking this tablet?

1. Flash new TWRP image using ADB or directly from old TWRP?
2. Wipe Data, Cache, System partitions in TWRP and install new ROM?
3. Does the latest Magisk works with this ROM?
4. What GApps version I can use? (probably the system partition is very small).

Thanks!

1. I think both ways work,
2. but for a clean install i've made the best experiences with wiping all partitions (besides micro sd card) and formatting data partition from TWRP first.
If you wanna be extra sure the install works fine, also use the repair partition function in TWRP for every partition possible.
From ADB the risk of accidentially erasing a partition or getting mount problems during the installation is a bit higher in my experience, when you clean up partitions (unless you know exactly what you're doing).
If you wanna use an encrypted data partition, i think updating TWRP first is the way.

To 3.: Up to TWRP version 3.6.1-9.0 Magisk should work fine. If you install Magisk with TWRP 3.6.1-9.2, it leads to a bootloop. It's possible to make it work, but more complicated. AFAIK TWRP 3.6.1-9.2 supports usb-otg and MTP, so if you don't need that and are installing the ROM just from an external sd card, you could stay on TWRP 3.6.1-9.0.
If you only need root access and no magisk modules (or wanna post logcats which ggow accepts ;-) ), alternatively you could use the ROM's built in su (i think it's the LineageOS su addon).

4. opengapps 9 arm64 pico is fail safest.
Just Netflix and Disney+ installation is a bit more complicated then (either magisk safetynet mod and using props way or direct download from apkmirror.com)
If you need more space on system partition you could use my script to delete system apps: https://forum.xda-developers.com/t/...-0-05-july-2022.4232785/page-34#post-87282103
I also tried bitgapps and bitgapps microg before, which also work if you do a clean install of the ROM each time. But in case you wanna do dirty ROM updates later, other guys here have reported problems with bitgapps after doing a dirty flash of a new ROM version, which seem to have to do with some boot scripts of bitgapps.
Aurora store and pure microg setup also kind of works as a basic setup for using apps from playstore (this rom has the possibility of enabling signature spoofing which you need for microg to work properly).
 
Last edited:
  • Like
Reactions: FirstEver

psi78

Senior Member
Feb 22, 2020
109
32
Hi,
I am using the older LineageOS 12.1-20200505-UNOFFICIAL-suez on my FIre 10 with some older TWRP version.
What is the easiest way to upgrade it to LineageOS 16, without bricking this tablet?

1. Flash new TWRP image using old TWRP? [DONE]
2. Wipe Data, Cache, System partitions in TWRP and install new ROM? [DONE]
3. Does the latest Magisk works with this ROM? [DONE]
4. What GApps version I can use? (probably the system partition is very small). [ERROR 70]

Is is possible to install GApps on this ROM without changing the size of System partition size?
I tested PICO, NANO and MICRO and always see ERROR 70.

Thanks!
Use opengapps pico, others are really too big.

To get pico installed, delete unneeded LineageOS apps with my script (or look at the script with a text editor and remove apps mentioned there by hand in TWRP file manager). It backups the apps, so if you need them later you could reinstall them.

bromite-webview in /system/app/ directory is also a big file.
You could delete it and reinstall it later, or install Google Android Webview later, depending on your liking.
I described the manual installation of webview here:
And here:
You can download the current version of bromite webview.apk here:
Install instructions also here:
 
Last edited:

Top Liked Posts

  • 2
    Netflix and Disney is playing at 1024p, can you confirm the widevine status ?
    Only L3 / Max. SD resolution stated in Netflix 7 App for LOS12.1 (like on LOS16). DRM Check - DRM Info app reports Widevine DRM Level1, but Security L3, so L3 in the end i guess. But Netflix on LOS12.1 at least playing longer than 23 mins without having to reboot. Hope ggow fixes it though in the times when the baby is sleeping😆
  • 10
    Hi all, we now have a new little member to our family so as you can imagine I'm busy.
    When I have time, I'll be looking at the CPU / GPU issues.

    Hope everyone is keeping well!
    3
    Hi all, we now have a new little member to our family so as you can imagine I'm busy.
    When I have time, I'll be looking at the CPU / GPU issues.

    Hope everyone is keeping well!
    Congratulations! Happy arrival to the new earth resident😃
    Just became a father myself too on Thursday 😊🕺
    2
    Hi all, we now have a new little member to our family so as you can imagine I'm busy.
    When I have time, I'll be looking at the CPU / GPU issues.

    Hope everyone is keeping well!
    Wooohooo :)!! Congrats!!

    It's undestandable to shift the priority to cuddling ;-)!! Enjoy it!!
    2
    Hi all,

    Thank you for all the effort! The build ist just amazing and the tablet works like a charm!

    Is there any information about when the overheating problem will be fixed or what can I do to try to avoid it?

    The tablet is mainly used for my son to play the cartoons over plex :).

    What I also noticed, when playing youtube videos the video starts to “shake” does anybody has the same issue?
    I also have an issue playing videos over chrome - they are good for a while but then they zoom to like 200% and I can only see one part of it. (Imagine that a screen is devided to four equal parts (2 - top und 2 - down) then I only see the top left part) does someone has the same issue?

    Thank you!! Keep up the awesome work!!
    See in my posting here (after the installation steps) to reduce the overheating problems/probability:
    2
    Netflix and Disney is playing at 1024p, can you confirm the widevine status ?
    Only L3 / Max. SD resolution stated in Netflix 7 App for LOS12.1 (like on LOS16). DRM Check - DRM Info app reports Widevine DRM Level1, but Security L3, so L3 in the end i guess. But Netflix on LOS12.1 at least playing longer than 23 mins without having to reboot. Hope ggow fixes it though in the times when the baby is sleeping😆
  • 50
    Disclaimer
    Code:
    /*
    * I am not responsible for bricked devices, dead SD cards, thermonuclear war,
    * or you getting fired because the alarm app failed.
    * Please do some research if you have any concerns about features included
    * in the products you find here before flashing it!
    * YOU are choosing to make these modifications.
    */

    - EVEN MORE IMPORTANT: This ROM only works on devices using the bootloader hack. See <<< HERE >>> to unlock your devices.

    - IMPORTANT: Do not update Magisk via the Magisk Manager App, your device will enter a bootloop if you do. Instead update Magisk via TWRP only. If you do this by accident then it is recoverable by just flashing the latest version of the ROM again (with gapps etc as required). This will be fixed in a later update.

    Rules
    - Please search the thread before asking questions
    - Please try to stay on topic, I know it's not always possible
    - When reporting bugs please post a logcat and/or dmesg where possible

    Lastest TWRP version
    - 3.6.1-9.2

    Downloads

    - Google Drive

    Source Code

    Thanks
    - @k4y0z and @xyz` for the bootloader hack
    - @k4y0z for the initial kernel
    - LineageOS
    16
    🛠 Worklist / Tasks

    - [fixed] Bluetooth works
    - [fixed] Audio works
    - [fixed] Internal storage isn't accessible from any app
    - [done] Sensors working
    - [fixed] Touch sounds are working
    - [done] Test audio format playback - mp3 working
    - [done] Tested video playback with NewPipe which is working
    - [fixed] WiFi signal strength not working
    - [done] Support aptX-HD encoder for bluetooth
    - [fixed] No adb during boot
    - [fixed] WiFi working
    - [fixed] Navbar icon corruption
    - [fixed] Wallpaper corruption
    - [fixed] Laggy graphics
    - [fixed] High cpu usage
    - [fixed] DRM not working
    - [fixed] Hardware OMX (for the most part)
    - [fixed] Wired headphones not working
    - [done] Enable OTG USB for ethernet
    - [fixed] Youtube black screen with audio
    - [fixed] MtkOmxCore crash
    - [fixed] Battery showing wrong capacity - reported here
    - [fixed] "There's an internal problem with your device." dialog
    - [fixed] SIM card prompt
    - [fixed] Chrome cannot access internal storage
    - [fixed] Poor WiFi throughput (potential cause of choppy video playback)
    - [fixed] Disney app crashing (more info here)
    - [fixed] Speakers continuing to play while headphones are plugged in
    - [fixed] Cannot switch wifi on after storage encryption enabled
    - [hold] Bluetooth not working properly - can't see issue here
    - [fixed] Magisk update by app
    - [fixed] Storage permission issues (cause of some apps crashing)
    - [done] Upstreamed kernel
    - [todo] TWRP: USB-OTG not working
    - [fixed] USB-OTG Ethernet
    - [fixed] TWRP: MTP access
    - [todo] Voice assist MIC not working
    - [done] Added android.hardware.opengles.aep.xml permissions
    - [fixed] LiveDisplay not working
    - [fixed] Backlight HAL Errors

    - [todo] Shutdown after entering sleep mode (suspect cpu/gpu coming up in the wrong state -> overheating)
    - [todo] Gapps > pico causing not enough space error
    - [todo] Youtube black screen with audio
    - [todo] Mirrorcast not working
    - [todo] Multi-user not working
    - [todo] Navbar problem when keyboard is in horizontal mode
    - [todo] Playing videos over SMB failure after 30 min (more info here)
    - [todo] Can't connect to hidden WiFi networks
    - [todo] Lego app not working (more info here)
    - [todo] Cameras not working (more info here)
    - [todo] SELinux
    - [todo] Intermittent high idle cpu usage
    - [todo] Investigate L1 widevine support (L3 currently)
    - [todo] Pass safetynet
    - [todo] Device build fingerprinting
    - [todo] Enable zram?
    - [todo] Device encryption (TWRP)
    - [todo] Battery idle mode
    - [todo] Offline charging mode
    - [todo] Low speaker volume
    - [todo] Thermal Shutoff, overheating
    - [todo] System partition needs to be increased in size to accomodate gapps
    12
    But why OP decided to go back to 14.1?

    Never said for suez I was going back to 14.1.
    I will be continuing with lineage-16.0 for suez.
    12
    ℹ️ New Build is Up

    Dated: 16 March 2022

    - [fixed] MtkOmxCore crash
    - [fixed] Better auto adjust on backlight
    - [fixed] SIM card prompt
    - [fixed] Changed battery capacity to 6300mAh
    - [fixed] sdcard access for chrome and other apps
    - [fixed] "There's an internal problem with your device." dialog
    - [info] Explicitly enable sdcardfs
    - [info] Refactor root init scripts
    - [info] Remove deprecated storage_list.xml
    - [info] Clean-up build.prop

    Download from Google Drive link on OP.
    11
    ⏱ Change log / Release Notes

    05 July 2022

    - [fixed] Backlight HAL Errors
    - [fixed] LiveDisplay not working

    06 May 2022
    - [fixed] Voice assist MIC not working
    - [fixed] USB-OTG Ethernet
    - [fixed] TWRP: MTP access
    - [fixed] TWRP: Fixed USB-OTG
    - [info] Added android.hardware.opengles.aep.xml permissions

    13 April 2022
    - [fixed] Terminal input via apps and adb shell

    12 April 2022
    - [kernel] Up-streamed to 3.18.140
    - [kernel] Enable per user storage quota
    - [kernel] Optimized build flags for Cortex-a53
    - [kernel] Boeffla Wakelock Blocker Driver v1.1.0
    - [kernel] Enable some TCP congestion algorithms
    - [kernel] Westwood Default TCP congestion algorithm
    - [kernel] Sdcardfs v2.0
    - [info] Remove aptX bluetooth libraries for now
    - [info] Mount /system partition early-mount style
    - [info] Add vendor security patch

    06 April 2022
    - [fixed] Fix KernelUidCpuTimeReader errors
    - [info] Revert audio HIDL from 2.0 to 4.0 back to 2.0 - our drivers aren't ready for this
    - [info] Put storage permissions force close on the todo list
    - [info] Chrome browser works
    - [info] Jelly browser works
    - [info] WeDo lego app works

    Show Further History

    03 April 2022
    - [fixed] Magisk update by app
    - [fixed] Storage permission issues (cause of some apps crashing)
    - [fixed] Lego app not working (more info here)
    - [fixed] Cannot switch wifi on after storage encryption enabled
    - [info] Update suez defconfig in kernel to be more inline with aosp
    - [info] TWRP 3.6.1-9.0 available from Google Drive (no encryption support)
    - [info] Up-rev audio HIDL from 2.0 to 4.0
    - [info] Disabled amazon logging functions in kernel
    - [info] Disabled unused squashfs in kernel
    - [info] Conditionally compile MTK_M4U in the ion kernel driver as our device doesn't use it

    27 March 2022
    - [reverted] WiFi changes from previous build
    - [removed] 26 March Build

    26 March 2022
    - [fixed] Speakers continuing to play while headphones are plugged in
    - [fixed] Disney+ crashing
    - [didn't work for everyone] Slow WiFi throughtput
    - [didn't work for everyone] 5GHz connectivity to AX-88U router and in general
    - [didn't work for everyone] 5GHz connectivity to across all channels
    - [info] Include Bromite Webview
    - [request] WiFi: Can someone test connecting to hidden SSID's and report back?
    - [request] Magisk: Can someone test whether updating through the application works and report back?

    16 March 2022
    - [fixed] MtkOmxCore crash
    - [fixed] Better auto adjust on backlight
    - [fixed] SIM card prompt
    - [fixed] Changed battery capacity to 6300mAh
    - [fixed] sdcard access for chrome and other apps
    - [fixed] "There's an internal problem with your device." dialog
    - [info] Explicitly enable sdcardfs
    - [info] Refactor root init scripts
    - [info] Remove deprecated storage_list.xml
    - [info] Clean-up build.prop

    01 March 2022
    - [info] Re-build of 28 February version

    28 February 2022
    - [fixed] DRM Widevine L3 support
    - [new] Signature spoofing (enable and disable via developer options)
    - [fixed] Wired headphones not working
    - [fixed] Backlight HAL crashing
    - [fixed] Hardware OMX (MTK codecs now been used)
    - [info] Disable camera completely until fully investigated to stop logcat spam
    - [info] Enable OTG for ethernet in kernel

    07 February 2022
    - [fixed] OMX regression was breaking NewPipe and local video file playback
    - [info] Clean-up amazon binaries - media playback should be better - config file mess


    05 February 2022
    - [fixed] Navbar icon corruption
    - [fixed] Wallpaper corruption
    - [fixed] Laggy graphics
    - [fixed] High idle cpu usage
    - [info] Updated amazon binaries to fireos 5.6.9.0

    12 February 2021
    - Initial Release