Has anyone seen or been able to confirm if the US dock will be able to utilize SDXC cards? Some sites lists SDXC compatibility while others do not.
Well, the specs say that it does have 4 in 1 SD card reader and that it supports SDXC:
http://www.amazon.com/gp/product/B0...17145&creative=399349&creativeASIN=B004U78628
What's in the Box
TF101 Tablet Docking Station
User manual
Specifications
Input/Output: 2 x USB 2.0
Card Reader: 1 x 4-in-1 Card Reader / MMC / SD (SDHC/SDXC)
Battery: 24.4 W/h Li-polymer battery (up to 6.5 hours)1
Dimensions: 10.67" x7.28" x 1.1" inches (W x D x H)
Weight: 1.41 lbs (with battery)
Color: Espresso
Some SDXC cards with good reviews but prices are too high IMO!
I know that the specs say that but has it been comfirmed that sdxc cards work?
Not yet. Would be nice to see someone try.
I'll hopefully have my TF by some time next week. I'll be getting a 64GB XC card to go with it, so I'll let you know if someone hasn't already by then.
*Daedalus said:
I'll hopefully have my TF by some time next week. I'll be getting a 64GB XC card to go with it, so I'll let you know if someone hasn't already by then.
Click to expand...
Click to collapse
That would be awesome! Thank you!
*Daedalus said:
I'll hopefully have my TF by some time next week. I'll be getting a 64GB XC card to go with it, so I'll let you know if someone hasn't already by then.
Click to expand...
Click to collapse
Have you gotten your TF yet? If so, does the SDXC card work?
I already ordered a 64gb sdxc card, would be good to know if I should cancel my order.
I have a feeling it might not work at the moment but a future firmware update might unlock it, if indeed the slot is capable of it. But hey if you're getting a card and it doesnt work you can always send it back and let us know.
I've been running the SanDisk 64GB SDXC for a few days and it is working, BUT I had to format the sdcard as NTFS and I only ran it with RaYmAn's kernel which is found in Roach2010's rom Prime! and it worked with netarchy's kernel named Netformer also. Both kernels support NTFS.
I have not tried it with the stock kernel yet. I could be wrong, but I don't think it will work with the stock kernel. I also loaded up Blades kernel this morning and it didn't work. I only ran that kernel for a little bit and I see ntfs.ko is in there. I'm sure it will work with Blades kernel. I'll load it up later because that thing is crazy fast.
A big thanks to all of the developers out there
{
"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"
}
Thanks for that cky2000.
Thou I'm no Android wiz, so when you say "kernal" I'm just thinking ROM, but that is not the same is it? I'll prefer to use the stock ROM, thou I might root it to get Titanium back or the likes of it.
Wazkyr said:
Have you gotten your TF yet? If so, does the SDXC card work?
Click to expand...
Click to collapse
I've had to hold off on the TF purchase unfortunately. The money situation isn't quite as good as I'd hoped, and ASUS's Computex teaser has given me pause. I've decided to wait and see what they unveil.
*Daedalus said:
I've had to hold off on the TF purchase unfortunately. The money situation isn't quite as good as I'd hoped, and ASUS's Computex teaser has given me pause. I've decided to wait and see what they unveil.
Click to expand...
Click to collapse
Hehe the Computex show got me waiting too. I wont get my TF for a few weeks anyway, plenty of time to cancel, I just doubt(but hope) they release a new tablet with attachable keyboard, and i dont really need a pure laptop/tablet.
Wazkyr said:
Hehe the Computex show got me waiting too. I wont get my TF for a few weeks anyway, plenty of time to cancel, I just doubt(but hope) they release a new tablet with attachable keyboard, and i dont really need a pure laptop/tablet.
Click to expand...
Click to collapse
Yeah, I'm the same way. The ideal solution for me would be a 10.1 tablet/phone that could use the TF dock, but that's unlikely.
If anyone tries an SDXC card with a totally stock unit please let me know if it functions at all. Thanks.
Alright, went back to .9 and took asus's update .13 (HRI66.US_epad-8.2.3.13-20110511) meaning: totally stock
Formatted the 64GB sdxc sd card back to the way it came exFAT. Slapped it in there and it was a no go. Formatted to NTFS and threw it back in the dock (thinking it wasn't going to work) and like F'ing magic, it worked.
This was from some help in irc (just proof).
cat /proc/partitions
major minor #blocks name
179 0 15675392 mmcblk0
179 1 524288 mmcblk0p1
179 2 542208 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 542208 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 512 mmcblk0p6
179 7 14035456 mmcblk0p7
179 8 7977472 mmcblk1
179 9 7976448 mmcblk1p1
8 0 62367744 sda
8 1 62351360 sda1
One line from mount.
/dev/block/vold/8:1 /data/Removable/SD tntfs rw,relatime,uid=0,gid=0,umask=00,nl
I put about 2 GB of music, vidz and pix on the sd and everything worked. Copied back and forth (with the stock file manager) between the Microsd and the SD and that worked too. Alright, enough of this stock crap
I guess you could kind of test it before spending the $$$ on an sdxc. If your totally stock and have an regular sd card. Format it to ntfs and make sure it reads. I didn't think the stock kernel had support for ntfs....ummmm formatting will erase all your data.
Thanks for testing. That's great news.
Sent from my HTC Glacier using XDA Premium App
cky2000 said:
Alright, went back to .9 and took asus's update .13 (HRI66.US_epad-8.2.3.13-20110511) meaning: totally stock
Formatted the 64GB sdxc sd card back to the way it came exFAT. Slapped it in there and it was a no go. Formatted to NTFS and threw it back in the dock (thinking it wasn't going to work) and like F'ing magic, it worked.
This was from some help in irc (just proof).
cat /proc/partitions
major minor #blocks name
179 0 15675392 mmcblk0
179 1 524288 mmcblk0p1
179 2 542208 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 542208 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 512 mmcblk0p6
179 7 14035456 mmcblk0p7
179 8 7977472 mmcblk1
179 9 7976448 mmcblk1p1
8 0 62367744 sda
8 1 62351360 sda1
One line from mount.
/dev/block/vold/8:1 /data/Removable/SD tntfs rw,relatime,uid=0,gid=0,umask=00,nl
I put about 2 GB of music, vidz and pix on the sd and everything worked. Copied back and forth (with the stock file manager) between the Microsd and the SD and that worked too. Alright, enough of this stock crap
I guess you could kind of test it before spending the $$$ on an sdxc. If your totally stock and have an regular sd card. Format it to ntfs and make sure it reads. I didn't think the stock kernel had support for ntfs....ummmm formatting will erase all your data.
Click to expand...
Click to collapse
exFAT < - - - Well there's your problem.
benmyers2941 said:
exFAT < - - - Well there's your problem.
Click to expand...
Click to collapse
you are the best
Thanks for trying and reporting. Bring on the 2tb cards!
cky2000 said:
Alright, went back to .9 and took asus's update .13 (HRI66.US_epad-8.2.3.13-20110511) meaning: totally stock
Formatted the 64GB sdxc sd card back to the way it came exFAT. Slapped it in there and it was a no go. Formatted to NTFS and threw it back in the dock (thinking it wasn't going to work) and like F'ing magic, it worked.
This was from some help in irc (just proof).
cat /proc/partitions
major minor #blocks name
179 0 15675392 mmcblk0
179 1 524288 mmcblk0p1
179 2 542208 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 542208 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 512 mmcblk0p6
179 7 14035456 mmcblk0p7
179 8 7977472 mmcblk1
179 9 7976448 mmcblk1p1
8 0 62367744 sda
8 1 62351360 sda1
One line from mount.
/dev/block/vold/8:1 /data/Removable/SD tntfs rw,relatime,uid=0,gid=0,umask=00,nl
I put about 2 GB of music, vidz and pix on the sd and everything worked. Copied back and forth (with the stock file manager) between the Microsd and the SD and that worked too. Alright, enough of this stock crap
I guess you could kind of test it before spending the $$$ on an sdxc. If your totally stock and have an regular sd card. Format it to ntfs and make sure it reads. I didn't think the stock kernel had support for ntfs....ummmm formatting will erase all your data.
Click to expand...
Click to collapse
What brand of card is it? I am also looking to get one.
Related
( moderator please consider pinning this post )
You can mess up your tablet "IF" you do some wrong steps. Wish to list terse ( one line ) bullets to make it direct. There are other post that lay out the details.
The forum has a VERY nice search function. It is silly not to take advantage of it.
==================================================
1) Do not put cm7.2 'internal' upgrade on the 8GB units ! Fixed ! ! ! !
2) Do not load Chainfire3D drivers on your cm7.2 . . . . . this one killed me !
3) Using cm7.2 'external' on 8GB and 16GB units will not touch the nook's original os.
4) Using the 'Ubuntu - total wipe & re-flash' will erase your 'serial number' and 'deviceID'. Fixed ! !
5) Recoveries can and will FAIL if you have a damaged partition table.
6) Some sd card's brands ( Lexar ) and classes ( 10 ) will work poorly ( or not at all ! ) in your nook as your external os.
7) Always flash on a full battery.
8) Always format your sd card ( first ) with fat32. . . . . ( sdformatter v3.0 )
9) Side loading will not work until you turn 'on' unknown sources in settings \ applications.
10) Display is easily the #1 battery drain... Want it to last longer, dim the display.
11) Loading in 100+ apps will only take away one third of your ( app ) storage. . . . . typically, your mileage may vary
12) Your nook will not charge if turned 'on' and using your phone's charger.
13) Key app in GingerBread / cm7.2 - app2sd is not available / usable in ICS / cm9.
14) OTA stands for 'Over The Air' - B&N is sending your ( stock ) unit an update.
15) The devs need to fix tough problems, so please don't post in their area.
16) Rooting your stock NT does NOT block OTA's.
17) Take note of apps with "HD" in their title. They require h/w accelleration ( which we do not have working yet )
18) If its 'off' but the back lite is still 'on' then it is hung.
19) One possible way to get it out of a hang is to: press and hold the 'N' button and the 'Volume Up'. Now in addition, press and hold the power for a count of ten and let go.
20) Always backup before trying something ( anything ! )
21) Turn 'off' unknown sources when you don't need it. New virus uses unknown sources to infect your tablet.
22) CM9 is in 'alpha' for 16 and 8GB units. Please don't load unless you understand the risk and know how to back it out.
23) Ad-hoc tethering works ! Must apply a wpa_supplicant fix via adb to your rooted nook
24) Use a partition manager to resize your booting sd and regain the unused space on the card. ALERT ! Danger ahead !
25) Windoze 7 people have to remember to 'right click' and then 'run as administrator' .
26) cm9 will quit working on purpose. http://forum.xda-developers.com/showpost.php?p=25478233&postcount=446
27) the b&n usb cable is "special" and plugs "deeper", which is required for charging.
28) the microphone is NOT working for a lot of people with cm7 & cm9. devs will fix... soon...
29) if your stock nook says software version 1.0.0 ... it is not OTA blocked. ... Heads up !
30) Connecting useful items to usb is called "usb hosting", which is NOT working yet.
31) Never trust a big download. ( especially if its slow ) Use md5 crc checksum to validate the integrity.
32) You can clean up your 'Dalvik cache' in Titanium Backup, goto menu / more.
33) if you're ONLY interest is reading books then the 'rooted' stock 'os' is best. do not install cm7 / cm9 ( yet ! )
34) when given the choice between App Installer, and Packaging Installer, always choose the second.
35) for cm7, an error has been reported in the build.prop file that results in emmc not mounting when connected to a PC
36) want to see what's going on with your memory/partitions ? get 'free' app "Storage Analyzer" to see internal and external !
37) asked to make a logcat/dmesg report ? get/use free app, 'Voodoo Report'. you can reboot and mail it to yourself.
38) turbo prop tweak : http://forum.xda-developers.com/showthread.php?t=1684997
Yeah good idea i have think about doing this because im really getting tired of repeat things over and over again but you beat me to it . You get my thanks.
~ Veronica
Sent from my Nook Tablet using xda premium
old_fart said:
( moderator please consider pinning this post )
You can mess up your tablet "IF" you do some wrong steps. Wish to list terse ( one line ) bullets to make it direct. There are other post that lay out the details.
==================================================
1) Do not put cm7.2 'internal' upgrade on the 8GB units.
2) Do not load Chainfire3D drivers on your cm7.2 . . . . . this one killed me !
3) Using cm7.2 'external' on 8GB and 16GB units will not touch the nook's original os.
4) Using the 'Ubuntu - total wipe & re-flash' will erase your 'serial number' and 'deviceID'.
5) Recoveries can and will FAIL if you have a damaged partition table.
6) Some sd card's brands ( * ) and classes ( 10 ) will work poorly ( or not at all ! ) in your nook as your external os.
7) Always flash on a full battery.
8) Always format your sd card ( first ) with fat32. . . . . ( sdformatter v3.0 )
9) Side loading will not work until you turn 'on' unknown sources in settings \ applications.
10) Display is easily the #1 battery drain... Want it to last longer, dim the display.
11) Loading in 100+ apps will only take away one third of your ( app ) storage. . . . . typically, your mileage may vary
12) Your nook will not charge if turned 'on' and using your phone's charger.
Click to expand...
Click to collapse
My mileage differs on #4. If you boot recovery afterwards your sn, deviceid, mac address, etc return. I have used this numerous times and still have all my stock info as when I took it out of box.
Maybe whatever happened that caused you to use this restore method caused you to loose your info or maybe I'm just lucky!
Hey old_fart or anyone with 8GB version NT,
Since I don't have an 8GB version, can you test something for me?
meghd00t told me this, MLO and u-boot are the only ones that will pass the correct cmdline to the kernel to tell it about the 512 RAM on the 8GB units.
I want to see if flashing the MLO and u-boot from 1.4.2 fix this problem.
Go here, https://github.com/succulent/acclaim_recovery_sdcard
Click on flash_u-boot_and_MLO.zip, view raw to download the zip and flash it. Then flash CM7 Alpha Final and see if it work. If not, my pre-built rom.
You can't brick your NT by doing this since it's the same files from BN update.
succulent said:
Since I don't have an 8GB version, can you test something for me?
Click to expand...
Click to collapse
sorry, i too have the original 16GB model.
.
ahh, what's an MLO ? ( x-loader ? )
old_fart said:
sorry, i too have the original 16GB model.
.
ahh, what's an MLO ? ( x-loader ? )
Click to expand...
Click to collapse
{
"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"
}
http://omappedia.org/wiki/Bootloader_Project
MLO is signed x-loader that load the bootloader (u-boot).
bump, new stuff learned and so added to the list...
old_fart said:
bump, new stuff learned and so added to the list...
Click to expand...
Click to collapse
ditto
added a couple new ones.
Changes to reflect the "NEW" cm7 beta compiled by CelticWebSolutions. It's really great that he has ( once again ) donated his expertise and did the hard work for the benefit of the group. Bravo Zulu !
.
Now let's clobber the cm9. Beat it into submission...
Great info. Thanks.
It was posts like this one that helped me to learn enough about the NT to allow me to root, add CM7, modify the build prop, etc. We noobs really do read these posts and we appreciate them. Thank you.:good:
I got a deal for the 8 gig for 80 bucks, I also see on frys they have the 16 gig for 105 shipped... what's the better deal and bargain? I just want to throw ICS on it and have a decent cheap tablet.
better late than never and for all those asking the same question
sah0724 said:
I got a deal for the 8 gig for 80 bucks, I also see on frys they have the 16 gig for 105 shipped... what's the better deal and bargain? I just want to throw ICS on it and have a decent cheap tablet.
Click to expand...
Click to collapse
Well the difference there would be the ram the 8gb has 512 Mb of RAM and the 16 gig has 1024 Mb of RAM. I have used both, owning the 8gb and working on my friends 16gb and the real difference is the 16gb loads a little faster, maybe 10 secs faster at most over the 8 gb and also I hate to say it but a little smoother gameplay. if it were me, at those prices I would spend the extra $25, see I was one didn't want to wait and went and bought it at B&N, regrettably.
As for putting ICS on it, there are ways for both tablets, most are compatible with each other, but just double check to make sure as you can severely mess things up if you do not use proper avenues of approach. Not to worry though, if you do, once again there are many way out there to fix it if you do. Well HoPe this helps any and all who wonder!
I recently picked up a Nook Tablet 8gb version second hand. I have been toying with the idea of rooting and adding CM10 to try to get more out of it. I was wondering how hard this process is and if its really worth it.
TheAndroidN00BIE said:
I recently picked up a Nook Tablet 8gb version second hand. I have been toying with the idea of rooting and adding CM10 to try to get more out of it. I was wondering how hard this process is and if its really worth it.
Click to expand...
Click to collapse
It's not that hard and is absolutely worth it. See http://forum.xda-developers.com/showthread.php?t=2575489 for info/pointers.
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.
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.
[MOD][GUIDE][TUTORIAL][SYSTEM PARTITION] STOCK NOTE 3 ODEXED & DEODEXED - N900PVPUBMI3 System
THIS IS THE O/P AND IS THE FIRST POST.. :fingers-crossed:
{
"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 is just the Stock System partition from a Stock Sprint galaxy Note 3. Build - N900PVPUBMI3
None Required, This is Stock Based!
Code:
[B][I][U]Jer24cumber[/U][/I][/B] - FOR ALLOWING ME TO TAKE A DEVICE BEFORE RELEASE, AND PULL THE SYSTEM IN THE SPRINT STORE. DID I SAY BEFORE RELEASE...!
[B][I][U]Chainfire[/U][/I][/B] - FOR ALWAYS GETTING US THE ROOT PRIVLEDGES THAT WE WANT. THANKS FOR THE HELP ON THE NOTE 3.
[B][I][U]DONATORS[/U][/I][/B] - FOR YOUR CONTINUED SUPPORT!
[B][I][U]TO ALL THE OTHER DEVS AND THE XDA COMMUNITY[/U][/I][/B] WITHOUT YOU, WE WOULDNT BE HERE!!!
Code:
[B]
- DEODEXED
- ZIPALIGNED
[/B]
Here are the Note 3 Mounting Points Guys:
Code:
Mounting Points for Samsung n900P - Sprint Galaxy Note 3.
aboot -> mmcblk0p6
apnhlos -> mmcblk0p1
backup -> mmcblk0p17
boot -> mmcblk0p14
cache -> mmcblk0p24
carrier -> mmcblk0p25
dbi -> mmcblk0p4
ddr -> mmcblk0p5
efs -> mmcblk0p11
fota -> mmcblk0p16
fsc -> mmcblk0p19
modem -> mmcblk0p2
modemst1 -> mmcblk0p12
pad -> mmcblk0p9
param -> mmcblk0p10
persdata -> mmcblk0p22
persist -> mmcblk0p21
recovery -> mmcblk0p15
rpm -> mmcblk0p7
sbl1 -> mmcblk0p3
ssd -> mmcblk0p20
system -> mmcblk0p23
tz -> mmcblk0p8
userdata -> mmcblk0p26
JellyBomb Supporters... Feel Free to add this to your signatures...
Code:
http://i921.photobucket.com/albums/ad51/518Loans/Publication5.pnG
Click to expand...
Click to collapse
Code:
[U][B]ATTENTION OTHER DEVELOPERS: I HAVE NO PROBLEM WITH YOU USING MY WORK, HOWEVER PLEASE DO THE FOLLOWING SHOULD YOU DECIDE TO USE MY WORK.[/B][/U]
[I]-RATE MY THREAD 5 STARS
-THROW ME A FEW THANKS
-THANK ME IN YOUR O/P
-LINK TO MY THREAD IN YOUR O/P[/I]
Never ever ask for an ETA!!!! - Ever!!!!!!! -IT IS VERY, VERY DISRESPECTFUL!
-Always search before posting a question or bug
-Never post a bug if you didnt wipe everything before flashing, and not restoring data. Data corruption is the number one cause of male impotence!
-Do not troll my threads, KennyGlass will whip yo a$$$$!!!
-Do NOT kang my work... Im a nice guy, just ask first, ill probably say yes... Obviously give credit where credit is due!
-If I helped you, or you like my ROMs and Themes, Thank Me, OR consider making a donation... Whats a couple bucks for a dev that worked countless hours bringing you a beast of a phone!
-Bootloops are only good with milk
-Only you can prevent forest fires!
-Enjoy the show....
:D
KANGERS WILL BE PROSECUTED!!!
XDA:DevDB Information
[SYSTEM PARTITION] STOCK NOTE 3 ODEXED & DEODEXED - N900PVPUBMI3 System , a ROM for the Sprint Samsung Galaxy Note 3
Contributors
JoshBeach
ROM OS Version: 4.3.x Jellybean
Based On: STOCK TOUCHWIZ - N900PVPUBMI3
Version Information
Status: Testing
Created 2013-10-02
Last Updated 2013-11-09
RESERVED
THIS IS THE O/P AND IS THE SECOND POST.
ONLY YOU ARE RESPONSIBLE FOR WHAT YOU DO WITH YOUR DEVICE!!! DONT BLAME ME IF IT BLOWS UP IN YOUR FACE!!!
*DISCLAIMER: - EVERY MOD OR ROM OR THEME I DO IS BASED ON DEODEXED! IF YOU FLASH ANY OF MY MODS OR THEMES, AND YOU ARE ON AN ODEXED ROM, I DONT CARE THAT IT BROKE YOUR PHONE! READ THE POSTS... BOOTLOOPS ARE ONLY GOOD WITH MILK
LATEST ROMS, AND MODS ARE - HERE
ADDITIONAL MIRRORS ARE - HERE
PLEASE DO NOT POST ANY MIRRORS OR TORRENTS WITHOUT PERMISSION FROM ME!!!
IF YOU WANT TO DONATE TO THE DEVELOPER OF THIS ROM... HERE IS THE LINK
ALL DONATIONS HERE SUPPORT DEVELOPMENT, AND FUTURE ROM ENHANCEMENTS.
IF YOU WANT TO DONATE TO XDA FILE SERVER... HERE IS THE LINK
ALL DONTATIONS HERE SUPPORT OUR HOSTING ACCOUNT
AS ALWAYS - PLEASE READ CHANGELOG FOR DETAILS...
Code:
YOU CAN BACKUP WITH TITANIUM BACKUP, AND AFTER ROM INSTALL, RESTORE DATA ONLY APPS WITH TITANIUM BACKUP. DO NOT RESTORE ANY SYSTEM/APPS OR SYSTEM DATA. (DATA CORUPTON IS THE NUMBER ONE CAUSE OF MALE IMPOTENCE)
THIS IS NOT INSTALLABLE. -THIS IS A SYSTEM PULL TO KICKSTART DEVELOPMENT FOR THE GALAXY NOTE 3 ON SPRINT.
[IMG]http://i921.photobucket.com/albums/ad51/518Loans/CHANGELOG.png[/IMG]
[CODE]
========================================================================================================
[B][U]VERSION 1.0.0 - SYSTEM PULL[/U][/B]
YAY!
Mine!!!!!
Sent from my SPH-L900 using JellyBombed Tapatalk 2
Nice work, Kevin
Sent from my SPH-D710 using Tapatalk 4
What!!! Team who? Really! Jb homie you kill it. A spot for custom.........
Sent from my SCH-I535 using Tapatalk 2
And it begins... Thanks Josh!!!!
Let's do this
Sent from my Rat infested Note 2
Avatar said:
Let's do this
Sent from my Rat infested Note 2
Click to expand...
Click to collapse
*pumps fist in the air and fireworks explode behind him which causes a wreck on the highway because it blinds drivers...
Kangers will be beheaded ......:what:
Hells yes! Game Time
So you just wonder into Sprint store with a laptop every time a new phone drops?
Rock, Flag and Eagle!
You rock Josh thanks
Sent from my SPH-L710 using JellyBombed Tapatalk 2
StevetotheH said:
So you just wonder into Sprint store with a laptop every time a new phone drops?
Rock, Flag and Eagle!
Click to expand...
Click to collapse
Its funny cus my guy was on another rom. Had bugs. I helped fix his bug. Antways now hes JellyBombed and is eagerly awaiting JellyBomb on his Note3.
If the phone was activated I couldve gptten the msl. And I wouldve been able to get mounting points, boot.img modem.img ect. But it isnt actovated yet so all I could nab was a system pull.
We will put together an odin tar ect once we get a device in hand. (And preferably activated)
Sent from my SPH-L900 using Xparent Skyblue Tapatalk 2
Traded my Note 2 straight up for an [email protected]#$%& 5 for my spoiled baby girl who couldn't appreciate the S4 I got for her. Sold the S4 on Swappa for enough to cover my costs to upgrade to my N3 - 1st in Wisconsin's virtual line... Here we go !!!
JimHuff said:
Traded my Note 2 straight up for an [email protected]#$%& 5 for my spoiled baby girl who couldn't appreciate the S4 I got for her. Sold the S4 on Swappa for enough to cover my costs to upgrade to my N3 - 1st in Wisconsin's virtual line... Here we go !!!
Click to expand...
Click to collapse
I can't believe you just said that in public!
How much was "enough to cover cost" from Swappa? If you don't mind me asking.
Edit: Is that your way of throwing your girl under the bus Jim? Throw her face out there so we know who to blame?
Rock, Flag and Eagle!
@JoshBeach.... you a ninja man... word life.. #impressed
Hell yea dude cant wait for friday getting it with best buy in black with the jet black watch. They better have it friday or im going go crazy haha.
Sent from My Jellybomb Note 2
That's awesome JB! That is pretty cool they let you do that. I can't wait. Dunno if I am gonna be able to get Friday, but hopefully shortly thereafter. Looking forward to it!
I got to get up early in the morning on Friday, the BB near me only have 6 in Stock for sprint. They open at 10... Got to be to work by 10... Lol going to have to be running late on Friday, lol
------
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