Hello XDA forum!
I think that this is my first post and I hope that this is the right place to post it. :angel:
I bought a Galaxy Nexus three weeks ago: 16GB Maguro, Takjuxw 4.0 updated to 4.1.1 right after having opened the box.
I am having the same issue as the Nexus 7 owners: when the free storage space gets under 3GB, the write speed goes down to 10kb/s (yes, you are reading it right). Of course the phone becomes unusable if you're using any app that uses a disk cache: Maps, Chrome, Twitter, Facebook, basically almost every app has a cache.
The only way to fix this issue is to factory reset your phone.
Yes, removing your media files to restore the free space is not gonna work (I already tried this and so every Nexus 7 owner did).
My phone is not rooted and it's running a stock firmware. I recently converted my phone from Takjuxw 4.1.1 to Takju 4.2 stock, but the bug was not solved at all by this release (I loaded it up with songs and I had to factory reset it again - just 2,5GB were free).
There is actually a post on Google Forums regarding this issue (sorry, new user, I cannot post links yet) but they only talk about the Nexus 7 while I want to let Google know about the Galaxy Nexus too.
So, dear XDA GNex owners...Are you having a similar issue?
If you DON'T have this issue AND your free space is about 1-2GB:
- What hardware revision do you have? (Maguro? Other?)
- Which version of Android are you running? (4.0.1 - 4.1.1 - 4.1.2 - 4.2 - Other)
- Are you running any particular custom ROM?
- Was your phone NOT filled using the USB cable (eg. your storage is made of film/songs you downloaded using wifi/bluetooth).
- Which operating system are you using? (Maybe MS Win and the OSX app are treated differently by the phone)
- Are you using a firmware mod on a Maguro revision?
If you do have this issue:
- Did you try to clear the Dalvik cache? If so, how? (CWM or stock recovery?)
- Are you using ADW Launcher EX?
- Again, list your hardware revision and OS version - Mine is Maguro, takju 4.2 but I had a takjuxw 4.1.1 when I bought the phone.
- Did you have this issue by rewriting big files a lot of times (example: you have 8GB free and you loaded and then deleted movies with a size of 1,2GB more than 6 times)
The phone has been around for more than a year and it's very strange that nobody had this bug until now, so I want to know about Verizon users too.
I think that this has to be related to the phone internal memory not being TRIM-ed correctly 'cause other Android handsets do not seem to have this bug. Strangely, when you reset the phone, it just works, so it seems file-system related more than TRIM related or factory reset actually uses TRIM to format the partition.
Please, report anything that could be of help to spot what is causing the issue.
I love this phone, if you love it too, post here your experience.
Cheers,
Stefano
In reply
Phoenix128zx said:
If you DON'T have this issue AND your free space is about 1-2GB:
- What hardware revision do you have? (Maguro? Other?)
- Which version of Android are you running? (4.0.1 - 4.1.1 - 4.1.2 - 4.2 - Other)
- Are you running a particular firmware mod?
- Was your phone NOT filled using the USB cable (eg. your storage is made of film/songs you downloaded using wifi/bluetooth).
- Which operating system are you using? (Maybe MS Win and the OSX app are treated differently by the phone)
- Are you using a firmware mod on a Maguro revision?
Click to expand...
Click to collapse
- I've got a maguro phone
- running on Kalo v5.0 android version 4.2 (going to update soon to version 5.1^^)
- No specific firmware mod is running at the moment
- No my phone is completly filled using the USB cable
- I'm in use of Windows 7, I don't think this affects your writing on the phone. Maybe try on another computer if you think this can be the problem, and report back?
- No firmware mod on a magura revision in use.
I do hope your problem will be solved soon.
geynske006 said:
- I've got a maguro phone
- running on Kalo v5.0 android version 4.2 (going to update soon to version 5.1^^)
- No specific firmware mod is running at the moment
- No my phone is completly filled using the USB cable
- I'm in use of Windows 7, I don't think this affects your writing on the phone. Maybe try on another computer if you think this can be the problem, and report back?
- No firmware mod on a magura revision in use.
I do hope your problem will be solved soon.
Click to expand...
Click to collapse
Sorry, I forgot to specify custom Rom instead of firmware mod. Can you please tell me how much free storage space do you have left?
Regards,
Stefano
+1
Maguro, stock 4.2 rooted.
The phone does get a little slow when storage gets low, but it's definitely much faster than 10kb/s. My storage gets filled from the camera app by taking videos. I have a Windows PC from which I sometimes transfer some data.
I never had this problem with any version of Android. (Beginning from 4.0.1 ICS)
Gesendet von meinem Galaxy Nexus
Related
I am using gNexus but i have still not recieved official update to 4.04.
I was wondering why is thwt?
My baseband version is I9250XXKK6
Kernel version 3.0.8-gaaa2611 [email protected] #1
Build # ICL53F.I9250JPLA1
Please let me know if i need to manually update it or do i need to stay calm n wait for the update?
Any further sources will be helpfull.
Faadiz said:
I am using gNexus but i have still not recieved official update to 4.04.
I was wondering why is thwt?
My baseband version is I9250XXKK6
Kernel version 3.0.8-gaaa2611 [email protected] #1
Build # ICL53F.I9250JPLA1
Please let me know if i need to manually update it or do i need to stay calm n wait for the update?
Any further sources will be helpfull.
Click to expand...
Click to collapse
I gave up with OTA's takes too long. I usually just wait until someone has a stock update zip and just do that. Im on 4.0.4 now and so far so good! Hope that helps.
Please refer to my post here and it'll answer your question
You could wait but that would be an indefinite timeframe OR you could just flash the stock yakju images (I'm not sure if you can do this if you are using CDMA though). If you're on a CDMA network, you might have to wait for your carrier to update it.
Hey man. This "Problem" has been fixed a few times already around the forums here.
You will most likely have the "samsung-updated" version of the galaxy nexus. I had that to.
There are a few types of Stock Roms on the Galaxy nexus right now.
- The stock ROM powered and updated by google (also known as Galaxy Nexus with yakju builds)
- Other ROMS that are powered and updated by Samsung or your cellphone provider
This basically means that you live in a place were not all functions accessible to Android are available (government rules) or you got a phone from such a batch by accident.
- What you need to do is unlock your OEM (you can re-lock it after the change to keep your warranty).
- Wipe your complete phone so it can become a dev phone (the OEM unlock) your phone does this by itself on unlock.
- Flash an official ROM from Galaxy Nexus itself.
- Re-lock the OEM again (or not. I have it unlocked and my phone still works)
- update if you haven't flashed the newest version (normal updates).
Your phone will be a Google Powered phone after that!
Here the instructions on how to do it:
http://forum.xda-developers.com/showthread.php?t=1626895
Don't hesitate to send me a private message if this stuff is to hard for you. We can Skype or something and Ill help you set-up your phone.
Unlawful said:
Please refer to my post here and it'll answer your question
You could wait but that would be an indefinite timeframe OR you could just flash the stock yakju images (I'm not sure if you can do this if you are using CDMA though). If you're on a CDMA network, you might have to wait for your carrier to update it.
Click to expand...
Click to collapse
No I am using GSM Version!
amonfog said:
Hey man. This "Problem" has been fixed a few times already around the forums here.
You will most likely have the "samsung-updated" version of the galaxy nexus. I had that to.
There are a few types of Stock Roms on the Galaxy nexus right now.
- The stock ROM powered and updated by google (also known as Galaxy Nexus with yakju builds)
- Other ROMS that are powered and updated by Samsung or your cellphone provider
This basically means that you live in a place were not all functions accessible to Android are available (government rules) or you got a phone from such a batch by accident.
- What you need to do is unlock your OEM (you can re-lock it after the change to keep your warranty).
- Wipe your complete phone so it can become a dev phone (the OEM unlock) your phone does this by itself on unlock.
- Flash an official ROM from Galaxy Nexus itself.
- Re-lock the OEM again (or not. I have it unlocked and my phone still works)
- update if you haven't flashed the newest version (normal updates).
Your phone will be a Google Powered phone after that!
Here the instructions on how to do it:
http://forum.xda-developers.com/showthread.php?t=1626895
Don't hesitate to send me a private message if this stuff is to hard for you. We can Skype or something and Ill help you set-up your phone.
Click to expand...
Click to collapse
Thx Alot Buddy! I am much aware of the instructions you provided.
I shall try them
If i get stuck, i will surelly bug you
Whats your twitter handle? mine is @Faadi
It's @amonfog ;-)
amonfog said:
Hey man. This "Problem" has been fixed a few times already around the forums here.
You will most likely have the "samsung-updated" version of the galaxy nexus. I had that to.
There are a few types of Stock Roms on the Galaxy nexus right now.
- The stock ROM powered and updated by google (also known as Galaxy Nexus with yakju builds)
- Other ROMS that are powered and updated by Samsung or your cellphone provider
This basically means that you live in a place were not all functions accessible to Android are available (government rules) or you got a phone from such a batch by accident.
- What you need to do is unlock your OEM (you can re-lock it after the change to keep your warranty).
- Wipe your complete phone so it can become a dev phone (the OEM unlock) your phone does this by itself on unlock.
- Flash an official ROM from Galaxy Nexus itself.
- Re-lock the OEM again (or not. I have it unlocked and my phone still works)
- update if you haven't flashed the newest version (normal updates).
Your phone will be a Google Powered phone after that!
Here the instructions on how to do it:
http://forum.xda-developers.com/showthread.php?t=1626895
Don't hesitate to send me a private message if this stuff is to hard for you. We can Skype or something and Ill help you set-up your phone.
Click to expand...
Click to collapse
Hello:
Thanks for the info. I have a google nexus phone with the problems described in this thread. I have a question before I try to go through the steps outlined in the instructions. When you say "Your phone will be a Google Powered phone after that", does that mean that the google nexus phone will be able to get updates over the air and become like google nexus phones from the play store.
Any info on this will be appreciated.
Again thanks.
Anyone finding that Dolphin 9.0 says it's incompatible with the Nexus 7 running stock 4.1.2?
I just went to install the new Jetpack add on, and found that the version running on my N7 is older (8.5 something) versus my phone (running a CM10 based ROM with 4.1.2 in it).
haloeight said:
Anyone finding that Dolphin 9.0 says it's incompatible with the Nexus 7 running stock 4.1.2?
I just went to install the new Jetpack add on, and found that the version running on my N7 is older (8.5 something) versus my phone (running a CM10 based ROM with 4.1.2 in it).
Click to expand...
Click to collapse
Doesn't look like jetpack is available yet for tablets. Where jetpack requires 9.0 where you found out that the current N7 has an older version.
On an off note, there is a Dolphin for Pad version. Made for Android tablets. However the browser is not compatible with the jetpack add on...yet. Be patient, I'm sure they will come out with a tablet version soon.
Thanks for confirming.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Just received a response from Dolphin support:
I'm so sorry for the inconvenience.
We find the issue occurs while installing Dolphin Browser on tablets. And we are currently working on it. Please keep update with us.
Click to expand...
Click to collapse
+1 Was just about to ask the same question, its the same on 4.1.1 and 4.1.2 "not supported on your device" i can install jetpack though, gutted because its a really smooth browser, why isnt chrome that smoooth!?
What i did was sideload the dolphin 9 apk from a titanium backup on my phone. Just shared it to google drive and installed from that app on my nexus...installs just fine and jetpack works as intended.
Sent from my SPH-D710 using Tapatalk 2
Is flash compatible with Dolphin?
Dolphin is visible in the app store again. They must have fixed the compatibility flags.
I seriously doubt if the new version works with Flash though - we had to use a specific older version for that.
Someone install the new one and try it!
rmm200 said:
Dolphin is visible in the app store again. They must have fixed the compatibility flags.
I seriously doubt if the new version works with Flash though - we had to use a specific older version for that.
Someone install the new one and try it!
Click to expand...
Click to collapse
Yep..they fixed it and I can install it on my tablet today. Last night it wouldn't.
Really fast browser....but why don't they make the interface better? You have to press 3 buttons to get to share or settings.
Anyone have issues with 9.0 constantly crashing? I've never had it either just "disappear" or pop up a "Dolphin has Crashed, E-mail debug log" before today, and it's happened twice in the space of 5 mins with the latest update.
kcrudup said:
Anyone have issues with 9.0 constantly crashing? I've never had it either just "disappear" or pop up a "Dolphin has Crashed, E-mail debug log" before today, and it's happened twice in the space of 5 mins with the latest update.
Click to expand...
Click to collapse
I have got it running fine no issues no fc's
From the darkest reaches of my mind...... Somebody turn on the light
zolaisugly said:
I have got it running fine no issues no FCs
Click to expand...
Click to collapse
Yeah, wiping its data cleared up my FC issues.
But I had to revert to the previous version- the context menu (long-press) is gone on images, so I can't save them anymore. I've reported it though, so hopefully it'll come back in the next version.
kcrudup said:
I had to revert to the previous version- the context menu (long-press) is gone on images, so I can't save them anymore. I've reported it though, so hopefully it'll come back in the next version.
Click to expand...
Click to collapse
They released an update to Jetpack (go figure) that fixed this today, so I'm now up-to-date!
Folks,
Look at this screenshot attached.
I am an ex-googler and seems that when i was using this phone (Google Nexus Prime, i9250 or Nexus3 as they say) I was using internal (Google internal) upgrades. But probably I left the company while I was having an interim build and since then could not move to latest ICS or JB.
Hope fully you got the issue. Could you please guide me on how could I get to the latest android without hassles? (my current build IMM76B is probably not known outside Google)
Help please.
Regards,
Ankit
real.batman said:
Folks,
Look at this screenshot attached.
I am an ex-googler and seems that when i was using this phone (Google Nexus Prime, i9250 or Nexus3 as they say) I was using internal (Google internal) upgrades. But probably I left the company while I was having an interim build and since then could not move to latest ICS or JB.
Hope fully you got the issue. Could you please guide me on how could I get to the latest android without hassles? (my current build IMM76B is probably not known outside Google)
Help please.
Regards,
Ankit
Click to expand...
Click to collapse
use fastboot command to flash latest stock http://forum.xda-developers.com/galaxy-nexus/general/how-to-return-to-stock-galaxy-nexus-t1626895
or use odin (see my signature)
Hello,
I detected the following systematic problems of cm9..11
1.) Skype cannot be started at all. It does not even react on a click of its icon. And no error message appears.
2.) the akku load status is shown incorrect during load process. E.g. after 4 hours load it shows 37% instead of true 100% (which is shown after reboot).
3.) The wonderful app 'lgCamera' runs very slow and jerky. This was fine in Android 2.x versions.
4.) the FM radio app for the WFS radio tuner (no internet radio!). How can I find it (and flash it into the system folder as a system app)?
I suppose that everybody can confirm my problems!?...
Are those already known by the development team? Cause I wonder that they are not fixed in ALL CyanogenMod versions yet!
Will there be a chance to expect their fix soon?...
5.) Furtheron I have big compatibility problems when flashing cm9..cm11 ROMs and others. Error message: "cannot load volume /misc. Can't partition non-vfat: /storage (vfat)". For nearly each ROM I have to change the recovery. Currently I change between the following recoverys (one of them allways works):
twrp-2.2.2.0, twrp-2.7.1.0, Phil-Z 6.43.7, cwm-5.0.2.8, cwm-6.0.5.3. Nobody else having that problem?...
Is there any recovery version that can read all 'formats' of zip files?...
Will there be compatibiliy at least at the backup files between all of them?...
Thank you VERY much for a quick help!
1.) not compatible anymore, say Thanks to Skype
2.) This is probably problem with battery not reading voltage correct anymore on charger (happens) for me on all roms even stock. (After 100000 of flashes and almost 3years old down sucked battery
3) ics and up isn't made for this phone, slow downs and other incompatibility can happen.
4) There is a solution called spiritfm(free) Google it, you will find the xda thread.
5) twrp 2.2.2.0 and cwm 5 is working on all ROMs beside newer kk builds (needs recovery compiled with TLS support, newest ones available)
Greetings Kevin
Hallo Kevin,
I am so glad that you answer! Thank you very much!!
to 1.) Yes, I realised meanwhile that Skype 4 ist still running fine. So the reason why the new Skype 5 version does not work on Wildfire S (or even on all CM versions of all devices??) you don't know!?...
to 2.) So this is a general Andrid 4.x problem of Wildfire S device only?... (cause e.g. on Galaxy S4 stock (of my girl-friend) it works fine!...
to 4.) Thank you. I installed this free version '0918fr.apk' but I get the error message (su rights confirmed): "Error: No FM accessible. SU: 0 Fm:BC2 SU:0 Bt:3 Ht:0 Mo:BCU". It does not seem to be compatible although I have read everywhere that it should work. Is this maybe antoo old version? Or what can be the reason?...
to 5.) So I used newer version 'cwm-6.0.5.3' and 'twrp-2.7.1.0', as I mentioned, but then these versions do not support older version than KK. E.g. 'CronMod-INT2EXT+_signed.zip'. This is the problem. Any solution?...
Is TLS ment as 'Thread-local storage'?...
Another short request:
a) Video recording with cm11 on Wildfire S works now without any patch. But if I record a video longer than about 5 seconds and I want to watch it directly after having stopped recording (timeframe about 7 seconds) then the camera app crashes. Can you confirm that on Wildfire S? What can be the reason?...
If Olivier's camera patch will help here as well I have not tested yet...
b) Management of Launcher and App screen is somehow circumstancial or not even possible. This is why the option 'Homescreen' is missing in 'Personalization' ('cm-11-20140816-Nightly') although the related screenshots of cm11 in XDA show this option!! E.g. App icons cannot be sorted alphabetically or cannot be manually moved within the screen. Or the home panel is the most left one instead of the middle one. Etc.
Any reason why the option 'Homescreen' was deleted (in XDA cm11 screenshots for Wildfire S still show it!! S. http://forum.xda-developers.com/showthread.php?t=2735775 )?...
c) CM11 OTA update suggests me 'cm-11.0.0-RC9' as the first in the list. Is this really more actual than the installed 'cm-11-20140816-Nightly' (version 11.0-20140816) ?...
d) In this version the Email system app is missing. Why?
Any zip to flash it anywhere? Or do I have to use one of the market?...
e) No warm reboot option available anymore in cm versions?...
Thanks for your help again, Kevin!
Many greetings, Falk
to 5.) I could solve that problem meanwhile by myself. I downloaded a modified version of cwm 6.0.5.3 here:
http://click.xda-developers.com/api...5.0] - Post #52 - XDA Forum&txt=the new build
But I still do not know what was modified! You?...
6.) you forgot the ever present mobile data bug at least for cm9 and cm10. Which no1 evens bothers to mention
Beeefalo said:
6.) you forgot the ever present mobile data bug at least for cm9 and cm10. Which no1 evens bothers to mention
Click to expand...
Click to collapse
Because it does not exist? I never faced any bug like that.
aWFSuser said:
Because it does not exist? I never faced any bug like that.
Click to expand...
Click to collapse
oh, its super present .
It was a "common" problem in cm9, cm10 based roms, at least judging from the various threads dating back to 2013. And as I discovered yesterday its also present in CM11 RC9 for me.
Occurence of the bug is very random and seems to be bound to certain providers which makes it hard to debug/fix i guess.
Sadly, from what I've read "deal with it and toggle airplane mode when you need mobile data" or "install cm7" are the ways to handle this bug.
cheers
Beefalo
My sony z3 has gone back to sony for repair, so I got my i9250 out as a spare. It was installed with cm13, but as it hadn't been used for a while I updated to the latest nightly. all was good but the camera kept crashing, so i wiped everything, flashed cm13 and pico g-apps, but when it restarts google play, won't start. (nano is too big apparently??)
So i tried using cm12 and the relevant g-apps and got the same result
then i tried http://forum.xda-developers.com/galaxy-nexus/development/rom-omap4-aosp-project-t3334574 and it just boot loops on the the 7.1 & kk versons
It will install cm13 & 12 and start no problems, but i need all my google contacts and stuff
Any suggestions??
jonallwright said:
My sony z3 has gone back to sony for repair, so I got my i9250 out as a spare. It was installed with cm13, but as it hadn't been used for a while I updated to the latest nightly. all was good but the camera kept crashing, so i wiped everything, flashed cm13 and pico g-apps, but when it restarts google play, won't start. (nano is too big apparently??)
So i tried using cm12 and the relevant g-apps and got the same result
then i tried http://forum.xda-developers.com/galaxy-nexus/development/rom-omap4-aosp-project-t3334574 and it just boot loops on the the 7.1 & kk versons
It will install cm13 & 12 and start no problems, but i need all my google contacts and stuff
Any suggestions??
Click to expand...
Click to collapse
Did you use Gapps Pico...? It's smallest...
Day by day letest changes makes ROM bigger, and then our phone doesn't have enough space for Gapps... That is reason....
While flashing, keep eye on Log of Custom Recovery, starting of flash checks space on device first and gives result, then see if Gapps got flashed or not...
Pico, Pico, Pico!
__Madddy said:
Did you use Gapps Pico...? It's smallest...
Day by day letest changes makes ROM bigger, and then our phone doesn't have enough space for Gapps... That is reason....
While flashing, keep eye on Log of Custom Recovery, starting of flash checks space on device first and gives result, then see if Gapps got flashed or not...
Click to expand...
Click to collapse
You can't use anything bigger than pico since Marshmallow (and I don't recommend anything bigger than pico, period). I have never had success with anything nano (the largest I have ever tried - and that was only with CM 13); however, pico has never done me wrong (I moved to Unlegacy Android - currently 7.1.0 - for performance issues that it fixes compared to CM13; yes, for some rather odd reason, Nougat performs better than MM on this device).
PGHammer said:
You can't use anything bigger than pico since Marshmallow (and I don't recommend anything bigger than pico, period). I have never had success with anything nano (the largest I have ever tried - and that was only with CM 13); however, pico has never done me wrong (I moved to Unlegacy Android - currently 7.1.0 - for performance issues that it fixes compared to CM13; yes, for some rather odd reason, Nougat performs better than MM on this device).
Click to expand...
Click to collapse
That's right Pico is the only option from MM and upper. It's very usefull the performance tip you give about Nougat.
I have installed last MM build from:
builds.unlegacy-android.cf/aosp-6.0/tuna (2017/01/09)
Everything goes well (even GPS), it's fast and reliable. But I have a doubt, should I wait till next Nougat (with GPS functional) or should I stay in MM with everything functional and good performance?
Is N release better in any aspect than MM?, obviously I miss the new improvements in Android N that have developed Google, but I mean general performance and hardware related issues.
I prefer an older Android release, faster and more stable than the newer one with more issues or slower.
Anybody can tell? Thanks in advance!
yossSP said:
That's right Pico is the only option from MM and upper. It's very usefull the performance tip you give about Nougat.
I have installed last MM build from:
builds.unlegacy-android.cf/aosp-6.0/tuna (2017/01/09)
Everything goes well (even GPS), it's fast and reliable. But I have a doubt, should I wait till next Nougat (with GPS functional) or should I stay in MM with everything functional and good performance?
Is N release better in any aspect than MM?, obviously I miss the new improvements in Android N that have developed Google, but I mean general performance and hardware related issues.
I prefer an older Android release, faster and more stable than the newer one with more issues or slower.
Anybody can tell? Thanks in advance!
Click to expand...
Click to collapse
So far, N has stood that meme on its head (compared to MM, L, KK, and even JB) and it's NOT the first OS for any device to have done so..
It's a meme that dates back to MS-DOS (that's right - it pre-dates Windows of any sort) and it's based on a canard that a newer OS is designed for newer hardware. While it CAN be true, there are reasons why the Galaxy Nexus in particular stands the meme on its head.
1. Basic storage capaciousness. Unlike most devices that succeeded it, the Galaxy Nexus in particular not only does NOT support microSD physically, it also does not lose over half the base storage to its firmware - in fact, PureNexus 7.1.1 - even installed as a pour-over upgrade from Unlegacy AOSP - takes up less than ten percent of the GNex storage space; all of 3 GB at worst. That means that more of the basic storage can be used for ZRAM - the Android equivalent of virtual memory in Linux distributions, Windows, or other modern OSes. More modern phone designs support microSD - which has itself grown in capacity as a storage mechanism; however, you pay a price in loss of first-tier storage capacity - every S-series Samsung phone proves it - how do ANY of them compare to the GNex in non-SD-based storage after firmware loadout? Also, you can't use microSD for ZRAM; if you need ZRAM, you must use free basic storage for it - and most modern Android devices simply don't have it to spare. (It's not just a phone problem; in fact, my Lenovo A7-30F - which supports microSD and is running Lollipop right now - illustrates the point rather painfully, despite being a tablet - it is also a MediaTek big.LITTLE "4+4" design that is hamstrung by the lack of ZRAM. Being able to throw more cores at the problem won't help when the processor is not the biggest problem.)
2. CPU vs. ZRAM - Performance of a given application on a given phone is NOT always determined by processor power; the same is, in fact true on OSes other than Android. Still , what happens merely in Android as ZRAM availability - which IS a secondary function of basic storage capacity - decreases? (This is whether the device supports microSD or not.) Does or does NOT performance decrease as basic storage fills up?
3. Not every app needs more CPU or GPU. Out of everything I've thrown at the PureNexus/GNex combo, only two apps (and one game) explicitly require Marshmallow or better - and in all three cases, they were designed for Marshmallow OR Nougat in the first place.