• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root CM10 Development (moved to upp)

oh and superr, it does support usb mass storage and all kinds of other modes, usb mass storage is just disabled in the menus, i did a init hack to turn it on instead of mtp when you have debugging enabled but i never implemented it kuz i got distracted before i figure out how to permanently edit the right init file
 
Most of the error files for the device tree are for missing files our device doesn't have. That's why it says no rule to make target. Because the target doesn't exist. So check your device for the file if it doesn't have it then remove the line with the file name from warp2-vendor-blobs.mk in the vendor folder. That's why you get errors when you run extract-files.sh
 
i dont think that would cause any real issues if we just used a prebuilt, its graphical conversion software kinda like a piece of the video output driver, it would be BETTER if we could tweak it but for now we should be able to get something going by using the old one we already have

add this to the proprietary files
lib/libgenlock.so

and you may have to throw in the divx decryptor and a couple other things too, when it errors like that, just throw the file in question at it, we can work out how to build our own versions later if necessary
 
well see, we do have both of those files tho they were just never pulled from the phone
both the divx drm and genlock are in your lib directory take a look, just add them to the proprietary-files.txt
 
wish i coulda thought of that last night when everybody was on a mission but i had a headache like you wouldnt believe, had to start fresh this morning to be able to get anything done
 
and also we are probably gonna need our system firmware files...
they are stored in /etc/firmware and /vendor/firmware
just not sure what parts of what go where
 
Not all of it would be needed like the stuff in the pitt-patt folder. That's all for face unlock which sucks lol
 
these are all the firmware files and vendor specific libraries i know of, not sure how to impliment them or whether they are all even necessary as far as the build but at least now they are all listed nice and neat

Code: 
vendor/lib/libwvdrm_L3.so
vendor/lib/libwvm.so
vendor/lib/libWVStreamControlAPI_L3.so
vendor/lib/drm/libdrmwvmplugin.so
vendor/firmware/libpn544_fw.so
etc/firmware/cyttsp_7630_fluid.hex
etc/firmware/fw_bcmdhd.bin
etc/firmware/fw_bcmdhd_apsta.bin
etc/firmware/fw_bcmdhd_p2p.bin
etc/firmware/leia_pfp_470.fw
etc/firmware/leia_pm4_470.fw
etc/firmware/N970_N861_PR1183396_s2202_32313037.img
etc/firmware/vidc_720p_command_control.fw
etc/firmware/vidc_720p_h263_dec_mc.fw
etc/firmware/vidc_720p_h264_dec_mc.fw
etc/firmware/vidc_720p_h264_enc_mc.fw
etc/firmware/vidc_720p_mp4_dec_mc.fw
etc/firmware/vidc_720p_mp4_enc_mc.fw
etc/firmware/vidc_720p_vc1_dec_mc.fw
etc/firmware/yamato_pfp.fw
etc/firmware/yamato_pm4.fw
etc/BCM4330B1_002.001.032.0518.0520.hcd
edit: found another one, its the BCM thing at the bottom of the list above... sneaky bastard lol

and here is the libgenlock to make things easier, figure if i put everything in one post theres no confusion or missing of anything

Code: 
lib/libgenlock.so
stick that in your proprietary-files and build it, then if you run into another file that says it cant be built like that, just dont have it build it lol, we can figure out how to build our own files later, right now lets just see if we can manage to make it through a build and get it to boot

my theory is, if we keep throwing prebuilts at it, eventually we will make it through the build

also, i found a couple items in framework that might be rather phone specific
Code: 
framework/ZteDrmClient.jar
framework/sprint.jar
thought i wouldnt recommend adding them, that is just for future reference to be studied and tested once we get things going
 
Zup guys, got a question and forget my ignorance on building a rom thingy.

I was looking inside the built that PG posted last night to test and noticed that in all the apk's the drawable-hdpi folder is missing, why? aren't those folders what the phone needs for the graphics to work?

Again, sorry for the dumb question :o
 
no you might very well be right as to whether we need it, the problems we are currently having arent related im sure but that may help us in the future. the drawable-hdpi folder is the settings for screen size and pixel count. not sure if we would be building that or not. and it doesnt seem to be necessary, the phone can adjust using generic settings but it would be better if we could implement device specific variables. we will check into that once we get over this current speedbump, thank you guspeed

and btw, we have no idea what we are doing either, so anything that comes to might feel free to share we wont judge, you might stumble onto something that we havent
 
ok well apon further research into it, it would seem those are just resources like pictures for buttons and things of that nature, so that would be if we were building for multiple phones with different screen sizes, since we are building specifically for this phone all resources will be built to spec by default. so no need to worry about that i dont think

here is a good article on the subject, a little hard to grasp at first, but the general idea is that its the system generic resources resized to fit the screen, we may or may not end up using that but it wouldnt effect the ability to boot
http://developer.android.com/guide/practices/screens_support.html

go poke around in there and start viewing the png files youll get what i mean. theyre just pictures of buttons and icons for various things
 
on a good note though i now understand what the drawable folders are, so in a way you did still help even if it doesnt come into play here. the more i can learn about android the better
 
junkie2100 said:
ok well apon further research into it, it would seem those are just resources like pictures for buttons and things of that nature, so that would be if we were building for multiple phones with different screen sizes, since we are building specifically for this phone all resources will be built to spec by default. so no need to worry about that i dont think

here is a good article on the subject, a little hard to grasp at first, but the general idea is that its the system generic resources resized to fit the screen, we may or may not end up using that but it wouldnt effect the ability to boot
http://developer.android.com/guide/practices/screens_support.html

go poke around in there and start viewing the png files youll get what i mean. theyre just pictures of buttons and icons for various things
Click to expand...


Will do, thanks :)
 
junkie2100 said:
on a good note though i now understand what the drawable folders are, so in a way you did still help even if it doesnt come into play here. the more i can learn about android the better
Click to expand...


Finally!!! someone that understand me better than my wife! LOL :D
 
Going back to your comment about systems with different screen size.
Since you're building this room, wouldn't be better to build it from the beginning with the correct graphic size?
Sorry, I'll keep asking dumb questions!

I'll stop now!
 
right, that is what we are going to be doing, everything is going to be custom tailored to this phone and this phone only. and no youre good, it gives me something to do while i wait for superr lol
 
[HIGH]make: *** No rule to make target `/home/shinru2004/android/system/out/target/product/warp2/obj/SHARED_LIBRARIES/libgenlock_intermediates/export_includes', needed by `/home/shinru2004/android/system/out/target/product/warp2/obj/SHARED_LIBRARIES/libOmxVdec_intermediates/import_includes'. Stop[/HIGH]
 
there is something wrong then if you added my line to the proprietary-files.txt because both of those files should be pre-built
both libgenlock, and libomxvdec should not even be built, they are pulled from the phone
 
ok, got 3 more files added:
lib/libDivxDrm.so
lib/libdivxdrmdecrypt.so
lib/libgenlock.so
building now. Thanks for all the suggestions :)
 
its what i do :D just gotta get some sleep in every now and then, keep myself fresh and let it rattle around in my head a bit. we got this, we are just a little slow lol
 
downthemachine said:
Are you adding this to the device.mk?
Click to expand...

not sure how this is being implimented fully, i know its being put into the proprietary-files.txt which passes things off to the extract-files.sh but im not sure what else its being input into, superr would be the one who could answer that question, i cant see any of the files
 
You must log in or register to reply here.
Back
Top Bottom