Try bitgapps arm64 9.0.0 R45. It's more than half the size compressed.
[ROM][testing][suez] Lineage-16.0 [05 JULY 2022]
- Thread starter ggow
- Start date
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.
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.
I just had a thought if you are doing a dirty update then you shouldn't need to flash gapps again
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
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.
You may want to talk with k4y0z. amonet already modifies the GPT, so maybe everything can be done there.
Last edited:
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
/s
Last edited:
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:
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.
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:
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
Last edited:
@ggow A different (and more reasonable) approach to gain some space in /system is to exclude extraneous fonts from the /system partition. Alternatively, you can also exclude unnecessary apps with RemovePackages.
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
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
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
2
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 -
- Grabbed the parted binary from https://github.com/edk2-porting/parted-android
- Booted into twrp, adb pushed the parted binary to /tmp, chmod a+x'ed it
- "unit b" tells parted to display partition start/end/size down to the byte
- 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...)
- 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.
- Make sure you rename your newly created partitions to system, cache and userdata to match their original names...
- 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.
- 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.
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.
1Just picked up one of these devices through a deal at woot... Some notes:
(1) I had to open it up and do the "short CLK to ground" thing to get twrp and the tweaked bootloader on there. As far as I can tell none of the software-only root methods work with the latest stock firmware.
(2) After getting twrp on there, the system partition was too small to fit either this lineage16 ROM or the older lineage14 ROM with their accompanying pico opengapps package. I ended up sideloading a parted binary and editing the partition table by hand to get a larger system partition.
(3) If you manually enlarge your system partition like that, after you flash the ROM you need to use the Resize function (under Wipe/Repair) to resize the newly flashed system partition so it takes up the full size of your larger system partition, rather than the smaller size in the image. After the resize you need to either reboot or go in the Mount tab and mount and unmount the newly resized system partition so the recovery recognizes it's been resized properly.
(4) Once all this is done...
(a) I had a *lot* of wifi connectivity problems with the lineage16 ROM. Anyone have any suggestions on what I could try tweaking, either tablet side or router side? I actually tried cloning the lineage16 source code to mess around with but some of the externals in it seem to be broken at the moment...
(b) With the lineage14 ROM wifi is 100% solid but the Gmail app can't see Gmail accounts I have configured into the system... Even though they're actually being synced and I'm getting notifications when there's new Email in them... I can't actually VIEW those Emails...1Respect @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 script1
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.
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. -
50Disclaimer
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
GitHub - android-extra/twrp_device_amazon_suez: TWRP device tree for Amazon Fire HD10 (2017)
TWRP device tree for Amazon Fire HD10 (2017)...
github.com
Thanks
- @k4y0z and @xyz` for the bootloader hack
- @k4y0z for the initial kernel
- LineageOS16🛠 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 gapps12
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
