I have install Linux Installer 1.7 from market, looks pretty cool!
It is able to run (install?) Ubuntu on our phones. On startup it says that the kernel does not have EXT2 or EXT3 support. That is because i run froyo.
But it also needs LOOP features.
Now almost every ROM here support EXT2 and EXT3, but which supports LOOP features?
By the way, is it not possible to make froyo support real Linux partitions?
Related
Does anyone know how to partition the sdcard.img used by the Android SDK emulator? You can't get a lot of ROMs running without Ext and Swap partitions. I've been fussing around with Yaffs2 on Ubuntu and had some success, but I'm not sure exactly how to accomplish this.
I've installed the lagfix for my Samsung galaxy S and it's so much good thing for speed of phone.
So my question is if exist anything like this for wildfire. Thank you for every reply.
LagFIX creates a tiny (4kb), virtual, EXT2 filesystem within the stock RFS filesystem on the SD card. This then acts to buffer between the real FS, and Android FS, therefore reducing the disk IO requirements. However, I don't think that the Wildfire uses the RFS filesystem, which is the bottleneck on the Galaxy. Perhaps someone clever can tell me if I'm right or wrong
OK, thank you
danne_jo enabled JIT on his wildpuzzle custom rom, it should bring a good "boost" to our WF when we'll be able to use a custom recovery :3
Hi guys,
I'm cooking a WM6.1 ROM with a small set of applications using osKitchen Zero v1.33.5. This gives me lots of free space on the user partition. I have been searching for way to redefine the partition sizes and shrink the user data partition, but haven't found any information regarding this.
Does any one know how to do this or is it even possible?
Thanks
jlsaraiva
Any reason to shrink it?
The idea is to use the remaining space to create the android partitions and boot android with haret from the WM partition. Having both WM and Android on NAND.
Well, that's the thing you can't do via ROM. At least I think so. You need some extra storagemanager drivers.
sounds intriguing though at first - moving the ext2-partitions to nand and telling haret to look for them there instead on sd. you'd still have to boot winmo first, but android would be faster. "semi-nand-flash", kinda.
but thinking about it - not enough internal memory for two os on the x1.
Dont think this is possible just yet. Like your thinking of having two os on internal memory but especially with us poor EURO 512mb devices I dont think it could cope. It would also mean a resdign of haret.exe as it looks for android on SD card.
I striped out pretty much all non essential WM parts from the ROM and I get about 400MB of free space on the user data partition, which is enough to have xdandroid.
You would have to boot into WM first, but I wouldn't mind if it ment running everything out of nand.
No need to change haret. It would be just like we have now, running xdandroid out of the sd card. Only need to change the init script on initrd to mount the nand partitons instead of the sd card and change the init script on the rootfs filesystem. Both are not dificult to do. The only issue here is really "to be or not to be" able to resize the user data partition of WM.
jlsaraiva said:
I striped out pretty much all non essential WM parts from the ROM and I get about 400MB of free space on the user data partition, which is enough to have xdandroid.
You would have to boot into WM first, but I wouldn't mind if it ment running everything out of nand.
No need to change haret. It would be just like we have now, running xdandroid out of the sd card. Only need to change the init script on initrd to mount the nand partitons instead of the sd card and change the init script on the rootfs filesystem. Both are not dificult to do. The only issue here is really "to be or not to be" able to resize the user data partition of WM.
Click to expand...
Click to collapse
This could be a nice idea as you could in theory have android running on nand with out the limitations of either magldr or clk. You would be hard pushed to get a sense build running, but a gingerbread version would be cool! I assume you really have to strip down WM to get it to fit?
I remember looking into this a long time ago before magldr came out and found out some registery keys that could run hart.exe and clard.exe for you with out any user input. I'll see if I can digg them up for you!
I removed almost all EXT packages plus some microsoft apps like office, windows live etc...
But all this falls short if we can't resize the WM partitions.
I've been looking into re-partitioning the NAND on my Xperia X1, so I could increase the storage space when using a smaller rom, but I also have not found a way to do it.
I was originally hoping there was an app, either in Windows mobile, or android, that would work as a partition manager, but I have only found apps that will partition SDcards.
Another option I'm thinking of is using a linux partition manager in android, or using a full blown linux on my phone and using a linux partition manager that way.
I've also thought of using mtty, but I don't know any commands that will let me manipulate the partitioning.
I actually have no idea if any of this will work out, I don't know how the whole boot-procedure works, so I don't know if the bootloader expects the WM-rom partition to be at a certain address, or if it just goes to a certain partition, regardless of the starting and ending positions.
Alright...I have a bit of a project going on here. I have a Lenovo S10-3t convertible touch tablet/netbook that I am creating a multiboot scenario for.
To help cover all the details, here are my disks and my partition setup.
640GB HDD as the primary drive
32GB SDCard as the secondary drive.
Primary HDD has these partitions:
MBR PARTITION SCHEME
Partition 1: Windows 8 Pro 64-bit (492.33GB) NTFS, with Win 8 bootloader
Partition 2: Mac OS X Snow Leopard (79.28GB) HFS+ Journaled, with standalone mini-chameleon bootloader
Partition 3: Linux Mint 15 64-bit (23.28GB) EXT4 Journaled, with GRUB2 on this same partition
Partition 4 (in extended partition): Linux Swap (1.27GB) ...swap space
The SDCard has these partitions:
MBR PARTITION SCHEME
Partition 1: Dedicated to ReadyBoost (5GB) FAT32
Partition 2: Android x86 4.2.2 (24.84GB) EXT3, legacy GRUB SHOULD be in the MBR of this disk
I am using the Windows 8 graphical bootloader to manage everything, as it is a touch-screen tablet, and I like having the touch support for the bootloader. So I would PREFER to use it if possible.
I have currently added entries for OSX Snow Leopard and Linux Mint Olivia to the Windows 8 boot manager, and all three OSes chainload properly to their respective bootloaders and are happy with each other.
So...my question is this...is it possible to chainload the Legacy GRUB bootloader in the EXT3 partition on the SD Card that has Android on it with the Windows 8 Bootloader? And, if so, will you walk me through this process?
WHY am I doing this? There's a couple of reasons...as this is a touch screen tablet I would prefer the convenience of having an option to boot Android from the touch-enabled Windows 8 Boot Manager instead of having to fold the screen away from the keyboard, press FN+F11 and selecting the SD Card as the primary boot device every time I want to go into Android. I could have android on a fifth partition on my HDD, but one of the reasons for having Android on flash memory is BECAUSE I have a mechanical HDD, and I use Android if I'm actively moving the laptop around in a rough environment (say, walking or in a moving vehicle for example, and the HDD would be off since it isn't needed). I know I could use an SSD, but I prefer having a mechanical HDD in my laptop for my own reasons.
I am using a combination of VisualBCDEditor and EasyBCD, and I cannot get either to see or acknowledge the existence of the EXT3 partition on the SDCard (though they all see the EXT4 and HFS+ volumes on the primary HDD, and the FAT32 partition on the SDCard...)
feherneoh said:
I'm almost sure that you are using EasyBCD, so just add NeoGRUB to Win8 Bootmenu, and configure it to set root to sdcard's proper partition and do a chainboot.
Click to expand...
Click to collapse
EDIT: Nevermind, I screwed up on the boot arguments and figured out what the problem was (I used windows' notepad to copy the arguments as opposed to Notepad++, which actually respects linux's formatting). I'm able to successfully boot Android chainloading from the Windows 8 graphical bootloader, to NeoGrub, and allowing NeoGrub to boot directly into the kernel. I appreciate the help. I will leave my previous post for future searchers that need help in doing this as well.
-----
Yeah, I mention at the bottom of my post that I'm using a combination of EasyBCD and Visual BCD Editor. I followed your suggestion and added NeoGrub to the list, and opened the menu.lst config file for it.
I copied the majority of the contents of the menu.lst from the "grub" folder in Android x86's partition and pasted it into NeoGrub's menu.lst (editing the harddrive and partition to reflect what it should be, of course).
It sees the kernel and ramdisk images, begins to load them, and then goes into an infinite loop of spawning dots across my screen (I can tell from experience that this means it isn't loading properly and the kernel halted). It seems NeoGrub doesn't support the "special" arguments that need to be passed to the kernel (that passes properly with the legacy GRUB loader), so I guess I need to figure out how to chainload GRUB from NeoGrub now. Back to square one, essentially.
Here is the menu.lst for the existing legacy GRUB on Android's partition:
Code:
default=0
timeout=6
splashimage=/grub/android-x86.xpm.gz
root (hd0,1)
title Android-x86 4.2-test
kernel /android-4.2-test/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86 video=-16 SRC=/android-4.2-test
initrd /android-4.2-test/initrd.img
title Android-x86 4.2-test (Debug mode)
kernel /android-4.2-test/kernel root=/dev/ram0 androidboot.hardware=android_x86 video=-16 DEBUG=1 SRC=/android-4.2-test
initrd /android-4.2-test/initrd.img
I notice in the JellyBean entry you have
Code:
acpi_sleep=s3_bios,s3_mode
I'm curious on what this and the "VGA=778" does. My "VGA" is set to -16 for whatever purpose it fulfills.
I'm assuming the acpi_sleep option allows the kernel to use the S3 sleep state for the hardware, like the same state other OSes use when you shut the lid? Currently all my Android install does is shut the screen off if I close the lid...and I'm fairly certain that's hardware-based anyway.
Has anyone installed Phoenix OS v3.0.2.451 on an ext4 partition?
I installed it on a dual boot laptop yesterday, on a ext4 partition. I hadn't had time to check it out yet, only know that the default file manager don't see Linux partitions, but see only NTFS partitions. That's not a problem, as I keep most of my data on NTFS partitions, for both Linux and Windows to see (read/write) them.
This is an UEFI system.
It seems pretty snappy.
(I had both Remix OS and Phoenix OS quite sometime ago, but had removed them .)
Now on a MBR laptop, also on a ext4 partition...
Installed same version of POS on an ext4 partition of a MBR laptop. It has Debian Sid, few other Linuxes and older Windows 7 Home Basic in it. Works alright atm. Can't uninstall some Chinese only apps from Phoenix from both laptops. Its Stardust browser didn't want to work well in this, so installed Chrome from Play Store. But in the UEFI laptop, the Stardust browser worked quite well.
Installation was done manually in both laptops, the way it was done in the early days.
I find Phoenix OS 3.0.2...works better on a UEFI laptop. No idea why. In an MBR laptop, I can't highlight text in the web browser and copy, the mouse right click doesn't work. The right click doesn't work in the UEFI too, but text can be highlighted, especially in Opera, not in Stardust, nor in Chrome. Btw, Play Store is available.
Maybe I should write how I installed it in another thread?