Related
I'm coming from the G1. You could run "cat /proc/mtd" to get the layout of the internal storage device.
It looks to me like the glacier is using /dev/block/mmcblk0 for internal, and mmcblk1 for the sdcard.
'fdisk -l' shows 60 partitions on mmcblk0... Is that even correct? Can someone give me the quick explanation of the how the Glacier is handling its internal storage device?
Thanks
(and I did try search first)
Ohsaka said:
I'm coming from the G1. You could run "cat /proc/mtd" to get the layout of the internal storage device.
It looks to me like the glacier is using /dev/block/mmcblk0 for internal, and mmcblk1 for the sdcard.
'fdisk -l' shows 60 partitions on mmcblk0... Is that even correct? Can someone give me the quick explanation of the how the Glacier is handling its internal storage device?
Thanks
(and I did try search first)
Click to expand...
Click to collapse
You are correct mmcblk0 is internal and mmcblk1 is the sd. I discovered this when creating an ext partition, it seems that a2sd scripts rarely support it by default (a la g2). Also, clockwork doesnt seem to properly support sdext dalvik clearing, which is specifically a complication for regular ROM flashers.
I'm not sure about the exact number of partitions on the RAM/Internal storage blk.
Sent from my MT4G using XDA App
do i see a super wipe being built>?
I sure hope so! Used it regularly on my g1
Sent from my RoyalGlacier using XDA app
Looking into it...
It appears to be a complete rewrite at this point if I want it to actually be writing zeros to the disk at a low level. The statically linked 'erase_image' executable uses the /proc/mtd file to get the partition boundaries and that file is now blank.
I could probably toss together a script that will run "rm -rf" on all the mounts, but I assume anyone with 10 spare minutes can do that...
I will just need to do some more research into how the Glacier is setup. Unfortunately (for you guys) my baby is able to crawl now, so when I'm home I spend alot of free time chasing her around and keeping her out of the cats' drinking fountain.
Ohsaka said:
Looking into it...
It appears to be a complete rewrite at this point if I want it to actually be writing zeros to the disk at a low level. The statically linked 'erase_image' executable uses the /proc/mtd file to get the partition boundaries and that file is now blank.
I could probably toss together a script that will run "rm -rf" on all the mounts, but I assume anyone with 10 spare minutes can do that...
I will just need to do some more research into how the Glacier is setup. Unfortunately (for you guys) my baby is able to crawl now, so when I'm home I spend alot of free time chasing her around and keeping her out of the cats' drinking fountain.
Click to expand...
Click to collapse
Very cute kid. She yours?
Sent from my HTC Glacier using XDA App
Yea, i used it on my G1 pretty much daily with all the flashing that was going on at its prime. Great tool. Good luck man, looking forward to it.
OuncE718 said:
Very cute kid. She yours?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
She better be! I didn't pay all that money to have her genetically engineered in a lab for her to end up being someone else's kid....
Ohsaka said:
She better be! I didn't pay all that money to have her genetically engineered in a lab for her to end up being someone else's kid....
Click to expand...
Click to collapse
lol, sorry, i tamper with all the samples and mix em up and it is now a coctail of samples the we implanted... you lucked out and got the same race!!!
michaelmcelveen913 said:
lol, sorry, i tamper with all the samples and mix em up and it is now a coctail of samples the we implanted... you lucked out and got the same race!!!
Click to expand...
Click to collapse
You mean shes gonna stay that color?!?!??!
Based on my own experience, as well as many requests in various ROM release threads, as well as many other comments in various ROM release threads...
RFS please.
Any speed gain from EXT4 with no journaling is made moot the first time one has to wipe and re-flash, even with backups (maybe especially with backups, which seem to cause some issues as well).
I like speed, I overclock my computer, my video card, and even my phone, but I need stability in my phone. I need the dependability that if my phone crashes it isn't going to force me to do a wipe and re-flash half the time. So... suppress your inner flash-happy geek enough to realize that stability and dependability are important aspects of a phone and at least give the option of an RFS file system.
You are in the minority my friend,90% or more that use EXT4 have no problems at all,,,I don't trust no journaling 100%,but I havnt had 1 problem running it for almost 3 months; And you can enable journaling...
Sent from my SPH-D700 using XDA Premium App
ecooce said:
You are in the minority my friend,90% or more that use EXT4 have no problems at all,,,I don't trust no journaling 100%,but I havnt had 1 problem running it for almost 3 months; And you can enable journaling...
Click to expand...
Click to collapse
Same here... I haven't had a single problem on any of the ROMs I have run here. I have been enjoying speed + reliability.
I understand what JMMusic is saying though...the whole premise of having a custom ROM is that you can modify it how you want. Maybe RFS should be an option for those that want it. I do think that EXT4 with journaling enabled is the best route though.
I personally agree with OP. I'd rather have stability over speed in my phone. I? Ok with just ext4 journalling over rfs, but I would rather have journalling on.
Sent from my SPH-D700 using XDA App
Epic experience is rfs
Sent from my SPH-D700 using XDA Premium App
I cosigned OP, this is the reason I'm not flashing anymore custom roms now. Everybody is on this ext4 banwagon. I'm good, they can miss me with that. I've never had problems out of the ordinary from RFS. I can go on for days about ext4. When I do flash a rom it will be CM7 before anything now.
I hate "Top Flight Security Mods"
Add me to the jouraling ON list. I need stability more than I need the highest quadrant score.. Re-flashing gets old when your supposedly great ROM decides to bork itself every couple days.
caspertodd said:
Same here... I haven't had a single problem on any of the ROMs I have run here. I have been enjoying speed + reliability.
Click to expand...
Click to collapse
Lucky you. I flashed a certain popular ROM. Everything was amazing...for a few days. Then it screwed up. Flashed it again. Everything cool. Couple days later it's crashing again. This process happened over and over. I NEVER had this problem with stock or stock minus bloat or stock minus bloat plus OC kernel. Only when using an EXT4 ROM with journaling turned off.
Coincidence? Not.
Guess one of u guys that want RFS better learn how to cook
ExT4 > RFS
Sent from my Epic 4G using XDA Premium app
..........
dchawk81 said:
Lucky you. I flashed a certain popular ROM. Everything was amazing...for a few days. Then it screwed up. Flashed it again. Everything cool. Couple days later it's crashing again. This process happened over and over. I NEVER had this problem with stock or stock minus bloat or stock minus bloat plus OC kernel. Only when using an EXT4 ROM with journaling turned off.
Coincidence? Not.
Click to expand...
Click to collapse
Why not just stay stock?
caspertodd said:
Why not just stay stock?
Click to expand...
Click to collapse
Well, that's my plan now that I've learned my lesson the hard way.
dchawk81 said:
Well, that's my plan now that I've learned my lesson the hard way.
Click to expand...
Click to collapse
Stock ran very well for me. The only reason I went with a custom rom is just because I could. If I do start having issues such as data corruption, then I probably would go back to stock. So far though I guess I am lucky...I just hope I stay lucky for another 15 months or so when I'm eligible for my next upgrade.
caspertodd said:
Stock ran very well for me. The only reason I went with a custom rom is just because I could. If I do start having issues such as data corruption, then I probably would go back to stock. So far though I guess I am lucky...I just hope I stay lucky for another 15 months or so when I'm eligible for my next upgrade.
Click to expand...
Click to collapse
That's why I gave it a go too. I didn't fare so well. Performance was amazing, but it never lasted. You could almost set your clock to the system failure. I'm not the only one, either.
No RFS for me but EXT4 with journaling enabled would be nice.
Sent from my SPH-D700 using Tapatalk
Anyone saying they want RFS after all the test we have done for stability is like saying Id rather not upgrade to FROYO, Eclair works just fine even though its gimped compared to it.
Sent from my SPH-D700 using XDA Premium App
ecooce said:
Anyone saying they want RFS after all the test we have done for stability is like saying Id rather not upgrade to FROYO, Eclair works just fine even though its gimped compared to it.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
I have to respectfully disagree here - apples and oranges. Huge differences between an OS and FS here. Yes RFS is older and slower but does seem to be less prone to corruption. Luckily I have 2 phones, the epic being for personal use so I don't mind the risk. But if this was my business use phone Id want the functionality of custom roms, and the slow but sturdy filesystem. Just my .02....
Sent from my SPH-D700 using XDA App
ecooce said:
Anyone saying they want RFS after all the test we have done for stability is like saying Id rather not upgrade to FROYO, Eclair works just fine even though its gimped compared to it.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
I don't know if I'd go that far. RFS is compatible with FAT so it can be read in windows. Not having to connect a USB cable to copy files from/to your SDCard is an advantage over EXT4.
Of course, while writing this post, I got curious, searched and found ext2fsd. Which might provide a solution to the ext4 'disadvantage'. Haven't tried it though.
foxBlade107 said:
I don't know if I'd go that far. RFS is compatible with FAT so it can be read in windows. Not having to connect a USB cable to copy files from/to your SDCard is an advantage over EXT4.
Of course, while writing this post, I got curious, searched and found ext2fsd. Which might provide a solution to the ext4 'disadvantage'. Haven't tried it though.
Click to expand...
Click to collapse
I don't understand. How could you transfer files on RFS without a USB cable? I did then, and now, with an FTP server. Was there another way?
I need stability over performance. That is why I've stayed with stock. I would be using SRF 1.0.1 right now if it had journaling enabled. Then again, I haven't had the time to do the research yet on how to enable it after the fact.
Sure it's nice to frequently backup to have a snapshot handy, but that should never be a requirement to maintain stability of a custom rom, IMO.
The lack of journaling still doesn't detract from the good job the ACS crew has done thus far with CIQ removal and whatnot.
Hey guys(mostly devs,would post in dev section but you know,it's not "right").
I was monitoring something that had gone haywire on my phone with OS Monitor and I found something rather odd.
The /cache partition on the Desire HD is roughly 300Mb,while ONLY almost 19Mb were used.Summing it up,it's more than 250mb of space going to waste.So I thought,especially when coming from a Desire(512mb nand anyone? ) and with all Sense 3 roms coming up,/cache could get smaller with some of the "wasted" space going to a slightly larger /system partition and mostly to a larger /data partition,which might be big enough for most,but for those of us that just forget their devices have certain limits,it would be cool.And in many cases A2SD won't be needed.
So?What do you say guys?If many of us gather we could attract developers' attention.Or at least I hope so!
Regards
Apostolis
Not possible to change partitions size so far on Desire HD. And wont be possible probably
mike1986. said:
Not possible to change partitions size so far on Desire HD. And wont be possible probably
Click to expand...
Click to collapse
Oh...And may I ask why is that so?HTC's security?If yes I think I'm a step closer to buying the Galaxy S 2 and not the Sensation...
Anyway,thanks mike!
Sent from my Desire HD using XDA App
mike1986. said:
Not possible to change partitions size so far on Desire HD. And wont be possible probably
Click to expand...
Click to collapse
It should be, it was done on the desire without even touching the bootloader, all it took was a script to modify cwm and the boot.img
Sent from my R800i using Tapatalk
AndroHero said:
It should be, it was done on the desire without even touching the bootloader, all it took was a script to modify cwm and the boot.img
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
Yep,that's what I was thinking,but the level of security on the DHD is far worse(Worse for us that is! ) than it is on the Desire.I wouldn't know,development isn't my speciality,so Mike will know better.If only you could clarify a little Mike...
Or we could contact Firerat.Isn't he the guy that started the whole MTD partition thing?
Wanna push that thing up!
Now on CM12+ i think its more interesting and four years later maybe someone knows a bit more?
Is there something new?
not sure if anyone remembers me here but ive moved on the the motorola photon and gave my wife my hero which she wanted fully stock
unrooted.............. well today she finally cracked and begged me to fix her phone, so i rooted it and put cm7 on it with data2ext 1gb mod needless to say she is super happy and now is curious about the different roms and mods for her phone...... so looks like ill be lurking around here again..... wohoooo knew it had to happen sooner or later by the way anyone due for an upgrade soon i highly recommend the photon incredible phone does everything you tweak others to do straight out the box.... thanks to all the awesome devs here for opening my wife's eyes big smile here guys have a great one
what's data2ext mod? I googled it but didn't find anything on what it dose.
zeroshot said:
what's data2ext mod? I googled it but didn't find anything on what it dose.
Click to expand...
Click to collapse
Its a set of scripts that change the mount points so that your data partition gets mounted to a ext2/3/4 partion on the sdcard instead of internal storage.
zeroshot said:
what's data2ext mod? I googled it but didn't find anything on what it dose.
Click to expand...
Click to collapse
allows you to have way more storage space gave my wife 1gb of app storage
o I did it that way before, didn't seem to be any different then apps on the sd.
Just seems more automatic and cleaner to me flash zip input code into terminal reboot and everything is all good
Sent from my MB855 using xda premium
Some other threads discussing "full partition" problems loading custom ROMs onto the Xoom led me to some digging around. The short story is that Motorola only allocated 236MB to the system partition on the Xoom, and the current JB stock build (JZO54K) occupies nearly 231MB.
{
"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"
}
Given that various features were not included in the JB update when compared to the Nexus 7 and Galaxy Nexus, it's all starting to make more sense why. When Honeycomb rolled out for what is now thought to be a public beta test of the Android tablet form factor, the system partition likely had plenty of space for growth. Dial the calendar ahead several months, and ICS emerges with a footprint that is nearing the Xoom's capacity. And the first item to go - face unlock. It's all good, no one really uses it for actual security but is a cool novelty to show your non-Android/non-ICS friends. Then comes Jellybean. And it's BIG. The Galaxy Nexus system.img file is over 400MB for toro (obviously apples and oranges due to its use as a phone, but you get the idea). So, to make it work for the Xoom, a lot of the frills are stripped away - new wallpapers, sound search as a system app, on-device voice search, Google hot word to start a search in Google Now, etc. It all just doesn't fit inside the partition that Motorola assigned in early 2011. Sad when you realize that there is a giant 32GB flash memory chip built in. And I suspect the Nexus S is faced with the same problems - hardware will work, but the system partition is just too small.
And now we hope for custom ROMs for 4.2 that can fit inside that tiny system partition. Based on the current size of CM10 for wingray, I'd say Team EOS has the best possibility from the size standpoint. That shiny Nexus 10 is looking better and better...
Sent from my Xoom using xda premium
I was under the assumption that re-partitioning was possible?
TheStickMan said:
I was under the assumption that re-partitioning was possible?
Click to expand...
Click to collapse
Possible, but Motorola would first have to write an updated boot loader, and the OTA would have to move existing files to the new blocks. Probably an OTA nightmare. I recall HTC skipping updates to ICS for this reason.
Sent from my Xoom using xda premium
They can skip the unnecessary **** like google now and keep it as clean as possible and 4.2 will fit
romdroid. said:
They can skip the unnecessary **** like google now and keep it as clean as possible and 4.2 will fit
Click to expand...
Click to collapse
I personally use Google now and really find the information helpful. However you are correct-get rid of the Motorola crap like Cordy and Dungeon Defender, and the Google apps that no one uses like Currents. Make Maps, Earth, and other Google products optional instead of being system apps and it will probably fit. I do think both CM and Team EOS will need to strip lot some of their own system apps to make it fit.
Sent from my Xoom using xda premium
I am obviously no Dev. But, is it not possible for any of the Devs here to write a new bootloader and partition for the Xoom? Or at least modify the current one? Seeing as it is unlocked. I only ask because well, the Xoom is such a very nice peace of hardware, as old as it is. The shear fact that it is virtually a pure Google device, has a metal housing, mSD slot, and is all around a cool device. One could hope for such a monumental mod.
Another thing, is it possible to boot off of a mSD card and install the OS on there? Not that that would be such a hot idea due to read and write problems. But an option either way?
Sent from my SCH-I535 using xda app-developers app
Jaytronics said:
I am obviously no Dev. But, is it not possible for any of the Devs here to write a new bootloader and partition for the Xoom? Or at least modify the current one? Seeing as it is unlocked. I only ask because well, the Xoom is such a very nice peace of hardware, as old as it is. The shear fact that it is virtually a pure Google device, has a metal housing, mSD slot, and is all around a cool device. One could hope for such a monumental mod.
Another thing, is it possible to boot off of a mSD card and install the OS on there? Not that that would be such a hot idea due to read and write problems. But an option either way?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
More power to the Dev that could make this happen, but modifying the boot loader can be a quick journey to a bricked Xoom.
Sent from my Xoom using xda premium
Having owned the Advent Vega and used many home brew ROMs it was very common to change the partition layout to make the ROM fit. An issue used to be when using nvflash from a PC as it would not account for any bad nand blocks. But, in the main it worked.
Owning the Skate phone that too has the opportunity to change the system / cache / data partition layout to fit the custom ROMs.
Whether that would be an option supported for the Xoom I do not know.
Sent from my Nexus 7 using xda app-developers app
The nexus s has a system 528mb system partition.
There is no hardware limitation at all for that device.
You could. make a case that its amount of ram makes for a bad user experience though. It has around 345mb available. But they put 4.1 on it so there is a no reason they shouldn't have supported 4.2 IMHO.
Looks a like a case of we don't want to bothered supporting that old device to me.
So let me get this straight, there is literally no way we can repartition our system storage space to anything different? Even with an unlocked bootloader and such?
alex94kumar said:
So let me get this straight, there is literally no way we can repartition our system storage space to anything different? Even with an unlocked bootloader and such?
Click to expand...
Click to collapse
I can't with certainty say there is" no way", but from what I've read on this recently it isn't easy. The boot loader has partition info so it knows where to look for the files to make the device function. Modifying the boot loader could brick the device. I've also become aware of symlinks that enable moving files from the system partition into the data partition to save space-no idea how this works.
Sent from my Xoom using xda premium
let's get a developer in here and find out then!
Nexus One has had a fair few partitions changed in its life span. Up to Gingerbread with stock, ICS and JB had different .... Someone reach out to some nexus one dev perhaps to see if the same sort of thing could be applied here?
Sent from my HTC EVO 3D X515m using xda premium
Nexus One devs rely on the Blackrose bootloader to allow repartitioning. The Blackrose author would be the one to contact if you needed a pointer on where to start to at least figure out IF it's doable or not on the Xoom (the two don't have the same bootloader, obviously).
Somewhere over in the dev section Big Rush Dog said it would lead to certain brick and couldn't be done. They also said youtube HQ wouldn't work on armv6 due to lack of omx libs, but that got hacked (eventually) and we got that. so may be possible but not without hard work and bricked devices
albundy2010 said:
The nexus s has a system 528mb system partition.
There is no hardware limitation at all for that device.
You could. make a case that its amount of ram makes for a bad user experience though. It has around 345mb available. But they put 4.1 on it so there is a no reason they shouldn't have supported 4.2 IMHO.
Looks a like a case of we don't want to bothered supporting that old device to me.
Click to expand...
Click to collapse
I am going to go out on a limb and say that the RAM could end up being a non issue. Reason I say this is because it can be replaced with other RAM chips from another device. Say the Thunderbolt or whatever. The only question I have pertaining that would be. Does RAM for mobile devices follow a specification as far as pin outs is concerned? If they do, and as long as the voltage and frequency threshold are the same if not similar to a degree. Then we could upgrade those. I know that not all people hers would be willing to try such a feat. But I would. And if it worked, I would be willing to help others out in that area.
I believe it is safe to say that I am not the only person that is passionate about how cool devices is. Its age and lack of NFC does not bother me. The thing is solid and has mSD. I can not tout how important that one feature is to me. Its funny, we live in a world where there is supposedly this "Green" movement. Yet no one is pushing these companies to make the hardware they make last longer or make them upgradable. I understand the whole making money model. But we are either ruining this planet or we are not. It is not both ways. You are either "Green" or not. A woman can not be some what pregnant. She either is or is not. These corporations don't give a rats ass about the future generations or their home.
I don't know, it is a bit sickening
. And I as usual, am ranting on like a crazy man. Oh well.
Sent from my SCH-I535 using xda app-developers app
Winesnob said:
I can't with certainty say there is" no way", but from what I've read on this recently it isn't easy. The boot loader has partition info so it knows where to look for the files to make the device function. Modifying the boot loader could brick the device. I've also become aware of symlinks that enable moving files from the system partition into the data partition to save space-no idea how this works.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Mount it in Linux and rebuild the partitions with lvm... it's not too difficult. If you've ever owned a Touchpad, you might have followed one of my guides to get Ubuntu running in a triple boot, doing this is necessary. But unfortunately there is no Novaterm for Android, so the easiest way would be through ADB shell while booted into recovery.
Also, the bootloader has nothing to do with resizing partitions. It just directs your device to the desired partition to boot from. For example, GRUB tells your PC whether to boot into Linux or Windows.
Sent from my Xoom using Tapatalk 2
Jaytronics said:
I am going to go out on a limb and say that the RAM could end up being a non issue. Reason I say this is because it can be replaced with other RAM chips from another device. Say the Thunderbolt or whatever. The only question I have pertaining that would be. Does RAM for mobile devices follow a specification as far as pin outs is concerned? If they do, and as long as the voltage and frequency threshold are the same if not similar to a degree. Then we could upgrade those. I know that not all people hers would be willing to try such a feat. But I would. And if it worked, I would be willing to help others out in that area.
I believe it is safe to say that I am not the only person that is passionate about how cool devices is. Its age and lack of NFC does not bother me. The thing is solid and has mSD. I can not tout how important that one feature is to me. Its funny, we live in a world where there is supposedly this "Green" movement. Yet no one is pushing these companies to make the hardware they make last longer or make them upgradable. I understand the whole making money model. But we are either ruining this planet or we are not. It is not both ways. You are either "Green" or not. A woman can not be some what pregnant. She either is or is not. These corporations don't give a rats ass about the future generations or their home.
I don't know, it is a bit sickening
. And I as usual, am ranting on like a crazy man. Oh well.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I think most folks in the Xoom forums would agree that RAM is not an issue; we're mainly discussing the system partition size in storage memory. If this was in reference to the Nexus S, I only mentioned that device in the OP since it was dropped from AOSP at the same time as the Xoom.
Sent from my Xoom using xda premium
MikeyCriggz said:
Mount it in Linux and rebuild the partitions with lvm... it's not too difficult. If you've ever owned a Touchpad, you might have followed one of my guides to get Ubuntu running in a triple boot, doing this is necessary. But unfortunately there is no Novaterm for Android, so the easiest way would be through ADB shell while booted into recovery.
Also, the bootloader has nothing to do with resizing partitions. It just directs your device to the desired partition to boot from. For example, GRUB tells your PC whether to boot into Linux or Windows.
Sent from my Xoom using Tapatalk 2
Click to expand...
Click to collapse
This is helpful. So to make sure I understand, the boot loader isn't looking for specific blocks, but for the partitioned folders?
Sent from my Xoom using xda premium
Winesnob said:
I think most folks in the Xoom forums would agree that RAM is not an issue; we're mainly discussing the system partition size in storage memory. If this was in reference to the Nexus S, I only mentioned that device in the OP since it was dropped from AOSP at the same time as the Xoom.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Good call on that. Not sure where my head was at when reading your other post. I apologize for that. Though, the whole upgrading the RAM chip thing in my opinion is something I would like to under take. More RAM could help in the performance field. Imagine having 3 maybe 4 gigs onboard this thing? Heck 2Gigs would make a killer difference. Any way, I'll jump off the RAM topic. Another subject for another day and post. Thanks for the head check.
Sent from my SCH-I535 using xda app-developers app