[ROM][WIP]CM10.0.0-RC0-BobZ

Explain? I'm a bit naive.

For Netflix to work on our phones, we would need to have the drivers that Netflix needs updated to work with the newer operating system. Unfortunately, they never released those drivers for ICS or JB, and it's only by a miracle of modern science and coding that we have CM9 or 10 at all.
 
While this may be something of an OT thought from the current thread, the discussion about JB and the increasing size of the OS has bubbled a thought to me. When I was a kid, I worked some on old windows 3.1.1 boxes, and for a while, I owned a set of the old floppies. Later, I had a computer die, and I ended up having to use those disks to install windows in a RAMdrive environment to get the box running and try to get information off the compie in order to make repairs and try and save the hardware. It was a work around, much like the sdEXT stripts allowing us to move apps and such to the SD card and have the OS treat them as if they were on the internal memory.

The thought is, essentially, how much of the OS can we put onto the SD partition safely? And at what point can that data be moved? Can we build a rom that flashes a complete barebones OS with minimal architecture and such (in expectation that the OS itself will continue to put on bulk as time goes by) and then flash the rest of the apps/utilities/etc after first boot, or even before first boot to the SD?

Also, I have heard tell of certain phones being run off a ROM that booted from the SD card, though that may have been through a bootloader. This could also be a solution, though performance may be severely affected, and USB Mass Storage would be completely impossible at that point... but another thought.

Being that we're at a stage where developers for this device are going to have to go off the deep end, I'm OK with being the first one on the board. :)
 
While this may be something of an OT thought from the current thread, the discussion about JB and the increasing size of the OS has bubbled a thought to me. When I was a kid, I worked some on old windows 3.1.1 boxes, and for a while, I owned a set of the old floppies. Later, I had a computer die, and I ended up having to use those disks to install windows in a RAMdrive environment to get the box running and try to get information off the compie in order to make repairs and try and save the hardware. It was a work around, much like the sdEXT stripts allowing us to move apps and such to the SD card and have the OS treat them as if they were on the internal memory.

The thought is, essentially, how much of the OS can we put onto the SD partition safely? And at what point can that data be moved? Can we build a rom that flashes a complete barebones OS with minimal architecture and such (in expectation that the OS itself will continue to put on bulk as time goes by) and then flash the rest of the apps/utilities/etc after first boot, or even before first boot to the SD?

Also, I have heard tell of certain phones being run off a ROM that booted from the SD card, though that may have been through a bootloader. This could also be a solution, though performance may be severely affected, and USB Mass Storage would be completely impossible at that point... but another thought.

Being that we're at a stage where developers for this device are going to have to go off the deep end, I'm OK with being the first one on the board. :)

The problem with using system apps on ext, is that there is a chance the rom won't boot without sdcard inserted. Yes, some devices can run roms off of the sdcard, but that's all of the rom, not just part of it.

Sent from my One V using Android Central Forums
 
The problem with using system apps on ext, is that there is a chance the rom won't boot without sdcard inserted. Yes, some devices can run roms off of the sdcard, but that's all of the rom, not just part of it.

Sent from my One V using Android Central Forums


rom wont boot without the sdcard? thats your reason..? really? If thats the only barrier then make an sd card mandatory for jb, im sure everyone has one and would prefer something working rather than nothing.
 
That's exactly my thought. If the biggest problem is "it won't boot without the SD card in..." well then i won't take my SD card out. PROBLEM EFFIN' SOLVED. GIMME SOME JB, AOKP UNMODIFIED STYLIE... OK, I need to start learning to code so I can just try my wacky ideas out. LOL
 
Tdm is going to start on JB soon and he mentioned that he might have to place the system folders on the sdcard. I'm going to buy a class 10 sdcard for this. My otterbox case covers the sdcard slot anyways.
 
Whenever I'm sitting in driver's end my phone starts roaming, and won't let me send texts. Can you turn this off?
 
I really don't know why someone would try to boot without the SD card in... really, I never take mine out. So, no big deal here.
Koeylondon, I love your pic.
 
