Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
sorry for sounding like a noob, but im really new to androids and this phone. but what is this?
CC arch/arm/mach-msm/clock-7x30.o
arch/arm/mach-msm/clock-7x30.c: In function 'msm_clk_soc_init':
arch/arm/mach-msm/clock-7x30.c:1262: error: ri_list causes a section type conflict
make[1]: *** [arch/arm/mach-msm/clock-7x30.o] Error 1
make: *** [arch/arm/mach-msm] Error 2
well, offf to a good start..
it wont build using the default config...
well, offf to a good start..
it wont build using the default config...
"
> It might be useful to find out which toolchain you guys are using. For
> previous kernels I've used the 4.4.3 toolchain from the most recent
> Android NDK (android-ndk-r7), but to get the arthur kernel to build I
> need to use the 4.4.0 toolchain from an older Android NDK > (android-ndk-r5c)..."
which is the usb networking module... not exactly necessary I dont think, but if i can get the ramdisk from the boot.img in the b08 update, I can probably steal it from there...;-)ERROR: "support_assoc_desc" [drivers/usb/gadget/g_ether.ko] undefined!
ERROR: "get_mute_switch" [drivers/usb/gadget/g_ether.ko] undefined!
ERROR: "switch_set_state" [drivers/usb/gadget/g_ether.ko] undefined!
ERROR: "switch_dev_register" [drivers/usb/gadget/g_ether.ko] undefined!
ERROR: "switch_dev_unregister" [drivers/usb/gadget/g_ether.ko] undefined!
ERROR: "set_mute_switch" [drivers/usb/gadget/g_ether.ko] undefined!
ERROR: modpost: Found 3 section mismatch(es).
...
Well, managed to find the lib/modules folder in the system.img.ext4 file in the b08 update. Also, judging by the way it's setup, i can try doing a custom rom with it, then repacking it into the update.. dunno tho, worth a try... also seems like the g_ether.ko is unnecessary as i thought, here's a screenie if ya want to see what im up to...;-)
can I be the guinea pig? I have a zte warp and I want to be part of something as big as this and willing to take risks! Unless it involves bricking ofc and/or is dangerous (but even then I'll see what I can do)
edit: unless you just wanna go ahead and wait for your zte warp to come
well i wouldnt mind having guinea pigs, but without a zte warp of my own, i wont know for sure if this will brick your units or not, so until i can test myself, and make sure that it works, I wont release it. Too bad the warp isnt like the prevail and could use odin... odin rox.... shouldnt be too long till i get my own zte warp tho, gotta wait a bit for my cash monies to come. as soon as i get it ima test it out.
EDIT:
Im also trying to port cyanogen to it too.. Im no experienced dev, so it's difficult to say the least considering i dont have a device of my own to test out.
First of all thanks for what you are trying to do.
I don't want to put a damper on what you are doing. But, Shouldn't we get the custom recovery working correctly before anything else.
Thanks for your effort on this. A working custom kernel would be awesome but how would we install it with out a proper custom recovery.