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

Search This thread

jmw0235

New member
Jul 6, 2022
1
0
If you are watching the application AFREECA TV, the screen will stop. (Infinite buffering)
I can still see the sound and the chat.

I asked AFREECA TV about this problem, but it is not compatible because it is an abnormal Android.
Please modify it to be compatible.
 

Legitsu

Senior Member
Aug 30, 2013
1,362
434
I have never tried to resize or mess with the partitions on an android device. Can it be done safely on our device?
uh not easily no if I remember correctly partition stuff should be done directly after doing the bootloader unlock I forget why, I could be wrong and newer trwp might do it
 

Nosepull

Senior Member
Jan 9, 2015
243
48
I just had a thought if you are doing a dirty update then you shouldn't need to flash gapps again
Yes. It re-installs itself. But that's the problem when switching to another provider of GApps - the old ones always get reinstalled.
And judging from the posts here, I assume that dirty flashing with too big GApps will fill up /system.
 

Legitsu

Senior Member
Aug 30, 2013
1,362
434
You may want to talk with k4y0z. amonet already modifies the GPT, so maybe everything can be done there.
yea that was in something in the exploit is what defines the gpt
even without gapps /system is a tight fit its always a good idea to have more room since we are not
treble

btw @ggow when are we getting LOS 18.1 :p /s
 
Last edited:

droidjunkie

Senior Member
Try bitgapps arm64 9.0.0 R45. It's more than half the size compressed.

I just had a thought if you are doing a dirty update then you shouldn't need to flash gapps again

I did a dirty flash from the previous version, with pico gapps, to the July 5th version without wiping anything and I had zero issues.

I then made a backup, I always make backups of known good setup's, wiped system, dalvik, and cache. Installed July 5th rom, reboot back into recovery and attempted to flash pico gapps which failed like others have said. I then attempted to flash BiTGApps (BiTGApps-arm64-9.0.0-R45_signed) and it flashed no issues.

I am guessing we are still having the issue with 2 of the cores being pegged at 100%? Is there anything specific you would like tested?

Edit -
I forgot to install Magisk so I downloaded the newest apk version from the official github, renamed it to .zip and flashed it via recovery. I didn't not perform any kind of wipe and instead attempted to reboot the system. This resulted in a boot loop. Rebooting back into recovery and perform a dalvik cache wipe only and that resolved my bootloop issue. This resulted in the app not being installed after flashing via recovery, after installing manually The app is reporting that Magisk IS NOT installed. Reboot back into recovery, flash the .zip again this time wiping cache and dalvik after the flash resulted in another bootloop. Back to recovery one last time to wipe cache and dalvik again, fixed bootloop but the Magisk app still reports Magisk isn't installed. It was at this point that I remembered the newest version of TWRP for some reason has issues installing Magisk. Downgrading my twrp version, flashing Magisk, then flashing back to the newest TWRP worked fine.

So to sum up -
- Dirty Wipe from previous version with pico gapps installs fine with no errors due to size
- Fresh Install (wiped system, data, cache, dalvik) July 5th rom then attempting to flash pico gapps results in error due to not enough free space
- Fresh Install (wiped system, data, cache, dalvik) July 5th rom then flashing BiTGApps (BiTGApps-arm64-9.0.0-R45_signed) works fine with no errors due to size.
- Flashing Magisk via recovery with newest recovery image (twrp_suez_3.6.1-9.2) results in Magisk not actually being installed (it reports no errors when flashing in recovery). Have to flash twrp_suez_3.6.1-9.0 in order for Magisk to be properly installed. (checked root with root check and Magisk superuser is working fine)
- Initial testing (htop via terminal) still shows at least 2 cores pegged at 100% usage with them sometimes dropping but then going back to 100%
 
Last edited:
  • Like
Reactions: twocrows and ggow
For the heck of it, I tried resizing the /system (expanding) and /userdata (shrinking by same amount) partitions and it seems to have worked for me. My tablet is a 32GB version, so I figured i had some room in /userdata to spare, but I only added a few hundred MB (was not sure what size would be optimal).
Before changes TWRP showed /system size as 1557MB with 216MB free, and now shows 1936MB with 595MB free. (parted binary showed 1693MB before and 2097MB after). Also using TWRP backup and restore options I was able to do this without losing any data (I was able to boot right back into LOS as it was previously). My partition table has /cache, /userdata, /boot, and /recovery after /system, so I was not sure I could do it without messing with the boot and recovery partitions (which is a little scarier if I ran into trouble) but I did not have to touch them. I just deleted /system, /cache, and /userdata, then recreated /system at new size, recreated /cache using same size but moving to new position following /system, and then created /userdata using remaining sectors between /cache and /boot.