rom wont boot without the sdcard? thats your reason..? really? If thats the only barrier then make an sd card mandatory for jb, im sure everyone has one and would prefer something working rather than nothing.

I'm going to ignore the dickishness of your post and say this. If you have a crappy sdcard, it won't be worth it, because the whole rom will be really slow. And while the phone not booting or working with no sdcard may be no big deal to you, it may be to others. And I never said that it shouldn't be done I said that was a problem with it. Calm down.

Sent from my One V using Android Central Forums
 
You guys are all...sort-of correct. Yes, you should have an SD card...hell, your phone comes with one. However, there are other factors to consider, like your SD card being mounted after boot, and the read/write speed of the SD card vs internal storage. Those are both big factors in system apps being moved to SD.
 
I for one am not completely excited about booting off the sdcard.... all my friends are tech saavy and during class I've had them take my phone me and pull the sdcard out and hide it. We all screw with everyone elses gadgets when we get the chance and I can totally see booting off the sdcard coming back to bite. Not to mention not being able to mount SD storage to my PC.

Sent from my LG-VM670 using Tapatalk 2
 
I'm not to big on the idea of system apps on the SD ext. Id prefer if we could find ways to slim the ROM and gapps. I have a 32gig class 4 SD. But it just all seems too sketchey to me honestly
 
As I said before, part of the discussion revolves around future-proofing. Part of the problem as stated is that the base OS is getting big... really big. Big enough that slimming the OS for this phone is failing to be enough to keep it within the realms of possibility for this phone.

Sure, there will be drawbacks. People with slow SD cards, or who have really douchey friends that steal your SD card might have some issues. However, if its the difference between being able to run the latest OS or having to gimp the OS itself to make it fit, that's a decision each ROM cooker is going to have to deal with themselves. Personally, my case (Otterbox) completely occludes the SD slot, and I never really remove the card in the first place.

The part that makes me think is what Cole said, about the SD not mounting until after the phone boots. If that's true, how would it be possible to rom entirely from SD? And can we make the SD mount early?
 
The part that makes me think is what Cole said, about the SD not mounting until after the phone boots. If that's true, how would it be possible to rom entirely from SD? And can we make the SD mount early?

Very briefly, the phone boots like this...

First, the kernel and initial ramdisk are loaded from the boot partition. The initial ramdisk contains the init binary, the various init scripts (/init.rc and such), the offline charging and bootlogo bits, etc. init.rc has entries that tell init to create various directories, mount the core filesystems (/system, /data, /cache), set permissions, start daemons, and such. Note that one thing that is typically run very early after /system is mounted is an init.d type script, which runs through /system/etc/init.d and executes the scripts there. And one of these scripts typically mounts sdext.

So, if one were so inclined, it would not be terribly difficult to change or even remove the mounts for the core filesystems in favor of using the sdcard. All that would be required is changing /init.rc.
 
I'm going to ignore the dickishness of your post and say this. If you have a crappy sdcard, it won't be worth it, because the whole rom will be really slow. And while the phone not booting or working with no sdcard may be no big deal to you, it may be to others. And I never said that it shouldn't be done I said that was a problem with it. Calm down.

Sent from my One V using Android Central Forums

I am glad you ignored any dickishness because i didnt intend to be that way (sarcastic tones dont translate well through the net...so im sorry if it seemed i was attacking you.) , i was just saying if there is no alternative and its a differnce between no jb at all and a working jb then by all means lets move what we need to sd. if theres a workaround that makes everyone happy then im all for it.
 
if you put ROM files on an sd-ext partition instead of the FATpartition, you can mount removable storage just fine. i personally have had no issues running ROMs from the sd-ext... except something in quattrimus init.rc didn't get along with Multirom and it won't boot without modification. but the usb mass storage, at least, shouldn't be an issue. as far as not being able to remove the card, if the core system is in NAND and just system apps and such on sd-ext, then the card should be removable too.