I want to know what is the amount of internal memory available (for installing apps) in GS3 International version (not the internal storage which is 16/32/64 GB respectively) !!
12.1 GB
Sent from my GT-I9300 using Tapatalk 2
The 16GB version comes out at 11.35GB for me.
out of 16 gb 14.9 gb is usable, 2 to 3 gb is used for system/cache/dev partitions so the remaining 11+ gb is used for apps+ user data
bala_gamer said:
out of 16 gb 14.9 gb is usable
Click to expand...
Click to collapse
Yes and no.
16GB, as reported by any hardware manufacturer is always 14.9GB.
For anyone who cares....
Hardware manufacturers of "disk space" use the idea that there are 1000MB in a GB and 1000KB in a MB and 1000B in a KB.
This is not true. Actually there are 1024B in a KB, 1024KB in a MB and 1024MB in a GB. So when software reports the true value of space, it seems smaller than what the hardware is advertised as.
Here is some simple maths.
If hardware is reporting as 16GB, do this:
16GB/1024MB/1024KB/1024B = 0.000000015
0.000000015*1000B*1000KB*1000MB = 14.9GB
Thats how you work out the true size of disk space.
ketani73 said:
I want to know what is the amount of internal memory available (for installing apps) in GS3 International version (not the internal storage which is 16/32/64 GB respectively) !!
Click to expand...
Click to collapse
I believe the Galaxy S III uses the same internal memory for both installed apps and internal storage, and that this can be up to 16/32/64 GB in total. This means that you can either use all of it for apps, or all of it for files, or something in-between, as long as it does not exceed the total space which is available.
rootSU said:
Actually there are 1024B in a KB, 1024KB in a MB and 1024MB in a GB. So when software reports the true value of space, it seems smaller than what the hardware is advertised as.
Click to expand...
Click to collapse
Things have changed slightly. 1024B = 1KiB, 1024KiB = 1MiB and 1024MiB = 1GiB. 1000B = 1KB, 1000KB = 1MB and 1000MB = 1GB. Due to the confusion caused by the two methods of counting, the IEC established the Ki, Mi... in 1999. However the computer industry refuses to change, so the battle still rages.
guhvanoh said:
Things have changed slightly. 1024B = 1KiB, 1024KiB = 1MiB and 1024MiB = 1GiB. 1000B = 1KB, 1000KB = 1MB and 1000MB = 1GB. Due to the confusion caused by the two methods of counting, the IEC established the Ki, Mi... in 1999. However the computer industry refuses to change, so the battle still rages.
Click to expand...
Click to collapse
Nope. As an IT technician, 1024 B = 1 KB. 1024 KB = 1 MB.
If anyone wants to have the fictional convention of KiB and MiB, let it be those who feel the need to make 1000 B = 1KB. They're the ones who are wrong, making the maths simpler with the "inadvertant" (is it really?!) bonus of making less sound more.
Anyway thats another discussion. Suffice to say, I will not start changing the naming convention of the true MB for corporations who feel it is their place to take something, change it and then proclaim it to be the truth.
I feel the same about American English and UTC time.
And the correct answer is...
ketani73 said:
I want to know what is the amount of internal memory available (for installing apps) in GS3 International version (not the internal storage which is 16/32/64 GB respectively) !!
Click to expand...
Click to collapse
Out of the 1gb ram the on the I9300, how much is available to install apps on?
I think that's his question. He mentions, not the storage amount, specifically.
-CC
EDIT: According to the app Android System Info, my phone has 778MB available...
clockcycle said:
Out of the 1gb ram the on the I9300, how much is available to install apps on?
I think that's his question. He mentions, not the storage amount, specifically.
-CC
EDIT: According to the app Android System Info, my phone has 778MB available...
Click to expand...
Click to collapse
You cannot install apps in RAM. That is not what RAM is for.
rootSU said:
You cannot install apps in RAM. That is not what RAM is for.
Click to expand...
Click to collapse
Perhaps you're correct about the "ram"..
Where are the /data/app and /system/app directories located?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If anyone wants to have the fictional convention of KiB and MiB, let it be those who feel the need to make 1000 B = 1KB
Click to expand...
Click to collapse
Actually there are 2 different 'standard' units for data calculation:
- Disk capacities have 1KB = 1024B
- Traffic is 1KB = 1000B
By the way the convention of 1KB = 1024B is also fictional, altough it makes more sense in terms of low-level storage.
Guys , let me be more clear !! Presently i have GS2 & though it's internal storage is 16 GB , the memory available for installing apps (apps which cannot be moved to external sd) is 2015 MB (nearly 2 GB) !!
Now i seriously wish to buy GS3 & that's the reason i wanted to know it's internal memory useful for installing apps which cannot be moved to sd card ... For example say SPB Shell 3D !!
ketani73 said:
Guys , let me be more clear !! Presently i have GS2 & though it's internal storage is 16 GB , the memory available for installing apps (apps which cannot be moved to external sd) is 2015 MB (nearly 2 GB) !!
Now i seriously wish to buy GS3 & that's the reason i wanted to know it's internal memory useful for installing apps which cannot be moved to sd card ... For example say SPB Shell 3D !!
Click to expand...
Click to collapse
The image attached in the above post shows 1.5gb as System Storage.
Sent from my GT-I9300 using Tapatalk
I remember on my Note is had a 1.97 for system apps and 11gb for internal USB...Now i my Galaxy S 3 there is no 1.97 for system apps..its all one partition right?
pachi72 said:
I remember on my Note is had a 1.97 for system apps and 11gb for internal USB...Now i my Galaxy S 3 there is no 1.97 for system apps..its all one partition right?
Click to expand...
Click to collapse
That's exactly what i want to confirm ... I handled one GS3 unit & in the memory usage option i could not see a different partition like system or device memory...It showed only internal memory of around 11 GB or so (can't remember the exact number) !!
d4fseeker said:
Actually there are 2 different 'standard' units for data calculation:
- Disk capacities have 1KB = 1024B
- Traffic is 1KB = 1000B
By the way the convention of 1KB = 1024B is also fictional, altough it makes more sense in terms of low-level storage.
Click to expand...
Click to collapse
Traffic? As in data transfer over a network? That's in bits not Bytes. Its still 1024 to 1 to. But 1KB is 8Kb.
Anyway its irrelevant. Working in IT, only 1024 makes sense to me
Sent from my GT-I9300 using Tapatalk 2
clockcycle said:
Perhaps you're correct about the "ram"..
Where are the /data/app and /system/app directories located?
Click to expand...
Click to collapse
The entire partition set /system, /data and /cache etc is all on the.physical internal sdcard. That is the only memory available.
The physical sdcard is also home to the partition /sdcard. /data and /sdcard use the same 11.35GB space
The entire size of the physical sd card is 14.9GB. 11.35GB for /data and /sdcard. The rest is for /system, /cache, /recovery, /boot etc
So to answer the OP, 11.35GB to install apps on.
Sent from my GT-I9300 using Tapatalk 2
This is awesome news. No more restrictions on storage. Only bad part is when flashing ROMs it will wipe it completely.
pachi72 said:
This is awesome news. No more restrictions on storage. Only bad part is when flashing ROMs it will wipe it completely.
Click to expand...
Click to collapse
Well, you say that but large games download sometimes a GB or more of data to /sdcard which is also your internal storage, so there are some restrictions in that respect. Download a handful of large games and you will definitely see an impact.
Related
hi
i got notification on my sg2 today, that say the phone memory in nearly full
so my question is how to move them to internal storage
ps: i don't have micro SD card on my phone
you dont need the external SD card (if you have enough space on the internal SD card) i guess you might have enough space... just do the following
go to settings -> applications -> manage applications
then tap the on SD card on top
this will list the applications which can be moved to SD card
check the box on the right to the application you want to move to SD card.
it will take you to another screen, click Move to SD card
job done.... do it one by one if you need more applications moved
hi i follow your steps but when i try "Move to SD Card" buttom i get Failed to move application: not enough memory, and yes i have 4gb free space
problem moving apps to phone memory
woodstock_ahem said:
you dont need the external SD card (if you have enough space on the internal SD card) i guess you might have enough space... just do the following
go to settings -> applications -> manage applications
then tap the on SD card on top
this will list the applications which can be moved to SD card
check the box on the right to the application you want to move to SD card.
it will take you to another screen, click Move to SD card
job done.... do it one by one if you need more applications moved
Click to expand...
Click to collapse
Tried doing tat..but it says "Failed to move application:Not enough memory".
My storage stats :
System storage :1.54GB/1.97GB
USB storage :2.16GB/11.50GB
SD card :0.00B/0.00B
I doubt whether it takes sd card as d external memory card which i abesnt in my phone & hence "not enough memory" ???
go to task manager -> clear memory from RAM
then try following my steps again...
wait a minute, just noticed that your System storage :1.54GB/1.97GB
which shows space available
the external SD card is not a requisite...phone will be fine without it
woodstock_ahem said:
go to task manager -> clear memory from RAM
then try following my steps again...
wait a minute, just noticed that your System storage :1.54GB/1.97GB
which shows space available
the external SD card is not a requisite...phone will be fine without it
Click to expand...
Click to collapse
Same
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Device memory 1.8GB USED /208 MB FREE
SD CARD 7.5 gb used/4.0GB free
provide the following details :
go to settings -> applications -> memory usage
then click the last tab - running
what do you see at the bottom of screen? the free RAM , how much is free , how much is used
then click the first tab - downloaded
what are the device memory details
OK try uninstalling few least essential apps to get the device memory free upto 400 MB... then start moving the rest of the Apps to SD card one by one
RAM : 237MB used / 415MB FREE
device memory details: 1.8GB used / 208 FREE
Running :209MB used, 499MB free
Device memory :1.5GB used, 443MB free
On SD card : 2.2GB used, 9.3GB free
I know i've got some space available..but still wen required to move apps to device memory...how can i do it?
Any help please?
moving apps to sd
woodstock_ahem said:
provide the following details :
go to settings -> applications -> memory usage
then click the last tab - running
what do you see at the bottom of screen? the free RAM , how much is free , how much is used
then click the first tab - downloaded
what are the device memory details
OK try uninstalling few least essential apps to get the device memory free upto 400 MB... then start moving the rest of the Apps to SD card one by one
Click to expand...
Click to collapse
(SRY 2 quote ur entire msg...but i can't figure out wats going wrong here..Help admired )
Running :209MB used, 499MB free
Device memory :1.5GB used, 443MB free
On SD card : 2.2GB used, 9.3GB free
I know i've got some space available..but still wen required to move apps to device memory...how can i do it?
I have run out of ideas !!
If you dont find any help from elsewhere and finding it hard to use the phone right now, i suggest doing a hard reset.
i dont know if you guys are running any customized ROM.
This is what i have and what i do.
I have the Stock official non-leaked ROM on UK generic phone which has been rooted.
I have around 45-50 the usual useful apps installed plus couple of game demos.
whenever i see the apps requiring 50mb + download required i tend to move it to SD Card and provide the SD card destination for any offline reference files (for example)
this i do just after the installation...(if it cant be done during installation)
this way i have managed to keep the device memory to around 400 MB usage
i keep the most frequently used apps on the phone memory/device memory... pushing others to SD card.
if you get stuck with no further help on your query
i suggest start over again after hard reset and follow the good practices whichever ROM you are using
Good Luck
You can't move apps to the internal SD. That is why you are getting failure messages. You need to add an external SD card to move apps to.
yes i was wrong all the time
apologies for providing misleading information earlier ( it wasnt intentional)
i pulled out my external SD card and i started getting the same reported error messages...
i got confused with the naming convention of the folders... hand up..my fault
so there you have it.. get a SD card
thanks @aterlecki
ok so now i need to find a new memory
whats best 32gb (for the price) i can find for my SG II?
Thanks for help guys!
Hussainoo said:
ok so now i need to find a new memory
whats best 32gb (for the price) i can find for my SG II?
Thanks for help guys!
Click to expand...
Click to collapse
Best is relative to your needs but I, and many others, prefer a card with a good balance of read/write speeds and decent IOPS. The Class 4 32GB Sandisk card is well respected and a solid performer for the price. It is faster in reads/writes than the class 4 spec suggests and has much better IOPS performance that the supposedly better class 10 cards.
Install and Configure a2sdgui ROM's CyanogenMod
Hello fellow good here I leave this tutorial hos to use a2sdgui based on CyanogenMod ROMs, as these ROMs do not include this system and its installation is different from a stock rom; a2sdgui is an app that allows us to extend the internal memory the mobile to have more space to install apps, this is accomplished by configuring two aspects: SD memory partition and installing a script called darktremor a2sdgui, well initiate:
THE WHOLE PROCESS IS DONE AT YOUR OWN RISK, I AM NOT RESPONSIBLE FOR BRICKS IN MOBILE IF YOU DO EVERYTHING AS SHOWN TO WORK ALL YOU ASSURE THAT CORRECTLY
RECOMMENDED TO DO BEFORE INSTALLING THE MOBILE APPS
Requirements:
- ROM based CyanogenMod 7.1 or 7.2
- Install a2sdgui (DOWNLOAD FROM THE MARKET)
- Script darktremor a2sdgui 2.7.5.3 Beta 04 (Download)
- SD card partitioned
Instructions:
1. - Install a2sdgui
2. - MicroSD Memory Partitioning:
First download the MiniTool Partition Wizard.
http://download.cnet.com/Partition-W...=dl&tag=button
Once installed, we put our SD on the PC (with a reader, adapter or anything like that) and open the program.
If you already have some partitions it is recommended that if we start from 0 erase all as shown.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After deleting all now begin creating them.
We give and we get this Edit menu and the first is FAT32.
We have to make FAT32 and Primary, we assign space is relative, I having 8GB (class 6) I put all but 1.5 will be for ext4 and swap.
Now for the ext4 partition, select PRIMARY. Now the partition type is relative, it is recommended that if your card is less than 6 class partition is ext2. If Class 6 or more ext4. That and I leave to your judgment, in my case I assign 1 GB will be to host the apps as if they were in the internal memory.
Now we use the remaining space for the swap partition (PRIMARY), in my case 500 Mb RAM With this more of our ACE will have 800 MB of Ram (the swap partition is a partition that is used like RAM, it is so important!)
APPLY Now we give and we get this message should accept and the thing to end as you see in the two screenshots below.
Partitions that I recommend are:
3. - Restart the phone in recovery mode
4. - Scroll to and select mounts & storage mount / data and mount / system
5. - Made the above should be unmount / data and unmount / system
6. - Now return to the main menu of recovery
7. - Enter to install zip from sdcard> choose zip from sdcard>-2.7.5.3-beta04 dtapps2sd-signed.zip
8. - Restart the phone, when you start DO NOT OPEN OR ANYTHING IN THE MOBILE, the mobile just restart again, it is NORMAL not alarmed.
9. After reboot, enter A2SDGUI. On the menu that appears in the display of APPS on SD are expected to be active and SWAP may also, in case this is not no more to give up and active. At the end of the menu is the VALUE SET 0-100, I got 100 and I gave the side.
10. - Now we turn to LowMen directly and I have chosen this, to me is the one that best suits me. The option below elijais leave more free memory, it is better but in my case having 800 mb is fine for me up there.
11. - Now let's Dalvik-Cache and choose it and click Move & Rebuild and phone will reboot.
AND THIS IS WHAT WE HAVE TO END MUCH MEMORY FREE AND ESPECIALLY A lot of RAM! ENJOY!
Link2sd is better ..and s2e is better heavenly
Sent from my SGA rocking CM7.2 by vo-1 + all-in-one script
@tazlooney89, thanks for sharing this tutorial.
Could you please explain the difference between link2sd, s2e and app2sdgui??
there are so many methods, gets pretty confusing which to use.
ayush29k said:
@tazlooney89, thanks for sharing this tutorial.
Could you please explain the difference between link2sd, s2e and app2sdgui??
there are so many methods, gets pretty confusing which to use.
Click to expand...
Click to collapse
Yeah, Im pretty confused on this too.
What are the differences and cons/pros of each?
Thanks in advance
ayush29k said:
@tazlooney89, thanks for sharing this tutorial.
Could you please explain the difference between link2sd, s2e and app2sdgui??
there are so many methods, gets pretty confusing which to use.
Click to expand...
Click to collapse
Robbang said:
Yeah, Im pretty confused on this too.
What are the differences and cons/pros of each?
Thanks in advance
Click to expand...
Click to collapse
I haven't used s2e, so i can't give you a description of, but i can say that the main difference between links2sd and app2sdgui is that meanwhile the first only moves the apps to the sd (even those that aren't allowed to by the os), app2sdgui "cheat" Android to "think" that it have more internal memory, but really it's just part of your sdcard.
Hope you'd understood me
raymanlololo said:
I haven't used s2e, so i can't give you a description of, but i can say that the main difference between links2sd and app2sdgui is that meanwhile the first only moves the apps to the sd (even those that aren't allowed to by the os), app2sdgui "cheat" Android to "think" that it have more internal memory, but really it's just part of your sdcard.
Hope you'd understood me
Click to expand...
Click to collapse
Ok. Thanks. So what do you use? app2sdgui? I have used Link2Sd for a week or so now. I think it is really good. it gets the job done nicely.
Robbang said:
Ok. Thanks. So what do you use? app2sdgui? I have used Link2Sd for a week or so now. I think it is really good. it gets the job done nicely.
Click to expand...
Click to collapse
No one, 'cause I've installed the stocklite and,I don't know why, app2sdgui doesn't run on it (to me at least).
try this
raymanlololo said:
No one, 'cause I've installed the stocklite and,I don't know why, app2sdgui doesn't run on it (to me at least).
Click to expand...
Click to collapse
did u see this thread http://forum.xda-developers.com/showthread.php?t=1485470
raymanlololo said:
No one, 'cause I've installed the stocklite and,I don't know why, app2sdgui doesn't run on it (to me at least).
Click to expand...
Click to collapse
DTaaps2sd doesnt work on stock rom .. as it need supported kernel.... ext4 sd-ext partition....
and stock provides with rfs system type....so running app2sdgui is not possible..
refer the link here...
DT A2SD thread on xda : http://forum.xda-developers.com/showthread.php?t=715940
this one is my try on explaing DTA2sd--
http://forum.xda-developers.com/showthread.php?t=1530270
ps1max said:
did u see this thread http://forum.xda-developers.com/showthread.php?t=1485470
Click to expand...
Click to collapse
ambujpriyadarshi1991 said:
DTaaps2sd doesnt work on stock rom .. as it need supported kernel.... ext4 sd-ext partition....
and stock provides with rfs system type....so running app2sdgui is not possible..
refer the link here...
DT A2SD thread on xda : http://forum.xda-developers.com/showthread.php?t=715940
this one is my try on explaing DTA2sd--
http://forum.xda-developers.com/showthread.php?t=1530270
Click to expand...
Click to collapse
I think you guys didn't understood me; I'm on the stocklite v3, and it's a custom rom with DT scripts installed. Anyway I'll take a look over that threads ;-)
EDIT:
Haha, i've messed it up!
I don't know why or how, but now i have the app2sdgui running, but....also i had runngin link2sd, and several apps linked. Now i have a lot of "andro-boxes" (linked apps that are, seems, not readable) in my phone, a sdcard partitioned and a lot of information blocked.
I'm trying to create the mount scripts on link2sd to unmake the links, and start using app2sdgui, but link2sd can't because "device or resource busy"
Good, i'm the best! XD
I can't activate de Swap.
When I pres the button to activate the swap, appears "Changing setings..." after that "Reading setings...", some buttons appears in background but after 1 sec disappear.
how to fix that ? thx before...
myshowbiz said:
I can't activate de Swap.
When I pres the button to activate the swap, appears "Changing setings..." after that "Reading setings...", some buttons appears in background but after 1 sec disappear.
how to fix that ? thx before...
Click to expand...
Click to collapse
If you use Swype beta you need authenticate them, but u can use a altenative, a swype modify, i dont know if i can post the link here, because i dont know if this is a warez... ?? but put in the google and search for DA SWYPE. In this web site you have many options of colors of swype.
myshowbiz said:
I can't activate de Swap.
When I pres the button to activate the swap, appears "Changing setings..." after that "Reading setings...", some buttons appears in background but after 1 sec disappear.
how to fix that ? thx before...
Click to expand...
Click to collapse
Same goes here...cant activate the swap
Copied from CarlDeanCatabay post
Increase RAM using Swap File and Swap PartitionNOTE:
I spent hours updating my guides and I don't ask you to press that THANKS button, be kind enough not to copy my guides to other forums. I know some noobs want to make a name on other forum boards... but hey, that's not an excuse! WARNING: This mod may degrade SD card life.
What you need:
MiniTool Partition Wizard for SD Card Partitioning
A MicroSD HC 4GB or higher class 6 or class 10
MicroSD HC Card Adapter
A card reader (if your pc doesn't have card reader built in | USB Mount is not adviseable)
Swapper2 from Google Play Store [DOWNLOAD]
ADB Shell or terminal Emulator (to check if swap is activated)
Make sure you have BusyBox installed
Before we start, lets do some reading . . .
RAM
What is RAMRandom Access Memory (RAM) is temporary data storage that the CPU uses during calculations. The more RAM a device has, the more calculated results the CPU can store - which means less time the CPU has to do the same thing over and over again. In other words, the CPU can check RAM to see if it has already made a particular calculation in the recent past. If it has, it can use the pre-computed results instead of wasting processing time recomputing the same calculation. In short, more RAM means a more efficient (and faster) device. SWAP
What is SWAPSwap is, in short, virtual RAM. With swap, a small portion of the hard drive is set aside and used like RAM. The computer will attempt to keep as much information as possible in RAM until the RAM is full. At that point, the computer will begin moving inactive blocks of memory (called pages) to the hard disk, freeing up RAM for active processes. If one of the pages on the hard disk needs to be accessed again, it will be moved back into RAM, and a different inactive page in RAM will be moved onto the hard disk ('swapped'). The trade off is disks and SD cards are considerably slower than physical RAM, so when something needs to be swapped, there is a noticeable performance hit.
Unlike traditional swap, Android's Memory Manager kills inactive processes to free up memory. Android signals to the process, then the process will usually write out a small bit of specific information about its state (for example, Google Maps may write out the map view coordinates; Browser might write the URL of the page being viewed) and then the process exits. When you next access that application, it is restarted: the application is loaded from storage, and retrieves the state information that it saved when it last closed. In some applications, this makes it seem as if the application never closed at all. This is not much different from traditional swap, except that Android apps are specially programed to write out very specific information, making Android's Memory Manager more efficient that swap. Step by Step GuideHow to create Swap PartitionUsing MiniTool Partition Wizard
Plug in you MicroSD HC Card to your computer using the card adapter. (Do not use USB Mount)
Open MiniTool Partition Wizard and look for the card
Right Click on it and select Delete Partition
Click on Apply to Delete the Partition
Right Click on it again and select Create Partition
Set the partitions as follows:1st partition:
Label: Android-SD
Create as: Primary
File System: Fat32
Partition size: as much as you want! 2nd partition:
Label: Android-EXT3 (2nd partition is for EXT which you can use for A2SD or Link2SD)
Create as: Primary
File System: EXT3 (be it a custom kernel or ROM with EXT4 support, use EXT3 still -play safe! )
Partition size: MIN: 256 MB MAX: 1024MB (1GB)3rd partition:
Label: (do not put anything)
Create as: Primary
File System: Linux Swap
Partition size: MIN: 32MB MAX: 1024MB(1GB) RECOMMENDED: 256MB
After creating partitions, click Apply to apply changes.
Using ClockWorkMod
Reboot to Recovery
Go to Advanced and Debugging
Select partition SD card and select the partition size that delights you
How to use Swap
For us to be able to use swap file or swap partition, we need to use Swapper2 which you can get from Google Play.
Download and Install Swapper2 (of course)
After installing, open Swapper2 and navigate to Menu > Settings
Swapper preferences: (for kernels that doesn't have swap partition support)
Run swapper at startup (put a check)
Swap place: /sd card/swapfile.swp (you can place it in a folder if you don't like a messy sd card structure )
Swap size: MIN: 10 MB MAX: 256MB RECOMMENDED: 32MB (choose any)
Swapiness: RECOMMENDED: 10MB SYSTEM DEFAULT: 60MB MAX: 100MB (choose any)
Safe unmount (put a check)
Safe remount (put a check)
Advanced preferences: (for Kernels that supports swap partition only)
Use swap partition (put a check)
Swap partition: /dev/block/mmcblk0p2
After setting preferences, press back and tap on "ON" to turn on swap. Reboot afterwards
How can I tell if swap is running?Go to the terminal emulator - or open adb shell - and run 'free'.
If it looks like this (with zeros in the swap line), you do not have swap:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If it looks like this (with anything other than zeros in the swap line), you do have swap:
NOTE:
You need to turn off swap before you mount SD via USB, if you don't you will not be able to mount sd as swapfile is active and set to read only which will deny request to mount USB Storage.Confirmed Working:
works on my ace Rom StockLite v6 with kernel : cf-root b83 from ketut
Thanks!
Very helpful - noob notwithsanding
thanks for the info. Will it show in task manager the total ram size increase?
\\
says swapper 2 is incompatible ace. can i have the apk?
BUMP !! Anyone?
lukip005 said:
BUMP !! Anyone?
Click to expand...
Click to collapse
No
Sent from my GT-S5830 using Tapatalk 2
does anyone have tried this. ?
is this really working . ?
manthan2611 said:
does anyone have tried this. ?
is this really working . ?
Click to expand...
Click to collapse
its impossible to increase the ram size. it is a Hardware part. swapping will destroy your flashmemory
Sent from my GT-S5830 using Tapatalk
I try these steps More than once, but also each time have 1 error when try turn on swap:
Code:
swapoff /dev/block/mmcblk0p2 invalid argument
Thanks for this post
Friends, you can't increase your RAM. It's size is fixed in the RAM chip. There's nothing like a Linux swap partition/Windows ReadyBoost to help with this but overclocking your CPU can increase your performance and also try to install lighter ROMs like AOSP ROM. I hope this will help you.
Kindly,
MZ
Does it affect on battery's life? shorter?
nambont12 said:
Does it affect on battery's life? shorter?
Click to expand...
Click to collapse
Yes, it will affect your battery life a bit as it is always running in the background. Hope I Helped
Hi devs,
hoping on help of people who better know about this materia than me, I hope to create a workaround for OTA repair on faulty Iconia B1-A71 from Acer.
In this case we need devs who has knowledge about stock JB and also testers, who has a B1 with problems on installing OTA Updates with "Invalid partition settings" on FAT.
Status:
More and more user of B1 report the problem of updating their device by OTA. It appears to be a mass problem, which Acer has no solution for.
After checking on rooting issues we already know, that there is a difference in dumchar_info between "normal" and "faulty" B1´s:
Android Partition:
http://forum.xda-developers.com/showpost.php?p=40987372&postcount=197
Normal - android 0x0000000026500000 0x00000000020e8000 2 /dev/block/mmcblk0p3
Faulty - android 0x0000000015e00000 0x00000000020e8000 2 /dev/block/mmcblk0p3
Furthermore there is a difference (and this I assume is the problem for OTA routines) on FAT partition:
Normal - fat 0x0000000148638000 0x00000000882e8000 2 /dev/block/mmcblk0p6
Faulty - fat 0x00000001b0a38000 0x00000000232e8000 2 /dev/block/mmcblk0p6
Those who was in charge of rooting the B1 knows, that we have dumped the android partition by dd using the offset shown in dumchar_info.
In this logic it would be impossible to dump a faulty B1 system.img by using the normal offests - you would not "meet the partition/bits", if you use wrong data.
BUT - as we found out it was possible to dump the system.img from a faulty B1 using the offset of a normal B1! User agentdeep confirms a successful root from scratch on Linux base using the normal offsets: http://forum.xda-developers.com/showpost.php?p=40988791&postcount=202
Now my idea:
- According entonjackson pawitp already assume, that the dumchar_info may be wrong, since otherwise agentdeep would have a bricked device. IF we can proof that OTA checks this value - would it make sense to push a corrected dumchar_info through the ENGMODE backdoor? Anyone out there, who is able to save and extract the OTA, to see the routine?
- If it dont work, does it make sense to try a root from scratch on Linux - and fix the dumchar_info afterwards? Is it possible?
- How can I check a report of existing partitions on Android? Do I have to run busybox from terminal, to start fdisk? I would like to validate the partition information inside the dumchar_info...
This subject may be not as hot as a rooting thread - but more and more user report their problem with update errors, and we may help lots of them ... and show Acer, how this work has to be done...
Thank you in advance!
Sub.
I would like to try that procedure enton asked me by replacing 15e to 265 in dumchar_info. But knowing there is no way I can restore my nandroid backup if something bad happens, I will hold for now
Nice to meet you here, agentdeep I was hoping you will join this thread, since you are the one who made me thinking about this solution...
From my point of view the risk of bricking the tab after changing the dumchar_info is ... pretty low. As long as we have a working system you still can switch back to your origin value. But at that point I would also like to get some more background from the Linux masters in here. Currently I have a problem to understand about the dumchar_info - what is it? How it is created? Do I understand right, that it is an output from Linux kernel?
When this file is accessed? On boot? Which result we will have, if we change it? Is it a properties file, used to set up partitions - or just an info? IF it is only an information we can change it without any fear...
https://github.com/ameer1234567890/...To-Gather-Information-About-Partition-Layouts
This page gives us the information, that "fat" is not just the format - it is the internal memory on MTK based devices. Which finally gives me more inscentive to believe that we have an issue with 8gb and 16gb versions. On that I have seen a thread in a different forum, where a user reported to have opened the B1 and found out that there were 16gb internal memory instead of 8gb as shown in the device properties.
Probably we have "masked" 16gb-versions declared as 8gb???
alba81 said:
Nice to meet you here, agentdeep I was hoping you will join this thread, since you are the one who made me thinking about this solution...
From my point of view the risk of bricking the tab after changing the dumchar_info is ... pretty low. As long as we have a working system you still can switch back to your origin value. But at that point I would also like to get some more background from the Linux masters in here. Currently I have a problem to understand about the dumchar_info - what is it? How it is created? Do I understand right, that it is an output from Linux kernel?
When this file is accessed? On boot? Which result we will have, if we change it? Is it a properties file, used to set up partitions - or just an info? IF it is only an information we can change it without any fear...
Click to expand...
Click to collapse
1st, thanks for the thread! It's really been time to create one for this issue.
I will put a link on the 1st post of my thread to this one, for people experiencing this issue.
Regarding agentdeep, I also think changing the dumchar_info won't brick the device. But we should first make sure it won't brick.
Although I'm using Linux for like 10 years now, I cannot help a lot at this moment.
But if there will be a solution, I will put it immediatly into my toolkit
So, I made a small calculation for the offsets, and this seems to confirm a wrong information in the dumchar_info:
Normal B1 Offset Android size:
Hex: 26500 Dez: 156928 Multiplied with 4096=642777088 Divided by 1024 = 627.712kB
Faulty B1 Offset Android size:
Hex: 15e00 Dez: 89600 Multiplied with 4096=367001600 Divided by 1024 = 358.400kB
If you take into consideration, that the system.img.gz takes (in packed form!) about 350 MB, unpacked even 627,712kB (size of the parition, see above) - then it appears that the information MUST be wrong - if I am right with my calculation...
Following this we have these values for internal memory on both versions:
Normal B1 Offset FAT size:
Hex: 148638 Dez: 1345080 Multiplied with 4096=5509447680 Divided by 1024 = 5.380.320kB
Faulty B1 Offset FAT size:
Hex: 1b0a38 Dez: 1772088 Multiplied with 4096=7258472448 Divided by 1024 = 7.088.352kB
Anyone with 15e can check available space on internal memory? In fact it should be about 5GB as I remember (have the B1 not with me now).
Maybe I am writing complete bull**** here? Anyone can confirm my calculation..??
Thanks in advance!
alba81 said:
So, I made a small calculation for the offsets, and this seems to confirm a wrong information in the dumchar_info:
Normal B1 Offset Android size:
Hex: 26500 Dez: 156928 Multiplied with 4096=642777088 Divided by 1024 = 627.712kB
Faulty B1 Offset Android size:
Hex: 15e00 Dez: 89600 Multiplied with 4096=367001600 Divided by 1024 = 358.400kB
If you take into consideration, that the system.img.gz takes (in packed form!) about 350 MB, unpacked even 627,712kB (size of the parition, see above) - then it appears that the information MUST be wrong - if I am right with my calculation...
Following this we have these values for internal memory on both versions:
Normal B1 Offset FAT size:
Hex: 148638 Dez: 1345080 Multiplied with 4096=5509447680 Divided by 1024 = 5.380.320kB
Faulty B1 Offset FAT size:
Hex: 1b0a38 Dez: 1772088 Multiplied with 4096=7258472448 Divided by 1024 = 7.088.352kB
Anyone with 15e can check available space on internal memory? In fact it should be about 5GB as I remember (have the B1 not with me now).
Maybe I am writing complete bull**** here? Anyone can confirm my calculation..??
Thanks in advance!
Click to expand...
Click to collapse
Yeah internal space is 5.12 GB like posted here in bullbrands post:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Note: this is after swapping internald and external sd...
The calculation looks good, but i don't know why the f... you multiply with 4096 and divide by 1024... I'm working as a developer and now I really feel stupid, because I really just don't know.
entonjackson said:
The calculation looks good, but i don't know why the f... you multiply with 4096 and divide by 1024... I'm working as a developer and now I really feel stupid, because I really just don't know.
Click to expand...
Click to collapse
Dont worry I could explain as follows: 4096 is the qty of bits you write at once on dd, and 1024 - logically to convert bits to KB.
Well, so we see that nothing is right in the dumchar_info, at least on Android and FAT partition, on faulty B1´s. Now we know there is a mistake - and need to validate the right offsets. Anyone has experience with fdisk on Android? Do I have to run it from busybox from terminal emulator?
And can anyone experienced tell us the specifications of dumchar_info? I found out it is a MTK-own chart, which is not existing on other CPU based devices .... which means for me - it can not be that critical in regards to format table, right?
On a rooted device - can we use a log to see when the dumchar_info is triggered?
alba81 said:
Dont worry I could explain as follows: 4096 is the qty of bits you write at once on dd, and 1024 - logically to convert bits to KB.
Well, so we see that nothing is right in the dumchar_info, at least on Android and FAT partition, on faulty B1´s. Now we know there is a mistake - and need to validate the right offsets. Anyone has experience with fdisk on Android? Do I have to run it from busybox from terminal emulator?
And can anyone experienced tell us the specifications of dumchar_info? I found out it is a MTK-own chart, which is not existing on other CPU based devices .... which means for me - it can not be that critical in regards to format table, right?
On a rooted device - can we use a log to see when the dumchar_info is triggered?
Click to expand...
Click to collapse
Ah I see. very easy. so bs=4096 is blocksize and well ok 1024 I already guessed could be convertion from bits to bytes. alright.
Then I would say, yes. the calculation makes sense indeed.
Now we only need someone that tries to write the right parition info into dumchar_info.
volunteers hands up! :victory:
entonjackson said:
Now we only need someone that tries to write the right parition info into dumchar_info.
volunteers hands up! :victory:
Click to expand...
Click to collapse
The biggest problem on that point is - you need to have either root, or do it by obtaining "temporary backdoor root" through ENGMODE. And the qty of user having root on faulty B1 is still pretty low...
alba81 said:
The biggest problem on that point is - you need to have either root, or do it by obtaining "temporary backdoor root" through ENGMODE. And the qty of user having root on faulty B1 is still pretty low...
Click to expand...
Click to collapse
i know busybox has fdisk binary.
adb doesn't know fdisk?
Where can I call it thru ADB?
Starting busybox from internal memory thru Terminal Emulator also makes me problems ... permission denied.
alba81 said:
Where can I call it thru ADB?
Starting busybox from internal memory thru Terminal Emulator also makes me problems ... permission denied.
Click to expand...
Click to collapse
There is none. I thought fdisk comes with adb, but... no.
But maybe we need no fdisk. If i understood it right, wie only must edit the dumchar_info so the system "believes" it has the right partitions again.
Yes, obviosly the update process checks this value. As you already checked the /proc/emmc shows different values, and /proc/mtd is empty. /proc/partitions contain different information type.
Before changing an important value I think we need to validate that any change in dumchar_info remains after reboot, since the update failure notification appears in recovery mode during update - right?
Edit:
I do not get access to dumchar_info. Going through ES File Manager I set the properties, and even it shows after changing its saved - its not. How can I get the rights? And how I can take the rights for system away to not be able to access it any more? Each time I open the properties of it I see a different date ... is it in permanent access?? Or do I need a different file Explorer?
Edit2:
Wikipedia is my friend. Ok, now I know - dumchar_info is a procfs, generated by the kernel during boot and not saved. So I am affraid ... we are stuck on a faulty kernel issue?
Where does the kernel gain this Information from during boot? Anybody an idea?
I hope this helps
agentdeep said:
I hope this helps
Click to expand...
Click to collapse
Thank you - I will validate later on, once I am at home ... have now only my n8000 with me.
Ok, checked - my version is the same, except:
[email protected] (after Linux version 3.4.0)
which I think can not be that important, since all other release data is similar. So it is not the kernel we have to fight with - at least...
Ok, so following on this subject we need to see what comes up in the future:
http://forum.xda-developers.com/showpost.php?p=41168837&postcount=295
At least the reason seems to be confirmed from Acer site - a faulty format which is reported.
IMHO it can not be only the update with the problem, the device itself reports a different format in dumchar_info, not the update.
Well - we´ll stay tuned...
hi there,
i have a faulty B1 with root....also i tried the Factory Reset Workaround several times, it does not work for me....everytime about 10-15% i got the message "partition error...bla".
So if you want me to to test things...go on
I'm new here, however I successfully rooted my device using the "toolkit" even though I have
Code:
Faulty - android 0x0000000015e00000 0x00000000020e8000 2 /dev/block/mmcblk0p3
Thanks to Enton.
My internal storage is reported to be just 5.17GB (not 8GB as expected) confirming the figures in a previous post.
I complained to acer support about the size of the internal storage being nearly 3GB short of what it should be and that I thought it was down to a "memory allocation error".
There response was " As you have mentioned in the previous e-mail internal storage shows as a 5.17GB, I would like to inform you that the other space of the unit is occupied by Android Operating System, customer will not be able to use the complete 8GB from the unit, as Operating system needs a space. "
Is this complete and utter BS? I understand 4.1.2 Jelly Bean is just over 200MB.
Can someone please confirm.
BTW if any dumps are required from my "faulty" device (I do not have the partition error though) I'm happy to try.
BTW2 I've installed the new PMTUpdate patch "FixG1PMT" and that did nothing for my problem.
------
TLDR
---
As most people know, 8GB is not enough for modern smartphones. With this mod, I provide a modified 'fstab' file and instructions on how to expand '/data' to install apps without root and in a universal way. All apps will install as if in internal storage.
Furthermore, given the old age of these phones, internal eMMC will progressively degrade until the phone dies completely. I have experienced going from 10MB/s writes, to 5, to 2 and then a completely dead phone. This extends the life of eMMC by only writing Android updates to eMMC and will improve responsiveness in phones with very worn eMMC flash.
This is work in progress (some slowdowns occur depending on the card), but I have been daily driving this mode for two months now. I have made adjustments so that the microSD stalls less than stock 'fstab' and EXT4 filesystem.
Example of 64GB card, w/ backup partition (p2) created, still 26GiB free for apps:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---
THIS MAY DELETE YOUR DATA OR SOFT-BRICK YOUR PHONE. Be careful beforehand and backup your data to another microSD card.
IF YOUR PC HAS eMMC DRIVE, /dev/mmcblk1 MAY BE YOUR OS. Check before doing anything and after each reboot, as sometimes Linux reassigns them on machines with eMMC + card reader.
---
TODO/BUGS
---
- Used space will be messed up if you use more than one partition (can't be mounted as removable storage) but free space will be correct.
- Sometimes I have experienced reboots, with no data loss that I can find. I don't think it is related to this ROM mod.
- F2FS is still experimental and has no way to recover from a corrupted drive/card. If something goes wrong, your only option is to dump the files with PhotoRec software and try to recover what you can.
The data will be there but F2FS can't seem to recover from a damaged superblock.
I have used on one phone without issues for 3+ years but when there is SB corruption it can't recover.
- Push this to a 16.0 ROM, which is lighter on the RAM and has ambient display. (just personal preference) This requires a custom ROM.
---
HARDWARE
---
First you need a capable microSDXC card, I have only tested SanDisk Ultra A1 which are not perfect. SanDisk Extreme 64GB A2 class are probably good but please report performance if you try it. I only recommend this class of cards.
The problem with Sandisk Ultra is that sometimes they stall doing GC and the phone also stalls. This is quite random and will be worse if you use the phone for extended periods without time for background GC to run.
The advantages is they do some kind of wear-levelling and I am yet to see one of these cards die to wear out, despite being used on RPi machines 24/7.
SanDisk Ultra cards (A1 class) and most SanDisk USB drives have issues where they perform great when new but don't do proper garbage collection and will get very slow after a couple of days. So benchmarks look fine but real world it becomes really bad. I had a USB drive that only recovered to 5MB/s writes, that was the baseline, after three or four sequential wipes to most of the drive. These types of cards will also be very slow if you try them as adoptable storage.
Any microSD will work but choose a fast one and please help test different brands.
You also need a PC, preferably with Linux, and a card reader of any kind. This can be done in Windows through TWRP and ADB access but I don't recommend it.
---
BASICS
---
We will format the microSD card with one or two partitions. If you split it, you can do manual backups for the second partition but you can't mount it. Remember that by using /data on the SD card, you cannot use TWRP to backup to it. The modded '/data' partition will mount as a removable SD card in stock TWRP.
Download files:
Arco68's LineageOS 17.1 ROM
The new 'fstab' file from Pastebin: fstab.qcom.
Process flow:
Install 'adb' and enter TWRP mode to access shell,
Use fdisk to create a DOS partition table
Add a new partition with half or full size, starting at block 32768. Leave 1 or 2GiB space free and don't touch it with data. Some types of cards will be able to use these for better performance.
(OPTIONAL) Create 2nd partition right after the first one.
Change the partition(s) type to 'Linux' and spare space as 'Hidden HPFS/NTFS'.
Format partition(s) as F2FS (can also do ext4 but should be unusable),
After this, we will install arco68's 17.1 ROM and push a new 'fstab.qcom' file that will mount the microSD partiton as '/data' and the phone can use it to install apps and user data.
Encryption has not been tested and is not expected to work.
---
PREPARE microSDXC CARD
---
You should also format the card on a Linux PC if you can, as recovery has outdated f2fs-progs or not at all. The ROM has modules and will boot F2FS when instructed to do so.
Check that /dev/mmcblk1 is your microSD card reader BEFORE PROCEEDING! Otherwise, you may nuke your OS!
Do the procedure as listed before, first thing is to 'p' to check you are on the right microSD drive.
Then create the new DOS table and the partitions. This is for expert users only, at this time I will not post detailed fdisk commands.
The output from 'p' print command looks something like this:
Disk /dev/mmcblk1: 31.00 GiB, xxx bytes, 16252928 sectors
Disk model: Sandisk Ultra
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xZZZYYYXXX
Device Boot Start End Sectors Size Id Type
/dev/mmcblk1p1 * 32768 62947327 62914560 30G 83 Linux
/dev/mmcblk1p2 62947328 yyyyyyyy xxxxxx 900M 17 Hidden HPFS/NTFS
Click to expand...
Click to collapse
You have to manually type '62947328' for the start of the hidden partition. This is only required if you had put data on the card, upon which you should TRIM the unused blocks:
blkdiscard -v /dev/mmcblk1p2
Click to expand...
Click to collapse
If you have a partition to do backups, this moves to p3. Next we format p1 to use as '/data':
mkfs.f2fs -s 2 -z 1 -g android /dev/mmcblk1p1
Click to expand...
Click to collapse
Now we move the card into the phone.
---
ADB COMMANDS
---
This tutorial assumes you have arco68's LineageOS 17.1 from this ROM already installed.
You need to boot the phone in recovery mode by rebooting with VOLUME UP + HOME pressed, until you see 'recovery booting' on the top of the screen.
Next, mount the /system partition and push the new 'fstab' file from your PC:
adb push fstab.qcom /system/vendor/etc/fstab.qcom
Click to expand...
Click to collapse
After this is completed wait a few seconds, unmount system and reboot the phone. It should take a while for the first boot but you should see the setup screen and everything should be running.
If it is not booting, go to recovery or remove the microSD card and check if files are being created on the drive. If yes, everything seems ok. S4 Mini has a very long first boot, for some reason.
Enjoy your new S4 Mini storage of 32/64/128 GB!
RESERVED FOR microSDXC user reports.
I already have LOS 17.1 on my gt-i9192, is there any video tutorial to help out in the SDCARD mod process?
Not really. Are you familiar with Linux and formatting hard drives? If you are, it's mostly install the software and run the commands. You need to know how to find the sdcard device node in /dev (if it's sdX or mmcblk0/1, depending on the PC).
I can help you out or post a preformatted MBR file so you can just write it to the SDCard.
As my 18.1 phone has eaten it's eMMC, I think I'll do this on my next one. Have you used this with Magisk?
ivorget said:
As my 18.1 phone has eaten it's eMMC, I think I'll do this on my next one. Have you used this with Magisk?
Click to expand...
Click to collapse
I definitely recommend doing this then, as I had my eMMC also down to something like 2MiB/s sequential writes before it died - after a few months - and killed the phone completely.
I have never used Magisk nor really understand it's purpose. What would you want to accomplish?
so it's possible format microSD as EXT4?
Yes, it is but you would need to change the above FSTAB file entry for 'mmcblk1p1' from F2FS to:
/dev/block/platform/msm_sdcc.3/mmcblk1p1 /data noatime,nosuid,nodev,auto_da_alloc
I would advise you to not use EXT4 as that is usually more suited to flash with advanced FTL and even TRIM support.
tM&M said:
I definitely recommend doing this then, as I had my eMMC also down to something like 2MiB/s sequential writes before it died - after a few months - and killed the phone completely.
I have never used Magisk nor really understand it's purpose. What would you want to accomplish?
Click to expand...
Click to collapse
Sorry, just saw this now. Yeah I went and ahead and did on 18.1 and it's working great so thanks for making this guide. I guess it's not really necessary as it hasn't caused you issues but I also fixed the relevant userdata partition line in /vendor/etc/selinux/vendor_file_contexts.
A GPT partition table also works fine now, maybe was just lucky as I saw afterwards that was a recent fix lifted into our kernel. Using gparted and mkfs.f2fs from a recent linux system doesn't seem to have caused any issues either.
I'm using a V10 speed card which I think is about the speed of the original eMMC so should probably be the suggested minimum.
Magisk I use for root, mainly for a Tasker setup to tweak charging to extend battery life. I'll tidy it up enough to share at some stage.
Anyway I took a chance and Magisk does work on this setup too.
ivorget said:
Sorry, just saw this now. Yeah I went and ahead and did on 18.1 and it's working great so thanks for making this guide. I guess it's not really necessary as it hasn't caused you issues but I also fixed the relevant userdata partition line in /vendor/etc/selinux/vendor_file_contexts.
A GPT partition table also works fine now, maybe was just lucky as I saw afterwards that was a recent fix lifted into our kernel. Using gparted and mkfs.f2fs from a recent linux system doesn't seem to have caused any issues either.
I'm using a V10 speed card which I think is about the speed of the original eMMC so should probably be the suggested minimum.
Magisk I use for root, mainly for a Tasker setup to tweak charging to extend battery life. I'll tidy it up enough to share at some stage.
Anyway I took a chance and Magisk does work on this setup too.
Click to expand...
Click to collapse
If you can share the context file that would be great. I was having some issues with contexts but this was not MOD related - happened wit the stock ROM - and had to manually fix contexts on TWRP. So maybe that was the issue.
Do please post what card you are using and if you experience performance degradation after a couple of weeks. SanDisk cards are notorious for only running well the first couple of days as they don't have background GC and maybe are not suited to F2FS/EXT4 at all.
tM&M said:
If you can share the context file that would be great. I was having some issues with contexts but this was not MOD related - happened wit the stock ROM - and had to manually fix contexts on TWRP. So maybe that was the issue.
Do please post what card you are using and if you experience performance degradation after a couple of weeks. SanDisk cards are notorious for only running well the first couple of days as they don't have background GC and maybe are not suited to F2FS/EXT4 at all.
Click to expand...
Click to collapse
OK I've attached the file - remove the .txt extension. Search for mmcblk1p1 to see the changes - one line referencing mmcblk1p1 commented out and another line where the data partition is changed to that.
(Full disclosure: I'm using partition 4 so I didn't need to comment out the mmcblk1p1 partition line in my setup.)
Reminder that the file is for 18.1 (unless you find that it's the same for 17.1). And to be clear for anyone else reading the full path it goes under is:
/system/vendor/etc/selinux/
My SD card is a Kingston Canvas Select Plus. The package indicates Class 10 U1 so maybe better to say that as the V10 only appears on the card label.
I am a little concerned that the default android 3-day trim seems to be taking longer but I'll keep an eye on it:
$ logcat | grep -E 'trim |Trimmed'
02-04 06:50:34.969 191 9173 D vold : Starting trim of /data
02-04 06:51:09.778 191 9173 I vold : Trimmed 397697024 bytes on /data in 34799ms