I'm trying big brother lol. I did some clean up on it. I'll post the new one soon. If you can work your magic for me and find out what info goes in "init.warplte.rc" and "ueventd.warplte.rc" it would be appreciated.
Maybe even a init.warplte.usb.rc
I mean my process is simple.
Choose two devs that work on similar phones.
Go to github
Study how they compiled it.
Then cherry pick the commits
Yesterday it was Shinru & PG
It works cuz my pc is so slow I get to see the errata as it scrolls down
I have been going in and fixing code in the source folders as well.
Remember,
no more "repo sync" if you change anything in the source folder.
Unless you add a folder.
Folders aren't affected by what I see
Always grab a repo of Cyan. I didnt do it, but I see where I need to now.
Sometimes during sync .cpp .h .o etc will come through broken. And need to be pulled from another source that was used as base.
Believe one thing. This is just the beginning. We will see ChA0$ L3G|0N $R0M$.
I need to make an account @ qcom I think we need drivers.
I pulled the hardware/qcom/display-media-legacy folders .
They were transferred from OG to 2 not to 3
I think the ueventd.rc works on permissions. And the init sets parameters for boot initiation. But did they pull this from init.rc , init.qcom.rc , init.goldfish.rc, init.cos.rc, init.target.rc ???
https://www.dropbox.com/s/0nda8epbnxz530p/warplte.tar.gzThis thing is torn up but its clean. Most of it. Device.mk needs subtractions.
Prop list needs to be finished.(google each lib and move it to its section)
My cos.mk needs to be switched back to common_full.mk . Etc drivers etc lol
Removed dexopt./ Config.mk
thats how you make odex .
I learn something new everyday
Errata on mesa3d, setting config.mk to 3d := false
Re-added build-info.text.
Removed the root of device/prebuilt/lib
make -C kernel O=/home/h311sdr0id/android/system/out/target/product/warplte/obj/KERNEL_OBJ INSTALL_MOD_PATH=../../system ARCH=arm CROSS_COMPILE=" /home/h311sdr0id/android/system/prebuilt/linux-x86/toolchain/arm-eabi-linaro-4.6.2/bin/arm-eabi-" modules_install
make[1]: Entering directory `/home/h311sdr0id/android/system/kernel'
INSTALL arch/arm/mach-msm/dma_test.ko
INSTALL arch/arm/mach-msm/msm-buspm-dev.ko
INSTALL arch/arm/mach-msm/reset_modem.ko
INSTALL block/test-iosched.ko
INSTALL crypto/ansi_cprng.ko
INSTALL drivers/crypto/msm/qce40.ko
INSTALL drivers/crypto/msm/qcedev.ko
INSTALL drivers/crypto/msm/qcrypto.ko
INSTALL drivers/gud/mcdrvmodule.ko
INSTALL drivers/gud/mckernelapi.ko
INSTALL drivers/input/evbug.ko
INSTALL drivers/media/radio/radio-iris-transport.ko
INSTALL drivers/media/video/gspca/gspca_main.ko
INSTALL drivers/mmc/card/mmc_test.ko
INSTALL drivers/scsi/scsi_wait_scan.ko
INSTALL drivers/spi/spidev.ko
INSTALL drivers/video/backlight/lcd.ko
DEPMOD 3.4.0
i like lol
But I did it by adding them in device.mk it found the ones in the kernel folder wtf?
Went back to a d tree backup. I broke the ota package and couldnt fix it.
I could have changed code in the source but I was getting "VALUE ERROR" so I said forget it.
Did a sync. And back at it.
My slow system is a curse and a blessing
I can see errata, but I can't make changes and get back a output fast enough
@ninja . You was asking me about the device tree.
Granted I dont follow it cuz I like to learn the hard way
But go to main.mk and Makefile in build/core of source.
Good reading lol
My way goes through hundreds of variables and hack it until it either breaks or boot. I have seen too much breaking though
A little hint to aspiring developers
When you speak to the source developers for permission.
You should relay what it is you like about the rom
Be humble
Thank people that help you.
No credit= $tealin
Credit=)
LoL
Thank you goes out to
ChameleonOS
The inspiration for this forum
Got to get back to this building
My pc sucks I need Alienware