I used the info from here to attempt this.

I used a size of 4096000 sectors (was going for 2000 MB x 2048) for /system thinking it would give me approx 307MB extra space.

Note: I did a full backup in TWRP before starting, as well as another backup of just /system, /cache, and /data, but only needed the second. I also renamed /data/media/ (to mediabak) so that TWRP would include internal storage in the backups and of course renamed it back after restoring from backup.

I also printed out the partition table with sector start and end points before starting so I could use them as reference and to have original values to revert to if I ever need to.

In any case, just figured I would share this in case anyone else wants to try and do the same.

Edit: correction, deleted /userdata not /recovery

Note: While I do not expect to have any issues I have not yet tried to flash the latest LOS release yet (nor anything else for that matter), so I cannot say for sure that resizing the partitions will not cause any issue there.
 
Last edited:
  • Like
Reactions: ggow

droidjunkie

Senior Member
- Initial testing (htop via terminal) still shows at least 2 cores pegged at 100% usage with them sometimes dropping but then going back to 100%
I have inserted a screenshot of htop showing cpu% of a few processes over 100%, doing a shutdown and turn on seems to get rid of the cpu pegged at 100% issue and the few processes that were showing over 100% cpu are not anymore.

Its been a while since I have done any kind of in-depth diag of a Linux system, but am I seeing correctly that in the first attached image it says my uptime is 1 hr 19 minutes but the top 2 system_server processes and the system/bin/surfaceflinger process show WAY MORE then 1 hr 19 minutes of run time?
 

Attachments

  • Screenshot_20220707-020228_Terminal_Emulator.png
    Screenshot_20220707-020228_Terminal_Emulator.png
    484.8 KB · Views: 36
  • Screenshot_20220707-021640_Terminal_Emulator.png
    Screenshot_20220707-021640_Terminal_Emulator.png
    373.2 KB · Views: 34
Last edited:
Ran into some weirdness today with the resizing partitions stuff. Decided to flash (dirty) the latest LOS release and that went OK, but checked size in TWRP and it now shows the size as 1589MB, which is different from both before and after sizes that I got yesterday. Checked with parted binary and although it shows same size as yesterday (after resizing) it now shows the fs-type as ext2 instead of ext4. However TWRP and mount and other tools show it as ext4, so not sure what is up with that. Tried a clean install as well with the same results. Anyway, restored my backup and reflashed (dirty) the LOS update (same results) and aside from the above, everything seems OK.
 

Legitsu

Senior Member
Aug 30, 2013
1,362
434
Ran into some weirdness today with the resizing partitions stuff. Decided to flash (dirty) the latest LOS release and that went OK, but checked size in TWRP and it now shows the size as 1589MB, which is different from both before and after sizes that I got yesterday. Checked with parted binary and although it shows same size as yesterday (after resizing) it now shows the fs-type as ext2 instead of ext4. However TWRP and mount and other tools show it as ext4, so not sure what is up with that. Tried a clean install as well with the same results. Anyway, restored my backup and reflashed (dirty) the LOS update (same results) and aside from the above, everything seems OK.
thats the problem I had when I tried I don't remember what the issue was I think amonet might be fiddling with the gpt definition
 
  • Like
Reactions: gRooster

droidjunkie

Senior Member
I'm having issues with Magisk. It won't install again, we had a similar problem with an older build.
I am going to assume you are on twrp_suez_3.6.1-9.2 and are attempting to flash using the .zip file via recovery. If so first you need to downgrade to twrp_suez_3.6.1-9.0, flash the .zip file via recovery, boot into the system and make sure that magisk is installed and root works properly, then you can reboot back into recovery and flash back to twrp_suez_3.6.1-9.2.

I had the same issue and I documented how I resolved it (what i told you to do) in my previous post from yesterday
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    widevine L1 still isn't working so netflix is limited to 720p
    hardware acceleration is still a bit dodgy
    there are performance issues yet
    its wip
    tbh suez is pretty dead ggow is the only one working on it
    Depemding on your needs still a solid tablet with this ROM, IMHO.
    1
    Depending on your needs still a solid tablet with this ROM, IMHO.
    didn't say it wasn't but he specified he was going to be using audio/and video which both still have some issues I use mine to monitor my wyze cameras and for unified remote
  • 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