[Fire HD 8 and HD 10 Original Android Development] timpster:
O.K. performance is just as atrocious as it was before I wiped data, and not a smidge better. As I have stated before I use a firewall program to filter network activity I do not want. It consumes about 50 or so megabytes of memory on average. I have had to re-open it and start it again, three times, make that four, I just decide that I have to go without it for a few minutes because I cannot restart it, disconnect, reconnect to the network, and switch back, without my tab being reset and having to copy paste three tines during the typing of this post.

If I open two firefox tabs, the firewall program (lock icon in status bar) closes. Also, switching tabs will cause the inactive tab to reload, usually forcing the wifi to be connected but not every time, is incredibly annoying and not something that happened on the stock software. I still cannot play music and browse the web, as five seconds after I switch to fennec (firefox) pandora or spotify just close.

This is either out of memory daemon running (because I have enough swap to use, but it doesn't all get used up) which hasn't been discussed at all in this system, or some horrendous configuration of z-ram which doesn't seem to do anything remotely useful, only compressing SINGLE DIGITS of megabytes, where as 100+ mb of compressed memory at the absolute minimum might actually be a starting point to better memory management.

I have the following suggestions for the main dev, or, maybe the main person creating this rom, could explain how to nodify the system settings of the system / main zip archive etc and find what does work, so more people could test performance with more than one program open.

- Swap: 100 is not a logical setting as I don't think the cache is helping the performance. 100 means to treat physical memory and swap completely equal and since they are different sizes (swap being smaller) it doesn't leave enough real memory to be used by programs, vs using 50% of it for cache or a buffer.

Let's try the 1990s default of 60, which will allow more of the memory for programs, and the swap will be used more for the buffers and cache. 30 would probably be a better setting.

Increasing the swap partition fron 677 MB to at least 1,5410 MB for 1.528 GB of swap space might also help, so that more things in total can stay in memory, so allowing nearly 2.8 GB of memory space including swap, vs the just barely 2.0 GB of total memory space now.

Figure out why zram is misconfigured and only compressing very small amounts, and how to increase how much and how strongly it compresses memory, the most compressed options would be the best to try first, since Amazon desperately wants these devices repurchased so they can recoup some of their losses from selling, and my firewall is down again, from selling devices already under powered, for below cost.

That was their bet, and I bet they lost massively. They can still win again, with performance still being terrible on this device and not being usable. That is what they crave, greed and corruption.

If there were any business on this planet, and I don't think one exists or will ever exist, at least not in 100 years, that puts society, and environment far far above any money, then we would not have a device released with 1.5 GB of memory in 2018. The developers know that isn't enough, everyone knows it is not going to last, which is why Amazon sold it that way, they do not want it to be used for a decade or more, they want new hardware purchases as often as they can persuade people to buy their products. And I'd be fine with that, if they had reasonable hardware for at least seven or eight years, like 3 GB of memory or more and I'd say that is more than enough.

Believe it or not, smartphones running on Android in 2010 had 256 MB of memory, because that is all it needed. So why does it take nearly 900 MB for the base system to stay in memory? Exactly what has been added to create this avoidable requirement?

I read that Andriod go was a part of this, but that still hasn't seemed like enough to lighten the system memory use, so what else can be done?