Root *what info goes in "init.warplte.rc" and "ueventd.warplte.rc" Or Maybe even a init.warplte.usb.rc

[bcrichster]

Any help would be appreciated... I'm lost, lol.

 

[junkie2100]

depends on what youre trying to do, whats in your init.rc, whats in your init.qcom.rc, what your device variable is set to, etc

uevent you probably wont need to screw with. usb is probably unnecessary unless you wanna put in custom crap, the qcom one will handle that stuff

as far as the init.warplte.rc goes though, if it is used, and that would depend on the init.rc, you would put init.rc commands that arent in the init.rc in there, proprietary things, mount commands, things of that nature. its only purpose is for you not to have to modify the init.rc directly, you leave the init.rc built by cm or whatever, then the import init.${device}.rc or whatever is called, i never remember the correct import syntax for that but youll see it, that line calls the ro.device variable, say its "crap", and combines the init.crap.rc with init.rc, making them one file essentially

as i said, the bare init.rc made by cm or pretty much any android build will not have mount commands, so mount commands are put into a secondary init like the init.qcom.rc or init.warplte.rc, proprietary things go in there like special zte startup commands, things like wifi that need adjustments go in there, but its all up to what you want and what you need, it and the init.rc are individual pieces of the same puzzle, what the init.rc doesnt have and you feel you need you put into the init.whatever.rc

 

[junkie2100]

also keep in mind, init.warplte.rc is probably nothing without a special import line unless you changed up the kernel initialization commands, the warplte has a special kernel command line that sets device to qcom if im not mistaken, so it would be init.qcom.rc thats imported, you could then use that init file to import the init.warplte.rc or whatever you want really but there is a thin line between organization and overkill in that respect. you could have a seperate .rc file for every function if you really wanted but that leaves alot of clutter in the ramdisk, in the same respect one huge .rc file for everything makes for alot of clutter to sort out in the one massive text file

the point of all of this though, which i neglected to mention before but meant to, is to allow the build to define certain variables based on changes you make. you decide to include certain things into the build, it will adjust the init.rc for you to enable said function, so they have the import lines to allow you to adjust the init.rc without actually touching it and therefore negating the builds ability to adjust

 

[junkie2100]

to get more specifics about what you will need, you will need to tear apart the stock ramdisk, and learn more about building a proper ramdisk

i did most of the ramdisk work for the sequent myself, but i still cant tell you exactly what is necessary, its a game of chance, coupled with alot of research. i originally combined both the stock init.rc and the stock init.warp2.rc, searched out and removed the entries that already appeared in the cm built init.rc, then began to weed out unnecessary crap, things that werent there for instance, we dont carry over all binaries, so some services were useless remnants of the stock rom, from there you just gotta tinker, see what breaks stuff, what fixes stuff, what does nothing at all. remove things one at a time, see what they do, remember that wpasupplicant is necessary for wifi but the command may not work in its stock form, so dont delete it just adjust it till you hit something, same with hostapd, that is for wifi tether, research other devices, find common ways of doing those things, as well as the ip stuff, dhcp crap, common things that are in any and every ramdisk for any device

hope this helps you guys