hi
how is posible transfer file to tablet because it doesn't recognized in windows 7
due ext4
thanks
Your partition on sdcard can be in fat not ext4
MOderator Message
Please post the Folio3xx v0.4 discussions here
http://forum.xda-developers.com/showthread.php?t=1310196
Dont want multiple threads..
THREAD CLOSED
Related
Hi y'all!
Currently, I'm running CM7 Nightly 177 on my NookColor and I have the custom partition scheme on my NookColor's internal memory. (/data = 2GB & /media 4GB)
I'm recently being troubled by not having enough memory for all of my apps. I have too many, but I don't want to uninstall them so I would like to increase my data partition.
Is there an existing .zip partition scheme that would give me the ff:
OPTION 1:
/data = 3GB
/media = 3GB
or...
OPTION 2:
/data = 4GB
/media = 2GB
Right now, the only ones I was able to find are:
Old NookColor:
/data = 1GB
/media = 5GB
Blue-dot NookColor:
/data = 5GB
/media = 1GB
and
Custom (I'm currently using this one)
/data = 2GB
/media = 4GB.
I've just realized that I don't use the emmc's memory that much so it would be great if I can take some of that unused memory and give it to the /data partition for my apps.
Any ideas?
EDIT:
I AM TERRIBLY SORRY. IT WAS TOO LATE WHEN I REALIZED THAT I POSTED THIS IN THE APPLICATION & THEMES SECTION, NOT IN THE Q&A WHERE I ORIGINALLY INTENDED TO BE. MY BAD. I TRIED TO FIND THE OPTION WHERE I CAN DELETE MY OWN POST BUT ALAS--I COULDN'T FIND IT. I HOPE THE MODERATOR WILL TAKE PITY ON ME.
PLEASE DON'T COMMENT ON THIS THREAD ANYMORE, I'VE MOVED MY QUERY TO THE Q&A SECTION.
SORRY, XDA!
OK, I have a Gtab with the 11/15 FB build.
I am curious about the partitions. Really, why ? I have worked in Unix for a bunch of years and am a fan of few, large partitions. So why am I choosing 2048 ? Or the max if 4096 ?
If it were a Sun box (which is what i cut my teeth on) I would make the main card (disk) a 12 GB root partition and 4 GB swap.
Do the same rules not apply ? It looks like there are a few different partitions (/system, /data, etc) but my eyes cannot read the terminal emulator all that well.
Andy
Different beasts
aknipp said:
OK, I have a Gtab with the 11/15 FB build.
I am curious about the partitions. Really, why ? I have worked in Unix for a bunch of years and am a fan of few, large partitions. So why am I choosing 2048 ? Or the max if 4096 ?
If it were a Sun box (which is what i cut my teeth on) I would make the main card (disk) a 12 GB root partition and 4 GB swap.
Do the same rules not apply ? It looks like there are a few different partitions (/system, /data, etc) but my eyes cannot read the terminal emulator all that well.
Andy
Click to expand...
Click to collapse
This may not be 100% correct (& if it's not I'm sure someone will correct me).
Really no comparison between a Sun box & a tablet. Sun would be bigger & better hardware.
The tablet only has a 512M nand chip (that holds most of the os), 512M of ram (to run the os, apps & no dedicated graphics memory), a processor that is designed for low power vs performace & and a emmc...basically a thumb drive( in place of an hdd). On top of that Andoid is really a hydrid os (a linux kernel with a java vm to run apps).
As far as partitions go, here is the structure for the nand chip on MOST of the gTabs:
Partition 2 = BCT = boot Config Table
Partition 3 = PT = Partition Table (this list)
Partition 4 = EBT = Bootloader
Partition 5 = MBT = ?
Partition 6 = BLO = Viewsonic Bird Logo
Partition 7 = MSC = ? inandop.log /possibly inter kernel comm tween part9/10
Partition 8 = OGO = logodata (gTablet logo I believe)
Partition 9 = SOS = recovery kernel
Partition 10 = LNX = kernel
Partition 11 = APP = system(rom)
Partition 12 = CAC = cache
If you look at gtablet.cfg file in any of the nvflash packages you will see these partition definitions, fs types & sizes used by nvflash to create them.
You also have 2 additional partitions on the the 16GB internal sd (emmc):
/data - user apps & settings - only accessible via root access
/sdcard = user & app storage
Don't know why exactly why /data is set @ 2 G . Apps in Android don't have the bloat of desktop/PC apps and are considerably smaller. I can tell you that with 83 apps installed I still have nearly 1G of space left on mine out of the 2G.
For the most part, Android doesn't truly multitask apps like on a desktop. From what I understand, Android has it's own mechanism for freeing memory when needed (swapping). When space is needed, non running apps are terminated but the app is responsible for storing persistent data so that it can be reactivated (assuming the app saves persistent data) when called.
Hope this helps.
Al
Cool, thanks, I boosted it up to 4 GB, does not sound like that will hurt (had to reinstall because it was full- could not tell why)
aknipp said:
I am curious about the partitions. Really, why ? I have worked in Unix for a bunch of years and am a fan of few, large partitions. So why am I choosing 2048 ? Or the max if 4096 ?
Click to expand...
Click to collapse
As to what the various partitions are, I can elaborate a bit more on Al's post above. Try these 2 posts:
SD card partitions
NAND Flash partitions
The Android OS has its distributions (ROMs) divided into those partitions described above for pragmatic reasons which are not hard to figure out--mainly to enable easy upgrades of running distributions; with security being a secondary concern.
There is no reason why you couldn't merge some partitions together. For example, GtabComb-b3.3 merges /cache into /data at system bootup time. If you were willing to lose the protected read-only status of /system, that too could be merged with /cache+/data on the SD card by modifying the init rc files. You could muck around with the system at an even lower level since you have access to the source code. It's really up to you how far you want to go. The kernel doesn't care about the no. of partitions or the filesystems on them, or even where they are.
As for your question about the 2GB size of /data, that's just how VS deemed it to be when they released the gTab and that's the size that's followed by most custom ROMs. You can have a smaller or larger size if you want. I, for example, run 2 different ROMs--VEGAn-Tab 7.1 and GtabComb-b3.3--the former on the internal SD card and the latter on a micro SD card just by loading a different boot partition using CWM. And since my micro SD is just 2GB in size, I've shrunk my /data to 256 MB.
aabbondanza said:
From what I understand, Android has it's own mechanism for freeing memory when needed (swapping).
Click to expand...
Click to collapse
None of the currently used kernels swap; and neither does Android. That's why they kill apps when there is no memory.
Explains things very well. Thank you both.
Hello all,
I have a couple of questions regarding the rootfs ("/" partition).
1. When I use adb I can write files to /. Where are they (physically) stored?
(I was able to write files of total size as large as ~300M.)
2. The content of / is recreated on every reboot. Which "process" is responsible for that?
Thanks!
Alexei.
Found the answer here.
Devices: Samsung A125F and Samsung A8 Star
Terminal commands that have been run: mount -o rw,remount / (but reports read only)
Why does Android 9+ default Android root system ro and that hard to be remounted rw?
And what patches will be helpful for doing so when terminal fails?
This also makes build.prop and fstab prevented to be written
Hi @hd_scania you can try my SystemRW / SuperRW featuring MakeRW script. Also keep in mind I am working on brand new version which will be released very soon!
To make it work in Android 12 you can simply open the file systemrw.sh with text editor and comment out line number 415 by adding comment symbol ( # ) in front. It should look like this #sdkCheck. Now save file and run script as usual. Please show me your log afterwards. Thanks. Good luck!
Wait a second you are running Android 9 ? Please keep in mind my script was designed for Android 10 and later!
In Android 9 and earlier by default you should be able to remount your partitions as rw without any problems as long as your device is rooted.
I instead flashed the VNDK edition of the Lineage 19.x GSI (i.e. I’m running Android 12, system rw/ro is ultimately GSI dependent), and now system becomes RW
hd_scania said:
Devices: Samsung A125F and Samsung A8 Star
Terminal commands that have been run: mount -o rw,remount / (but reports read only)
Why does Android 9+ default Android root system ro and that hard to be remounted rw?
And what patches will be helpful for doing so when terminal fails?
This also makes build.prop and fstab prevented to be written
Click to expand...
Click to collapse
@hd_scania
Prior to your next posting please read the guidances that are stuck on top of every forum like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
and the others. I've moved the thread to Android Q&A as it didn't qualify for development.
Thanks for your cooperation.
Regards
Oswald Boelcke
Senior Moderator
Hello everyone,
Glad to be here! This is my first time posting on the forum, I apologise in advance if I inadvertently break any rules.
I have installed Android x86 9.0_r2 in a virtual machine using the virt-manager application (QEMU/KVM connection) on Ubuntu 22.04, and I installed it using the ISO and manually selecting the OS as Android x86 9.0. Upon booting, I see a Trusted GRUB 1.1.5 menu and I am able to boot Android x86.
However, my resolution is stuck in 1024x768, and I have to manually edit the GRUB entry and add 'vga=914' after the kernel option to boot with a resolution of 1920x1080.
I read some forum posts stating that the GRUB boot options are located in either a 'menu.lst' file or an 'Android.cfg' file, so I opened the terminal emulator and ran the following commands to find these files in the root directory or sub directories. I also searched for the GRUB directory directly.
su
find / -iname menu.lst -type file -mindepth 100
find / -iname android.cfg -type file -mindepth 100
find / -iname grub -type directory -mindepth 100
However, these commands did not yield any results. So I decided to use grep to try and find the statements present in the boot commands in any of the files present in the system. I decided to search for the statement "root=/dev/ram0", so I ran the following commands to run grep recursively and print the filename where the given text occurs, ignoring errors and binary files:
su
grep --exclude-dir /proc -sIrl "root=/dev/ram0" /
This search took too long, so I narrowed my search to the term "ram0" and checked individual directories instead. However, there were no readable text files containing the boot menu configuration.
Am I making a mistake in any of these commands? Where is the GRUB configuration file located? Please feel free to ask for any additional information to troubleshoot this problem.
Thank you in advance for your help and have a nice day.
kb_android_x86 said:
Hello everyone,
Glad to be here! This is my first time posting on the forum, I apologise in advance if I inadvertently break any rules.
Click to expand...
Click to collapse
Hello and good morning, @kb_android_x86
Welcome to XDA. I hope you'll always get the support you require.
However, prior to your next posting please read the guidances that are stuck on top of every forum like
[Read Before Posting]QUESTIONS DO NOT BELONG IN GENERAL
Hello Everybody, In order to attempt to keep this forum neat and tidy the moderation team is asking you to post your questions into the Questions and Answers (Q&A) forum and not into the General section. You can find the Q&A forum by clicking...
forum.xda-developers.com
and the others. I've moved your thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
Hello everyone,
I have found the solution to this problem.
To access the GRUB configuration files, you must boot Android x86 in Debug mode, and then type the following commands into the terminal:
mount -o remount rw /mnt
cd /mnt/grub
vi menu.lst
Then you can edit the GRUB configuration permanently. I am unsure why these files are hidden when booting Android x86 normally, even when I browse the filesystem with root privileges enables.